Re: problem getting boot verbosity
- From: Robert Grasso <Robert.Grasso+111@xxxxxxxxxx>
- Date: Wed, 05 Apr 2006 13:02:11 +0200
David Candy wrote:
Type bootlog in Help for local help. Type userenv in help while online (the page is on MS servers). These are the two main logs. There are MANY others for specific purpose like modems, news, and mail that are set by specific components or programs. Logging is slower so it is normally off or set to minimal. Type gflags too - not strictly logging but maintains extra data structures to allow tracking.thank you David. Thanks to your suggestions, I discovered the boot.ini
reference at Sysinternals, and just tried /sos and /bootlog. The
ntbtlog.txt yielded in systemroot is the same I got when using some
option at boot (when you can select the safe boot) : there are only the
drivers listed. Anyway, you made me discover the boot.ini reference,
which is interesting.
I guess that MS OSes won't log anything more at boot - it's sad.
Thank you anyway. Feel free to ask if you need help on GNU/Linux ;-)
Robert
.
- References:
- problem getting boot verbosity
- From: Robert Grasso
- Re: problem getting boot verbosity
- From: Wesley Vogel
- Re: problem getting boot verbosity
- From: Robert Grasso
- Re: problem getting boot verbosity
- From: Robert Grasso
- Re: problem getting boot verbosity
- From: Robert Grasso
- problem getting boot verbosity
- Prev by Date: customize xp hotkey bindings
- Next by Date: Re: how do I easily change sound cards?
- Previous by thread: Re: problem getting boot verbosity
- Next by thread: Re: folders
- Index(es):
Relevant Pages
|