Message-Id: <199805231359.IAA19970@endeavor.flash.net>
MIME-Version: 1.0
To: <ben DOT jemmett AT ukonline DOT co DOT uk>
From: "Mark AT BlinkLink DOT NET  AKA" <mwarchol AT flash DOT net>
CC: <opendos AT delorie DOT com>
Date: Sat, 23 May 1998 09:59:20 +0400
Subject: Re: linux with OD?
Precedence: bulk

  If it is storage you want from drive B, you can use a superdisk which fits
internally as a standard drive, reads the 1.44 disks and also stores onto
120 meg disks holding more than the 100 zip type.  If your computer has the bias
choice then it's easy to config, if not you may need a card such as the
Promise card which fits into a isa slot.
    Mark

On 1998-05-23 ben DOT jemmett AT ukonline DOT co DOT uk said:
   >> The only problem I see here is with b: zip
   >>As far as I know, dos machines require that b: is the second
   >>floppy. HD's start at c: and go up from there. (zip drives are
   >after all, HD's) >
   >> I may be wrong on this.
   >>Does anyone know for sure wheather or not b: can be used
   >>for the zip drive?
   >Drive B: cannot be used for a Zip drive (or any other non-floppy
   >device) as DOS uses A and B for floppy drives.  If drive B does not
   >exist in hardware, DOS emulates a second floppy drive, producing
   >prompts like 'Insert disk for drive B: and press any key to
   >continue...'  It may be possible to set up the Zip drive and use a
   >command like ASSIGN B=E (or whatever), but I fear this may produce
   >the error message 'Cannot ASSIGN a network drive'.  I may be
   >possible to write a device driver to reroute requests to drive B:
   >to the Iomega drivers, but this would probably be a rather
   >inelegant solution, and would most likely require a lot of
   >programming/DOS knowledge - any offers? Regards,
   >Ben A L Jemmett