I have to install QRTP on a scsi machine. It seems that it was impossible with the 08-00 pre-release because of problems with timeout problems while scanning devices.
Is it fixed now?
I think that I can install QRTP merging a QNX4 IDE disk and making an install …
But what about booting after?
I have to install QRTP on a scsi machine. It seems that it was impossible with the 08-00 pre-release because of problems with timeout problems while scanning devices.
Is it fixed now?
I think that I can install QRTP merging a QNX4 IDE disk and making an install …
But what about booting after?
Thanks, Alain.
We’re working on solutions for non-EIDE installs. The main problem is that
if we include SCSI support in the booter and installer, the image gets
too big to install on any machine.
I have to install QRTP on a scsi machine. It seems that it was impossible with the 08-00 pre-release because of problems with timeout problems while scanning devices.
Is it fixed now?
I think that I can install QRTP merging a QNX4 IDE disk and making an install …
But what about booting after?
Thanks, Alain.
We’re working on solutions for non-EIDE installs. The main problem is that
if we include SCSI support in the booter and installer, the image gets
too big to install on any machine.
We’re working on solutions for non-EIDE installs. The main problem is that
if we include SCSI support in the booter and installer, the image gets
too big to install on any machine.
why not create a scsi-only install image?
That’s one possible solution, but there are better ones. We would actually
need a SCSI install image for each type of SCSI controller, or we would
have the same problem with the image size being too big.
Martin Maciaszek <> mmaciaszek@gmx.net> > wrote:
We’re working on solutions for non-EIDE installs. The main problem is
that
if we include SCSI support in the booter and installer, the image gets
too big to install on any machine.
why not create a scsi-only install image?
That’s one possible solution, but there are better ones. We would actually
need a SCSI install image for each type of SCSI controller, or we would
have the same problem with the image size being too big.
The problem is, where to get the stuff to put into RAM? it is probably
on your CD, which requires SCSI driver to access. They don’t support
BIOS CD-as-floppy emulation, which is what allows BIOS to access the CD.
Last time I heard, they were intended to put the rest of drivers on the
floppy, outside of boot image. That allows to have only floppy driver in
the image, but of course it will require you to have a floppy.
Hopefully, they won’t foret about LS120 (some machines have LS120
instead of floppy) and will squeeze eide driver there too.
igor
Roland Henkel wrote:
Couldn’t you first after basic boot create a ramdisk containing a minimal
system with the appropriate drivers? This can do the rest.
Regards,
Roland
pete@qnx.com> > schrieb im Newsbeitrag news:8qvt2f$c3p$> 2@nntp.qnx.com> …
Martin Maciaszek <> mmaciaszek@gmx.net> > wrote:
We’re working on solutions for non-EIDE installs. The main problem is
that
if we include SCSI support in the booter and installer, the image gets
too big to install on any machine.
why not create a scsi-only install image?
That’s one possible solution, but there are better ones. We would actually
need a SCSI install image for each type of SCSI controller, or we would
have the same problem with the image size being too big.