Sorry for the long pause in this thread. I’ve been tied up with a few
details (shipping a release, etc) and just recently got back to my DOM
Could you try the following:
Use a dos formatted floppy, then run the makedisk util with the destination
drive and the file “cf_dsk.nto”.
Then using that disk boot a system and use the driver Fsys.eide and
the dinit util on the disk to dinit the DOM.
If you have a QNX4 system handy you can use that instead.
As I mentioned in my previous response to this thread, I do not run
either DOS or Windows. So, that’s no good. I have a QNX4 system on one
partition, but it was installed when I was using a different machine and
I cannot get it to boot on the machine I now use, so that’s out.
Also another few things to try:
When creating the partition, try creating it 1 block smaller than the entire
or better yet try 1/2 the size of the disk and see if that still exibits the
Is DMA running on the DOM? If so try turning it off in the BIOS and make
the eide driver doesn’t start DMA.
What happens if you init the DOM, then copy a file to it, then copy the
exact same file
back. Is there a difference in the size of the file? or anything else (try
This I can do. In fact, I’ve been able to jury rig a 6.1 setup on my
test machine. Namely, I set up the DOM, master, and a CD-ROM, slave, on
the primary IDE bus and a CompactFlash on the secondary IDE bus. I boot
from a 6.1 CD in the CD-ROM drive. The software I eventually want to
install on the DOM lives on the CompactFlash.
With this setup, I ran 6.1’s fdisk on the DOM, making the partition 10
blocks smaller than the capacity of the DOM (the DOM has 500 blocks, I
made the partition 490 blocks). After restarting the system (from the CD
again), I ran 6.1’s dinit on the DOM. dinit told me it was using the
floppy loader, so I used ‘dinit -h -B /dev/hd0t77’
to initialize the DOM.
From that point, restarting the system no longer caused chkfsys to
report errors on the DOM.
I then installed my software, copying it from the CompactFlash to the
DOM. I double checked everything to make sure the software came over
correctly (including the all-important .boot file). When I boot from the
DOM, I now get different behavior from before, although it still doesn’t
Boot Partition 4 ? 4
Hit Esc for .altboot…[lots of periods]
After this point, the system spontaneously reboots. Previously, the
system just hung here.
After three or four iterations of print-reboot, print-reboot. I got a
new message after the periods:
could not allocate 0xe1d180d8 bytes for syspage/cpupage
That seems like an excessive amount of memory to allocate (particularly
since there’s only 64MB RAM in this little tyke).
I don’t know whether to call this an improvement or not. It’s still not
working, but we’re getting different, possibly more traceable, behavior.
Where shall we go from here?
Thanks in advance.