This content has been marked as final. Show 4 replies
We are sorry for the inconvenience caused to you but I don’t find any reason where you would be getting the BSOD after running the Dm setup file. It might happen if you have any conflicting software or program while installing the product.
But the solution for this issue is performing the repair installation with Windows XP disk that you might receive it with computer. Or you have to check with manufacture for preparing boot Disk.
Actually I did not get the infamous BSOD-- the problem occurs very early in the boot process while the screen is still white text on black, before any Windows logo or anything appears.
IIRC, during the McAfee install process there was a step which involved moving some system code out of its normal location, to be replaced with something new from McAfee. So I suspect that the replacement part of that failed for some reason, probably as you suggest, "It might happen if you have any conflicting software or program while installing the product."
Whatever, I'm quite disappointed with McAfee at this point. The installation process should not leave the machine unbootable if it has difficulty, but should put things back in order before terminating with an error.
But thank you for your response.
Things may be okay now. I got the recovery disk from the computer manufacturer and was able to get to the point of being able to boot again, but everytime I restarted or cold started, I was back at the same error and had to go thru the recovery disk again. I found from reading other forums that there is a "bootcfg /rebuild" option when I go through the Recovery Console part of the recovery disk. After doing this (faster than the whole recovery), I could again boot once before seeing the problem. I finally booted in safe mode and reinstalled the McAfee package successfully, so had security back.
A week or so later, after installing some minor XP updates and installing a new level of RealPlayer, I was able to reboot without having to go through the recovery disk. I don't know which update fixed the problem, but at least I'm running normally now.
Glad things are running better now...:)