Running Snes9xGX 4.2.5 on Wii with FAT32 USB HDD corrupts entire HDD

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Start Snes9xGX 4.2.5
2.  Change settings to USB and folder path to snes9xgx/roms
3.  Select a game, and play a few seconds
4.  Return to menu

What is the expected output? What do you see instead?

When returning to the menu, there is an error, unable to open folder.  I am 
then unable to browse the entire drive.  Disconnecting the drive and connecting 
it back to my PC shows the drive is corrupted.  The disk is replaced with 256 
files named ",,,,,,,,.,,,".

What version are you using? On GameCube or Wii?
Wii version 4.2.5
Launched from HBC

Are you using the official build (from the downloads page or auto-update)?
Official build 4.2.5 from download page.

Please provide any additional information below.

This is is new Wii 4.3u, just modified a few days ago.  The latest versions of 
WiiFlow, HBC, Genesis Plus GX, FCE Ultra GX all work fine (Including using 
IOS58).  IOS58 version is 24.32

Downgrading my version of Snes9x Gx to 4.2.2 work fines (IOS 202), however it 
has constant update reminders

Original issue reported on code.google.com by Robot...@gmail.com on 6 Dec 2010 at 6:26

[GoogleCodeExporter]

:(

Does it still happen on this version? 
http://tantric.dyndns.org/snes9xgx-beta.zip

Original comment by dborth@gmail.com on 17 Dec 2010 at 3:31

[GoogleCodeExporter]

This is some improvement...

After I exit a game, it still gives me errors and I am unable to open a 2nd 
game off the HDD, and it is unable to read any folders on the HDD.

However, when I plugged the HDD back into my computer, it still looks OK.  A 
step in the right dirrection.

Thanks for all the work on this, hopefully we can get it sorted out before it 
happens to someone without their whole drive backed up.

Original comment by Robot...@gmail.com on 17 Dec 2010 at 5:18

[GoogleCodeExporter]

This is not related to code in Snes9x GX, it's a libogc issue. I can't help you 
here. You'll just have to wait and see, it would be nice to see this fixed in 
libogc for 1.8.6.

Original comment by dborth@gmail.com on 17 Dec 2010 at 7:30

• Changed state: Invalid