Verifying DMI Pool data

[Oscar]

I had the problem Verifying DMI Pool data and then
computer hangs. Can i replace the sys file for boot, like
Win98 and so.

Please some

 

[Mistoffolees]

I had the problem Verifying DMI Pool data and then
computer hangs. Can i replace the sys file for boot, like
Win98 and so.

Please some

Windows 2000 is not like Windows 98 in that neither the
fdisk /mbr command nor the sys c: command would be effective
in this situation. The first thing to do is to determine why
or where the DMI Pool values have been corrupted in the bios
tables. What has happened is that the bios cannot locate the
HD boot sector to boot the computer. Run bios configuration
setup, paying particular attention to reset the autodetect
HD and LBA values. If this fails, then the process becomes a
lot more complicated. If the values for the HD in the bios
are OK, then run a repair of the boot sector starting with
the Windows 2000 setup diskettes or cdrom. If this does not
work, then clear the CMOS settings via the jumper on the
motherboard, reflash and lay in the default bios settings,
and hope whatever corruption of the bios tables is cleared.
In some instances, a new bios solves the problem nicely.

Check in Google. There is an excellent bulletin put out by
Maxtor for this particular problem.

 

[Ghostrider]

Windows 2000 is not like Windows 98 in that neither the
fdisk /mbr command nor the sys c: command would be effective
in this situation. The first thing to do is to determine why
or where the DMI Pool values have been corrupted in the bios
tables. What has happened is that the bios cannot locate the
HD boot sector to boot the computer. Run bios configuration
setup, paying particular attention to reset the autodetect
HD and LBA values. If this fails, then the process becomes a
lot more complicated. If the values for the HD in the bios
are OK, then run a repair of the boot sector starting with
the Windows 2000 setup diskettes or cdrom. If this does not
work, then clear the CMOS settings via the jumper on the
motherboard, reflash and lay in the default bios settings,
and hope whatever corruption of the bios tables is cleared.
In some instances, a new bios solves the problem nicely.

Check in Google. There is an excellent bulletin put out by
Maxtor for this particular problem.

The original Maxtor Knowledge Base Article being referred to,
#15007, no longer exists. But it seems to have been re-written
as a FAQ, #1044, and is available here:

http://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/olh_adp.php?p_faqid=1044

(URL line may wrap.)