KMDF10 ...

Two stack dumps, each includes the command used:

1: kd> !stacks 1
Proc.Thread .Thread Ticks ThreadState Blocker

Max cache size is : 1048576 bytes (0x400 KB)
Total memory in cache : 0 bytes (0 KB)
Number of regions cached: 0
0 full reads broken into 0 partial reads
counts: 0 cached/0 uncached, 0.00% cached
bytes : 0 cached/0 uncached, 0.00% cached
[867c47c0 System]
4.000008 867c4548 0000209 Blocked
nt!IopInitializeSystemDrivers+0x49
4.00000c 867c3c98 000037a Blocked Stack paged out
4.000010 867c3a20 00000f7 Blocked Stack paged out
4.000014 867c37a8 00001f7 Blocked Stack paged out
4.000018 867c3530 0000007 Blocked nt!ExpWorkerThread+0xcc
4.00001c 867c32b8 0000037 Blocked nt!ExpWorkerThread+0xcc
4.000020 867c2020 000037a Blocked Stack paged out
4.000024 867c2da8 000037a Blocked Stack paged out
4.000028 867c2b30 000037a Blocked Stack paged out
4.00002c 867c28b8 000037a Blocked Stack paged out
4.000030 867c2640 0000203 Blocked Stack paged out
4.000034 867c23c8 0000004 RUNNING nt!RtlpBreakWithStatusInstruction
4.000038 867c1020 0000006 Blocked
VolSnap!VspWaitToRegisterWorker+0x8d
4.00003c 867c1da8 0000008 Blocked nt!ExpWorkerThread+0xcc
4.000040 867c1b30 000003a Blocked
nt!ExpWorkerThreadBalanceManager+0x5e
4.000044 867c0268 0000372 Blocked Stack paged out
4.000048 867b7020 0000372 Blocked
nt!MiModifiedPageWriterWorker+0x45
4.00004c 867b6020 0000372 Blocked nt!MiMappedPageWriter+0x54
4.000050 867b6da8 0000032 Blocked nt!KeBalanceSetManager+0x75
4.000054 867b6b30 0000037 Blocked nt!KeSwapProcessOrStack+0x2b
4.000058 867e8900 0000370 Blocked nt!FsRtlWorkerThread+0x35
4.00005c 867e8688 0000370 Blocked nt!FsRtlWorkerThread+0x35
4.000060 867a0370 0000344 Blocked ACPI!ACPIWorker+0x47
4.000064 867746c8 0000346 Blocked dmio!voliod_loop+0x399
4.000068 86738640 000031c Blocked NDIS!ndisWorkerThread+0x30
4.000070 86631bb8 0000006 Blocked nt!KiFastCallEntry+0xfc

Threads Processed: 26

Max cache size is : 1048576 bytes (0x400 KB)
Total memory in cache : 0 bytes (0 KB)
Number of regions cached: 0
0 full reads broken into 0 partial reads
counts: 0 cached/0 uncached, 0.00% cached
bytes : 0 cached/0 uncached, 0.00% cached
** Transition PTEs are implicitly decoded

1: kd> !stacks 2
Proc.Thread .Thread Ticks ThreadState Blocker

Max cache size is : 1048576 bytes (0x400 KB)
Total memory in cache : 0 bytes (0 KB)
Number of regions cached: 0
0 full reads broken into 0 partial reads
counts: 0 cached/0 uncached, 0.00% cached
bytes : 0 cached/0 uncached, 0.00% cached
[867c47c0 System]
4.000008 867c4548 0000209 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2
nt!IopInitializeSystemDrivers+0x49
nt!IoInitSystem+0x7a3
nt!Phase1Initialization+0xac7
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.00000c 867c3c98 000037a Blocked Stack paged out
4.000010 867c3a20 00000f7 Blocked Stack paged out
4.000014 867c37a8 00001f7 Blocked Stack paged out
4.000018 867c3530 0000007 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
nt!ExpWorkerThread+0xcc
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.00001c 867c32b8 0000037 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
nt!ExpWorkerThread+0xcc
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000020 867c2020 000037a Blocked Stack paged out
4.000024 867c2da8 000037a Blocked Stack paged out
4.000028 867c2b30 000037a Blocked Stack paged out
4.00002c 867c28b8 000037a Blocked Stack paged out
4.000030 867c2640 0000203 Blocked Stack paged out
4.000034 867c23c8 0000004 RUNNING nt!RtlpBreakWithStatusInstruction
nt!KiBugCheckDebugBreak+0x19
nt!KeBugCheck2+0x574
nt!KeBugCheckEx+0x1b

nt!PspUnhandledExceptionInSystemThread+0x1a
nt!PspSystemThreadStartup+0x5a
nt!KiThreadStartup+0x16
4.000038 867c1020 0000006 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2

VolSnap!VspWaitToRegisterWorker+0x8d
nt!ExpWorkerThread+0xef
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.00003c 867c1da8 0000008 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
nt!ExpWorkerThread+0xcc
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000040 867c1b30 000003a Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForMultipleObjects+0x284

nt!ExpWorkerThreadBalanceManager+0x5e
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000044 867c0268 0000372 Blocked Stack paged out
4.000048 867b7020 0000372 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForMultipleObjects+0x284
nt!MiModifiedPageWriterWorker+0x45
nt!MiModifiedPageWriter+0x165
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.00004c 867b6020 0000372 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2
nt!MiMappedPageWriter+0x54
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000050 867b6da8 0000032 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForMultipleObjects+0x284
nt!KeBalanceSetManager+0x75
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000054 867b6b30 0000037 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2
nt!KeSwapProcessOrStack+0x2b
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000058 867e8900 0000370 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
nt!FsRtlWorkerThread+0x35
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.00005c 867e8688 0000370 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
nt!FsRtlWorkerThread+0x35
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000060 867a0370 0000344 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForMultipleObjects+0x284
ACPI!ACPIWorker+0x47
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000064 867746c8 0000346 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2
dmio!voliod_loop+0x399
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000068 86738640 000031c Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeRemoveQueue+0x22a
NDIS!ndisWorkerThread+0x30
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
4.000070 86631bb8 0000006 Blocked nt!KiSwapContext+0x2f
nt!KiSwapThread+0x6b
nt!KeWaitForSingleObject+0x1c2
nt!NtWaitForSingleObject+0x9a
nt!KiFastCallEntry+0xfc
nt!ZwWaitForSingleObject+0x11
Ntfs!EfsGetSessionKey+0x20
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16

Threads Processed: 26

Max cache size is : 1048576 bytes (0x400 KB)
Total memory in cache : 0 bytes (0 KB)
Number of regions cached: 0
0 full reads broken into 0 partial reads
counts: 0 cached/0 uncached, 0.00% cached
bytes : 0 cached/0 uncached, 0.00% cached
** Transition PTEs are impl

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 6:29 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Sources would not help here, this is purely a build issue (and not
really a runtime issue b/c he can’t get past WdfDriverCreate). A
callstack with WdfDriverCreate (or imp_WdfDriverCreate) resulting from
running the .exr and .cxr (or perhaps finding it in !stacks) goes a long
way here.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Monday, December 05, 2005 4:17 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

It can be even slower. Once I had SMTP debug session with somebody
living in different time zone which resulted in one command and response
daily. It was necessary to use compression – pack more commands in one
e-mail according to presumed results :wink:

I guess it is an example why WDF/KMDF sources should be available. Are
they? If I understand correctly, it was already released but I just
don’t have time to install it and check because just debug WinCE USB
driver and praise MS they included signifficant part of CE sources in PB
installation. Debugging and finding problems is much eaiser.

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 Tony Mason[SMTP:xxxxx@osr.com]
Reply To: Windows System Software Devs Interest List
Sent: Tuesday, December 06, 2005 12:54 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

And this is an excellent example of WinDBG over SMTP (and you thought
that using a serial connection was slow!)

:wink:

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 6:40 PM
To: ntdev redirect
Subject: RE: [ntdev] KMDF10 …

Lm t n

f7587000 f75fd000 Wdf01000 Wdf01000.sys Wed Nov 30 16:03:42 2005

2: kd> kP
ChildEBP RetAddr
f7c9ad4c 805360bf nt!RtlpBreakWithStatusInstruction
f7c9ad98 80536b96 nt!KiBugCheckDebugBreak+0x19
f7c9b178 805371aa nt!KeBugCheck2+0x574
f7c9b198 80633685 nt!KeBugCheckEx+0x1b
f7c9b1b4 80603855 nt!PspUnhandledExceptionInSystemThread+0x1a
f7c9bddc 804efc81 nt!PspSystemThreadStartup+0x5a
00000000 00000000 nt!KiThreadStartup+0x16

Once I saw this happening, I uninstalled and purged the 5054 beta from
my
system. The BUILD I did per your request was done via that environment
using -cZe. I also deleted all instances of WdfXxxx from the target
and
then did a clean install with WdfCoinstaller01000. How then do I
correct
this situation?

By the way, the target is a dual Xeon with HT enabled and 1 gig of
memory.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 5:28 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

…and the resulting “kP” output after you called .cxr.

What I bet is happening is that your driver was not recompiled clean
and
that you are using old jump table offsets in your driver and jumping
into another function (probably WdfDpcWdmGetDpc based on seeing this
issue before). The callstack should confirm this.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 3:18 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I think I found it:

FxObjectHandleGetPtr calls GetObjectFromHandle and gets a WDF handle
(7xxxxxxx), which is moves into edi. It then attempts to compare
[edi+4]
to bx and panics since I do believe 799487a0+4 is not a valid address,
unless WDF structures are mapped to 7xxxxxxx. But, not having the
source,
that is all speculation.

The CXR you requested:

eax=799436a8 ebx=00001001 ecx=00000000 edx=864e7fd0 esi=f7c9b790
edi=799436a8
eip=f75a5213 esp=f7c9b758 ebp=f7c9b76c iopl=0 nv up ei pl zr
na
po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00000246
Wdf01000!FxObjectHandleGetPtr+0x8b:>
f75a5213 66395f04 cmp [edi+0x4],bx
ds:0023:799436ac=???

And the code preceding the IP of f75a5213:

Wdf01000!FxObjectHandleGetPtr+0x84:
f75a520c e8bffdffff call Wdf01000!FxObject::_GetObjectFromHandle
(f75a4fd0)
f75a5211 8bf8 mov edi,eax
f75a5213 66395f04 cmp [edi+0x4],bx
f75a5217 7507 jnz Wdf01000!FxObjectHandleGetPtr+0x98
(f75a5220)
f75a5219 893e mov [esi],edi
f75a521b e980000000 jmp Wdf01000!FxObjectHandleGetPtr+0x118
(f75a52a0)
f75a5220 832600 and dword ptr [esi],0x0
f75a5223 8b07 mov eax,[edi]

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 5:01 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

And .cxr for the callback…

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 2:55 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I assume you mean opening build in a 3790.1830 build and running
set_wdf_env since KMDF has no build environments.

However … doing that still produces the same error.

Here is the information you wanted:

1: kd> .exr fffffffff7c9b690
ExceptionAddress: f75a5213 (Wdf01000!FxObjectHandleGetPtr+0x0000008b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 799487a4
Attempt to read from address 799487a4

It looks like an attempt was made to directly access a WDF object
(799487a4) during manipulation of the registry path in
WdfDriverCreate.
This info was in the first !analyze -v dump.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 4:29 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Please use the DDK build environment first and see if it repros, as
ddkbuild.bat is not a supported build env that we have tested. I bet
there is some work Mark needs to do to get it working with the final
release. We did change the layout of the headers and libs so if
ddkbuild.bat assumes the previous layout, that might be the issue.

Thx
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 2:25 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I use DDKBUILD … I’ll get the call stack next breakpoint.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 4:07 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Are you building in the DDK build environment or via ddkbuild.exe/VS?
to get the real callstack, run the following

.exr fffffffff7c9b690
k

And then send the stack.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 1:26 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF10 …

I installed the released version of WDF and then built and installed
the
resulting driver. The only changes I have made to the sources were
those
required due to changes in WDF. When I load the driver, it panics the>

system in DriverEntry when I call WdfDriverCreate. From the
documentation
I can see no differences in that call. It is a access denied
(C0000005).

I purged the old installation from the target, deleting the olnd INF
files
as well as the WDF files on the target before doing the new install.

Here is !analyze:

1: kd> !analyze -v

************************************************************************

**
*****
*
*
* Bugcheck Analysis
*
*
*

************************************************************************

**
*****

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address
pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this
address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f75a5213, The address that the exception occurred at
Arg3: f7c9b690, Exception Record Address
Arg4: f7c9b38c, Context Record Address

Debugging Details:

*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at “0x%08lx”
referenced memory at “0x%08lx”. The memory could not be “%s”.

FAULTING_IP:
Wdf01000!FxObjectHandleGetPtr+8b
f75a5213 66395f04 cmp [edi+0x4],bx

EXCEPTION_RECORD: f7c9b690 – (.exr fffffffff7c9b690)
ExceptionAddress: f75a5213 (Wdf01000!FxObjectHandleGetPtr+0x0000008b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 79945c1c
Attempt to read from address 79945c1c

CONTEXT: f7c9b38c – (.cxr fffffffff7c9b38c)
eax=79945c18 ebx=00001001 ecx=00000000 edx=864ebc78 esi=f7c9b790
edi=79945c18
eip=f75a5213 esp=f7c9b758 ebp=f7c9b76c iopl=0 nv up ei pl zr
na
po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
Wdf01000!FxObjectHandleGetPtr+0x8b:
f75a5213 66395f04 cmp [edi+0x4],bx
ds:0023:79945c1c=???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at “0x%08lx”
referenced memory at “0x%08lx”. The memory could not be “%s”.

READ_ADDRESS: 79945c1c

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: 80560560 – (!locks 80560560)

Resource @ nt!IopDeviceTreeLock (0x80560560) Shared 1 owning
threads
Threads: 867c23c8-01<*>
1 total locks, 1 locks currently held

FAULTING_THREAD: 867c23c8

PNP_TRIAGE:
Lock address : 0x80560560
Thread Count : 1
Thread address: 0x867c23c8
Thread wait : 0x3a0

LAST_CONTROL_TRANSFER: from 805360bf to 804e2a52

STACK_TEXT:
f7c9ad4c 805360bf 00000003 f7c9b0a8 00000000
nt!RtlpBreakWithStatusInstruction
f7c9ad98 80536b96 00000003 00000000 00000000
nt!KiBugCheckDebugBreak+0x19
f7c9b178 805371aa 0000007e c0000005 f75a5213 nt!KeBugCheck2+0x574
f7c9b198 80633685 0000007e c0000005 f75a5213 nt!KeBugCheckEx+0x1b
f7c9b1b4 80603855 f7c9b1dc 804e2f39 f7c9b1e4
nt!PspUnhandledExceptionInSystemThread+0x1a
f7c9bddc 804efc81 804e22f1 00000001 00000000
nt!PspSystemThreadStartup+0x5a
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
Wdf01000!FxObjectHandleGetPtr+8b
f75a5213 66395f04 cmp [edi+0x4],bx

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Wdf01000!FxObjectHandleGetPtr+8b

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 438e21be

FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxObjectHandleGetPtr+8b

BUCKET_ID: 0x7E_Wdf01000!FxObjectHandleGetPtr+8b>

Followup: MachineOwner

Gary G. Little


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@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: xxxxx@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: xxxxx@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: xxxxx@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: xxxxx@osr.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


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

Further information on this issue:

The target has the following files installed:

WdfCoinstaller01000.dll 11/30/05
Wdf01000.cat 11/30/05
Wdf01000.sys 11/30/05
WdfLdr.sys 11/30/05

These are the only Wdf… files on the system disc. Since all the files
have the same date, and a time around 1400, I assume I have KMDF 1.0
installed on the target.

I am truly stymied at this point. But, I don’t see anyone else bellowing
about the same problem, so I can only assume it’s some leftover piece
flotsam from 5054 that is causing the difficulty. What, at this time I
have no idea.

Gary G. Little

Presumably you can verify this theory that it’s a leftover from WDF 5054
by installing the build env and runtime on a cleanly installed OS
(perhaps on a different partition if you have a shortage of machines)…
I’m not saying that’s pleasant, but neither is debugging over SMTP :-).

xxxxx@seagate.com wrote:

Further information on this issue:

The target has the following files installed:

WdfCoinstaller01000.dll 11/30/05
Wdf01000.cat 11/30/05
Wdf01000.sys 11/30/05
WdfLdr.sys 11/30/05

These are the only Wdf… files on the system disc. Since all the files
have the same date, and a time around 1400, I assume I have KMDF 1.0
installed on the target.

I am truly stymied at this point. But, I don’t see anyone else bellowing
about the same problem, so I can only assume it’s some leftover piece
flotsam from 5054 that is causing the difficulty. What, at this time I
have no idea.

Gary G. Little


Ray

Doron nailed it yesterday when he called it a build, and not a runtime
problem. My build process has not been properly updating libraries I build
before I link the SYS file. The libraries being used were built on the
2nd, but I installed KMDF on the 3rd. I’m working on my build process to
generate the proper libraries and resolve the problem.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Tuesday, December 06, 2005 9:55 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Well I was curious so I set out last night to port a usb wdf driver of
mine to the KMDF10 release. Compilation and build went fine after fixing
up the rather minimal DDI changes. My attempt to install on a XP64
system failed - first because the inf file format for the coinstaller
changed, and then because I got some as yet undebugged failure in driver
entry (error 37 in setupapi.log.) I don’t think this is quite Mr.
Little’s experience, and I’m fairly confident that I am suffering from
operator error on some level. Anyhow more to follow when I manage to get
some more cycles on it.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Tuesday, December 06, 2005 10:16 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

This is the first time I have seen this in the field. Make sure that
all the previous beta headers are no longer in the build environment and
that you are picking up the release headers (C:\WINDDK\WDF\KMDF10\inc on
my machine).

d

I already can’t keep up with the traffic from the email reflector. The
idea of trying this though IM is terrifying :slight_smile:

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Monday, December 05, 2005 8:32 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] KMDF10 …

It can be even slower. Once I had SMTP debug session with somebody
living in different time zone which resulted in one command and
response daily. It was necessary to use compression – pack more
commands in one e-mail according to presumed results :wink:

MSN Messenger is a good tool for WinDbg.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.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

Check c:\windows\setupact.log as well - the coinstaller puts out some
pretty detailed information about what its trying to do and whether it’s
been successful.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Tuesday, December 06, 2005 7:55 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Well I was curious so I set out last night to port a usb wdf driver of
mine to the KMDF10 release. Compilation and build went fine after fixing
up the rather minimal DDI changes. My attempt to install on a XP64
system failed - first because the inf file format for the coinstaller
changed, and then because I got some as yet undebugged failure in driver
entry (error 37 in setupapi.log.) I don’t think this is quite Mr.
Little’s experience, and I’m fairly confident that I am suffering from
operator error on some level. Anyhow more to follow when I manage to get
some more cycles on it.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Tuesday, December 06, 2005 10:16 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

This is the first time I have seen this in the field. Make sure that
all the previous beta headers are no longer in the build environment and
that you are picking up the release headers (C:\WINDDK\WDF\KMDF10\inc on
my machine).

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, December 06, 2005 6:45 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I did use a 3790.1830 checked build shell and a “pure” build using the
DDK only (no sshhtinking DDKBUILD :)). The end result was the same. It
crashed on a “cmp [edi+4], bx” with edi set to 79xxxxxx. Since that
test, all of my builds have been using DDKBUILD since I can do that from
VS in a single run.

That I have not completely purged the 5054 build of the WDF, is highly
likely, but the question is … what did I miss that is causing this
conflict, and how do I rectify the problem? I’ve fellow developers
waiting to use KMDF10 to release a driver we have been working on for
beta testing. If I have the problem, I’m sure they have it, and I’d
certainly like to determine the proper procedure to migrate from 5054.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Monday, December 05, 2005 7:48 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Ddkbuild assumes almost nothing. It limits its assumptions to the
instructions provided for invoking ‘setenv.bat’ and little else. That is
essentially the point of the whole mess. On the other hand, if the
instructions for building KMDF drivers have changed significantly then
there could be issues.

So what ddkbuild does is it runs the target ddk setenv.bat script and
then it runs the target wdf set_wdf_env.bat script and then it runs
build.
This
ought to be exactly what happens when one creates a command shell and
does things manually. Of course WDF_ROOT has to be set correctly (Gary -
you should check to make sure this is true - but as you claimed to have
purged the old WDF it must be true.) And of course you have to have
WDF_DDK pointed at 3790.1830.

Anyhow, Doron is right - pop a shell and run a clean build from a shell.
Eliminate everything extraneous.

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032 www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 5:29 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Please use the DDK build environment first and see if it repros, as
ddkbuild.bat is not a supported build env that we have tested. I bet
there is some work Mark needs to do to get it working with the final
release. We did change the layout of the headers and libs so if
ddkbuild.bat assumes the previous layout, that might be the issue.

Thx
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 2:25 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I use DDKBUILD … I’ll get the call stack next breakpoint.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, December 05, 2005 4:07 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Are you building in the DDK build environment or via ddkbuild.exe/VS?
to get the real callstack, run the following

.exr fffffffff7c9b690
k

And then send the stack.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Monday, December 05, 2005 1:26 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF10 …

I installed the released version of WDF and then built and installed
the resulting driver. The only changes I have made to the sources were

those required due to changes in WDF.
When I load the driver, it panics the system in DriverEntry when I
call WdfDriverCreate. From the documentation I can see no differences
in that call. It is a access denied (C0000005).

I purged the old installation from the target, deleting the olnd INF
files as well as the WDF files on the target before doing the new
install.

Here is !analyze:

1: kd> !analyze -v
**************************************************************
**********
**
*****
*
*
* Bugcheck Analysis
*
*
*
**************************************************************
**********
**
*****

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common
bugcheck. Usually the exception address pinpoints the driver/function

that caused the problem. Always note this address as well as the link

date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f75a5213, The address that the exception occurred at
Arg3: f7c9b690, Exception Record Address
Arg4: f7c9b38c, Context Record Address

Debugging Details:

*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000
*** Error in in reading nt!_ETHREAD @ 00000000

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at “0x%08lx”
referenced memory at “0x%08lx”. The memory could not be “%s”.

FAULTING_IP:
Wdf01000!FxObjectHandleGetPtr+8b
f75a5213 66395f04 cmp [edi+0x4],bx

EXCEPTION_RECORD: f7c9b690 – (.exr fffffffff7c9b690)
ExceptionAddress: f75a5213 (Wdf01000!FxObjectHandleGetPtr+0x0000008b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 79945c1c
Attempt to read from address 79945c1c

CONTEXT: f7c9b38c – (.cxr fffffffff7c9b38c)
eax=79945c18 ebx=00001001 ecx=00000000 edx=864ebc78 esi=f7c9b790
edi=79945c18
eip=f75a5213 esp=f7c9b758 ebp=f7c9b76c iopl=0 nv up
ei pl zr na
po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
Wdf01000!FxObjectHandleGetPtr+0x8b:
f75a5213 66395f04 cmp [edi+0x4],bx
ds:0023:79945c1c=???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at “0x%08lx”
referenced memory at “0x%08lx”. The memory could not be “%s”.

READ_ADDRESS: 79945c1c

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: 80560560 – (!locks 80560560)

Resource @ nt!IopDeviceTreeLock (0x80560560) Shared 1
owning threads
Threads: 867c23c8-01<*>
1 total locks, 1 locks currently held

FAULTING_THREAD: 867c23c8

PNP_TRIAGE:
Lock address : 0x80560560
Thread Count : 1
Thread address: 0x867c23c8
Thread wait : 0x3a0

LAST_CONTROL_TRANSFER: from 805360bf to 804e2a52

STACK_TEXT:
f7c9ad4c 805360bf 00000003 f7c9b0a8 00000000
nt!RtlpBreakWithStatusInstruction
f7c9ad98 80536b96 00000003 00000000 00000000
nt!KiBugCheckDebugBreak+0x19
f7c9b178 805371aa 0000007e c0000005 f75a5213 nt!KeBugCheck2+0x574
f7c9b198 80633685 0000007e c0000005 f75a5213 nt!KeBugCheckEx+0x1b
f7c9b1b4 80603855 f7c9b1dc 804e2f39 f7c9b1e4
nt!PspUnhandledExceptionInSystemThread+0x1a
f7c9bddc 804efc81 804e22f1 00000001 00000000
nt!PspSystemThreadStartup+0x5a 00000000 00000000 00000000 00000000
00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
Wdf01000!FxObjectHandleGetPtr+8b
f75a5213 66395f04 cmp [edi+0x4],bx

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Wdf01000!FxObjectHandleGetPtr+8b

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 438e21be

FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxObjectHandleGetPtr+8b

BUCKET_ID: 0x7E_Wdf01000!FxObjectHandleGetPtr+8b

Followup: MachineOwner

Gary G. Little


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as:
xxxxx@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:
xxxxx@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: xxxxx@seagate.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: xxxxx@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

Oh com’on guys … this ain’t debug via email. Its Doron smacking me up
side the head for not believing what I was seeing. Besides … if you want
slow, try debugging using an acoustic coupler at 300 baud. But then, in
1974 that was FAST!!!

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
Sent: Tuesday, December 06, 2005 1:45 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I already can’t keep up with the traffic from the email reflector. The
idea of trying this though IM is terrifying :slight_smile:

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Monday, December 05, 2005 8:32 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] KMDF10 …

It can be even slower. Once I had SMTP debug session with somebody
living in different time zone which resulted in one command and
response daily. It was necessary to use compression – pack more
commands in one e-mail according to presumed results :wink:

MSN Messenger is a good tool for WinDbg.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.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

Operating a mailing list through IM (10,000 member chatroom, anyone?) is
indeed overwhelming.

For two devs working through an issue that is only marginally interesting
to the rest of the mailing list, IM is quite an improvement over remote
desktop by SMTP. :slight_smile:

Sometimes it can take a while to ascertain that the issue you suspect is
globally interesting (A bug in the library or released tool) really is due
to quirks of your own environment.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
Sent: Tuesday, December 06, 2005 12:45 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I already can’t keep up with the traffic from the email reflector. The
idea of trying this though IM is terrifying :slight_smile:

-p

Ah, but the opportunity to watch Gary embarrass himself publicly is…
priceless.

And remember, the list has a VERY long memory…

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Looking forward to seeing you at the next OSR File Systems class in
Boston, MA April 24-27, 2006.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, December 06, 2005 2:59 PM
To: ntdev redirect
Subject: RE: [ntdev] KMDF10 …

Operating a mailing list through IM (10,000 member chatroom, anyone?) is
indeed overwhelming.

For two devs working through an issue that is only marginally
interesting
to the rest of the mailing list, IM is quite an improvement over remote
desktop by SMTP. :slight_smile:

Sometimes it can take a while to ascertain that the issue you suspect is
globally interesting (A bug in the library or released tool) really is
due
to quirks of your own environment.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
Sent: Tuesday, December 06, 2005 12:45 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I already can’t keep up with the traffic from the email reflector. The
idea of trying this though IM is terrifying :slight_smile:

-p


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Somebody in my generation once said “I don’t get no respect”. Oh well …
so live with it.

However … there really has been a change in KMDF that really is causing
a problem, or at least unexpected behavior. The culprit is in project.mk,
which I continue to use since my project is based on the PCIDRV example.

The KMDF10 project.mk defines TARGETPATH=obj, but the 5054 project.mk did
not. In my sources files I define my library builds with TARGETPATH=lib,
and all my lib’s were placed in the .\lib\i386 directory. Since project.mk
sets TARGETPATH to obj, and all my libs were going to
objchk_wnet_x86\i386, I can only assume the define in project.mk took
precedence over my define. Now THAT is not nice.

Anyway … I modified all of the lib references from …\lib\i386.. to
…$(TARGETPATH)$(TARGET_DIRECTORY).. Now my libraries are found and the
drivers build and load. This may or may not be a real live problem, but it
certainly is a behavioral change where a heads-up would be nice. The
caveat is that this changed forced a closer look at our sources files and
I think produced a good modification that will incorporate other CPU
builds.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Tuesday, December 06, 2005 2:36 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

Ah, but the opportunity to watch Gary embarrass himself publicly is…
priceless.

And remember, the list has a VERY long memory…

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Looking forward to seeing you at the next OSR File Systems class in
Boston, MA April 24-27, 2006.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, December 06, 2005 2:59 PM
To: ntdev redirect
Subject: RE: [ntdev] KMDF10 …

Operating a mailing list through IM (10,000 member chatroom, anyone?) is
indeed overwhelming.

For two devs working through an issue that is only marginally
interesting
to the rest of the mailing list, IM is quite an improvement over remote
desktop by SMTP. :slight_smile:

Sometimes it can take a while to ascertain that the issue you suspect is
globally interesting (A bug in the library or released tool) really is
due
to quirks of your own environment.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
Sent: Tuesday, December 06, 2005 12:45 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF10 …

I already can’t keep up with the traffic from the email reflector. The
idea of trying this though IM is terrifying :slight_smile:

-p


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@osr.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

Sorry, he isn’t really in our generation. I think he was one higher than
ours. Rodney was good and his routines good for you when the world was
trying to get you down. Life is fun, sometimes. When will those drives
(FDE) show up on the market?

wrote in message news:xxxxx@ntdev…
> Somebody in my generation once said “I don’t get no respect”. Oh well …
> so live with it.
>
> However … there really has been a change in KMDF that really is causing
> a problem, or at least unexpected behavior. The culprit is in project.mk,
> which I continue to use since my project is based on the PCIDRV example.
>
> The KMDF10 project.mk defines TARGETPATH=obj, but the 5054 project.mk did
> not. In my sources files I define my library builds with TARGETPATH=lib,
> and all my lib’s were placed in the .\lib\i386 directory. Since project.mk
> sets TARGETPATH to obj, and all my libs were going to
> objchk_wnet_x86\i386, I can only assume the define in project.mk took
> precedence over my define. Now THAT is not nice.
>
> Anyway … I modified all of the lib references from …\lib\i386.. to
> …$(TARGETPATH)$(TARGET_DIRECTORY).. Now my libraries are found and the
> drivers build and load. This may or may not be a real live problem, but it
> certainly is a behavioral change where a heads-up would be nice. The
> caveat is that this changed forced a closer look at our sources files and
> I think produced a good modification that will incorporate other CPU
> builds.
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
> Sent: Tuesday, December 06, 2005 2:36 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] KMDF10 …
>
> Ah, but the opportunity to watch Gary embarrass himself publicly is…
> priceless.
>
> And remember, the list has a VERY long memory…
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> Looking forward to seeing you at the next OSR File Systems class in
> Boston, MA April 24-27, 2006.
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, December 06, 2005 2:59 PM
> To: ntdev redirect
> Subject: RE: [ntdev] KMDF10 …
>
> Operating a mailing list through IM (10,000 member chatroom, anyone?) is
> indeed overwhelming.
>
> For two devs working through an issue that is only marginally
> interesting
> to the rest of the mailing list, IM is quite an improvement over remote
> desktop by SMTP. :slight_smile:
>
> Sometimes it can take a while to ascertain that the issue you suspect is
> globally interesting (A bug in the library or released tool) really is
> due
> to quirks of your own environment.
>
> Phil
>
> Philip D. Barila
> Seagate Technology LLC
> (720) 684-1842
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
> Sent: Tuesday, December 06, 2005 12:45 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] KMDF10 …
>
> I already can’t keep up with the traffic from the email reflector. The
> idea of trying this though IM is terrifying :slight_smile:
>
> -p
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@osr.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
>
>