I have seen KD lose it cursor position, esp if I am typing after I hit
ctrl+C but before it is broken in (or during a long command like lm).
Does the same corruption happen on windbg?
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Thursday, April 07, 2005 12:25 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Driver Verifier strange init message
No, pure ANSI only (FdRedir.sys in this case). It behaves this way for
all my drivers, all ANSI 8.3 names. Also, banner isn’t always broken the
same way. I guess timing influences it somewhat.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, April 07, 2005 8:02 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Driver Verifier strange init message
does the driver’s name contain non ANSI chars? Perhaps the banner
expects ANSI only and if it contains UNICODE chars, they are not
handled
properly.
Just a guess.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Thursday, April 07, 2005 9:06 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Driver Verifier strange init message
The checkin banner has been part of every version of DV released as
far
as I
know. It remains curious why the OP’s banner is corrupted.
=====================
Mark Roddy
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Henry
Gabryjelski
Sent: Thursday, April 07, 2005 12:00 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Driver Verifier strange init message
The string about “checkin string” was a method used within the
Windows
organization to ensure people ran their driver with DriverVerifier
enabled
prior to checking in any changes to said driver. I am somewhat
surprised
you would see that in an external, retail build. You can ignore it,
it
has
no value outside Microsoft.
Hth,
.
-----Original Message-----
From: Tim Roberts [mailto:xxxxx@probo.com]
Sent: Wednesday, April 06, 2005 10:28 AM
Subject: Re: Driver Verifier strange init message
Michal Vodicka wrote:
>Nothing important, I’m just curious. I use SoftICE and/or DbgView for
driver debugging and both display all the debug output I use in my
code
exactly as expected and formatted. However, whenever a driver with
verifier
enabled starts, both display following (XP SP2 but older versions
too):
>
>* Driver Verifier: Enabled for
F***********************************************************************
********
>*
>* This is the string you add to your checkin description
>
>Well, driver name starts with ‘F’ but I wonder if the message was
intended like this. Also, I’d like to know what the second part means
Is
the message displayed in the WinDbg the same crappy way?
>
>
No, it’s not. This is what I see in WinDbg with driver verifier:
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE Kernel
Debugger connection established. (Initial Breakpoint requested)
Symbol
search path is:
c:\dev\micronas\src\driver\base2\objchk_wxp_x86\i386;c:\dev\micronas\src
\driver\tuner\objchk_wxp_x86\i386;srv*c:\ddk\symbols*http://msdl.microso
ft.com/download/symbols;
Executable search path is:
c:\dev\micronas\src\driver\base2\objchk_wxp_x86\i386;c:\dev\micronas\src
\driver\tuner\objchk_wxp_x86\i386;c:\tmp
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built
by:
2600.xpsp_sp2_rtm.040803-2158 Kernel base = 0x804d7000
PsLoadedModuleList =
0x8055c700 System Uptime: not available Break instruction exception -
code
80000003 (first chance)
************************************************************************
*******
*
*
* You are seeing this message because you pressed
either *
* CTRL+C (if you run kd.exe) >
or, *
* CTRL+BREAK (if you run
WinDBG), *
* on your debugger machine’s
keyboard. *
*
*
* THIS IS NOT A BUG OR A SYSTEM
CRASH *
*
*
* If you did not intend to break into the debugger, press the “g” key,
then *
* press the “Enter” key now. This message might immediately reappear.
If it *
* does, press “g” and “Enter”
again. *
*
*
************************************************************************
*******
nt!RtlpBreakWithStatusInstruction:
8052a5d8 cc int 3
kd> g
************************************************************************
*******
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for MicNgBas.sys on Build 2600
3TCLXTodpyWcuQBunz7EFD
*
************************************************************************
*******
************************************************************************
*******
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for MicNgCap.sys on Build 2600
nhxPkZyOsrhJxWBunz7EFD
*
************************************************************************
*******
************************************************************************
*******
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for MicNgTun.sys on Build 2600
P7iKQYCWDN2YLaDunz7EFD
*
************************************************************************
*******
************************************************************************
*******
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for MicNgTst.sys on Build 2600
pWTP6ZF277efIaDunz7EFD
*
************************************************************************
*******
–
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag
argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com