Closed GoogleCodeExporter closed 8 years ago
We've thought about it, but we first have to determine the amount of work
needed for this.
Wiiflow depends on the harddrive or SD being available. If the harddrive is not
available, you might have no storage. No storage means no wiiflow. That's how
it's currently build.
Original comment by r-...@live.com
on 7 Oct 2010 at 7:32
Well it needs to be implemented. Wiiflow cannot be set as a "boot" app until
it is. (If a hdd isn't inserted a person couldn't start their wii!!)
The solution would be to simply check the wiiflow.ini to see where the storage
folders are pointing. If they are pointed to USB folders you just need to
disable the saving of settings or save settings to a temporary file where
wiiflow is located and add them in the next time the HDD is attached.
Original comment by hca...@gmail.com
on 10 Dec 2010 at 11:51
No, it's not that easy. And besides that, the vast majority of our users have a
hdd specially for their wii. So for them it's not an issue of having the hdd
inserted or not. If wiiflow is located on the sd card, it's easy indeed. But
it's the other situations that makes this harder.
Anyway, I don't see this issue as a must.
Original comment by r-...@live.com
on 11 Dec 2010 at 12:01
I agree with your comment about the most users having a HD. I feel like if it
is indeed installed on the SD card, it could be an option. Otherwise no check
needs to happen.
Otherwise, the current default is perfectly acceptable when there's HD
attached, where it eventually just exits back to the system menu or homebrew
channel when it boots without a USB drive attached.
Original comment by Anth...@gmail.com
on 29 Dec 2010 at 6:15
Fixed in dev svn r404, will be back ported to wiiflow eventually if dev doesnt
get synced directly.
Original comment by Miigotu
on 5 Aug 2011 at 9:05
Original issue reported on code.google.com by
jceggbert5@gmail.com
on 7 Oct 2010 at 7:23