Someone please help me out here

[Matt_H]

Cartridge drives can either be given a mountlist, or have an RDB installed on them.

Since you are seeing the drive in HDToolbox, it should just be a simple matter of hitting the "Install" button to prep the disk.

Alternatively, see SYS:Storage/DOSDrivers. 3.9 comes with a file called ZIP and another called ZIC. ZIP is a mountlist for FFS Zip disks, ZIC is one for CrossDOS disks. Adjust the device/unit info to match. I think it's in the ToolTypes. It'll be whatever the device name of the PowerFlyer is, unit 2. IOTools in SYS:Tools might be useful, too.

EDIT:
If the PowerFlyer uses scsi.device, it's going to conflict with the scsi.device in the 1200's ROM. One or the other will probably be renamed to 2nd.scsi.device. Adding
SKIPROMMODULES scsi.device
to your Setpatch line in the startup-sequence might help. You also might want to download the IDEFix package - there's a tool in there called FindDevice which will give you a scan of everything on your IDE buses. Might give you a clear picture of how exactly everything's configured.

Also, have you installed BB2? There's a new version of the NSDPatch.cfg in it that may help with your missing partitions. It's not activated by default, so you'll have to rename Devs:NSDPatch.cfg-BB2 (or whatever it's called) to plain NSDPatch.cfg. Be sure to back up the old one, just in case.

[Matt_H]

Why can't you remove the disk? What happens?

[Matt_H]

Ah. That's an easy fix. Load up mounter in SYS:Tools and just remount the device. I had to do that all the time when I swapped out SyQuest cartridges on my A500 many years ago. Some drive controllers can detect those changes automatically, but others can't, including this one, it seems.

Consider IOTools as well, since it's specifically designed to work with Zip drives.

[Matt_H]

Mounter and IOTools both require the device name to be set in ToolTypes. Make sure it's correct.

[Matt_H]

Gav wrote:
@ Matt
Which should be trackdisk.device,correct??? iotools asks me what buffer size my controller is so how do i find that out??

No, not trackdisk.device - that's the device for the internal floppy. If the PowerFlyer does claim to allow a Zip drive to be mounted under that device name, it's got to be a nasty hack and can't be very system friendly or stable. It's probably scsi.device or 2nd.scsi.device. Use that FindDevice tool I mentioned earlier to scan all your drive buses and see where your Zip drive is.

As for the buffer size, I'd suggest leaving it at the default value. I'm not really sure about that one. Maybe someone else reading knows?

[Matt_H]

They may have meant that the only device in the system that supports hot swapping is trackdisk.device, not that hot swapping is enabled by using trackdisk.device for the Zip drive.

Could another PowerFlyer owner verify this?

[Matt_H]

@ Doobrey & Gav

Huh. Well, I stand corrected on the trackdisk.device area. I have complete confidence in Doobrey's hardware knowledge :-).

Try setting the unit to 6, then.

[Matt_H]

@ Doobrey

Then you're as mad as a bag of badgers. There's people around here with a lot more experience and knowledge than me, I'm bound to be wrong sooner or later.

Hey, if you can build a FlashROM from scratch and wire in a missing access LED, that seems pretty damn good to me. :-)

@ Gav

Sorry to hear about your frustration. Hope you get things working.