Returning to systemmenu while holding reset

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable "Stop disc on startup" in the options 
2. Have a disc inserted in your wii (not sure if this is a requirement, I think 
so)
3. Hold reset while turning on the wii

What is the expected output? What do you see instead?
Expected output: priiloader loads and stays. 
I see instead: priiloader loads and boots to system menu after a few seconds
(note: autoboot and return to are both a forwarder to my USB loader.)
I managed to keep in priiloader by spamming down button on the wiimote while 
turning on my wii (doing the same on a GC controller doesn't work)

What version of priiloader are you using? On what ios/system menu?
Priiloader 0.6 running under sysmenu ios (4.1 so ios 60)

Do you have any IOS patches installed? (if so which ios and what patch?)
Trucha signed ios36 and patched ios60 

Original issue reported on code.google.com by chirimo...@gmail.com on 23 Jan 2011 at 2:04

[GoogleCodeExporter]

thats because of the failsafe.
after 15s in priiloader when you press reset and no wiimote is synced 
priiloader boots SM.
this is a failsafe incase there is no wiimote synced to the wii

im guessing you are still able to do anything before SM boots?

Original comment by dac...@gmail.com on 23 Jan 2011 at 3:19

[GoogleCodeExporter]

Well, it certainly isn't 15 seconds (more like 2 after priiloader shows up)
I can still do stuff using my gamecube controller but the 2 seconds isn't 
enough to choose the title I want to launch. 

It doesn't happen without the stop disc on startup enabled. So even if it's a 
feature, it's bugged the other way around :P
(I just checked, it has been on for more then a minute without going to sysmenu)

I'd like to just use my gamecube controller to navigate priiloader. 
So if it's a feature causing this, I request an option to turn that off or at 
least not let it happen when a gamecube controller is attached. 

Original comment by chirimo...@gmail.com on 23 Jan 2011 at 3:59

[GoogleCodeExporter]

ill check it out.
but wait, you hold reset to boot priiloader, priiloader boots up, you release 
reset and still it boots system menu?!

Original comment by dac...@gmail.com on 23 Jan 2011 at 7:55

[GoogleCodeExporter]

yep, I hold reset for a few seconds until priiloader pops up and then release 
it. 
It goes to the system menu after releasing reset. 

If you want, I can make a video of it (although it will be not too high quality 
since I'd have to make it using my phone camera)

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 1:55

[GoogleCodeExporter]

please do :/

Original comment by dac...@gmail.com on 24 Jan 2011 at 7:14

[GoogleCodeExporter]

http://www.youtube.com/watch?v=IXDO9Z75w2M
Here you go. 
Sorry for the bad quality but it's about the best I could do with my phone 
camera

If it's of any help: 
I use a european (PAL) wii, if that might be weirdly related to this error. 

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 8:07

[GoogleCodeExporter]

thats...odd
enable debug/gecko output (its in the settings) and see if it says anything ...

i wonder why the STM callback is so late...

Original comment by dac...@gmail.com on 24 Jan 2011 at 8:14

[GoogleCodeExporter]

well, it helped a bit...
At first I released the reset button at the moment it says "reset button is 
held down" it boots normally into priiloader without error (and stays there)

Then I held it a bit longer (after checking the reset button, it initializes 
SD, FAT and some other stuff) and released it on the black screen just before 
the menu pops up. 
Then a message popped up "ontime = 12959103xx.00s" (the xx is a random number 
that changes each time I tried)
followed by a bunch of stuff which seems to be loading my system menu hacks. 

When the "stop disc on startup" is disabled, this black screen is practically 
gone so  I can't release the reset at that moment. This is why it didn't happen 
then. 

The ontime = (number) also appears when I press reset after booting priiloader 
successfully. I'm guessing it's for the failsafe which also kind of explains 
why it kept resetting to the system menu. (but I bet you already knew this xD)

I hope this helps. 
I don't know what you mean by the STM callback and I saw no message mentioning 
it so sorry if that's important. 

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 8:48

[GoogleCodeExporter]

holy shit thats a big ontime o_O; (probably because its not init and its 
therefor a random number)

also, the STM callback is a function that is ran when the power or reset button 
is pressed.
the reset shows that ontime = number debug output ;)

thanks to that info i can figure out a few things.

now to testing; try and load this dol from HBC; does it still show the bug? (it 
could say that System menu booting failed etc etc; that doesn't matter as that 
shows it tried to boot system menu :') ) 

Original comment by dac...@gmail.com on 24 Jan 2011 at 9:12

Attachments:

• priiloader.dol

[GoogleCodeExporter]

No, just like when the option is disabled, the blackscreen doesn't show up at 
all anymore. Directly from the loading stuff to priiloader itself. 

Since the black screen isn't there, I can't release reset at the black screen :P
(though the disc isn't spinning to start with like it would on the real 
priiloader, not sure if that matters)

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 9:22

[GoogleCodeExporter]

give me a minute
ill build a dol to boot from HBC that will start the DVD drive on startup and 
shut it down no matter what the setting says

Original comment by dac...@gmail.com on 24 Jan 2011 at 9:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hmm, that new .dol does spin up the disc on startup, but I can't seem to get it 
to stop on startup (keep spinning no matter what the setting says :P)

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 9:45

[GoogleCodeExporter]

ye thats why i deleted the dol & comment haha :P

Original comment by dac...@gmail.com on 24 Jan 2011 at 9:46

[GoogleCodeExporter]

ah ok, then I was too fast downloading it :P

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 9:48

[GoogleCodeExporter]

well, you'll have to wait untill the installer is safe again

unless you have bootmii @ boot2 in which i'll gladly share an installer of a 
dol to test :)

Original comment by dac...@gmail.com on 24 Jan 2011 at 10:00

[GoogleCodeExporter]

That's not a problem, glad I could help in pinpointing the source.

At least I know the exact cause now so I can evade it (even though leaving the 
setting disabled shouldn't hurt either I guess, not spending hours in 
priiloader... :P)

Original comment by chirimo...@gmail.com on 24 Jan 2011 at 10:06

[GoogleCodeExporter]

if you want to try; please see if this issue is still active on 0.7 BETA 1
do note that its still beta and if you dont want to install it for its 
potential risk then im fine with it :)

Original comment by dac...@gmail.com on 16 Feb 2011 at 5:44

[GoogleCodeExporter]

ping?

Original comment by dac...@gmail.com on 7 Mar 2011 at 7:32

[GoogleCodeExporter]

Sorry, I haven't really had the chance to test it yet (because of my wii being 
all over the place but not in my room :P)

I will probably try it later today or tomorrow. 

Original comment by chirimo...@gmail.com on 7 Mar 2011 at 11:03

[GoogleCodeExporter]

I have downloaded 0.7b and it seems the problem is gone :)

Original comment by chirimo...@gmail.com on 7 Mar 2011 at 6:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

great! thank you for your test!

Original comment by dac...@gmail.com on 7 Mar 2011 at 7:42

• Changed state: Fixed