Hi,
The zip drive is configured as master and the only drive attached to this IDE controller.
The /!BIOS option was added during default installation of ECS RC5.
The documentation of DANIS506 tells me that it might be the best to switch this option because information is now based upon the drive it self: (Quote of DANIS506.DOC)
One user reported a boot failure in a particular situation which involved
SCSI and ATA/ATAPI units. The solution was to avoid BIOS INT13 calls. The
driver asks the BIOS about the geometry properties of the ATA drives. In
general, this information is not required because the most authorative
source of the geometry info is the drive itself (by inspecting the MBR and
BPBs). This implies that no BIOS INT13 calls are required in almost any
scenario. The only exception is if your disk is completely blank, and you
want to partition this blank disk by OS/2 FDISK with a geometry compatible
to the BIOS one.
So, if you prefer to deny the driver calling the BIOS, add the option
/!BIOS. When doing so, the "strange" VDM seen with some process management
utilities is gone as well.
I don't think the cabling is the problem because I can use all functionality of the drive under Linux as well as Windows XP on this same system and setup. This is a multi boot configuration with those operating systems.
In the past I have used 80wire cables with zipdrives and this worked fine under ECS.
I rebooted with the /!BIOS removed, with BASEDEV=DANIS506.ADD.
The system booted and showed Loading OS2DASD.DMD and stayed there forever.
After switching back to the options /!BIOS /A:2 /I the system booted normally again.
I have attached dumpide output in case I boot with the /A:2 /I options.
Also attached current config.sys containing more information about the system.
Regards,
Jan