Open GoogleCodeExporter opened 8 years ago
version?
vhats the whole error message?
Original comment by Howard_M...@yahoo.com
on 24 Dec 2014 at 3:35
I'm having the same problem with r271. I've verified my IOS 58 is correct, my
hard drive is FAT32 (specifically FAT32 LBA 0xC) with 32k clusters. I had
previously been using DIOS MIOS Lite (DML) 2.3 running DiscEx formatted
GameCube games from my SD card fine. I used Gamecube ISO Tool 1.0.1 Build 5 to
create the DiscEx files from raw GCM files. I started this from USB Loader GX
but when that didn't work, I've been now exclusively loading nintendon-t from
the Homebrew Channel 1.1.2.
Slightly unrelated, but potentially useful. I changed my cMIOS from DML 2.3 to
DM 2.11 and have attempted using that to load my DiscEx formatted GameCube
games with even less success. The screen goes black without a DIOS MIOS
screen. This makes me suspicious but I am still trying out different things.
Original comment by whi...@gmail.com
on 7 Jan 2015 at 6:29
First, a correction, or perhaps clarification. My drive had a partition type
of 0x0C (or 0Ch, whichever nomenclature you prefer). I've spent a good time
trying to figure out the difference between FAT32 and FAT32X, between CHS
(Cylinder-head-sector) and LBA (Logical block addressing). I haven't learned
as much as I'd liked but via trial and error I have resolved "my" error 13 by
changing the partition type on my hard drive from FAT32X (0x0C) to FAT32
(0x0B). I used MiniTool Partition Wizard Professional Edition 8.1 to do this
without needing to reformat the whole drive.
As for the 5 W's? Heck if I even know how I resolved the issue other than
brute force trial and error. I can't even remember how I formatted the drive
the first time around. I believe I used the Windows 7 format from the command
line with the arguments "/FS:FAT32 /A:32K". I'd love to do a trial and error
on a large drive to see if this holds true that Windows secretly uses the
FAT32X partition type without my knowledge. Regardless I can see how this
might be a problem as I've learned "FAT32x volumes store their FAT tables at
the end of the volume rather than the beginning."
(http://progettista.ru/0735711585_ch15lev1sec2.shtml) I could see how that
might give pause to a piece of software that concerns itself with the FAT table.
Regardless, my issue is resolved, hopefully this information proves useful to
someone else. I'll be doing a slightly more complete write-up for my Tumblr
soon (http://radiok19.tumblr.com/)
Original comment by whi...@gmail.com
on 8 Jan 2015 at 5:52
Original issue reported on code.google.com by
thewanil...@gmail.com
on 23 Dec 2014 at 4:58