The Fsys driver is a driver developed with a tool from Datalight that is
called FlashFX and is used for flashfilesystems.
So I don’t know if you are helped with my boot image build file, but here it
is:
sys/boot
$ boot -v
sys/Proc32
$ Proc32 -p 100 -D
sys/Slib32
$ Slib32
sys/Slib16
$ Slib16
/bin/Fsys
$ Fsys
/bin/Fsys.FxQNX
$ Fsys.FxQNX -w2
/bin/mount
$ mount /dev/rfd0 /
/bin/sinit
$ sinit TERM=qnx
The manual describes to option -w as follows:
“Set the number of seconds to allow Fsys to attach. Set to -w2 for boot.”
Would I really get this kind of behaviour if the Fsys driver wasn’t correctly
started? I didn’t think Fsys driver had anything to do with the reporting of
loaded modules at boot.
I have now tried to boot from floppy with the boot image described above, and
that worked fine. And that means I have a problem with the bios extension that
gives me access to the flashdisk. I will contact Datalight again to try to
resolve the problem.
Thank you
/Göran
In article <9p1quo$2rd$1@inn.qnx.com>, “Ivan Bannon” <ivan.bannon@rjginc.com>
wrote:
When you built the boot image did you use the correct Fsys.xxxx driver and
the
correct parameters? If you could post these and their options used.
“Göran Davidsson” <> goran.davidsson@aerotechtelub.se> > wrote in message
news:9p12sn$h9e$> 1@inn.qnx.com> …
Hello,
What could be wrong if I build a boot image with a working Fsys driver and
it
won’t boot?
If I boot from floppy and use the driver it works fine, but when I try to
boot
from the image it desn’t work. I get the message “Press Esc for alternate
OS.”
and after a second or two I get the usual extra dots, which indicates that
the
boot image is loading if I remember correctly. After that there is
nothing. I
don’t get the list of the modules loaded.
Is there anything I could be missing?
What happens if there is a module in the image that is faulty? Will I see
the
list of loaded modules up to tha faulty one?
Any suggestions are welcome
Best regards
/Göran Davidsson