Hi,
I’m trying to make a Neutrino 2.0 image on a floppy disk with TCP/IP
network and a QNX filesystem (using the Neutrino 2.0 sdk on Windows98).
I’ve implemented both separatly and it works correctly but when i want to
put
them in a single buildfile, the boot doesn’t start anymore.
Searching why, i observed that each time my image contains more than 600ko,
the boot can’t work.
Is there a limitation of data on a floppy disk that makes the boot image
unusable??? Why???
Does this constraint appear when we make an image on hard disk ?
Thanks for any responses.
Vincent
vcelerier@logisonic.fr
The boot image can only be so big before the BIOS chokes on it. One option
is to build a smaller boot image with just the console & floppy drivers on
it, then run the disk & network drivers from the (mounted) floppy. Are you
specifying the +compress flag in your build file? That would make a
difference, and perhaps allow everything to fit in the image…
-Warren
“Vincent Celerier” <vcelerier@logisonic.fr> wrote in message
news:8v380r$fid$1@inn.qnx.com…
Hi,
I’m trying to make a Neutrino 2.0 image on a floppy disk with TCP/IP
network and a QNX filesystem (using the Neutrino 2.0 sdk on Windows98).
I’ve implemented both separatly and it works correctly but when i want to
put
them in a single buildfile, the boot doesn’t start anymore.
Searching why, i observed that each time my image contains more than
600ko,
the boot can’t work.
Is there a limitation of data on a floppy disk that makes the boot image
unusable??? Why???
Does this constraint appear when we make an image on hard disk ?
Thanks for any responses.
Vincent
vcelerier@logisonic.fr
\
I have already specified the +compress option but i think
the insertion of the libraries for network and filesystem
make the image bigger than 600ko.
this is a part of my buildfile:
[virtual=x86,bios +compress] boot = {
startup-bios -s 64k
PATH=/proc/boot:/bin:/usr/bin
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib procnto
}
I have tried the manip. you advise but i didn’t manage
to automount the floppy disk with devb-fdc (and of course
the command mount doesn’t want to work when i insert it
in the buildfile after the [data=copy] option).
Vincent
Warren Peece <Warren@nospam.com> a écrit dans le message :
8v3fuu$mv1$1@inn.qnx.com…
The boot image can only be so big before the BIOS chokes on it. One
option
is to build a smaller boot image with just the console & floppy drivers on
it, then run the disk & network drivers from the (mounted) floppy. Are
you
specifying the +compress flag in your build file? That would make a
difference, and perhaps allow everything to fit in the image…
-Warren
“Vincent Celerier” <> vcelerier@logisonic.fr> > wrote in message
news:8v380r$fid$> 1@inn.qnx.com> …
Hi,
I’m trying to make a Neutrino 2.0 image on a floppy disk with TCP/IP
network and a QNX filesystem (using the Neutrino 2.0 sdk on Windows98).
I’ve implemented both separatly and it works correctly but when i want
to
put
them in a single buildfile, the boot doesn’t start anymore.
Searching why, i observed that each time my image contains more than
600ko,
the boot can’t work.
Is there a limitation of data on a floppy disk that makes the boot image
unusable??? Why???
Does this constraint appear when we make an image on hard disk ?
Thanks for any responses.
Vincent
vcelerier@logisonic.fr
\
“Vincent Celerier” <vcelerier@logisonic.fr> wrote in message
news:8v3ndv$132$1@inn.qnx.com…
| I have already specified the +compress option but i think
| the insertion of the libraries for network and filesystem
| make the image bigger than 600ko.
Well if you’re including a filesystem driver, then why not just boot from the
disk, and run your network stuff from there like everyone else does? To
rephrase, why is it necessary to get all of this onto a floppy disk? Usually
people don’t bother with that sort of thing unless they’ve got a diskless
workstation to support.
| this is a part of my buildfile:
| [virtual=x86,bios +compress] boot = {
| startup-bios -s 64k
| PATH=/proc/boot:/bin:/usr/bin
| LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib procnto
| }
| I have tried the manip. you advise but i didn’t manage
| to automount the floppy disk with devb-fdc (and of course
| the command mount doesn’t want to work when i insert it
| in the buildfile after the [data=copy] option).
|
| Vincent
If you’ve got a hard drive that you can mount and you’d rather run the network
stuff from a floppy (which would be strange), check out devb-fdc and io-blk.so
in the helpviewer. I think the auto= partition thingie under io-blk.so is what
you would need to auto-mount the floppy.
-Warren
Thanks for the help…
I didn’t manage to make an image under the hard disk, that’s the reason why
i would have liked to boot with a floppy disk.However the automount of the
floppy still doesn’t work, although i inserted the io-blk.so library.
I type manually the command debv-fdc blk automount=fd0:/floppy & but i have
no /floppy on my tree (but it creates a fd0 under /dev) so i can’t access
the floppy . I 'm starting sincerely to despair…
Vincent.
Warren Peece <warren@nospam.com> a écrit dans le message :
8v6q28$15v$1@inn.qnx.com…
“Vincent Celerier” <> vcelerier@logisonic.fr> > wrote in message
news:8v3ndv$132$> 1@inn.qnx.com> …
| I have already specified the +compress option but i think
| the insertion of the libraries for network and filesystem
| make the image bigger than 600ko.
Well if you’re including a filesystem driver, then why not just boot from
the
disk, and run your network stuff from there like everyone else does? To
rephrase, why is it necessary to get all of this onto a floppy disk?
Usually
people don’t bother with that sort of thing unless they’ve got a diskless
workstation to support.
| this is a part of my buildfile:
| [virtual=x86,bios +compress] boot = {
| startup-bios -s 64k
| PATH=/proc/boot:/bin:/usr/bin
| LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib procnto
| }
| I have tried the manip. you advise but i didn’t manage
| to automount the floppy disk with devb-fdc (and of course
| the command mount doesn’t want to work when i insert it
| in the buildfile after the [data=copy] option).
|
| Vincent
If you’ve got a hard drive that you can mount and you’d rather run the
network
stuff from a floppy (which would be strange), check out devb-fdc and
io-blk.so
in the helpviewer. I think the auto= partition thingie under io-blk.so is
what
you would need to auto-mount the floppy.
-Warren
I think at this point, your best option is to resolve why you can’t boot from
your hard disk- As long as you’ve got an IDE drive, it’s supposed to work.
Perhaps something simple went wrong during the installation…
“Vincent Celerier” <vcelerier@logisonic.fr> wrote in message
news:8vggb9$mr5$1@inn.qnx.com…
| Thanks for the help…
|
| I didn’t manage to make an image under the hard disk, that’s the reason why
| i would have liked to boot with a floppy disk.However the automount of the
| floppy still doesn’t work, although i inserted the io-blk.so library.
| I type manually the command debv-fdc blk automount=fd0:/floppy & but i have
| no /floppy on my tree (but it creates a fd0 under /dev) so i can’t access
| the floppy . I 'm starting sincerely to despair…
|
| Vincent.
|
|
| Warren Peece <warren@nospam.com> a écrit dans le message :
| 8v6q28$15v$1@inn.qnx.com…
| > “Vincent Celerier” <vcelerier@logisonic.fr> wrote in message
| > news:8v3ndv$132$1@inn.qnx.com…
| > | I have already specified the +compress option but i think
| > | the insertion of the libraries for network and filesystem
| > | make the image bigger than 600ko.
| >
| > Well if you’re including a filesystem driver, then why not just boot from
| the
| > disk, and run your network stuff from there like everyone else does? To
| > rephrase, why is it necessary to get all of this onto a floppy disk?
| Usually
| > people don’t bother with that sort of thing unless they’ve got a diskless
| > workstation to support.
| >
| > | this is a part of my buildfile:
| > | [virtual=x86,bios +compress] boot = {
| > | startup-bios -s 64k
| > | PATH=/proc/boot:/bin:/usr/bin
| > | LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib procnto
| > | }
| > | I have tried the manip. you advise but i didn’t manage
| > | to automount the floppy disk with devb-fdc (and of course
| > | the command mount doesn’t want to work when i insert it
| > | in the buildfile after the [data=copy] option).
| > |
| > | Vincent
| >
| > If you’ve got a hard drive that you can mount and you’d rather run the
| network
| > stuff from a floppy (which would be strange), check out devb-fdc and
| io-blk.so
| > in the helpviewer. I think the auto= partition thingie under io-blk.so is
| what
| > you would need to auto-mount the floppy.
| >
| > -Warren
| >
| >
| >
|
|
Vincent Celerier <vcelerier@logisonic.fr> wrote:
: Thanks for the help…
: I didn’t manage to make an image under the hard disk, that’s the reason why
: i would have liked to boot with a floppy disk.However the automount of the
: floppy still doesn’t work, although i inserted the io-blk.so library.
: I type manually the command debv-fdc blk automount=fd0:/floppy & but i have
: no /floppy on my tree (but it creates a fd0 under /dev) so i can’t access
: the floppy . I 'm starting sincerely to despair…
: Vincent.
Can you please post your entire boot file so that I could try it
out here? You may just be missing a couple of pieces…
Peter
Peter Martin <peterm@qnx.com> a écrit dans le message :
8vtv0j$6ub$1@nntp.qnx.com…
Vincent Celerier <> vcelerier@logisonic.fr> > wrote:
: Thanks for the help…
: I didn’t manage to make an image under the hard disk, that’s the reason
why
: i would have liked to boot with a floppy disk.However the automount of
the
: floppy still doesn’t work, although i inserted the io-blk.so library.
: I type manually the command debv-fdc blk automount=fd0:/floppy & but i
have
: no /floppy on my tree (but it creates a fd0 under /dev) so i can’t
access
: the floppy . I 'm starting sincerely to despair…
: Vincent.
Can you please post your entire boot file so that I could try it
out here? You may just be missing a couple of pieces…
Peter
Hi Peter,
First i must precise i’m developing a neutrino system with the SDK 2.0 C on
a Windows 98 host ('cause i want to use CodeWarrior). So i was suprised to
discover that the command mount was not provided with the rest of the exe. I
decided to copy mount from an existing QNX RTP I previously installed but it
seems to be in trouble as i have
error messages when i use it
Here is the script part of my buildfile:
[+script] startup.script = {
start up some consoles
devc-con -n4 &
reopen /dev/con1
display_msg Welcome to Neutrino on a PC-compatible BIOS system.
Pci slots scrutation
pci-bios &
waitfor /dev/pci
Disk drivers
devb-eide blk automount=hd0t79:/hd0p1 &
devb-fdc verbose blk cache=128k automount=fd0:/fd0 &
#devb-fdc blk auto=partition &
#devb-fdc blk automount=+fd0:/a /dos:dos,automount=+fd0:/fd:qnx4 &
Some common servers
pipe &
mqueue &
devc-pty &
Start a debug server for debugging programs with CodeWarrior
waitfor /dev/ser1
[+session] pdebug 8000 /dev/ser1 &
These env variables inherited by all the programs which follow
SYSNAME=nto
TERM=qainsi
Start the main shell
reopen /dev/con1
[+session] sh
}
Of course I put the appropriate .so :
Include the hard disk files so we can access files on the disk
libcam.so.1
[type=link] /usr/lib/libcam.so.1=/proc/boot/libcam.so.1
io-blk.so
[type=link] /usr/lib/io-blk.so.1=/proc/boot/io-blk.so
filesystem required shared libs
cam-disk.so
fs-qnx4.so
I have tried all the lines about devb-fdc but each one doesn’t work
correctly.
Any suggestions??? Thanks per advance…