Max:
-I usually get the “Unable to verify Timestamp …” warning when WinDbg
is loading my driver’s symbols. I don’t get it for ntoskrnl.exe or
hal.dll…
Gary:
-Bug or feature 
you’re absolutely right. As I said before, “.reload
/user”
usually brings up my driver’s symbols into memory and “solves up” the
problem for a while…
Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com
«Humour and love are God’s answers
to Human weaknesses»
On Sunday, March 18, 2001 1:33 AM “Gary G. Little” wrote:
Max,
I use !reload, or “bp DriveName!breakpoint”. I guess the WinDbg folks
think
this is a feature, as this is what they told me to do.Gary
PS: Generally, a “feature” is nothing more than a bug in drag.
On Saturday, March 17, 2001 11:56 AM “Maxim S. Shatskih” wrote:
> The message about the User Loaded Module List being paged out is
expected
> if you are breaking in the context of a process with no user mode
address
> space (system process).Another problem of the last WinDbg:
“Unable to verify Timestamp for xxxx” while loading a symbol file.
It complains on all symbols - NTOSKRNL, HAL, my driver just built
etc.Is it possible to shut if off?
Max
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