sumomo214 / cfg-loader-mod

Automatically exported from code.google.com/p/cfg-loader-mod
GNU General Public License v2.0
0 stars 0 forks source link

Loader do not recognize External HD #56

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. After launching CFG   it says that my hard drive is not connected
2. i Tried to load the 222IoS but nothing happened

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

Original issue reported on code.google.com by fabrizio...@gtempaccount.com on 6 Jun 2012 at 9:54

GoogleCodeExporter commented 8 years ago
I am also have this issue with my external hard-drive (having poor 
synchronization with CFG).  I am using CFG v70 initial release but have tested 
and experienced the issue with mods r15 and r51 as well.

The problem did not exist when a USB T-Flash Card Reader (w/ NTFS-formatted 
SDHC) nor when a USB NTFS-formatted thumb drive were used instead.  The problem 
only occurs for me when my Toshiba 1 TB Canvio Basics 3.0 NTFS-formatted 
portable hard-drive is used.

I receive the "Device is not responding!" message when attempting to start the 
program and then the 90-second timeout will being to run.  And time will just 
elapse away while the hard-drive LED blinks rapidly, appearing to be in some 
kind of seeking mode; on average for about thirty seconds, sometimes sooner, 
sometimes the full 90 seconds and then a restart are required before CFG 
successfully loads.

Please note that if the hard drive cable is removed from the Wii and reinserted 
during this process, the hard drive becomes immediately recognized.  So 
something isn't synchronizing 100% between the program and the hard-drive that 
can be overridden physically by simply unplugging and replugging.  Perhaps the 
program can mimic this physical off/on action through a command(s) before 
starting the seeking process to help negotiate a quicker connection with 
troublesome drives like mine.

Here's a debug log of my latest instance, where it took 48 seconds to 
synchronize.  I hope this will aid in resolving the issue.

Original comment by SpewH...@aol.com on 29 Jan 2013 at 6:48

Attachments: