build file...

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Hi…

The following build file will not boot. However, if I coment out

…
devn-smc9000.so
npm-ttcpip.so
npm-qnet.so
…
io-net
fs-nfs2
inetd
tftpd
tftp


then it will work and the machine will boot. What am I doing wrong?

Thanks…

Miguel.

P.S. 133 MHz PC104, no PCI, floppy + rotating HD.

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] .bootstrap = {
startup-bios -s 64k
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}

the startup script

[+script] .script = {
SYSNAME=nto
TERM=qansi
DL_DEBUG=1

seedres
display_msg Booting Neutrino

EIDE driver

devb-eide blk automount=hd0t79:/hd0 &
waitfor /hd0/usr 30

Start up some consoles

oepn console

devc-con -n4 &
reopen /dev/con1

Some common servers

pipe &
mqueue &
devc-pty &

Start some extra shells on other consoles

reopen /dev/con2
[+session pri=10r] fesh &
reopen /dev/con3
[+session pri=10r] fesh &

Start a high priority shell just in case…

reopen /dev/con4
[+session pri=30r] fesh &

Start the main shell

reopen /dev/con1
[+session pri=10r] fesh &

#floppy drive support
display_msg “Starting the floppy driver”
devb-fdc &
waitfor /dev/fd0 30

display_msg “Mounting filesystem”

mount -tqnx4 /dev/fd0 /fd0
waitfor /fd0 10

}

[type=link] /tmp=/dev/shmem
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so
[type=link] /usr/lib/libcam.so.1=/proc/boot/libcam.so.1

[type=link] /dev/console=/dev/con1
[type=link] /dev/log = /dev/null
[type=link] /proc/dumper = /dev/null
[type=link] /bin=/proc/boot

libc.so
fpemu.so
libm.so

libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so

libsocket.so

devn-smc9000.so
npm-ttcpip.so
npm-qnet.so

[data=c]
seedres
/sbin/diskboot
/sbin/devc-con
/sbin/devb-fdc
/sbin/devc-pty
/sbin/devb-eide
/sbin/devc-ser8250
/bin/dinit
/sbin/pipe
/sbin/mqueue
/bin/fesh
/bin/mount
/bin/umount
/usr/bin/passwd
/bin/ping
/bin/slay
/bin/ls
/bin/mkdir
/bin/cp
/bin/rm
/bin/mv
/bin/ln

stty
echo
pidin
uname
esh
ls
sleep
nicinfo


cat
ftp
ftpd
if_up

/etc=./fs/etc
/usr/lib/terminfo=./fs/terminfo
ping
telnetd
telnet
login
logout
sh

io-net
fs-nfs2
#/usr/sbin/inetd
tftpd
tftp

–
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/

2

It’s probably a size issue, on x86 systems there is a 640KB limit for
your image. This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <simon@ou.edu> wrote:

Hi…

The following build file will not boot. However, if I coment out

…
devn-smc9000.so
npm-ttcpip.so
npm-qnet.so
…
io-net
fs-nfs2
inetd
tftpd
tftp



then it will work and the machine will boot. What am I doing wrong?

Thanks…

Miguel.

P.S. 133 MHz PC104, no PCI, floppy + rotating HD.

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] .bootstrap = {
startup-bios -s 64k
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}

the startup script

[+script] .script = {
SYSNAME=nto
TERM=qansi
DL_DEBUG=1

seedres
display_msg Booting Neutrino

EIDE driver

devb-eide blk automount=hd0t79:/hd0 &
waitfor /hd0/usr 30

Start up some consoles

oepn console

devc-con -n4 &
reopen /dev/con1

Some common servers

pipe &
mqueue &
devc-pty &

Start some extra shells on other consoles

reopen /dev/con2
[+session pri=10r] fesh &
reopen /dev/con3
[+session pri=10r] fesh &

Start a high priority shell just in case…

reopen /dev/con4
[+session pri=30r] fesh &

Start the main shell

reopen /dev/con1
[+session pri=10r] fesh &

#floppy drive support
display_msg “Starting the floppy driver”
devb-fdc &
waitfor /dev/fd0 30

display_msg “Mounting filesystem”

mount -tqnx4 /dev/fd0 /fd0
waitfor /fd0 10

}

[type=link] /tmp=/dev/shmem
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so
[type=link] /usr/lib/libcam.so.1=/proc/boot/libcam.so.1

[type=link] /dev/console=/dev/con1
[type=link] /dev/log = /dev/null
[type=link] /proc/dumper = /dev/null
[type=link] /bin=/proc/boot

libc.so
fpemu.so
libm.so

libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so

libsocket.so

devn-smc9000.so
npm-ttcpip.so
npm-qnet.so

[data=c]
seedres
/sbin/diskboot
/sbin/devc-con
/sbin/devb-fdc
/sbin/devc-pty
/sbin/devb-eide
/sbin/devc-ser8250
/bin/dinit
/sbin/pipe
/sbin/mqueue
/bin/fesh
/bin/mount
/bin/umount
/usr/bin/passwd
/bin/ping
/bin/slay
/bin/ls
/bin/mkdir
/bin/cp
/bin/rm
/bin/mv
/bin/ln

stty
echo
pidin
uname
esh
ls
sleep
nicinfo



cat
ftp
ftpd
if_up

/etc=./fs/etc
/usr/lib/terminfo=./fs/terminfo
ping
telnetd
telnet
login
logout
sh

io-net
fs-nfs2
#/usr/sbin/inetd
tftpd
tftp

–
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/

3

<jclarke@qnx.com> wrote in message news:9dh893$3jd$1@nntp.qnx.com…

It’s probably a size issue, on x86 systems there is a 640KB limit for
your image.

It’s actually closer to 600k on most PC.

This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment out

…
devn-smc9000.so
npm-ttcpip.so
npm-qnet.so
…
io-net
fs-nfs2
inetd
tftpd
tftp


then it will work and the machine will boot. What am I doing wrong?

Thanks…

Miguel.

P.S. 133 MHz PC104, no PCI, floppy + rotating HD.

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] .bootstrap = {
startup-bios -s 64k
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}

the startup script

[+script] .script = {
SYSNAME=nto
TERM=qansi
DL_DEBUG=1

seedres
display_msg Booting Neutrino

EIDE driver

devb-eide blk automount=hd0t79:/hd0 &
waitfor /hd0/usr 30

Start up some consoles

oepn console

devc-con -n4 &
reopen /dev/con1

Some common servers

pipe &
mqueue &
devc-pty &

Start some extra shells on other consoles

reopen /dev/con2
[+session pri=10r] fesh &
reopen /dev/con3
[+session pri=10r] fesh &

Start a high priority shell just in case…

reopen /dev/con4
[+session pri=30r] fesh &

Start the main shell

reopen /dev/con1
[+session pri=10r] fesh &

#floppy drive support
display_msg “Starting the floppy driver”
devb-fdc &
waitfor /dev/fd0 30

display_msg “Mounting filesystem”

mount -tqnx4 /dev/fd0 /fd0
waitfor /fd0 10

}

[type=link] /tmp=/dev/shmem
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so
[type=link] /usr/lib/libcam.so.1=/proc/boot/libcam.so.1

[type=link] /dev/console=/dev/con1
[type=link] /dev/log = /dev/null
[type=link] /proc/dumper = /dev/null
[type=link] /bin=/proc/boot

libc.so
fpemu.so
libm.so

libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so

libsocket.so

devn-smc9000.so
npm-ttcpip.so
npm-qnet.so

[data=c]
seedres
/sbin/diskboot
/sbin/devc-con
/sbin/devb-fdc
/sbin/devc-pty
/sbin/devb-eide
/sbin/devc-ser8250
/bin/dinit
/sbin/pipe
/sbin/mqueue
/bin/fesh
/bin/mount
/bin/umount
/usr/bin/passwd
/bin/ping
/bin/slay
/bin/ls
/bin/mkdir
/bin/cp
/bin/rm
/bin/mv
/bin/ln

stty
echo
pidin
uname
esh
ls
sleep
nicinfo


cat
ftp
ftpd
if_up

/etc=./fs/etc
/usr/lib/terminfo=./fs/terminfo
ping
telnetd
telnet
login
logout
sh

io-net
fs-nfs2
#/usr/sbin/inetd
tftpd
tftp

–
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/

4

Jason…

Thanks. That would explain it.



jclarke@qnx.com wrote:

It’s probably a size issue, on x86 systems there is a 640KB limit for
your image. This should be changed to 3MB after the 6.1 release.

When will this release take place?? :slight_smile: Soon I hope!

Bests…

Miguel.



Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment out

…
devn-smc9000.so
npm-ttcpip.so
npm-qnet.so
…
io-net
fs-nfs2
inetd
tftpd
tftp

then it will work and the machine will boot. What am I doing wrong?

Thanks…

Miguel.

P.S. 133 MHz PC104, no PCI, floppy + rotating HD.

5

does that depend apon [image= being at it’s default of 4M ?

another stage in the boot loader?

Previously, Mario Charest wrote in qdn.public.qnxrtp.os:

jclarke@qnx.com> > wrote in message news:9dh893$3jd$> 1@nntp.qnx.com> …
It’s probably a size issue, on x86 systems there is a 640KB limit for
your image.

It’s actually closer to 600k on most PC.

This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment out

6

“Michael J. Ferrador” <n2kra@orn.com> wrote in message
news:Voyager.010518144655.978978A@aptiva.privateC…

does that depend apon [image= being at it’s default of 4M ?

Not to my knowledge, as a matter of fact, for PC I don’t think

you can specify an address, it has to load in the first meg.

another stage in the boot loader?

Previously, Mario Charest wrote in qdn.public.qnxrtp.os:

jclarke@qnx.com> > wrote in message news:9dh893$3jd$> 1@nntp.qnx.com> …
It’s probably a size issue, on x86 systems there is a 640KB limit for
your image.

It’s actually closer to 600k on most PC.

This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment out

7

I am not sure, but I think the [image=ADDRESS] means that on your
system is the base for the image file system at this address.
If in your system the file at 1 Meg put in 1 Meg.

I am not sure about that I have to take a look, but
I am not right now on neutrino.

–
Bye Sascha( sascha@bitctrl.de )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: sascha@bitctrl.de
WWW: http://www.bitctrl.de


“Mario Charest” <mcharest@antispam_zinformatic.com> schrieb im Newsbeitrag
news:9ee2f3$b70$1@inn.qnx.com…

“Michael J. Ferrador” <> n2kra@orn.com> > wrote in message
news:> Voyager.010518144655.978978A@aptiva.privateC> …
does that depend apon [image= being at it’s default of 4M ?

Not to my knowledge, as a matter of fact, for PC I don’t think
you can specify an address, it has to load in the first meg.

another stage in the boot loader?

Previously, Mario Charest wrote in qdn.public.qnxrtp.os:

jclarke@qnx.com> > wrote in message news:9dh893$3jd$> 1@nntp.qnx.com> …
It’s probably a size issue, on x86 systems there is a 640KB limit
for
your image.

It’s actually closer to 600k on most PC.

This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment out
\

8

news:99b8h3$sd7$1@inn.qnx.com - QNX RTP on 486SX (less than 4Mb)
on qdn.public.qnxrtp.install

4096 - 1024 = 3072K (3M)

although, if someone implements v86 mode / ports DOSEMU
might you want an option of the lower limit at 1088k (first 64k HMA) ?

Sascha Morgenstern <sascha@bitctrl.de> wrote in message
news:9effvm$75m$1@inn.qnx.com…

I am not sure, but I think the [image=ADDRESS] means that on your
system is the base for the image file system at this address.
If in your system the file at 1 Meg put in 1 Meg.

I am not sure about that I have to take a look, but
I am not right now on neutrino.

“Mario Charest” <mcharest@antispam_zinformatic.com> schrieb im Newsbeitrag
news:9ee2f3$b70$> 1@inn.qnx.com> …

“Michael J. Ferrador” <> n2kra@orn.com> > wrote in message
news:> Voyager.010518144655.978978A@aptiva.privateC> …
does that depend apon [image= being at it’s default of 4M ?

Not to my knowledge, as a matter of fact, for PC I don’t think
you can specify an address, it has to load in the first meg.

another stage in the boot loader?

Previously, Mario Charest wrote in qdn.public.qnxrtp.os:

jclarke@qnx.com> > wrote in message news:9dh893$3jd$> 1@nntp.qnx.com> …
It’s probably a size issue, on x86 systems there is a 640KB limit
for
your image.

It’s actually closer to 600k on most PC.

This should be changed to 3MB after the 6.1 release.

Jason

Miguel Simon <> simon@ou.edu> > wrote:
Hi…

The following build file will not boot. However, if I coment
out