Can someone tell me what is DMI Pool Data, and why a system would hang while
trying to verify dmi pool data?
On win98, I swapped out an ide hardrive for a scsi with controller. After
making changes in the bios to reflect this I also ran the auto-configure
program for scsi. all went well in boot up afterwards until the verifying
dmi pool data process. In an effort to determine if this was a scsi issue
or not, I re-swapped out the scsi and installed the ide drive, changed bios
settings, and continue to have the system hang at this same process! Can
anyone lend any comments, ideas, suggestions?
thanks!
wendy wrote:
> Can someone tell me what is DMI Pool Data, and why a system would hang while
> trying to verify dmi pool data?
> On win98, I swapped out an ide hardrive for a scsi with controller. After
> making changes in the bios to reflect this I also ran the auto-configure
> program for scsi. all went well in boot up afterwards until the verifying
> dmi pool data process. In an effort to determine if this was a scsi issue
> or not, I re-swapped out the scsi and installed the ide drive, changed bios
> settings, and continue to have the system hang at this same process! Can
> anyone lend any comments, ideas, suggestions?
> thanks!
The problem associated with this message has cropped up many times. But
"Verifying DMI Pool Data" is really not the cause of the hang up although it
may be a contributing factor. DMI = Desktop Management Interface. In an
attempt to have a better PnP interface with Win9X, data about a computer’s
hardware and its configuration are placed in bios tables. Occasionally, the
bios tables get corrupted — and it could be a one-bit shift. Last time I had
corresponded with the Desktop Management Task Force, the finger-pointing
went all the way around, including the possibility of a virus.
The hangup after the "verifying dmi pool data" line occurs because the computer
cannot locate the boot sector on the hard drive (and also possibly the floppy
disk drive). How this is remedied varies; the easier recourse is to replace the
bios and then never let Win9X write to the bios tables or the ESCD tables by
disabling the PnP OS option. Less successful is to clear the bios tables and
then reflashing and trying to go through bios setup including autodetecting the
IDE drives. Our success rate at recovering Award bioses (no problems at all
with AMI ones) was less than 25%.
Since this is a SCSI system, why not disable the primary and secondary IDE
controllers and rely on the SCSI host adapter to boot the SCSI hard drive?
Forgive my ignorance, but how exactly do I disable the P/S IDE controllers?
I don’t recall seeing that as an option in the Award Bios, but I’m sure now
that it must be there somewhere…..
thanks ghostrider for your thorough explanation. Much appreciated.
wendy
"Ghostrider" <-…@fitron.142> wrote in message
news:3A664247.E35AEF25@fitron.142…
- Hide quoted text — Show quoted text -
> wendy wrote:
> > Can someone tell me what is DMI Pool Data, and why a system would hang
while
> > trying to verify dmi pool data?
> > On win98, I swapped out an ide hardrive for a scsi with controller.
After
> > making changes in the bios to reflect this I also ran the auto-configure
> > program for scsi. all went well in boot up afterwards until the
verifying
> > dmi pool data process. In an effort to determine if this was a scsi
issue
> > or not, I re-swapped out the scsi and installed the ide drive, changed
bios
> > settings, and continue to have the system hang at this same process!
Can
> > anyone lend any comments, ideas, suggestions?
> > thanks!
> The problem associated with this message has cropped up many times. But
> "Verifying DMI Pool Data" is really not the cause of the hang up although
it
> may be a contributing factor. DMI = Desktop Management Interface. In an
> attempt to have a better PnP interface with Win9X, data about a computer’s
> hardware and its configuration are placed in bios tables. Occasionally,
the
> bios tables get corrupted — and it could be a one-bit shift. Last time I
had
> corresponded with the Desktop Management Task Force, the finger-pointing
> went all the way around, including the possibility of a virus.
> The hangup after the "verifying dmi pool data" line occurs because the
computer
> cannot locate the boot sector on the hard drive (and also possibly the
floppy
> disk drive). How this is remedied varies; the easier recourse is to
replace the
> bios and then never let Win9X write to the bios tables or the ESCD tables
by
> disabling the PnP OS option. Less successful is to clear the bios tables
and
> then reflashing and trying to go through bios setup including
autodetecting the
> IDE drives. Our success rate at recovering Award bioses (no problems at
all
> with AMI ones) was less than 25%.
> Since this is a SCSI system, why not disable the primary and secondary IDE
> controllers and rely on the SCSI host adapter to boot the SCSI hard drive?
wendy wrote:
> Forgive my ignorance, but how exactly do I disable the P/S IDE controllers?
> I don’t recall seeing that as an option in the Award Bios, but I’m sure now
> that it must be there somewhere…..
> thanks ghostrider for your thorough explanation. Much appreciated.
> wendy
Have not touched an Award bios in ages. We have not ordered a single
motherboard with them for over 3-4 years due to this very issue and the
pitiful replies I got from the Desktop Management Task Force, Intel,
Award and Microsoft. Have yet to have an AMI bios motherboard do
this "DMI Data Pool" event.
Anyway, when the computer starts, go into bios setup via the DEL key. In
one of the setup screens, there should be an option for (IDE) hard drives.
Select none, save and exit. To boot from the SCSI hard drives, follow the
instructions for the specific SCSI adapter host card.