PC won't boot past BIOS - Verifying DMI Pool Data

[Distance]

Hey guys,

Having abit of a problem with my dads computer, first, some specs;

[B]Acer Aspire T180[/B]

Acer EM61SM/EM61PM (Foxconn MCP61SM-AM Board)
AMD Sempron 3200+ CPU
2GB Memory
40GB Hitatch Sata HDD
Windows 7 Professional - 64bit

This all came about after trying to flash the BIOS with a newer version, I got the error;

erase failure, maybe hardware protected
fwh rom is write protected

Then when I rebooted the system to try and find some BIOS protection option after the BIOS had loaded and the acer screen etc had gone instead of booting windows it just comes up with the message;

Verifying DMI Pool Data..

I have read about and people have suggested trying to fix the boot records, by using a bootable floppy.

I have done this however the computer won't boot to anything, I have tried removing the CD and HDD and booting from floppy however it won't, it just shows the same message, Verifying DMI Pool Data.

There is nothing wrong with the HDD as I have just put it in my computer and am currently writing this thread using his HDD in my system.

I have tried booting from CD (I have a windows 7 disk) and it just came up with the same message, it seems it won't boot anything and past BIOS it just shows this message.


Someone, please enlighten me with a magic fix for this,

Thanks

Josh




P.S I have also tried cleaing the CMOS by removing the jumper and battery and rebooting

 

[trents]

Have you tried resetting the bios to default values with the menu choice in bios for that (F9 key in my bios)? Also, make sure your disk drive operation mode in bios is not set to ACHI if you originally configured your hard drive in non-ACHI mode.

 

[Inphormed]

Did you ever find a fix for this? I have the EXACT same problem caused by the EXACT same actions.

Please help if you can!

 

[RGone]

The poster joined about a year and a half ago to ask about that one problem and has not been seen since it seems. I doubt he comes back to answer your post.

You would do better to start your own thread with the particulars of your problem.