Anyone had any luck getting QNX booting on a IGS Industrial grade 40 pin IDE
Flash Disk Module or similar?
http://www.logicsupply.com/product_info.php/cPath/44/products_id/510
We can install and read/write files to it using a boot CD but it won’t boot
on it’s own (gets through the hit any key for alternate OS… but
crashes with invalid licence message with a bunch of bad characters after
that). Tried the eide and ide drivers with basic settings. Any ideas?
Thanks.
–
Allan Williams
“Al Williams” <sysadm@harding.ca> wrote in message
news:ep8fec$9q3$1@inn.qnx.com…
Anyone had any luck getting QNX booting on a IGS Industrial grade 40 pin
IDE Flash Disk Module or similar?
We use m-system 2Gig IDE Flash disk module, no problem so far. We are using
Fsys.atapi though.
http://www.logicsupply.com/product_info.php/cPath/44/products_id/510
We can install and read/write files to it using a boot CD but it won’t
boot on it’s own (gets through the hit any key for alternate OS…
but crashes with invalid licence message with a bunch of bad characters
after that). Tried the eide and ide drivers with basic settings. Any
ideas?Thanks.
–
Allan Williams
\
We tried that one as well - same result.
What version of the driver?
What sort of command line options are you using with it?
–
Allan Williams
“Mario Charest” root@127.0.0.1 wrote in message
news:ep9h3f$lf$1@inn.qnx.com…
“Al Williams” <> sysadm@harding.ca> > wrote in message
news:ep8fec$9q3$> 1@inn.qnx.com> …
Anyone had any luck getting QNX booting on a IGS Industrial grade 40 pin
IDE Flash Disk Module or similar?
We use m-system 2Gig IDE Flash disk module, no problem so far. We are
using Fsys.atapi though.http://www.logicsupply.com/product_info.php/cPath/44/products_id/510
We can install and read/write files to it using a boot CD but it won’t
boot on it’s own (gets through the hit any key for alternate OS…
but crashes with invalid licence message with a bunch of bad characters
after that). Tried the eide and ide drivers with basic settings. Any
ideas?Thanks.
–
Allan Williams
\
We’ve been booting off flash drives for years now… and mounting a SCSI
RAID array as the root file system. Works great.
What are you mounting as your root file system? The flash or some other
device, like say a hard drive. Whatever it is, you need to have at
least a .licenses file or /etc/licenses dir with enough valid licenses
to account for your node number e.g. if node # is 5 you’ll need at least
5 OS licenses.
-Rob
Al Williams wrote:
We tried that one as well - same result.
What version of the driver?
What sort of command line options are you using with it?
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?
We are using EIDE hard drives but we wanted to replace them with these FLASH
drives for reliability reasons. Maybe it’s this brand that doesn’t work
although we tried it with DOS and it boots OK.
–
Allan Williams
“Rob Hem” <rob@spamyourself.com> wrote in message
news:epalfg$odd$1@inn.qnx.com…
We’ve been booting off flash drives for years now… and mounting a SCSI
RAID array as the root file system. Works great.What are you mounting as your root file system? The flash or some other
device, like say a hard drive. Whatever it is, you need to have at least
a .licenses file or /etc/licenses dir with enough valid licenses to
account for your node number e.g. if node # is 5 you’ll need at least 5 OS
licenses.-Rob
Al Williams wrote:
We tried that one as well - same result.What version of the driver?
What sort of command line options are you using with it?
We’ve used several different relatively small (32M, 64M & 128M) ide
flash drives (I don’t recall the brand off hand). All that is ever on
them is the .boot and .altboot files. We’re just using Fsys.eide with
no explicit options set.
How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.
Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:
sys/boot
$ boot -v
sys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -D
sys/Slib32
$ Slib32
sys/Slib16
$ Slib16
/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)
/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)
/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 /
/bin/sinit
$ sinit TERM=qnx
-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these FLASH
drives for reliability reasons. Maybe it’s this brand that doesn’t work
although we tried it with DOS and it boots OK.
Fsys.eide works okay for us too. Rob is no doubt right that its something to
do with the size of the partition (we have only tested up to 128M - 1G is a
bit pricey still).
Fsys.atapi was less successfull for us. I guess different brands react in
different ways.
I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.
Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit 
anyone managed to boot from a USB 2.0 device?
“Rob Hem” <rob@spamyourself.com> wrote in message
news:epdavn$j5l$1@inn.qnx.com…
We’ve used several different relatively small (32M, 64M & 128M) ide flash
drives (I don’t recall the brand off hand). All that is ever on them is
the .boot and .altboot files. We’re just using Fsys.eide with no explicit
options set.How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that doesn’t
work although we tried it with DOS and it boots OK.
Hello,
Are you sure that yours IDE flash drive is OK? What’s about BIOS settings for
this drive?
Can you check an another model/another manufacturer? We use Transcend DOMs
(DiskOnModule) and M-Systems iDOCs without problem in QNX 4 and QNX 6.
Regards,
Igor.
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these FLASH
drives for reliability reasons. Maybe it’s this brand that doesn’t work
although we tried it with DOS and it boots OK.
Got it to work. It ended up not being an issue with the FLASH drive but an
issue with the motherboard. Boots no problem with our original
configuration (eide driver).
Now I just need to figure out how to determine how often we are writing to
the drive to make sure we won’t wear it out. We do some logging to disk on
this system…
Thanks for all the responses.
–
Allan Williams
“Igor Mazanov” <i.mazanov@swd.ru> wrote in message
news:epktag$kfn$1@inn.qnx.com…
Hello,
Are you sure that yours IDE flash drive is OK? What’s about BIOS settings
for this drive?Can you check an another model/another manufacturer? We use Transcend DOMs
(DiskOnModule) and M-Systems iDOCs without problem in QNX 4 and QNX 6.Regards,
Igor.Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that doesn’t
work although we tried it with DOS and it boots OK.
You can boot from a USB stick? Does that require special motherboard
support? We haven’t played with any of the USB stuff with QNX 4…
(PS: Solved my original issue, it was the MB)
–
Allan Williams
“Darel Cullen” <nospam-darelj@gmail.com> wrote in message
news:epkof3$hn0$1@inn.qnx.com…
Fsys.eide works okay for us too. Rob is no doubt right that its something
to do with the size of the partition (we have only tested up to 128M - 1G
is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react in
different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide flash
drives (I don’t recall the brand off hand). All that is ever on them is
the .boot and .altboot files. We’re just using Fsys.eide with no
explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
“Al Williams” <sysadm@harding.ca> wrote in message
news:epo165$o29$1@inn.qnx.com…
Got it to work. It ended up not being an issue with the FLASH drive but
an issue with the motherboard. Boots no problem with our original
configuration (eide driver).Now I just need to figure out how to determine how often we are writing to
the drive to make sure we won’t wear it out. We do some logging to disk
on this system…
I really doubt you have to worry about that. IDE flash disk (the good ones)
uses wear leveling. Calculating how much time a single sector is erased is
close to impossible since you don’t know how the flash disk handles it. The
trick in general though is to not keep the disk at full capacity to leave as
much “free sector” as possible. It’s not then number of write but the
number of erase cycles that counts. For example if you fill the hardisk
then delete the file and fill it again that counts a 1 erase cycle.
Thanks for all the responses.
–
Allan Williams
“Igor Mazanov” <> i.mazanov@swd.ru> > wrote in message
news:epktag$kfn$> 1@inn.qnx.com> …
Hello,Are you sure that yours IDE flash drive is OK? What’s about BIOS settings
for this drive?Can you check an another model/another manufacturer? We use Transcend
DOMs (DiskOnModule) and M-Systems iDOCs without problem in QNX 4 and QNX
6.Regards,
Igor.Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
\
As far as I remember, there were some topics about wear leveling on the QNX
newsgroups. The following link is from there,
http://www.sandisk.com/Assets/File/OEM/WhitePapersAndBrochures/RS-MMC/WPaperWearLevelv1.0.pdf
Probably, that’s all what you’re looking for.
Regards,
Igor.
Al Williams wrote:
Got it to work. It ended up not being an issue with the FLASH drive but an
issue with the motherboard. Boots no problem with our original
configuration (eide driver).Now I just need to figure out how to determine how often we are writing to
the drive to make sure we won’t wear it out. We do some logging to disk on
this system…Thanks for all the responses.
Hi.
Is it possible to boot with a USB stick?
TIA
Augie
“Darel Cullen” <nospam-darelj@gmail.com> wrote in message
news:epkof3$hn0$1@inn.qnx.com…
Fsys.eide works okay for us too. Rob is no doubt right that its something
to do with the size of the partition (we have only tested up to 128M - 1G
is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react in
different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide flash
drives (I don’t recall the brand off hand). All that is ever on them is
the .boot and .altboot files. We’re just using Fsys.eide with no
explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did you
use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
“Augie” <augiehenriques@hotmail.com> wrote in message
news:epsqrp$2rg$1@inn.qnx.com…
Hi.
Is it possible to boot with a USB stick?
Never tried it but in theory yes. I jsut wonder if there is enough room in
the image (640k limit) to put all the required software.
TIA
Augie
“Darel Cullen” <> nospam-darelj@gmail.com> > wrote in message
news:epkof3$hn0$> 1@inn.qnx.com> …
Fsys.eide works okay for us too. Rob is no doubt right that its something
to do with the size of the partition (we have only tested up to 128M - 1G
is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react in
different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide
flash drives (I don’t recall the brand off hand). All that is ever on
them is the .boot and .altboot files. We’re just using Fsys.eide with
no explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did
you use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
\
Mario,
Thanks for the reply.
I don’t recall a BIOS option to BOOT from USB.
How is this possible?
I have several USB sticks with QNX 4.
Augie
“Mario Charest” root@127.0.0.1 wrote in message
news:eptqgp$mo4$1@inn.qnx.com…
“Augie” <> augiehenriques@hotmail.com> > wrote in message
news:epsqrp$2rg$> 1@inn.qnx.com> …
Hi.Is it possible to boot with a USB stick?
Never tried it but in theory yes. I jsut wonder if there is enough room
in the image (640k limit) to put all the required software.
TIAAugie
“Darel Cullen” <> nospam-darelj@gmail.com> > wrote in message
news:epkof3$hn0$> 1@inn.qnx.com> …
Fsys.eide works okay for us too. Rob is no doubt right that its
something to do with the size of the partition (we have only tested up
to 128M - 1G is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react
in different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide
flash drives (I don’t recall the brand off hand). All that is ever on
them is the .boot and .altboot files. We’re just using Fsys.eide with
no explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to
partition it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what
our build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did
you use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
\
“Augie” <augiehenriques@hotmail.com> wrote in message
news:epvb4s$ojh$1@inn.qnx.com…
Mario,
Thanks for the reply.
I don’t recall a BIOS option to BOOT from USB.
That’s the first think you’ll need 
How is this possible?
Create an boot file that contains io-usb and Fsys.umass, instead of
Fsys.eide (you’ll still need Fsys though).
I have several USB sticks with QNX 4.
Augie
“Mario Charest” root@127.0.0.1 wrote in message
news:eptqgp$mo4$> 1@inn.qnx.com> …“Augie” <> augiehenriques@hotmail.com> > wrote in message
news:epsqrp$2rg$> 1@inn.qnx.com> …
Hi.Is it possible to boot with a USB stick?
Never tried it but in theory yes. I jsut wonder if there is enough room
in the image (640k limit) to put all the required software.
TIAAugie
“Darel Cullen” <> nospam-darelj@gmail.com> > wrote in message
news:epkof3$hn0$> 1@inn.qnx.com> …
Fsys.eide works okay for us too. Rob is no doubt right that its
something to do with the size of the partition (we have only tested up
to 128M - 1G is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react
in different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide
flash drives (I don’t recall the brand off hand). All that is ever on
them is the .boot and .altboot files. We’re just using Fsys.eide with
no explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to
partition it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what
our build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did
you use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with
these FLASH drives for reliability reasons. Maybe it’s this brand
that doesn’t work although we tried it with DOS and it boots OK.
\
Hi Al,
No special motherboard support required, although we only seemed to manage
to boot from V1 USB and not V2 USB for some reason (bug in either driver or
MB i guess, MB had both types).
“Al Williams” <sysadm@harding.ca> wrote in message
news:epo19o$o9k$1@inn.qnx.com…
You can boot from a USB stick? Does that require special motherboard
support? We haven’t played with any of the USB stuff with QNX 4…(PS: Solved my original issue, it was the MB)
–
Allan Williams
“Darel Cullen” <> nospam-darelj@gmail.com> > wrote in message
news:epkof3$hn0$> 1@inn.qnx.com> …
Fsys.eide works okay for us too. Rob is no doubt right that its something
to do with the size of the partition (we have only tested up to 128M - 1G
is a bit pricey still).Fsys.atapi was less successfull for us. I guess different brands react in
different ways.I recommend steering clear of Fsys.atapi as a non-boot filesystem, it
doesn’t work will with certain IDE emulation schemes by many new
motherboards.Booting from USB (V1.0) seems to work just fine too with no obvious
performance hit >“Rob Hem” <> rob@spamyourself.com> > wrote in message
news:epdavn$j5l$> 1@inn.qnx.com> …
We’ve used several different relatively small (32M, 64M & 128M) ide
flash drives (I don’t recall the brand off hand). All that is ever on
them is the .boot and .altboot files. We’re just using Fsys.eide with
no explicit options set.How big is your flash drive? If it’s >= 1G, maybe you need to partition
it with a relatively small 120M or so root file system.Also wierd things happen if your .boot file is too big. Here’s what our
build file looks like:sys/boot
$ boot -vsys/Proc32
$ Proc32 -l $(lnode) $(local) -p 1500 -t 300 -Dsys/Slib32
$ Slib32sys/Slib16
$ Slib16/bin/Fsys
$ Fsys $(fsys_opts) -Hdisk$(fsys_gig)/bin/$(fsys_driver)
$ $(fsys_driver) $(fsys_driver_opts)/bin/mount
$ mount -p/dev/hd0 /dev/hd0t77 //bin/sinit
$ sinit TERM=qnx-Rob
Al Williams wrote:
The FLASH drive is the (only) root file system and it is node 1. The
licence file is there as well. It seems to be crashing - a bunch of
gibberish characters after the licence file error. Which driver did
you use? Any special parameters? What type of flash drive?We are using EIDE hard drives but we wanted to replace them with these
FLASH drives for reliability reasons. Maybe it’s this brand that
doesn’t work although we tried it with DOS and it boots OK.
\