yes i guess i did say that. what i meant was having emunand on USB scares me. i have had issues with files getting corrupted in the past (3 or 4 years ago) being related to me messing around with emunands and wiiflow. and a user recently reported that when he used wiiflow to dump his nand it wiped his usb drive (although unproven).I'm sorry, I don't understand this part. Did you not said before that it's best to have emunand on SD?
And with WFL on SD and Nintendont games on HDD, how can it not write GC saves to HDD if it's coded that way?
I haven't had any issues with my emunand on usb since. so hopefully everything is fine now. and like i said it should be the cIOS that's controlling the reading/writing to emunand. wiiflow only writes to emunand for dumping the nand, dumping saves, copying sysconfig and miis to emunand, and installing wads.
gc saves are written to USB HDD if your gc games are on USB HDD. so ya i shouldn't say the usb HDD is read only. just that with apps/wiiflow and the wiiflow settings folder on SD then wiiflow hardly ever writes to USB HDD.
wiixplorer is good. but i have screwed up wiiflow_lite.ini once while using wiixplorer. no proof though that it was to blame. so i always try to stick with ini editing on my pc.
glad your freezing issues is gone. I wonder why it only did it with wfl on USB?