How to troubleshoot a system that will not boot to the hard drive.

You'll have to locate / borrow a Mac with a diskette drive, or an external diskette drive that you can plug into your current Mac.

Possibly a Mac support/repair location will have such a drive. Or look to purchase such a diskette drive in the used equipment market.

The computer is indicating that something is preventing it from booting to the hard disk drive. Ensure that if the system has a floppy diskette drive, there is no diskette in the drive as the system may be trying to boot to it and failing.
If no floppy or no other Media (DVD/CD) in any drive then the Hard Disk Drive may be having problems and need repair.
(La computadora est? indicando que algo est? evitando que pateara a la impulsi?n de disco duro. Aseg?rese de que si el sistema tiene una disquetera floja, no haya diskette en la impulsi?n pues el sistema puede intentar patear a ?l y a fallar. Si ningu?n disco blando o ningunos otros medios (DVD/CD) en cualquier impulsi?n entonces la impulsi?n de disco duro puede tener problemas y necesitar la reparaci?n.)
more info here:
http://www.fixya.com/support/r3728860-troubleshoot_system_will_not_boot_hard

Try using diskette in another pc drive,if it works copy data to new diskette, its not unusual for diskettes to wear out thro constant usage.

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.

Computer stops at verifying dmi pool data. Issue: Computer stops at verifying dmi pool data.
Cause: This issue can be caused by any of the below reasons.

1. Corrupt boot files on the computer.
2. Settings for hard disk drive are not correct.
3. Floppy diskette or CD in computer causing issue.
4. Boot devices not set properly.
5. BIOS corrupt or misc. setting not set properly.
6. Connections loose or disconnected.
7. 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.
Additional information about the "fdisk /mbr" command can be found on document CH000175.
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. Additional information about entering CMOS setup is found on document CH000192.
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 (steps found on document CH000192) 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