MathewWi / wiiflow

Automatically exported from code.google.com/p/wiiflow
0 stars 0 forks source link

Drive not always showing games #307

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Power on wii, autoboot into WiiFlow from Priiloader.
2.
3.

What is the expected output? What do you see instead?
Expect Wiiflow to load and show games.  Waiting for hard drive image shows for 
a couple of seconds, then Wiiflow loads to "I can't find any games" with 
options to install game, or choose partition.

What version of the product are you using? On what operating system?

WiiFlow r92 (tried both 249 and 222), System Menu 4.2E, cIOS 249 rev20b, Hermes 
v4 222(38)223(38+37)
Priiloader v0.5

Please provide any additional information below.
If I load wiiflow from System Menu through channel forwarder, or from HBC, it 
boots as expected.

When autobooting from priiloader, the return to upon exiting games, most of the 
time works and takes me back to wiiflow.  Although sometimes it doesn't.  When 
the wii has been switched off for more than around 30 seconds, autobooting to 
wiiflow just tells me that no games are found.  If I select choose partition, 
it show NTFS1 (my partition is NTFS1), it also lets me select WBFS1.  However, 
if I choose WBFS1, the option of NTFS1 disappears, as though it can't see my 
drive.  It then takes me back to the choose partition screen.  

I don't actually receive any errors, only that it doesn't list my games.  To 
complicate things, some of the time it works.  I have tried the NForwarder from 
this site, I have also tried my own forwarders, and the wiiflow executable 
itself, yet all have the same result.  I have considered that it may be my hard 
drive, yet I have tried a few hard drives with the same results, and other 
loaders find the drive straight away.  To that end, it must be something not 
quite write in wiiflow.  I have attempted various mods to the code affecting 
both ios reloads and device init and mounting, in an attempt to spin up the 
hard drive if this is the cause, but I get exactly the same results.

Other loaders seem to work, and other hard drives seem to still have the 
problem.  But reading around on the internet, I see that a large number of 
people have this working properly.

I would like to see either this issue fixed, or some suggestion as to what else 
I can try to get this working.  If someone can point me in the right direction, 
I am happy to mod the code myself, but I've tried all the things I can think of 
apart from updating the wbfs and ntfs libraries, which I don't want to do 
unless its necessary, as it'll probably cause as many problems as it will solve.

Any help much appreciated

Original issue reported on code.google.com by stevebry...@googlemail.com on 5 Sep 2010 at 12:59

GoogleCodeExporter commented 9 years ago
Please use the update feature to update to r166.  report back if it isnt fixed 
but for now this s closed.

Original comment by Miigotu on 5 Sep 2010 at 1:11

GoogleCodeExporter commented 9 years ago
Working. Thanks!  :)

Original comment by stevebry...@googlemail.com on 5 Sep 2010 at 2:21