Hi there,
does anyone know how to get a parallel port zip drive working with RTP?
Thanks,
Russ Bilbey
Previously, Russ Bilbey wrote in qdn.public.qnxrtp.os:
Hi there,
does anyone know how to get a parallel port zip drive working with RTP?
Not supported.
You can use IDE/SCSI zip drive…
Laveau.
Okay … so how do I get the IDE zip working with RTP?
Laveau Saint-Clair wrote:
Previously, Russ Bilbey wrote in qdn.public.qnxrtp.os:
Hi there,does anyone know how to get a parallel port zip drive working with RTP?
Not supported.
You can use IDE/SCSI zip drive…Laveau.
You just plug the ZIP drive into the EIDE port on your motherboard and it
will be detected automatically. However, the filesystem will only be mounted
if the ZIP disk is in the drive when the system is booted. I can’t figure
out how to mount the filsystem if the disk is not in the drive on boot-up,
or how to change between DOS & QNX filesystems. Anyone got an easy answer?
Jim Douglas
“Ken McGarvey” <kmcgarvey@keyww.com> wrote in message
news:3AF03E01.4F10EAFC@keyww.com…
Okay … so how do I get the IDE zip working with RTP?
Laveau Saint-Clair wrote:
Previously, Russ Bilbey wrote in qdn.public.qnxrtp.os:
Hi there,does anyone know how to get a parallel port zip drive working with
RTP?
Not supported.
You can use IDE/SCSI zip drive…Laveau.
Jim Douglas <jim@dramatec.co.uk> wrote:
: will be detected automatically. However, the filesystem will only be mounted
: if the ZIP disk is in the drive when the system is booted. I can’t figure
: out how to mount the filsystem if the disk is not in the drive on boot-up,
: or how to change between DOS & QNX filesystems. Anyone got an easy answer?
Use the “automount=” feature of io-blk.so …
Assuming your ZIP mounts as /dev/hd1, and your QNX partition is t77 and
your DOS is on a t6, then the following ‘blk’ option will do this -
“devb-eide blk automount=hd1t77:/zipqnx,automount=hd1t6:/zipdos”
If you refer to “/zipqnx” the filesystem will go out and see if the
current media has a t77 partition on it containing a QNX filesystem,
mount it, and let you use it. Ditto for a DOS if you access “/zipdos”.
Media ejection will cause an internal unmount/invalidation, and the
process begins again on media insertion.
This will work on any device that reports itself as being _DEV_REMOVABLE
(CD-ROM, DVD-RAM, floppy, etc). The floppy case is a little different
because you tend to not have partitions, so you need this variant -
“devb-fdc blk automount=+fd0:/fdqnx:qnx4,automount=+fd0:/fddos:dos”
Can you think of a way to stick support for this into mount utility
John? Driver is already running when system booted so you need to
rebuild image and reboot to use io-blk options.
People are reluctant to mess with boot image and cumbersome diskboot
options do not make it more attractive.
- igor
John Garvey wrote:
Jim Douglas <> jim@dramatec.co.uk> > wrote:
: will be detected automatically. However, the filesystem will only be mounted
: if the ZIP disk is in the drive when the system is booted. I can’t figure
: out how to mount the filsystem if the disk is not in the drive on boot-up,
: or how to change between DOS & QNX filesystems. Anyone got an easy answer?Use the “automount=” feature of io-blk.so …
Assuming your ZIP mounts as /dev/hd1, and your QNX partition is t77 and
your DOS is on a t6, then the following ‘blk’ option will do this -
“devb-eide blk automount=hd1t77:/zipqnx,automount=hd1t6:/zipdos”If you refer to “/zipqnx” the filesystem will go out and see if the
current media has a t77 partition on it containing a QNX filesystem,
mount it, and let you use it. Ditto for a DOS if you access “/zipdos”.
Media ejection will cause an internal unmount/invalidation, and the
process begins again on media insertion.This will work on any device that reports itself as being _DEV_REMOVABLE
(CD-ROM, DVD-RAM, floppy, etc). The floppy case is a little different
because you tend to not have partitions, so you need this variant -
“devb-fdc blk automount=+fd0:/fdqnx:qnx4,automount=+fd0:/fddos:dos”
Thanks everyone, comprehensively answered as ever.
Russ.
Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote in message
news:3AF07A37.97D1B366@motorola.com…
Can you think of a way to stick support for this into mount utility
John? Driver is already running when system booted so you need to
rebuild image and reboot to use io-blk options.
People are reluctant to mess with boot image and cumbersome diskboot
options do not make it more attractive.
- igor
John Garvey wrote:
Jim Douglas <> jim@dramatec.co.uk> > wrote:
: will be detected automatically. However, the filesystem will only be
mounted
: if the ZIP disk is in the drive when the system is booted. I can’t
figure
: out how to mount the filsystem if the disk is not in the drive on
boot-up,
: or how to change between DOS & QNX filesystems. Anyone got an easy
answer?Use the “automount=” feature of io-blk.so …
Assuming your ZIP mounts as /dev/hd1, and your QNX partition is t77 and
your DOS is on a t6, then the following ‘blk’ option will do this -
“devb-eide blk automount=hd1t77:/zipqnx,automount=hd1t6:/zipdos”If you refer to “/zipqnx” the filesystem will go out and see if the
current media has a t77 partition on it containing a QNX filesystem,
mount it, and let you use it. Ditto for a DOS if you access “/zipdos”.
Media ejection will cause an internal unmount/invalidation, and the
process begins again on media insertion.This will work on any device that reports itself as being _DEV_REMOVABLE
(CD-ROM, DVD-RAM, floppy, etc). The floppy case is a little different
because you tend to not have partitions, so you need this variant -
“devb-fdc blk automount=+fd0:/fdqnx:qnx4,automount=+fd0:/fddos:dos”