RE: .kdfiles problem

WINDBG
1

Drew,

Would that include having a bogus local (host) path in the mapfile?

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 Drew Bliss
Sent: Tuesday, February 07, 2006 12:37 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

That means that the target requested a remote file open but did not do
any I/O. It means that .kdfiles is active but not having any effect.
There’s no way for kd to know exactly why not, it can only warn that no
I/O was done.

The usual cause for this is that something interfered with the copying
on the target side, such as an antivirus or protection product
preventing access to the driver file on the target.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

Drew,

When using .kdfiles to map to a newer version of a driver, what does
“WARNING: No file I/O done by target, .kdfiles files may not be updated”
mean? I’ve rebuilt the driver and want it to load, but it does not when
this message is displayed. How do I correct the problem that this
message warns me about?

Gary G. Little

2

No, the warning should only occur on close of a successfully opened host
file.

If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
info about .kdfiles operations. On an open request from the target you
should see

KdFile request for ‘’ returns

and that’ll tell you whether the host file opened or not.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 12:06 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

Drew,

Would that include having a bogus local (host) path in the mapfile?

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 Drew Bliss
Sent: Tuesday, February 07, 2006 12:37 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

That means that the target requested a remote file open but did not do
any I/O. It means that .kdfiles is active but not having any effect.
There’s no way for kd to know exactly why not, it can only warn that no
I/O was done.

The usual cause for this is that something interfered with the copying
on the target side, such as an antivirus or protection product
preventing access to the driver file on the target.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

Drew,

When using .kdfiles to map to a newer version of a driver, what does
“WARNING: No file I/O done by target, .kdfiles files may not be updated”
mean? I’ve rebuilt the driver and want it to load, but it does not when
this message is displayed. How do I correct the problem that this
message warns me about?

Gary G. Little

—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

3

On my driver file I get
KdFile request for ‘\SystemRoot\system32\DRIVERS\Sk_SiI3124.sys’ returns
00000000

But later I get:
KdFile request for ‘\SystemRoot\system32\DRIVERS\WDFLDR.SYS’ returns
C000000F

So … kdfiles is not loading WDFLDR.SYS. I may be wrong but KMDF10 uses
wdf0100.sys. If that is so then it looks as though my upgrade to KMDF left
some trash behind.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Tuesday, February 07, 2006 2:22 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

No, the warning should only occur on close of a successfully opened host
file.

If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
info about .kdfiles operations. On an open request from the target you
should see

KdFile request for ‘’ returns

and that’ll tell you whether the host file opened or not.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 12:06 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

Drew,

Would that include having a bogus local (host) path in the mapfile?

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 Drew Bliss
Sent: Tuesday, February 07, 2006 12:37 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

That means that the target requested a remote file open but did not do
any I/O. It means that .kdfiles is active but not having any effect.
There’s no way for kd to know exactly why not, it can only warn that no
I/O was done.

The usual cause for this is that something interfered with the copying
on the target side, such as an antivirus or protection product
preventing access to the driver file on the target.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

Drew,

When using .kdfiles to map to a newer version of a driver, what does
“WARNING: No file I/O done by target, .kdfiles files may not be updated”
mean? I’ve rebuilt the driver and want it to load, but it does not when
this message is displayed. How do I correct the problem that this
message warns me about?

Gary G. Little

—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

That appears to have bee the problem. I removed my driver(s), deleted the
INF files and sys files, then deleted all instances of WDF I found on the
boot drive. After another install I find .kdfiles now working.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G Little
Sent: Tuesday, February 07, 2006 2:51 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

On my driver file I get
KdFile request for ‘\SystemRoot\system32\DRIVERS\Sk_SiI3124.sys’ returns
00000000

But later I get:
KdFile request for ‘\SystemRoot\system32\DRIVERS\WDFLDR.SYS’ returns
C000000F

So … kdfiles is not loading WDFLDR.SYS. I may be wrong but KMDF10 uses
wdf0100.sys. If that is so then it looks as though my upgrade to KMDF left
some trash behind.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Tuesday, February 07, 2006 2:22 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

No, the warning should only occur on close of a successfully opened host
file.

If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
info about .kdfiles operations. On an open request from the target you
should see

KdFile request for ‘’ returns

and that’ll tell you whether the host file opened or not.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 12:06 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

Drew,

Would that include having a bogus local (host) path in the mapfile?

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 Drew Bliss
Sent: Tuesday, February 07, 2006 12:37 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

That means that the target requested a remote file open but did not do
any I/O. It means that .kdfiles is active but not having any effect.
There’s no way for kd to know exactly why not, it can only warn that no
I/O was done.

The usual cause for this is that something interfered with the copying
on the target side, such as an antivirus or protection product
preventing access to the driver file on the target.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten

Drew,

When using .kdfiles to map to a newer version of a driver, what does
“WARNING: No file I/O done by target, .kdfiles files may not be updated”
mean? I’ve rebuilt the driver and want it to load, but it does not when
this message is displayed. How do I correct the problem that this
message warns me about?

Gary G. Little

—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

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

5

KMDF uses both of those sys files, WDFLDR is the loader stub and WDF0100 is
the actual library.

-scott

–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
> On my driver file I get
> KdFile request for ‘\SystemRoot\system32\DRIVERS\Sk_SiI3124.sys’ returns
> 00000000
>
> But later I get:
> KdFile request for ‘\SystemRoot\system32\DRIVERS\WDFLDR.SYS’ returns
> C000000F
>
> So … kdfiles is not loading WDFLDR.SYS. I may be wrong but KMDF10 uses
> wdf0100.sys. If that is so then it looks as though my upgrade to KMDF left
> some trash behind.
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
> Sent: Tuesday, February 07, 2006 2:22 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> No, the warning should only occur on close of a successfully opened host
> file.
>
> If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
> info about .kdfiles operations. On an open request from the target you
> should see
>
> KdFile request for ‘’ returns
>
> and that’ll tell you whether the host file opened or not.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 12:06 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> Drew,
>
> Would that include having a bogus local (host) path in the mapfile?
>
> 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 Drew Bliss
> Sent: Tuesday, February 07, 2006 12:37 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> That means that the target requested a remote file open but did not do
> any I/O. It means that .kdfiles is active but not having any effect.
> There’s no way for kd to know exactly why not, it can only warn that no
> I/O was done.
>
> The usual cause for this is that something interfered with the copying
> on the target side, such as an antivirus or protection product
> preventing access to the driver file on the target.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 11:29 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> Drew,
>
> When using .kdfiles to map to a newer version of a driver, what does
> “WARNING: No file I/O done by target, .kdfiles files may not be updated”
> mean? I’ve rebuilt the driver and want it to load, but it does not when
> this message is displayed. How do I correct the problem that this
> message warns me about?
>
> Gary G. Little
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

6

Well, after removing the WDF files and reinstalling the
driver/wdfconistaller01000, KDFILES is working, so I can only assume the
old WDF files had a high level of bogosity.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, February 07, 2006 3:04 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles problem

KMDF uses both of those sys files, WDFLDR is the loader stub and WDF0100
is
the actual library.

-scott

–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
> On my driver file I get
> KdFile request for ‘\SystemRoot\system32\DRIVERS\Sk_SiI3124.sys’ returns
> 00000000
>
> But later I get:
> KdFile request for ‘\SystemRoot\system32\DRIVERS\WDFLDR.SYS’ returns
> C000000F
>
> So … kdfiles is not loading WDFLDR.SYS. I may be wrong but KMDF10 uses
> wdf0100.sys. If that is so then it looks as though my upgrade to KMDF
left
> some trash behind.
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
> Sent: Tuesday, February 07, 2006 2:22 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> No, the warning should only occur on close of a successfully opened host
> file.
>
> If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
> info about .kdfiles operations. On an open request from the target you
> should see
>
> KdFile request for ‘’ returns
>
> and that’ll tell you whether the host file opened or not.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 12:06 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> Drew,
>
> Would that include having a bogus local (host) path in the mapfile?
>
> 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 Drew Bliss
> Sent: Tuesday, February 07, 2006 12:37 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> That means that the target requested a remote file open but did not do
> any I/O. It means that .kdfiles is active but not having any effect.
> There’s no way for kd to know exactly why not, it can only warn that no
> I/O was done.
>
> The usual cause for this is that something interfered with the copying
> on the target side, such as an antivirus or protection product
> preventing access to the driver file on the target.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 11:29 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> Drew,
>
> When using .kdfiles to map to a newer version of a driver, what does
> “WARNING: No file I/O done by target, .kdfiles files may not be updated”
> mean? I’ve rebuilt the driver and want it to load, but it does not when
> this message is displayed. How do I correct the problem that this
> message warns me about?
>
> Gary G. Little
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

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

7

Huh? If you are mixing beta KMDF implementation with a driver built
with the released 1.0 headers+libs, that is not a supported scenario.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 4:11 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

Well, after removing the WDF files and reinstalling the
driver/wdfconistaller01000, KDFILES is working, so I can only assume the
old WDF files had a high level of bogosity.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, February 07, 2006 3:04 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles problem

KMDF uses both of those sys files, WDFLDR is the loader stub and WDF0100
is
the actual library.

-scott

–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
> On my driver file I get
> KdFile request for ‘\SystemRoot\system32\DRIVERS\Sk_SiI3124.sys’
returns
> 00000000
>
> But later I get:
> KdFile request for ‘\SystemRoot\system32\DRIVERS\WDFLDR.SYS’ returns
> C000000F
>
> So … kdfiles is not loading WDFLDR.SYS. I may be wrong but KMDF10
uses
> wdf0100.sys. If that is so then it looks as though my upgrade to KMDF
left
> some trash behind.
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
> Sent: Tuesday, February 07, 2006 2:22 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> No, the warning should only occur on close of a successfully opened
host
> file.
>
> If you run with ctrl-d (Ctrl+Alt+d in windbg) you’ll get more
> info about .kdfiles operations. On an open request from the target
you
> should see
>
> KdFile request for ‘’ returns
>
> and that’ll tell you whether the host file opened or not.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 12:06 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] .kdfiles problem
>
> Drew,
>
> Would that include having a bogus local (host) path in the mapfile?
>
> 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 Drew Bliss
> Sent: Tuesday, February 07, 2006 12:37 PM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> That means that the target requested a remote file open but did not do
> any I/O. It means that .kdfiles is active but not having any effect.
> There’s no way for kd to know exactly why not, it can only warn that
no
> I/O was done.
>
> The usual cause for this is that something interfered with the copying
> on the target side, such as an antivirus or protection product
> preventing access to the driver file on the target.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@seagate.com
> Sent: Tuesday, February 07, 2006 11:29 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Command I’ve forgotten
>
> Drew,
>
> When using .kdfiles to map to a newer version of a driver, what does
> “WARNING: No file I/O done by target, .kdfiles files may not be
updated”
> mean? I’ve rebuilt the driver and want it to load, but it does not
when
> this message is displayed. How do I correct the problem that this
> message warns me about?
>
> Gary G. Little
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag
argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

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

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

8

I’m pretty sure the mixing wasn’t intentional… :slight_smile:

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 Doron Holan
Sent: Tuesday, February 07, 2006 5:22 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] .kdfiles problem

Huh? If you are mixing beta KMDF implementation with a driver built
with the released 1.0 headers+libs, that is not a supported scenario.

d

9

Nope … It was not the building of the drivers, it was the installing. I

had to do a system restore on the target disc to a pre-KMDF install. I

removed my driver but not the WDF files. Big oops. The driver that was

working was installed with KMDF WDf files so it worked.

Gary G. Little

-----Original Message-----

From: xxxxx@lists.osr.com

[mailto:xxxxx@lists.osr.com] On Behalf Of

xxxxx@seagate.com

Sent: Tuesday, February 07, 2006 7:01 PM

To: Kernel Debugging Interest List

Subject: RE: [windbg] .kdfiles problem

I’m pretty sure the mixing wasn’t intentional… :slight_smile:

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 Doron Holan

Sent: Tuesday, February 07, 2006 5:22 PM

To: Kernel Debugging Interest List

Subject: RE: [windbg] .kdfiles problem

Huh? If you are mixing beta KMDF implementation with a driver built

with the released 1.0 headers+libs, that is not a supported scenario.

d

You are currently subscribed to windbg as: glittle@mn.rr.com

To unsubscribe send a blank email to xxxxx@lists.osr.com

__________ NOD32 1.1398 (20060207) Information __________

This message was checked by NOD32 antivirus system.

http://www.eset.com http:</http:>