Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: paulstevens on September 26, 2007, 11:19:42 pm
-
I ma trying to use chdman to reimage a hard drive for a dedicated Rush2049 driving game.
I've tried using chdman -extract sf2049te.chd \\.\PHYSICALDRIVE0 without success.
I've tried it using 4 different hard drives, all of which are 10GB or more. The resulting drive when looked at using WinHex looks "correct" but it does not boot in my friends Rush2049 cabinet. It fails with HDIO Home Blocks Not found, or something to that effect.
The sf2049te.chd was obtained from [romsite name redacted].
The chdman version I used was 0.117 from the 0.117 release of MAME.
Can anyone offer any suggestions as to why this did not work? What I am doing wrong?
Or if someone has actually used chdman successfully to extract images to hard drives for use in original games, can they tell what version of chdman they used?
Also, if there is a more appropriate forum to place this question, please accept my apologies and let me know where I should ask.
Thank you very much for the help!
-
I've tried using chdman -extract sf2049te.chd \\.\PHYSICALDRIVE0 without success.
Yikes! \\.\PHYSICALDRIVE0 is almost always your boot drive. Good thing Windows is protective enough to make sure you can't do that!
The drive you plugged in is going to be a different drive number. Type this command line:
echo list disk | diskpart
And it should list all the drives on your system. Look for the one you added (by size) and then extract to that drive number. If it's drive 2 you want, then extract to \\.\PHYSICALDRIVE2.
-
Hi Aaron - thanks for taking the time to reply.
Yes in most cases \\.\PHYSICALDRIVE0 is the boot drive, but not in my case. I boot of 2 (master on the secondary IDE channel). Anyway, the problem I have is not with which drive to exctract to. I am absolutely sure I have that correct, verified by size and model/serial number.
So, given that I'm sure I'm extracting to the correct physical drive, can you think of any other reason the resulting drive does not work?
FWIW, I also tried this on two different pc's, one with XP the other with Win2K, each with different phsycal drives (one was "0" the other was "1"). Same result.
Thanks again. I really appreciate your advice.
-
Make sure you have the right version of 2049. There were a few versions.
-
Yes in most cases \\.\PHYSICALDRIVE0 is the boot drive, but not in my case. I boot of 2 (master on the secondary IDE channel). Anyway, the problem I have is not with which drive to exctract to. I am absolutely sure I have that correct, verified by size and model/serial number.
Good, glad to hear it. You were scaring me there. :)
So, given that I'm sure I'm extracting to the correct physical drive, can you think of any other reason the resulting drive does not work?
If it is extracting correctly to the drive, the only thing I can think of is that the sf2049 boot code doesn't support drives larger than a certain size (8GB would be my guess).
The only other thing I would try is extracting the standard sf2049 image to see if that works.