Hacking DIOS MIOS (Lite)

  • Thread starter Thread starter sk0ld
  • Start date Start date
  • Views Views 1,056,148
  • Replies Replies 4,949
  • Likes Likes 38
anyone try super mario sunshine on 2.4? just black screens for me. FIXED was the force progressive patch that caused it to black screen
 
Mhhh. Still get black pictures with Prince of Persia Warrior Within - Pal, Two Thrones Pal and Animal Crossing Pal.
I tried now, to burn the image and to check with neogamma. Works perfectly.
So it seems, it's not related to the image itself.
 
Mhhh. Still get black pictures with Prince of Persia Warrior Within - Pal, Two Thrones Pal and Animal Crossing Pal.
I tried now, to burn the image and to check with neogamma. Works perfectly.
So it seems, it's not related to the image itself.
do you have the force progressive mode on? that caused black screens for me
 
are there any HDD's that Don't sleep now that DID with 2.3?
I can't speak for everyone but for me it wasn't fixed sadly, I hate to be ungrateful though and I really appreciate the help!

Edit: This question may seem stupid so forgive me for asking, but I'm asking the technical members here, how come the hard drive doesn't go to sleep mode while running Wii games though? How does it work? Can this be done to DM?

I will report that my hard drive also seems to gos to sleep mode in Wii Explorer, but that's not a big issue for me!
 
Edit: This question may seem stupid so forgive me for asking, but I'm asking the technical members here, how come the hard drive doesn't go to sleep mode while running Wii games though? How does it work? Can this be done to DM?

I will report that my hard drive also seems to gos to sleep mode in Wii Explorer, but that's not a big issue for me!
I think for Wii games, the cIOS that they run off of does just the same thing, randomly reading from the hard drive to keep it alive.

WiiFlow, for example, while it's running off of IOS58 instead of a cIOS has to include code ITSELF for it to randomly read from the HDD since IOS58, being a normal IOS, doesn't do that on it's own.

Maybe crediar just didn't quite do it right, who knows (it WOULD be rather interesting to know from someone who knows how the cIOS's do it and how it compares. I haven't actually looked at the code myself.)


As far as Windows Explorer, it has code to wait until the HDD has finished waking up and start reading from it.
GameCube games don't KNOW they're running off of a hard drive. They just assume they can always read from the DVD drive whenever they want and crash when they don't get what they want.
 
As far as Windows Explorer, it has code to wait until the HDD has finished waking up and start reading from it.

I did not know that, if this works out then my only problem will be Dios Mios, thanks :)

Edit: I didn't find this code for Wii Explorer and while testing I wanted to delete a file and the hard drive no longer worked on my Wii with any software until I unplugged it and plugged it again!
 
I did not know that, if this works out then my only problem will be Dios Mios, thanks :)
Edit: I didn't find this code for Wii Explorer and while testing I wanted to delete a file and the hard drive no longer worked on my Wii with any software until I unplugged it and plugged it again!
Okay, I feel silly now. I read wrong and thought you were talking about Windows Explorer instead of Wii Explorer.
I think it's something they SHOULD add to WiiXplorer but, anyway, sorry for the confusion there.
 
It's at least just nice to know he hasn't abandoned audio streaming all together

anyway,

Just looking over the code for the random sector thingy (dip.c line 338 if I'm understanding where it is right) semi-blindly TRYING to figure out what's actually going wrong with it.

I'm not TOO clear on the math that's used there but I do seem to see there
that once a timer gets over a certain point
it chooses which sector to read based on the same timer and then resets the timer.

Maybe someone who better understands the code could look at this and get an idea of how much it really varies
because my gut feeling is that if it's based on a timer shortly after it reaches a fixed point, the "random" number's not going to get too far away from that fixed point. If it's not varying enough to get outside the drive's buffer size it might still be going to sleep.
 
On the other hand, if it DOES vary a lot, as it should, what I do understand about the math being used there is that it's limited to the first 8gb of the drive.
If using a drive that's smaller than 8gb it's very possible that it's trying to read outside of the limits of the drive which would explain the problem superrsonic was having with his 4gb drive.

(EDIT : The only thing I'm really having trouble with the math is what exactly 243000000LL means)
 
the ll is not important for the math, it's just a signal to the compiler that the number does not fit into the normal bitsize and that a larger one should be used
the only reliable way to get the amount of jitter occouring is measuring it e.g. via log output
 
  • Like
Reactions: Maxternal
(Curiosity killed the cat so maybe I should just leave this alone but ... )
That number looks to be half the clock speed of the processor (number of cycles in half a second)
Just a stab that the 243000000LL / 128 is just a convenient way to calculate a second then the 2 * 60 could mean every 2 minutes it's being read.

Anyone with a problematic drive know exactly how long their drive takes to go to sleep?
 
On a more normal subject matter:

I've noticed that the "new video method forcing method" that was added in later updates of 2.0 doesn't work in 2.2 or 2.3 (haven't had time time test 2.1 or 2.4 yet.)

The only reason I noticed this is I had gotten a new TV. My old CRT didn't benefit at all from the newer versions' features so I just hadn't updated previously.
I upgraded for the widescreen hack for my new TV but then realized my problematic PAL games that had been fixed in 2.0 were back to PAL only.
Fortunately, I later got component cables for my new TV, too, and forcing progressive DOES work quite well but just thought I'd throw that bug report out there.
 

Site & Scene News

Popular threads in this forum