Last Updated on September 30, 2010 by Dave Farquhar
Using bootlog.txt. I resurrected a dead Win95 box yesterday; it wouldn’t boot. Bootlog.txt to the rescue. (You can also use bootlog.prv, the log of the previous boot). Search the file for the string “fail” and note the device driver that isn’t working. Hot tip: frequently it’s a network driver. Boot into safe mode, remove the offending driver(s) from Device Manager and potentially problematic software (Anti-Virus software and RealAudio both come to mind; you can always reinstall those later after you’ve got the system back up and running), then reboot. If you boot successfully, add the drivers back in, then reinstall the software you uninstalled, and you’re back in business. Sure beats a reformat and reinstall.
Spam. And I understand some people want me to fly to a foreign country and open a bank account, deposit a large sum of their own money into the account, and at some later date they’ll come take back 2/3 of it. The remaining 1/3 is mine to keep, presumably for helping them hide their assets. Yeah. And Bill Gates wants to send me to Disney World.
I will give them credit though. This hoax was cleverly enough written that I read it in its entirety. A little entertainment to start my day.
David Farquhar is a computer security professional, entrepreneur, and author. He started his career as a part-time computer technician in 1994, worked his way up to system administrator by 1997, and has specialized in vulnerability management since 2013. He invests in real estate on the side and his hobbies include O gauge trains, baseball cards, and retro computers and video games. A University of Missouri graduate, he holds CISSP and Security+ certifications. He lives in St. Louis with his family.