I'm trying to troubleshoot a long boot up time so I've enabled boot logging.
The resulting file ntbtlog.txt is supposed to be readable but in my case
it's in hex format. Is there a way to set this so it's a normal .txt file?

jc

Doesn't sound right. It should be simply a text file. If the file is larger
than 64k, then NotePad.exe wont be able to open it. Try wordpad.exe



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"jbclem3" wrote:
> I'm trying to troubleshoot a long boot up time so I've enabled boot
> logging.
> The resulting file ntbtlog.txt is supposed to be readable but in my case
> it's in hex format. Is there a way to set this so it's a normal .txt
> file?
>
> jc
>
>

I tried wordpad, but it showed unreadable hex(??). I then switched wordpad
to another file(which it read correctly) , then back to ntbtlog.txt and this
time it showed the correct text. I don't know why this happened but I'm not
complaining at this point. Thanks for the suggestion.


"Dave Patrick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Doesn't sound right. It should be simply a text file. If the file is
larger
> than 64k, then NotePad.exe wont be able to open it. Try wordpad.exe
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "jbclem3" wrote:
> > I'm trying to troubleshoot a long boot up time so I've enabled boot
> > logging.
> > The resulting file ntbtlog.txt is supposed to be readable but in my case
> > it's in hex format. Is there a way to set this so it's a normal .txt
> > file?
> >
> > jc
> >
> >
>

You're welcome.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"jbclem3" wrote:
>I tried wordpad, but it showed unreadable hex(??). I then switched wordpad
> to another file(which it read correctly) , then back to ntbtlog.txt and
> this
> time it showed the correct text. I don't know why this happened but I'm
> not
> complaining at this point. Thanks for the suggestion.