Oh yeah a corrupt C:\WINDOWS\Security\*.log file somewhere
OK, that's common after a bad exit, and trivial to fix if there's
nothing else wrong. But bad exits DO imply something else is wrong;
either bad user habits (use the Shutdown, Luke) or something bad in
the system that crashes, resets, or stops it shutting down properly.
I can fix this but you'll break your EULA in the process
What? Explain that, please?
Yeah, right. Unless I'm missing something here (quite likely, given
this is the only post in the thread I'm reading) we have an unknown PC
that's presumably had a bad exit that's broken a trivial log file, and
you are advocating writing several megs of new OS code to it.
If that's the case, this will make things considerably worse (most
likely beyond anyone's ability to undo) if there were hardware reaons
behind whatever broke that log file.
If so,
http://cquirke.mvps.org/9x/bthink.htm applies.
That seems very scant reason to "upgrade" to XP Pro. I'd be more
inclined to discard the putative joys of multiple user accounts than
to spend more money trying to get this flawed facility to work.
--------------- ----- ---- --- -- - - -
Tech Support: The guys who follow the
'Parade of New Products' with a shovel.