QNX4 4.25 Install Problems

I am trying to install QNX4 4.25 on a “new” computer.

The computer is a Digital Celebris XL 5120
120 Mhz Pentium
64 MB RAM
NCR 53c810 scsi - 4 Gb drive
Intel PCI 82557 ethernet card

Originaly the problem was getting

QNX Loader
Boot Partition 1
(Unable to find OS - or something similar)

I re-fdisk-ed the disk using fsys h=255,63

now what I get is the following

QNX Loader
Boot Partition 1
Press Esc for alternate OS…_

and then the computer hangs…

If I boot from a floppy I can then perform

Fsys.ncr8scsi
mount -p /dev/hd0
mount /dev/hd0t77 /hd
/hd/bin/prefix -R /=/hd/

and get full access to the drive.

Anybody have an idea what the problem is?

What arguments are used to load the Fsys driver during installation time?
Are they the same arguments used in the build image?

From what media did you install? I had similar problems with QNX All
Products CD then I installed from a set of floppies and all worked well. I
didn’t look into it further but I find that the CDs tend to add more
arguments to the drivers then the floppies do.

FYI
Fsys.sym8scsi is new to 4.25D. I believe its replacing the Fsys.ncr8scsi.
You may want to try that.

  • Richard

The install was done with the following command

install -p “fsys h=255,63”

build script is

sys/boot
$ boot -vp

sys/Proc32
$ Proc32 -l 2

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys

/bin/Fsys.ncr8scsi
$ Fsys.ncr8scsi fsys -h=255,63

/bin/mount
$ mount -p /dev/hd0 /dev/hd0t77 /

/bin/sinit
$ sinit TERM=qnx

I do not believe that the OS is getting out of ./boot as I never see the
output from the -v option!
At what point would that output usually appear?

Regards
Mike Nunan






“Brown, Richard” <brownr@aecl.ca> wrote in message
news:9b4t0e$t3q$1@inn.qnx.com

What arguments are used to load the Fsys driver during installation time?
Are they the same arguments used in the build image?

From what media did you install? I had similar problems with QNX All
Products CD then I installed from a set of floppies and all worked well. I
didn’t look into it further but I find that the CDs tend to add more
arguments to the drivers then the floppies do.

FYI
Fsys.sym8scsi is new to 4.25D. I believe its replacing the Fsys.ncr8scsi.
You may want to try that.

  • Richard

I should add that the install was done from floppy.

I do not know what patch level I have (A,B,C…). I will look into it.

“Michael Nunan” <m.nunan@ieee.ca> wrote in message
news:9b4u5o$ke$1@inn.qnx.com

The install was done with the following command

install -p “fsys h=255,63”

build script is

sys/boot
$ boot -vp

sys/Proc32
$ Proc32 -l 2

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys

/bin/Fsys.ncr8scsi
$ Fsys.ncr8scsi fsys -h=255,63

/bin/mount
$ mount -p /dev/hd0 /dev/hd0t77 /

/bin/sinit
$ sinit TERM=qnx

I do not believe that the OS is getting out of ./boot as I never see the
output from the -v option!
At what point would that output usually appear?

Regards
Mike Nunan






“Brown, Richard” <> brownr@aecl.ca> > wrote in message
news:9b4t0e$t3q$> 1@inn.qnx.com> …
What arguments are used to load the Fsys driver during installation
time?
Are they the same arguments used in the build image?

From what media did you install? I had similar problems with QNX All
Products CD then I installed from a set of floppies and all worked well.
I
didn’t look into it further but I find that the CDs tend to add more
arguments to the drivers then the floppies do.

FYI
Fsys.sym8scsi is new to 4.25D. I believe its replacing the
Fsys.ncr8scsi.
You may want to try that.

  • Richard

    \