Emachine-searching for boot record from floppy\

MBR stands for Master Boot Record. It is an essential piece of information written on the Hard Drive that allows the program to load. If the MBR is corrupted the computer boot process cannot proceed.
You have to repair it.
On old systems with a floppy drive you would get a Win98 boot disk on a floppy, boot the system using the A:drive (floppy) then use a DOS command to refresh the Master Boot Record.
If your system is using Windows XP tablet PC edition you might be able to use the installation disk to boot to the recovery console and use the command FIXBOOT or FIXMBR. You can also reinstall the Operating System.
I hope this answer gave you some starting point to investigate further. There are on the web some software vendors who sell system recuperation CDs. Some may be free other you have to buy.

Try starting computer in safe mode (by pressing F8 before you see the windows logo) and the hidden administrator account should appear to log in from. If for some reason this doesnt work , try searching from another computer of course for "Hirams Boot Disk" to put on a floppy. Boot from this and follow one of the many options that works for you. You might have to adjust your boot order to boot from floppy. Hope this helps.

This issue can be caused by any of the below reasons.

-Corrupt boot files on the computer.
-Settings for hard disk drive are not correct.
-Floppy diskette or CD in computer causing issue.
-Boot devices not set properly.
-BIOS corrupt or misc. setting not set properly.
-Connections loose or disconnected.
-Bad Hard disk drive or other bad hardware.

Solution:

Corrupt boot files on the computer

If the computer has no bootable files on the drive it is attempting to boot from it is possible that the computer may halt at " verifying dmi pool data..."

To resolve this issue:

Boot from a bootable floppy diskette. Ensure that this diskette was made on the same Microsoft Windows operating system that is installed on your computer.

Once at the A:\> prompt type "sys c:" and press enter. This should report the message "File system transferred." Once transferred remove the diskette and reboot the computer.

If the computer continues to not boot attempt to re-create the master boot record by booting from the bootable floppy diskette again. Once at the A:\> prompt type "fdisk /mbr" and press enter. This should return you to the prompt without giving you any message. Once at the prompt remove the diskette and reboot the computer.

Note: The above information only applies to Microsoft Windows users. If you are running a Linux / Unix variant or other operating system such as OS/2 and the computer is freezing at this DMI message ensure that Linux / Unix has been properly installed first and/or your boot manger is not corrupt.

Settings for hard disk drive are not correct

The computer freezing at "Verifying dmi pool data..." may be caused when the hard disk drive settings within CMOS are not set properly. Enter CMOS and verify that the hard disk drive settings are set properly and/or that it is set to Auto Detect.

Floppy diskette or CD in computer causing issue

Verify no floppy diskette or CD is in the computer. In some cases the computer may be trying to boot from either of these drives causing issues with the boot sequence.

Boot devices not set properly

The computer stopping at " verifying dmi pool data..." can be caused when the boot devices on your computer are not set properly in CMOS. First, verify that no CD or diskette is in your computer. If a CD or diskette is in the computer attempt to remove this first to determine if it was attempting to boot from it.

If No CD or diskette is in the computer and your computer still halts at the DMI message enter CMOS setup and verify that the boot options are set properly. We commonly recommend that the floppy be set the first boot device, hard drive as the second boot device and the CD-ROM as the third boot device.

BIOS corrupt or misc. setting not set properly

If none of the above recommendations have resolved your issue attempt to reset the BIOS / CMOS settings to the factory or default settings.

Connections loose or disconnected

If the computer has been recently moved or new hardware has been installed in the computer it is possible that a connection may be loose or even disconnected. Verify that the hard disk drive, floppy and CD-ROM cables are properly connected.

Bad hard disk drive or other bad hardware

If you computer continues to freeze at the DMI message after attempting all of the above recommendations it is possible that the computer may be freezing because of a bad hard disk drive or other bad hardware in the computer.

Before replacing any hardware we first recommend you attempt to erase everything on the hard drive and start over.

If you're unable to get to the point of re-installing the operating system it's likely your computer has a hardware issue and it's suggested that the hard drive be replaced. If that doesn't resolve the issue then have the motherboard replaced.

A couple of things.

If the system has a floppy diskette drive, ensure that no diskette is in the drive. (I know it sounds simple but ...)

If no floppy drive issue, then run diagnostics on the hard drive. The drive may be failing.

Last you can try booting to the XP CD enter recovery console, and run the command: CHKDSK /R, then reboot.

My impression, if no floppy drive issue, then failing hdd

You could try unplugging your laptop and taking the battery out, wait a few minutes put the battery back in, then plug it back in to the wall receptable, if you were working on something you wanted to save when this happend it might not keep any of the information, you should be able to boot it back up normally.

hi im josh in cebu phils.may i help you? friend try to do this things. first i suggest to change new ide or sata cable.if still persist.try the following:
Boot order: Traditionally, a computer is set to boot first from the floppy drive, and then from the main hard drive (Drive C). This means that the computer will check the floppy drive first for boot files. If there is no disk in the floppy drive, the computer will then go to the hard drive to look for boot files. That is why if you leave a non-bootable floppy disk in the drive and try to boot up, you'll get an error message such as "NTLDR is missing. Press any key to restart." or "Non-system disk or disk error." This can be changed to pretty much any order, including CD and DVD drives. It is useful when installing Windows on a new or just-formatted computer to set the computer to boot first from a CD-ROM drive, and then insert the Windows installation CD-ROM into that drive. This saves you from having to use boot floppies that might or might not come with the Windows CD-ROM. Good luck.

check if you have floppy disk or cd-rom disk inserted, the bios may have look for the operating systems on this drive. If there's a disk on this drive, remove them and try to reboot your computer.

Make sure your bios defaults to the disk which has the master boot record. usually it's in C drive.

Let me know.

Thanks.

Non-System Disk or Disk Error results when the Basic Input/Output System (BIOS) cannot find the boot sector or the master boot record is missing or damaged; i.e. the device does not have bootable media. The BIOS searches drives in the order usually specified in the CMOS Setup. This order is often, but not always, A: (floppy drive), C: (first partition on the hard disk)… The error will occur during startup if the CMOS is set so the BIOS seeks the floppy drive first and a non-bootable (or blank) floppy is in (was left in) the floppy drive. Other causes include:

No bootable partition on a hard disk drive

A defective hard disk drive

The CMOS drive settings (parameters) are not correct for the boot device

Defective floppy

Defective floppy drive

A virus

Hi,

Your computer cannot find The Hard-drive Or operating System.
Your Primary Hard Drive, is reporting an error.
Try changing the Jumper setting on this From Master To slave.
( jumper is amall plastic Block ) on back of drive.
Then set your CD/DVD To Master.

Mike @ Compurepair.

Have you tried a BIOS firmware upgrade?