Instead of getting the normal string of .'s from the boot loader, I am now
getting a string (never ending) of ?'s. What does this indicate?
BTW this is happening on a newly programmed M-Sys DOC, other DOC’s
programmed in the same fashion are working fine.
TIA
Gregory Fedor <gfedor@grc.nasa.gov> wrote:
: Instead of getting the normal string of .'s from the boot loader, I am now
: getting a string (never ending) of ?'s. What does this indicate?
The ? marks indicate the image cannot be found. Are the disk translations
reported by fdisk the same as those which the BIOS reports?
Chris
: BTW this is happening on a newly programmed M-Sys DOC, other DOC’s
: programmed in the same fashion are working fine.
: TIA
Gregory Fedor <gfedor@grc.nasa.gov> wrote:
Instead of getting the normal string of .'s from the boot loader, I am now
getting a string (never ending) of ?'s. What does this indicate?
Failure to read a block from the device.
-David
BTW this is happening on a newly programmed M-Sys DOC, other DOC’s
programmed in the same fashion are working fine.TIA
David Gibbs <dagibbs@qnx.com> wrote:
: Gregory Fedor <gfedor@grc.nasa.gov> wrote:
:> Instead of getting the normal string of .'s from the boot loader, I am now
:> getting a string (never ending) of ?'s. What does this indicate?
Also not having an image will cause this. (i.e. the size of .boot is 0)
: Failure to read a block from the device.
: -David
:> BTW this is happening on a newly programmed M-Sys DOC, other DOC’s
:> programmed in the same fashion are working fine.
:> TIA