keirf / greaseweazle

Tools for accessing a floppy drive at the raw flux level
The Unlicense
997 stars 100 forks source link

Need help reading 5 1/4" Monkey Island 1 360k floppies #425

Closed CitricTabby closed 7 months ago

CitricTabby commented 7 months ago

I have a Greaseweazle 4.0 hooked up to a 3 1/2" and 5 1/4" floppy combo drive with an external Molex power supply hooked up to a dual Berg male to female Molex splitter cable, and I need the proper commands to use the Greaseweazle command line app to properly dump the disk images of all eight Monkey Island 1 authentic 5 1/4" 360k floppies that I bought via eBay recently.

Thanks!

CitricTabby commented 7 months ago

Another thing I should add is that when I first used GW to read the floppies' data to create disk images, the 5 1/4" section of my floppy combo drive had some initial "unknown mark" related problems and missing sectors due to the fact it hasn't been used in a good while. After setting the --revs option to around 50 to 100, it started to get the hang of it by getting back into sync and when I started to read the disks again as usual, it began working well.

My way of reading floppy disks of old retail games (whether it be DOS, Amiga, or even Atari ST) consists of the following command line parameters:

gw.exe read insertdiskimagename.here --drive=b --format=whatever --retries=10 --seek-retries=10 --revs=5

The reason why my drive letter is B is due to the fact I'm using a straight floppy ribbon cable hooked up to my GW 4.0 USB device that's usually found in Amiga computers.

As for 5 1/4 inch disks like the Monkey Island 1 kind mentioned earlier, my commands used after my 5 1/4" half of the floppy combo drive was back in sync were:

gw.exe read monkey_x.ima --drive=b --format=ibm.360 --retries=10 --seek-retries=10 --tracks="c=0-39:h=0-1:step=2" --revs=5

Before that, I used:

gw.exe read monkey_x.ima --drive=b --format=ibm.360 --retries=10 --seek-retries=10 --tracks="c=0-39:h=0-1:step=2" --revs=100

BTW regarding the --tracks parameter, I googled it up myself and found a closed support ticket regarding that and reading 360k 5 1/4" floppies under this GitHub project.