computer was stoping at verifing DMI Pool Data. Had a boot disk made at work from a PC running XP. Now at A:\> I typed in sys c: and got Bad command or file name. Then at A:\> typed in fdisk/mbr and still get bad command or file name. I found the boot disk I made and after booting up with it it ask me to remove disks or other media. Press any key to restart. It did not start the only thing that came up was Yo Yo....but the o's look more like a oval with 2 lines. or to me looks like a outlet that u would plug in to.

hi !!! I think in your system, Some registry files or infected files occurred So that why you are suffering. You know window registry files can very slow or may be currupted your system. If you want to solve your problem you can download registry easy. Only this soft can repair your window registry error.

Thanks for the reply doller99, where would I download the files you are talking about? Thanks Texasheat

I never heard of 'registry easy' It looks like a trial version that you have to pay for in order to fix any problems....I would steer away from that as it will give you lots of false positives. ccleaner slim has a user friendly registry cleaner that is safe to use: http://majorgeeks.com/CCleaner_Slim... texasheat, you may have to do a repair install: http://www.microsoft.com/windowsxp/... You will need an xp install disc for that. Some HELP in posting on Computing.net plus free progs and instructions Cheers

texasheat, take a look at what Google has to say @: http://www.google.com/#hl=en&source... BTW, I too am sorta leery of registry cleaners. Be sure to back it up first just in case. HTH. Ed in Texas.

Echoing both XP and Ed...: a repair routine would be more advisable... and ensure you "repair" not using the recovery console path... (as per XP user's link). If possible... backup - as in copy off - all data etc. first to optical media... If you can't get teh beast to boot up etc... and can't slave the drive to another working system (or via a usb connection) then boot up with a Knoppix or Ubuntu (Linux variants) CD to the same end... I would seriously steer clear of registry cleaners... Having had limited and not at all "happy" experiences with them... I tend to avoid them like the plague.

I'll just put my two pence worth in as well. For the most part registry cleaners are snake oil. When you consider to complexity of what they purport to do it would take many hours for them to do it with any degree of accuracy. Seeing as Sys C: and fdisk are DOS commands and there is no DOS in Windows XP, you are probably making a bad situation worse. Stopping at verifying DMI Pool Data would indicate a BIOS error that has absolutely nothing at all to do with Windows. The first thing to do in this situation is to reset CMOS memory. This is achieved by moving a jumper in the mother board from one place to another for a few seconds with power removed. The manual should show you were and how. Stuart