verifying dma pool data?

[mcoski]

WTF happens! My comp runs fine at 504 but when i pass the HDD detection it says verifyin g DMI pool data and dont do anyhting after that! Please help!

[Nathan]

If the BIOS sees your hard drive correctly, take your 95/98 startup disk and boot to it. Then type in the following;

sys c:

Remove the disk and reboot.

[Nathan]

If the boot sequence is A to C in CMOS, it will check the floppy first before it goes to the hard drive. There are a few exceptions to the rule like the BIOS not seeing the hard drive properly or there is damage to the hard drive. I've done it hundreds of times.

[kec95]

Regardless of the boot sequence, The mobo will still not load any drives if it cannot get past ver pool data.

Now if it is a drive error then its a different story.


Kenny C

[Nathan]

Hi Kenny.

I see I missed the boat on this one. Can you explain to me what the DMI is and how it's connected to the BIOS or whatever you are referring too?

[kec95]

Nathan, if he can't get by "verifying DMI pooldata" then he can't access the floppy drive.
I say try it at 300MHz. If it doesn't boot then, you fried something messing with voltage settings.

I'm gonna guess its a BH6 mobo you are using.
I had the same thing happen to me when I was trying to get my 300a to 504MHz.

I thought I fried the chip but It was the mobo that I had fried.

These are the chances taken when O/Cing.


Kenny C

[This message has been edited by kec95 (edited 07-16-99).]

[Nathan]

That's what I thought.

[BBA]

I think it's something like "Deveice Memory Interface" or something along this line, I have something to research now.

Kenny's right, if it doesn't go past Verifying DMI Pool Data, then it is not finishing the bios/cmos stuartup point.

I would definitely set all defaults in bios setup and then reboot. If it's not due to the Overclock, then it could also be a hardware conflict, in which case remove all devices but hard drive , vid card and memory. Once you get past this point to booting, then install one device at a time until you get any bugs worked out.


BBA

[This message has been edited by BBA (edited 07-18-99).]

[Nathan]

Susan is right. I knew what it meant. That's why I said in the one post "if the bios sees the hard drive correctly..."

[BBA]

Ok, I'll buy that!

Thanks Susan!

I've never had it happen from drive settings, but I've had it happen a bunch with over ambitious overclocking attempts, which he is doing, right?

I always set the drive to auto detect settings. I haven't had to set them manually since the days of 486's

BBA

[Nathan]

Right on BBA! With the days of auto-detect, I can't imagine when the hard drive is not found correctly, unless of course the hard drive is bad, lousy ribbon cable, etc..

So the GREAT BBA missed an explaination of a term. I think it's great. Here I make that mistake almost daily. But you only make it once every 3 to 4 months that I can tell. Do you walk on water too? hehe

[800XL]

That is sort of a generic place for the system to halt if any number of things aren't quite right. For example, a PCI card is choking on 112Mhz bus, or the RAM is. Solutions abound. Anything from lowering PIO mode or disabling UDMA for the drives, to setting SDRAM to CAS 3 could perhaps fix it.

On the hard drive note: I set drives manually on a certain few systems. Not all machines will autodetect a drive the same. So, if you copy an image to a drive on one machine, then drop it in another machine, it may not work. If you don't swap around drives much, no real need to bother with it though.

[Nathan]

It can get difficult I must admit. And not one answer fits them all. That's why companies/clients want techs that have experience. The sad thing is once you learn most of them, they change things and you are back at square one, well almost.

[BBA]

Help... I need new shoes, mine are wet!!!

**** that water, stop moving just one second and BOOM! all wet!

Oh well, I'll do better next time...I promise...


Please forgive me!

LOL


BBA

[Nathan]

We'll let it slide this time... LOL

[kec95]

Nathan, Don't knock BBA too much. He is one smart dude and might just make you look a little stupid when it comes to computers.

Kenny C


[This message has been edited by kec95 (edited 07-18-99).]

[Susan]

Here's a little explanation of what DMI is.

DMI (Desktop Management Interface) is an industry interface for keeping track of and monitoring the status of components in a system of desktop personal computers. The DMI was created by the Desktop Management
Task Force (DMTF). Each component in a PC system must provide a Management Information File (MIF) that describes its characteristics. Intel's LANDesk Client Manager (LDCM) is based on DMI.

I've had the DMI halt also, and corrected it by setting my HD parameters differently in the BIOS.