When I try the automated installation to 144MB DiskOnChip 2000 from the
latest release of QNX4 (the compact disk), Fsys.diskonchip just sits
there until it finally times out. I’m now resorting to using the
M-Systems supplied instructions (Ver. 5.00, Aug. 2001) and DOS utilities
kit (ver. 5.14). Using a hard disk with QNX on it, I can format and
mount the DiskOnChip, copy over needed directories, but when I shutdown
and re-start, the computer won’t boot QNX from the DiskOnChip. I do
remember to disable the hard disk in the BIOS per RTD instructions for
booting from a DiskOnChip. I’ve tried many things, based on the advice
of the M-Systems tech support guy. The M-Systems instruction for
starting with DOS DFORMAT.EXE without any special options beyond /WIN
and /S doesn’t work, so the M-Systems guy thought that the following
procedure would seem my best bet, but it doesn’t work either:
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /EMPTY (latest version from
M-Systems)
Power cycle
Boot QNX from hard disk
dformat (from QNX hard disk, latest version from M-Systems)
Fsys.diskonchip (latest version from M-Systems)
fdisk /dev/tffs0 add -f 1 QNX ALL
fdisk /dev/tffs0 boot QNX
fdisk /dev/tffs0 loader
mount -p /dev/tffs0
dinit -h /dev/tffs0t77
dinit -hb /dev/tffs0t77
mount /dev/tffs0t77 /diskonchip
I copy over ./boot, ./licenses, /etc, /usr, /bin to DiskOnChip
shutdown
Boot from DOS floppy
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /FIRST /NOFORMAT
This last command fails with the following messages:
DiskOnChip 2000 found in 0xd0000.
144 media, 16k unit.
ERROR - not enough binary area marked for EXB.
Error writing EXB.
Status code is 52 (flNoSpaceInVolume) received from flPlaceExbByBuffer.
Format failed.
It’s interesting that if I execute the following two DOS commands, one
right
after the other, the second DFORMAT doesn’t produce any error:
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /EMPTY
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /NOFORMAT
It seems like either the QNX dformat program or fdisk is screwing up the
effects of DFORMAT.EXE /EMPTY.
Does anybody see if I am doing something wrong? M-Systems is out of
ideas
to help me and I’ve tried every variation of the instructions I can
think of. Thanks…
On Tue, 21 Jan 2003 14:55:00 -0600, Matt DeMars <mdemars@facstaff.wisc.edu> wrote:
When I try the automated installation to 144MB DiskOnChip 2000 from the
latest release of QNX4 (the compact disk), Fsys.diskonchip just sits
there until it finally times out. I’m now resorting to using the
M-Systems supplied instructions (Ver. 5.00, Aug. 2001) and DOS utilities
kit (ver. 5.14). Using a hard disk with QNX on it, I can format and
mount the DiskOnChip, copy over needed directories, but when I shutdown
and re-start, the computer won’t boot QNX from the DiskOnChip. I do
remember to disable the hard disk in the BIOS per RTD instructions for
booting from a DiskOnChip. I’ve tried many things, based on the advice
of the M-Systems tech support guy. The M-Systems instruction for
starting with DOS DFORMAT.EXE without any special options beyond /WIN
and /S doesn’t work, so the M-Systems guy thought that the following
procedure would seem my best bet, but it doesn’t work either:
Just an idea:
When the PC boots, does it show the DOC signon messages?
(Just after the POST, just before the boot starts, there
are usually two messages that show that the DOC BIOS
extension have loaded)
Thanks for responding!
Just for the heck of it, I tried booting from the DiskOnChip after doing the QNX
shutdown
command, but before doing the
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /FIRST /NOFORMAT.
There are no messages related to the DOC printed. The system simply hangs when it gets
to
the point where it tries to boot from something. I then boot from DOS floppy, execute
the
DFORMAT.EXE command shown above, I get the errors described in my previous message,
I re-boot again, and still I don’t see any DOC sign-on messages.
I don’t know if this is a hint, but after I do the 3 fdisk commands, I do an
fdisk /dev/tffs0 show
and it shows the start cylinder for the DOC as being “0”. I’m not sure if this is a
problem or not,
since I’m not expert on how the DOC translation takes place.
I tried replacing the fdisk “ALL” option (which doesn’t error) with HALF, TENTH, and
others,
but each one of these causes an fdisk error. I think to use these I have to specify
other parameters
that I don’t feel very comfortable with.
I look forward to any suggestions you might have.
Thanks…
Alex Cellarius wrote:
On Tue, 21 Jan 2003 14:55:00 -0600, Matt DeMars <> mdemars@facstaff.wisc.edu> > wrote:
When I try the automated installation to 144MB DiskOnChip 2000 from the
latest release of QNX4 (the compact disk), Fsys.diskonchip just sits
there until it finally times out. I’m now resorting to using the
M-Systems supplied instructions (Ver. 5.00, Aug. 2001) and DOS utilities
kit (ver. 5.14). Using a hard disk with QNX on it, I can format and
mount the DiskOnChip, copy over needed directories, but when I shutdown
and re-start, the computer won’t boot QNX from the DiskOnChip. I do
remember to disable the hard disk in the BIOS per RTD instructions for
booting from a DiskOnChip. I’ve tried many things, based on the advice
of the M-Systems tech support guy. The M-Systems instruction for
starting with DOS DFORMAT.EXE without any special options beyond /WIN
and /S doesn’t work, so the M-Systems guy thought that the following
procedure would seem my best bet, but it doesn’t work either:
Just an idea:
When the PC boots, does it show the DOC signon messages?
(Just after the POST, just before the boot starts, there
are usually two messages that show that the DOC BIOS
extension have loaded)
On Wed, 22 Jan 2003 09:56:38 -0600, Matt DeMars <mdemars@facstaff.wisc.edu> wrote:
Thanks for responding!
Just for the heck of it, I tried booting from the DiskOnChip after doing the QNX
shutdown
command, but before doing the
DFORMAT.EXE /WIN:D000 /S:DOC514.EXB /FIRST /NOFORMAT.
There are no messages related to the DOC printed. The system simply hangs when it gets
to
the point where it tries to boot from something. I then boot from DOS floppy, execute
the
DFORMAT.EXE command shown above, I get the errors described in my previous message,
I re-boot again, and still I don’t see any DOC sign-on messages.
Get another DOC that hasn’t been formatted and try it.
If you still don’t see any sign-on messages, the problem
is almost certainly not the DOC but the socket, e.g. the
BIOS is not scanning the socket’s memory area for extension,
or there is a conflict of the memory area, or some
BIOS setting.
I’m sure if you tell RTD you don’t see the sign-on message
they should be able to help.