We are currently manufacturing a PC based product under QNX 4 that uses
a disk on module (DOM).
On a couple occasions, the system would not boot. Further investigation
found that the .boot file was corrupt. Recopying it to the DOM
corrected the problem. I thought that one of the advantages of using
QNX over a windows OS was to reduce the occurrances of such items.
If anyone has had a similar experience, or has any information with
regard to this, it is greatly appreciated.
We are currently manufacturing a PC based product under QNX 4 that uses
a disk on module (DOM).
On a couple occasions, the system would not boot. Further investigation
found that the .boot file was corrupt. Recopying it to the DOM
corrected the problem. I thought that one of the advantages of using
QNX over a windows OS was to reduce the occurrances of such items.
If anyone has had a similar experience, or has any information with
regard to this, it is greatly appreciated.
I’m trying to investigate something similar but not exactly the same. I’m
using Advantech PC/104 with CompactFlash. After power off, the file that was
last opened for writing (and then close) is corrupted (no matter how long I
wait after writing the file before switching the power off). I have disabled
the Fsys cache but this didn’t change anything. One more thing: this happens
on 486 but not on Pentium with the same CF card.
I didn’t use DOM but did use PCFD and DOC many times and never had such
experience (well, of course the hardware were different and they had their own
Fsys.* drivers).
Regards,
Greg Wrobel
wrobel@no-spam.zdania.com.pl Experimental Department of Scientific
phone: (+48 12) 617-2883 Equipment and Automation
fax: (+48 12) 634-2205 30-059 Krakow, al.Mickiewicza 30, Poland
I’m trying to investigate something similar but not exactly the same. I’m
using Advantech PC/104 with CompactFlash. After power off, the file that was
last opened for writing (and then close) is corrupted (no matter how long I
wait after writing the file before switching the power off). I have disabled
the Fsys cache but this didn’t change anything. One more thing: this happens
on 486 but not on Pentium with the same CF card.
Something similiar here, too:
Some of the latest written files were complety corrupted, though we
used some 'sync’s and ‘sleep’ before a regular shutdown.
We are using PC/104-boards with 16..32MB CompactFlash.
But our problems seemed to disappear after we modified the
Fsys call in our boot images to
“Fsys -c0M -A”
In fact we never analyzed , whether the disabling of the cache
or the ‘-A’ option did the trick.