Open GoogleCodeExporter opened 8 years ago
The device containing /ploader folder cannot be removed. Probably the main
reason for the hang are the covers, as almost of the other thing are already in
memory.
The only thing I can do is to check if the card is removed and ask the user to
insert it again.
Original comment by stf...@ilpistone.com
on 12 Jul 2012 at 9:10
Well, i replicated this issue again but now removiing all covers from covers
and covers.emu, then removing the sd, It still froze.
After, i reinput the SD card into the wii, the hand did move a few cm, but then
it refroze again fast, same is if i did not remove the covers.
Original comment by NoNextDo...@gmail.com
on 12 Jul 2012 at 10:26
Btw, if i remove the SD inside usbloader-gx, i can still move around or change
view without problems, including having the covers loaded last time+games,
except if i try view homebrew or any events where it needs the sd.
Even when i take out the USB device, it still does not mallfunction), though it
does not reload its data of games availble :/.
Original comment by NoNextDo...@gmail.com
on 12 Jul 2012 at 10:34
Postloader still freezes in beta 4.b33 if you try to take the sd out at
sections that involve the SD to be input, such as emulators and
homebrew(strangely also channels :?).
If you try this at sections that involve USB access, it will not freeze, though
it will freeze if you try to go over to any different sections from the upper
toolbar.
Original comment by NoNextDo...@gmail.com
on 13 Jul 2012 at 3:35
I suggest, that in the event someoene takes out the SD, a warning should be
given to put back the SD device, cancelling out most to all actions+darkening
the background perhaps.
When someone puts back the SD device, all actions are allowed again, same
applies to the USB, may it store its configs instead.
There is one problem still, if i try to put the SD back, postloader won't
return to what it should do, as if it does not reread the device and forgot it,
though it does not freeze as if it couldn't load the files :L.
Original comment by NoNextDo...@gmail.com
on 13 Jul 2012 at 3:44
Original issue reported on code.google.com by
NoNextDo...@gmail.com
on 11 Jul 2012 at 7:41