a little warning about Gflags.exe

Yesterday I played around with Gflags, trying to figure out why my ddk
sample ‘enable’ crashes in the debugger on startup but not when run by
itself. Couldn’t figure it out except that it was heap related. So this
morning I came in, turned on my system and it refuses to boot to completion.
It never gets to the login prompt, all you get is the blue background and
mouse pointer. Ctrl-alt-delete doesn’t do anything. The win2K recovery disk
is of no help, nor is safe mode or booting from the last known good config.
Something got trashed and there’s no way to recover. So my system was
re-installed. What a waste of time.

In any case, if you have to use Gflags, I’d recommend only using it to set
flags for a particular application rather than for the whole system. There’s
no 100% certainty but I didn’t install any software yesterday so I’m pretty
sure Gflags is to blame. Or rather me setting some options that cause
certain system processes from running properly.

On the plus side I am now able to debug my code properly. My application
runs, can be stopped when asked and debugged in source code mode rather than
assembly.

So I guess you could say Gflags solved my problem after all. It was just not
the way I hoped it would :slight_smile:

Thanks for everyone’s help,

Sander


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com