This is the message I see when booting.

"Bios checksum error
Detecting Floppy Drive A media
Driver error. System halt."

Can't go to bios. No floppy drive fitted.
Any help gratefully received.

"sandy58" <(E-Mail Removed)> wrote
> This is the message I see when booting.
>
> "Bios checksum error
> Detecting Floppy Drive A media
> Driver error. System halt."
>
> Can't go to bios. No floppy drive fitted.
> Any help gratefully received.


This isn't an XP OS issue. You are better off posting to a hardware
newsgroup, calling the tech support for the computer or taking it to a
competent computer repair tech.

--
Rock [MS-MVP User/Shell]

sandy58 wrote:

> This is the message I see when booting.
>
> "Bios checksum error
> Detecting Floppy Drive A media
> Driver error. System halt."
>
> Can't go to bios. No floppy drive fitted.
> Any help gratefully received.


What does "can't go to bios" mean? Have you tried? How? What happens when
you try?

BIOS checksum errors normally indicate that the battery on the motherboard
needs replacing.

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

"sandy58" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This is the message I see when booting.
>
> "Bios checksum error
> Detecting Floppy Drive A media
> Driver error. System halt."
>
> Can't go to bios. No floppy drive fitted.
> Any help gratefully received.
>

More likely, if a bios message, said "Drive error. System halted."

If the address and data lines for the cmos are functioning correctly, the
first part of the message is valid. In that case, the cmos has to be
cleared.

If the PC was custom/home built or the floppy removed, and the cmos battery
is kaput; more likely the bios went to default settings. Many bios with
floppy enabling capability, that part is a default setting.

Not enough info on how to enter your bios setup. That seems to be your
question.
--
Noncompliant

Money don't wag the dog's tail.

On Apr 8, 2:57 pm, davy <davy.2oq...@no.email.invalid> wrote:
> Hi Sandy
> Have a look here in the Reference link section you'll find a list of
> link's for bios error codes and maybe some fixes..
>
> http://www.howtofixcomputers.com/bb/ftopic186979.htmlI can't say if
> there is any help in this link but I will give it all the same..http://www.howtofixcomputers.com/bb/ftopic186983.html
>
> Think the way I would go about it is to disconnect eveything.... the
> lot except The CPU, the Graphic card and the RAM.... when you 'should'
> get bios boot and be able to access the set up screen... then all you
> have to do is to ...
>
> .. yep you got it insert em' one by one and see what happens - sounds
> logical to me..
>
> Maybe a bios re-boot might help but *NOTE* you will have to re set the
> bios screen up after - simply remove the battery for about 3 mins or so,
> if over about three years old swap it.
>
> davy
>
> Repetitive quoting just wastes space..!

Sorry, Rock. You're comment noted. Many thanks to the rest of the
helpful guys. :-)
You have been very helpful.

"sandy58" <(E-Mail Removed)> wrote

> On Apr 8, 2:57 pm, davy <davy.2oq...@no.email.invalid> wrote:
>> Hi Sandy
>> Have a look here in the Reference link section you'll find a list of
>> link's for bios error codes and maybe some fixes..
>>
>> http://www.howtofixcomputers.com/bb/ftopic186979.htmlI can't say if
>> there is any help in this link but I will give it all the
>> same..http://www.howtofixcomputers.com/bb/ftopic186983.html
>>
>> Think the way I would go about it is to disconnect eveything.... the
>> lot except The CPU, the Graphic card and the RAM.... when you 'should'
>> get bios boot and be able to access the set up screen... then all you
>> have to do is to ...
>>
>> .. yep you got it insert em' one by one and see what happens - sounds
>> logical to me..
>>
>> Maybe a bios re-boot might help but *NOTE* you will have to re set the
>> bios screen up after - simply remove the battery for about 3 mins or so,
>> if over about three years old swap it.
>>
>> davy
>>
>> Repetitive quoting just wastes space..!

> Sorry, Rock. You're comment noted. Many thanks to the rest of the
> helpful guys. :-)
> You have been very helpful.


You don't need to be sorry. Just trying to point you to the best places to
resolve the issue, since it is a hardware problem. Has it been fixed?

--
Rock [MS-MVP User/Shell]