Have to use Linux to fix Windows!

  • Thread starter Thread starter mareta
  • Start date Start date
M

mareta

All because the stupid motherfucker that put /BOOTLOG'ing together didn't
realize that people may actually want to READ ntbtlog.txt !

I can not believe that the motherfucker overwrites when you boot into safe
mode -- and even the recovery console.

You have to got to be ****ing joking. I thought it was unbelievable, but
laughable, when (some) CDROM drive manufacturers used to give you the
drivers on a CD -- but this is UNFUCKINGBELIEVABLE.

So, how the **** is someone supposed to read the bootlog from a failed
normal startup?

Boot to safe modes? It gets overwritten. (Why doesn't it get APPENDED?
That would make sense.)

Boot into a recovery console? It gets overwritten. ("")

Boot disk? Its NTFS.

Nope. The only way to read this Goddamn file after a failed normal boot,
without it getting overwritten, is to use some BS Linux LiveCD and mount the
HDD. Stuff that into your "Knowledge" Base, Bill.
 
Nope. The only way to read this Goddamn file after a failed normal boot,
without it getting overwritten, is to use some BS Linux LiveCD and mount the
HDD. Stuff that into your "Knowledge" Base, Bill.
Click to expand...
It isn't the only way, and if you had any brains, you would know that
all discs get mounted when a decent live CD boots.

Do yourself a favor, and grow the **** up.
 
And just for the heck of it, I checked the /BOOTLOG switch in
msconfig. I already had two logs in the text file from a year ago (I
only use bootlegging for troubleshooting purposes). The new bootlog
was appended to the bottom of the previous one. You have to examine
the log carefully for the start of the current log as there are no
spaces. It will begin with a line like this:
Service Pack 2 3 14 2007 20:14:22.500
Easy to miss. If I want to keep them, I separate them with a couple of
empty lines and maybe a dotted line or two.
 
Back
Top