I appolgise for sounding rude, but may I ask, do you actually fully
understand the content of what you posted, or have I mis-interpreted your
reason for posting?
.....ok. So the BIOS is involved in booting up a computer full stop.
Absolutely.
What I meant when I said:
<quote>
'And the issue here is nothing whatsoever to do with the BIOS.'
<end quote>
is not that booting up a computer, regardless of operating system or fault,
does not rely on the BIOS.
What I did say, I thought resonably clearly, is that the problem being had
by Dimetric Houston, is in no way related to a problem with the bios. (ie
the ISSUE HERE is nothing whatsoever to do with the BIOS). The BIOS, from
the fact that it was able, after running through POST's, to 'execute a
program in the first two disk sectors', which in turn was able to produce
valid error message, would appear to be perfectly fine, and to have no
issues.
As you quite rightly say, the issue is somewhere around the first two disk
sectors, or boot loader, or bootable floppy, or corrupt files etc.. And in
fact implies quite clearly, that THE ISSUE HERE IS (as in the case shown by
Dimetric Houston) to do with one of the above, and in fact, NOTHING
WHATSOEVER TO DO WITH THE BIOS. And so, the statement 'Right. Your bios has
no clue re: OS messages' is not only in support of an incorrect statement,
but also is completely irrelevant, and is also wrong in it's implication, as
it implies that the message seen on screen (relating to NT Loader) is a BIOS
message, when as you quite rightly quote <quote> Above are
the Microsoft error messages from the boot sector program. <end quote> the
message seen, is in fact, you guessed it, NOTHING WHATSOEVER TO DO WITH
THE BIOS!
I can see you are perhaps intelligent and well read, but perhaps you need to
read more carefully, and then think more about the implications of what you
have read, as I believe you have misunderstood the statement made by myself
in my previous post, and appear to have misunderstood the implications of
your own post.
Cheers.
L;ozT.............again!
"w_tom" <> wrote in message
news:...
> A program in first two disk sectors gets executed by BIOS.
> This boot program is uniquely modified both for that disk and
> for the operating system that formatted that disk. If that
> boot program does not exist, then BIOS outputs a unique
> message (from hardware manufacturer) about not finding
> bootable disks.
>
> If that program does exist and is for DOS based systems (ie
> Windows 9x), then the boot program looks for the files IO.SYS
> and either MSDOS.SYS or IBMDOS.SYS. These OS booting programs
> are different from the boot sector program and are next
> software to be executed. If boot program does not find these
> files only on that one disk, then this message is output:
>
> Non-System disk or disk error
> Replace and press any key when ready
>
> However if the boot sector is for NT based OS and if the
> unique parameters in that boot sector program do not find an
> NTLDR file, then this message outputs:
>
> BOOT: Couldn't find NTLDR
>
> If a boot diskette is formatted originally by NT, and if
> NTLDR is not on that diskette, then it will boot the latter
> message. If the NTLDR file is missing on hard drive and if
> the BIOS executes boot sector on hard drive, then system will
> output same message. To get this message, the boot sector
> program must have either of two problems:
> 1) the boot sector program is not unique to the disk format,
> or
> 2) the boot file (NTLDR or MSDOS.SYS, etc) is not on that
> disk.
>
> Diskettes not loaded to boot an operating system can still
> contain the boot sector program. Which message is posted can
> tell whether the diskette was formatted by DOS based or NT
> based OS. If the boot sector program is not read, then BIOS
> will output a unique message not from Microsoft. Above are
> the Microsoft error messages from the boot sector program.
>
>
> "L;ozT" wrote:
> > Actually, I would beg to differ. As would the author of the
> > webpage listed by Mark Mandel in the same thread.
> >
> > Link : www.computerhope.com/issues/ch000465.htm
> >
> > Specific points to note
> >
> > [snip]
> > Issue:
> >
> > NTLDR is Missing.
> >
> > Related errors:
> >
> > Below are the full error messages that may be seen when the
> > computer is booting.
> >
> > NTLDR is Missing
> > Press any key to restart
> >
> > Boot: Couldn't find NTLDR
> > Please insert another disk
> >
> > [snip]
> >
> > Cause:
> >
> > 1.. Computer is booting from a non-bootable source
> > [snip]
> >
> > Solutions:
> >
> > Computer is booting from a non-bootable source
> >
> > Many times this error is caused when the computer is attempting
> > to boot from a non-bootable floppy disk or CD-ROM. First verify
> > that no floppy diskette is in the computer, unless you are
> > attempting to boot from a diskette.
> >
> > [snip]
> >
> > As per comments from Plato, and Thor, quite simply, you are wrong.
The
> > precise nature of a fault may or may not give you either of the said
> > results. And the issue here is nothing whatsoever to do with the BIOS.
> >
> > In case you wondered, yes, I am a fully qualified Microsoft Certified
> > Systems Engineer, and have worked full time as Systems Administrator for
the
> > Largest NHS Trust in Europe for the last five years, on top of a vast
other
> > amount of experience and study. Because of this, I happen to know
something
> > about this.
> >
> > No offence intended by my snottiness.
> >
> > Cheers.
> >
> > L;ozt .............you certainly seem to be!
> >
> > "Plato" <|@|.|> wrote in message
> > news:415072be$0$30145$...
> > > Thor wrote:
> > > >
> > > > that would result in "non system disk or disk error" not "NTLDR is
> > missing".
> > >
> > > Right. Your bios has no clue re: OS messages.
> > >
> > > > > ...or maybe, just maybe, there is already a floppy disk in drive
A:
> > which
> > > > > got left in the computer when it shut down. Ask them to check the
> > floppy
> > > > > drive.
> > >
> > >
Similar Threads
