I ordered a Catweasel Mk4 PCI card from Amigakit several months ago and finally got around to fitting it into my trusty old eMachine T6420 running Windows XP.
For those not familiar with the Catweasel family, they are a series of floppy controllers that allow normal floppy drives to read and write to and from a multitude of formats. From an Amiga user's point of view, it allows you to use a PC to read Amiga floppy disks to make ADF images (including "corrupt" disks that your Amiga might have trouble reading) and to write ADF images back to a blank floppy all using a standard PC floppy disk.
In the box you get the following:
Catweasel PCI card
Cable to connect PC floppy controller to Catweasel
Cable to connect Catweasel to two floppy drives
3.5" to 5.25" floppy cable adapter
CD ROM containing drivers, software and "read me" files
4 page "idiots guide" to installing hardware
The Catweasel also has sockets for attaching two C64 SID chips, an Amiga keyboard port and two Amiga/C64 joystick/mouse/paddle ports. I've not got around to trying these yet with any emulation packages.
I bought the card primarily to write back *.D64 and *.ADF files back to Amiga 3.5" and 1571 5.25" floppy disks for use on real Amigas and C64s/C128s. My first task was to track down a couple of suitable drives as my tower had no floppy drive built in. The 3.5" drive came from an old Pentium 120MHz tower and the 5.25" drive came from an even older 486 desktop that had been gathering dust on my shelves.
I had a free 5.25" drive bay in the tower and when I prized the front panel off the card readers I found a hidden 3.5" bay below it. On the motherboard itself I also found a floppy controller port, but as I didn't intend to read PC disks from Windows I didn't bother to connect it.
I fitted the floppy cable to the Catweasel and then carefully connected the cables to the 3.5" and 5.25" drives (using the adapter for the 5.25" drive) making sure to have the red stripe on the cable lined up to pin 1 on each drive. The 3.5" drive attached to the end of the cable and the 5.25" drive attached to the center connector. This allowed the 3.5" in appear as "Drive A: (Unit 1)" and the 5.25" to be "Drive B: (Unit 0)".
I then installed the Catweasel in a spare PCI slot and switched on the computer (at this point I did not connect the power leads to the drives because I forgot! Doh!). Windows picked up the new hardware and each time it prompted for drivers (the card, the keyboard connector, the ports) I redirected the search to the CD ROM drive containing the drivers. I then powered the system down, connected the power connecters to the floppy drives, powered back up and watched as Windows detected the 2 drives. Once again I redirected the request for the drivers to the CD ROM.
The CD ROM has two versions of Imagetool for handling the reading and writing of disks. After looking at both I settled on the fancier Imagetool3 which pops up a simple to use interface where you can easily decide which drive to use and whether you want to write real disks, make image files, etc.
For my first test I decided to write back the 2 ADF images of "Wings" to a couple of old Amiga disks. In turn, I loaded each image from the ADF files, selected the 3.5" drive, inserted a disk and selected "write to disk". I watched the graphics display as the disk was written and verified and then tested both disks in my A3000. They worked perfectly. I then decided to try and make a copy of "Elite" which was always a pain on the Amiga without using hardware dongles or advanced coying software. Once again it spat out a fully working 3.5" floppy for the A3000.
I then switched to the 5.25" drive and used the software to format a C64 floppy and to read a 5.25" disk containing "Red Storm Rising" and it is here where I’m having problems. Everything on the Imagetool screen seems to go well, but the “produced disks don’t work. I finally formatted a SSDD floppy on the 1571 and verified that it was OK, a put it in the 5.25” drive attached to the Catweasel, loaded Ghostbusters D64 file and wrote it back to the floppy. I watched as the drive hummed and clicked and the screen showed the blocks being written. I then put it back in the 1571 and tried to load it with no luck. A check of the directory showed an empty formatted disk. Perhaps it’s just this ancient 5.25” drive. I can still write images to disk using the MMC Replay and the real 5.25”, but this problem is a mystery to me.