- Joined
- Oct 27, 2002
- Messages
- 23,744
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,678
- Country
oh, too bad. I hoped it was that issue (because it was simple to fix ), the symptoms were matching.
sorry I don't have any idea for the moment why it's random.
I might think about it again and come to you if I have an idea.
But the fact it loadsneek2o NK2O directly is strange.
Try to disable the "return to" option, set it to off to disable it and stays on neek2o even after a failed autoboot attempt, that way you can launch the game manually from the system menu (or channel hidden menu if you are on vWii as it has a bug and doesn't list channels)
It's not a fix, but at least it prevent a reboot cycle. see if neek can boot game from the first cycle or not. (no reason why not, but you never know before testing)
I guess a debugger would be useful in this situation, looking at the path generated by the loader, the generated neek2o config file, sent argument, etc.
sorry I don't have any idea for the moment why it's random.
I might think about it again and come to you if I have an idea.
But the fact it loads
Try to disable the "return to" option, set it to off to disable it and stays on neek2o even after a failed autoboot attempt, that way you can launch the game manually from the system menu (or channel hidden menu if you are on vWii as it has a bug and doesn't list channels)
It's not a fix, but at least it prevent a reboot cycle. see if neek can boot game from the first cycle or not. (no reason why not, but you never know before testing)
I guess a debugger would be useful in this situation, looking at the path generated by the loader, the generated neek2o config file, sent argument, etc.
Last edited by Cyan,