CD Mounting

Erick,

Starting a new thread for the CD Rom.

Please recall my sysinit.5 file:

#Image: /boot/sys/boot -v
#Image: /boot/sys/Proc32 -l 5
#Image: /boot/sys/Slib32
#Image: /boot/sys/Slib16
#Image: /bin/Fsys
#Image: /bin/Fsys.eide fsys -Ndsk0 -n0=hd0. -n5=cd0. eide -a1f0 -i14
#Image: /bin/mount -p /dev/hd0.0 /dev/hd0.0t77 /
#Image: /bin/sinit TERM=qnxm
#export NODE=5
export KBD=en_US_101.kbd
export ABLANG=en
export CON_KBD=USA
export TZ=est05edt04,M4.1.0/2,M10.5.0/2
/bin/rtc -l hw
Dev &
emu87 &
Pipe &
/bin/Dev.ser -N/dev/ser1 3f8,4 &
/bin/Dev.ser -N/dev/ser2 2f8,3 &
Dev.ansi -Q -n6 &
reopen /dev/con1
kbd $CON_KBD
prefix -A /dev/console=/dev/con1
Dev.par &
Dev.pty -n16 &
mousetrap start &
/bin/Fsys.floppy -a3f0 -i6
/bin/Iso9660fsys /cd0.0=/dev/cd0.0 &

Define the default CD Rom

/bin/prefix -A /cd0.0=//0/cd0.0
nettrap start &
sleep 2
netmap -f
nameloc &
chkfsys /
Dosfsys a=/dev/fd0 &
if test -f /etc/config/bin/tcpip.$NODE
then
… /etc/config/bin/tcpip.$NODE
fi
if test -f /etc/config/bin/ph.$NODE
then
… /etc/config/bin/ph.$NODE
else
tinit -t /dev/con1 &
tinit -T /dev/con[2-6] &
fi

I can mount a CD-Rom manually by typing in:
Fsys.eide &
Iso9660fsys &

However, this does not work at startup. Normally after I manually type in
“Fsys.eide &”, it shows two "Path"s, one for the hard drive (Path=0) and one
for the CD Rom(Path=1). But at startup, only the hard drive shows up. If I
check the /dev directory, “cd0” is not there.

Are the arguments correct for the “#Image: /bin/Fsys.eide …” command?

Szu Kay

On Fri, 14 Sep 2001, Mario Charest wrote:

I can mount a CD-Rom manually by typing in:
Fsys.eide &

Yeik, you are starting to Fsys.eide that will try to control
the HD, not good at all. I’m surprise it doesn’t screw things
up.

If your CDROM is ATAPI attached to the IDE controller, you definitely
need to have Fsys.eide running in order for Iso9660fsys to see the /dev/cdX.
If you have a SCSI CDROM, it’s a different story.

Frank



Iso9660fsys &

However, this does not work at startup. Normally after I manually type in
“Fsys.eide &”, it shows two "Path"s, one for the hard drive (Path=0) and
one
for the CD Rom(Path=1). But at startup, only the hard drive shows up. If I
check the /dev directory, “cd0” is not there.

Are the arguments correct for the “#Image: /bin/Fsys.eide …” command?

These is just the command that is execute in the image (as create during
the installation).

Is the CD primary slave?

Szu Kay


\

I can mount a CD-Rom manually by typing in:
Fsys.eide &

Yeik, you are starting to Fsys.eide that will try to control
the HD, not good at all. I’m surprise it doesn’t screw things
up.

Iso9660fsys &

However, this does not work at startup. Normally after I manually type in
“Fsys.eide &”, it shows two "Path"s, one for the hard drive (Path=0) and
one
for the CD Rom(Path=1). But at startup, only the hard drive shows up. If I
check the /dev directory, “cd0” is not there.

Are the arguments correct for the “#Image: /bin/Fsys.eide …” command?

These is just the command that is execute in the image (as create during

the installation).

Is the CD primary slave?

Szu Kay

If I’m not mistaken, when Fsys.eide detects that a drive is already in
control by another instance of Fsys.eide, doesn’t it just give control to
the instance that found it first? I’ve started Fsys.eide a few times before
when I was first learning QNX and it never caused any problems.

But you really should only need at most 2 (that I know of) Fsys.eide
instances, 1 to handle primary channel and the 2nd to handle the secondary
channel. You can run 1 to handle all too, but I like to keep mine
configured with the 2.

What I have in my boot image is one call to Fsys.eide:
/bin/Fsys.eide fsys -Ndsk0 -n0=hd0. -n5=cd0. eide -a1f0 -i14

and in my sysinit file somewhere before I start Iso9660fsys (a lot of other
things are started up in between):
/bin/Fsys.eide fsys -Ndsk1 -n0=hd1. -n5=cd1. eide -a170 -i15

(actually, it’s -n5=cd0. so even on the secondary channel my CDROM drive
will come up as /dev/cd0.0, but for this example it will list the CDROM
drive as a secondary channel device).

Note that the #Image lines in your sysinit file don’t do anything, they’re
just there for you to see what is being started by the boot image before the
sysinit file is loaded (/.boot or /.altboot). So if you change them they’re
not going to do anything. To change something in your boot image, you can
look through helpviewer I think to find out more. Plus if you got a nice
box of QNX documentation and manuals you can find it there too.


“Mario Charest” <mcharest@nowayzinformatic.com> wrote in message
news:9ntioh$8q0$1@inn.qnx.com

“Frank Liu” <> liug@mama.indstate.edu> > wrote in message
news:> Pine.LNX.4.33.0109141107210.29511-100000@mama.indstate.edu> …
On Fri, 14 Sep 2001, Mario Charest wrote:

I can mount a CD-Rom manually by typing in:
Fsys.eide &

Yeik, you are starting to Fsys.eide that will try to control
two
the HD, not good at all. I’m surprise it doesn’t screw things
up.

If your CDROM is ATAPI attached to the IDE controller, you definitely
need to have Fsys.eide running in order for Iso9660fsys to see the
/dev/cdX.
If you have a SCSI CDROM, it’s a different story.


Only one Fsys.eide must be in controller of each IDE interface.

If the CDROM is primary slave, only one Fsys.eide is needed as
it will should detect both HD and CDROM.

If the CDROM is secondary slave/master, either a second Fsys.eide
must be started with argument to specify interface to controle. Or
have one Fsys.eide control both primary and secondary.

Frank




Iso9660fsys &

However, this does not work at startup. Normally after I manually
type
in
“Fsys.eide &”, it shows two "Path"s, one for the hard drive (Path=0)
and
one
for the CD Rom(Path=1). But at startup, only the hard drive shows
up.
If I
check the /dev directory, “cd0” is not there.

Are the arguments correct for the “#Image: /bin/Fsys.eide …”
command?

These is just the command that is execute in the image (as create
during
the installation).

Is the CD primary slave?

Szu Kay





\

“Frank Liu” <liug@mama.indstate.edu> wrote in message
news:Pine.LNX.4.33.0109141107210.29511-100000@mama.indstate.edu

On Fri, 14 Sep 2001, Mario Charest wrote:

I can mount a CD-Rom manually by typing in:
Fsys.eide &

Yeik, you are starting to Fsys.eide that will try to control
two
the HD, not good at all. I’m surprise it doesn’t screw things
up.

If your CDROM is ATAPI attached to the IDE controller, you definitely
need to have Fsys.eide running in order for Iso9660fsys to see the
/dev/cdX.
If you have a SCSI CDROM, it’s a different story.

Only one Fsys.eide must be in controller of each IDE interface.

If the CDROM is primary slave, only one Fsys.eide is needed as
it will should detect both HD and CDROM.

If the CDROM is secondary slave/master, either a second Fsys.eide
must be started with argument to specify interface to controle. Or
have one Fsys.eide control both primary and secondary.

Frank




Iso9660fsys &

However, this does not work at startup. Normally after I manually type
in
“Fsys.eide &”, it shows two "Path"s, one for the hard drive (Path=0)
and
one
for the CD Rom(Path=1). But at startup, only the hard drive shows up.
If I
check the /dev directory, “cd0” is not there.

Are the arguments correct for the “#Image: /bin/Fsys.eide …”
command?

These is just the command that is execute in the image (as create during
the installation).

Is the CD primary slave?

Szu Kay



\