WDM and Softice

In SoftIce, you use

? PMY_DEVICE_EXTENSION(xxxxxxxx + 0x28)
or
watch PMY_DEVICE_EXTENSION(xxxxxxxx + 0x28)

where xxxxxxxx is a device object address in hex.

Shahar


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas Stylianides
Sent: Thursday, March 31, 2005 11:03 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice

Thanks everybody for your response. My question was clearly aswered.

Global variables are used when they addressed in DriverObject. I have
allready a banch of global variables which can be enclosed in a
DeviceExtension structure because they address in Device Objects.

Softice is able to format an address space in whatever type I want (not
clear to me but I will read the documentation more carefully and find out
how).

The conversation about WDF really tricked my curiosity. Although it Is not
in my intend to port my driver right now according to this new model, I will
safe some time in order to find out more and experiment with it. The debate
was just excellent.


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

Thank you very much. This is very helpful for my weird request. Sometimes
hardware guys do not trust software and need to access the hardware
manually. This way you save a lot of time trying to convince that a bug is
pure hardware.

Thank you very much.


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Thursday, March 31, 2005 12:12 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice

In SoftIce, you use

? PMY_DEVICE_EXTENSION(xxxxxxxx + 0x28)

or

watch PMY_DEVICE_EXTENSION(xxxxxxxx + 0x28)

where xxxxxxxx is a device object address in hex.

Shahar


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas Stylianides
Sent: Thursday, March 31, 2005 11:03 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice

Thanks everybody for your response. My question was clearly aswered.

Global variables are used when they addressed in DriverObject. I have
allready a banch of global variables which can be enclosed in a
DeviceExtension structure because they address in Device Objects.

Softice is able to format an address space in whatever type I want (not
clear to me but I will read the documentation more carefully and find out
how).

The conversation about WDF really tricked my curiosity. Although it Is not
in my intend to port my driver right now according to this new model, I will
safe some time in order to find out more and experiment with it. The debate
was just excellent.


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

Not at the moment.

=====================
Mark Roddy
Windows .NET/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 Maxim
S. Shatskih
Sent: Thursday, March 31, 2005 3:57 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDM and Softice

Is the WDF framework provided with full source?

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Roddy, Mark”
> To: “Windows System Software Devs Interest List”
> Sent: Wednesday, March 30, 2005 10:36 PM
> Subject: RE: [ntdev] WDM and Softice
>
>
> > Don’s points are well taken but they are counterbalanced by
> the other side,
> > expressed by both myself and by Peter, that WDF contains a
> standard and
> > correct* implementation of the PnP/PowerManagement
> infrastructure support
> > required of any WDM driver, and for that alone it is worth
> considering.
> >
> > AFAIC the showstopper is not quality or documentation but
> instability of the
> > API and lack of committed release dates. Peter’s October
> time frame for his
> > Big Deal Drivers might be aligned with an actual release of WDF, I
> > certainly wouldn’t know, but until I do know that the API
> is locked in and
> > that there is an actual release date for something which is
> shippable (like
> > for example a public beta) I can’t advise people to go WDF
> right now.
> >
> >
> > *correct not in the sense of provably correct, rather in
> the sense of it has
> > a low probability of major bugs :slight_smile:
> >
> > =====================
> > Mark Roddy
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> > Sent: Wednesday, March 30, 2005 1:20 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] WDM and Softice
> >
> > Peter,
> >
> > I agree with the principles of WDF and am hoping for
> the best on its
> > implemtation. But at the moment, I have had zero luck with
> getting anything
> > in the way of a driver that is not a simple clone of the
> WDF samples going.
> > With the current beta I run into:
> >
> > 1. It ain’t documented
> > 2. It is documented and the docs are wrong
> > 3. It doesn’t work (is this me, or is this WDF
> can’t tell since
> > there are only a few stock samples and no doc!)
> >
> > I have been build a large set of drivers for a
> project, the target is
> > Longhorn so WDF should be my friend. But it is totally
> worthless at the
> > moment to me, because the one condition of the project is
> “No discussions of
> >
> > anything that could allow Redmond to know what we are
> doing!”. From what I
> >
> > have seen, either you need to be doing something that you
> can find an
> > example of every call in the samples, you are willing to
> ask a ton of
> > questions on the beta group (and hope they are answered
> with something other
> > than “We changed that wait for the next drop”), or you can
> get inside
> > Redmond to read the source.
> >
> > I did believe in WDF strongly, now someone is going to
> have to prove to
> > me it is not a waste of time.
> >
> >
> > –
> > Don Burn (MVP, Windows DDK)
> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > Remove StopSpam from the email to reply
> >
> >
> >
> > “Peter Viscarola (OSR)” wrote in message
> > news:xxxxx@ntdev…
> > > Roddy, Mark wrote:
> > >> However WDF is neither released nor is the Beta
> currently locked in to
> > >> its
> > >> api, nor is the Beta release without ‘issues’, so ‘going
> with WDF’ at
> > >> this
> > >> point in time is problematic.
> > >
> > > All reasonably valid points.
> > >
> > > However I can tell you that I, personally, would not
> implement a new
> > > device driver using WDM at this point in time, if the WDF
> kernel mode
> > > driver framework was applicable to the device class in question.
> > >
> > > In fact, we’re about to start a new driver for a very
> high-profile piece
> > > of hardware… the driver nees to ship in the Sept/Oct
> timeframe… and
> > > we’re going to use WDF.
> > >
> > > Now, consider that I’ve been writing WDM drivers for more
> than 5 years,
> > > have access to some pretty decent resources for WDM
> assistance, and
> > > already have PnP/Power code that I think works pretty well.
> > >
> > > I STILL choose WDF.
> > >
> > > Peter
> > > OSR
> > >
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@stratus.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@storagecraft.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@hollistech.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

> -----Original Message-----

From: xxxxx@lists.osr.com [mailto:bounce-205209-
xxxxx@lists.osr.com] On Behalf Of Michal Vodicka

savoured enough single stepping and disassembling framework/support
library code when I developed NDIS drivers.

NT assembly code is relatively easy to read with public symbols, even easier
than poorly written C/C++ code. But lack of sources for any framework
certainly discourages the adoption no matter who wrote it.

Currently, drivers for the majority of HW devices (the essential HW OS
needed to provide basic service, such as video, audio, network, storage etc)
don't fit into the WDF, instead they're miniport/miniclass drivers wrapped
by libraries either dynamically or statically (AGPLIB is a sample). This is
another valid reason why WDF is not so popular at this time. I do hope MS
will get rid off all of miniport/port and class/miniclass model and I could
use WDF to write drivers for video, network or even FSD. Would that happen
in the near future?

Just my CND$0.024 worth.

Calvin

Calvin Guan Software Engineer
ATI Technologies Inc. www.ati.com

> will get rid off all of miniport/port and class/miniclass model and I could

use WDF to write drivers for video, network or even FSD. Would that happen
in the near future?

Unlikely. We will have NDIS 6 in Longhorn.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Calvin Guan[SMTP:xxxxx@ati.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, March 31, 2005 7:40 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-205209-
> xxxxx@lists.osr.com] On Behalf Of Michal Vodicka

> savoured enough single stepping and disassembling framework/support
> library code when I developed NDIS drivers.

NT assembly code is relatively easy to read with public symbols, even easier
than poorly written C/C++ code.

I’d agree but still source code is better. Especially when docs is missing or wrong; there are comments, variable and parameter names etc. Sources are important for understanding, for example FastFat source in the IFS kit is invaluable. Quick searching can save days of debugging and disassembling.

The important part for me in WDF is power management and USB selective suspend support. With all respect to MS developers I’d prefer to see sources before use to avoid future problems because similar code in DDK sample isn’t quite correct. When I examined WDF some time before it was commented out from samples and docs were under construction. Quite discouraging if sources are unavailable.

Finally, I see no good reason why framework sources aren’t available. MS wouldn’t lose anything, only gain. It isn’t native part of system. BTW, was noticed any bad effect of last year (or when in was) NT4 and w2k sources leak?

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

I’m afraid it might take the “off topic” direction, but I was quite vocal
about supressing the leak, bad effect of leak etc., etc. So once again I
will justify my args. I dont think it was widely published. Once leaked and
captivated is bit different. If MS gives out willingly, it’s a different
topic altogether. And I completely agree that if it is not base OS, having
source is going to help. If the source is about 100,000 lines or more, I
personally dont want to base my development, at least not so easily, with
the hope that I have 100+ thousands of source. But it might be good to have
while debugging down the trees of the forest. I WOULDN’T CERTAINLY OBJECT if
someone thinks I’m overly conservative or downright stupid. But people
would loose interest in very large source code also, specially when every
two years there is a new source code associated with new architecture, and
it is just my thinking.

Lot of ( if not all ) c-runtime and c++ std codes comes with MSVC
installation, and I hardly ever looked at it. Then for an all together
different reason ( Tim, one of our fellow community member and well
respected MVP pointed me to look at it after seeing my Pointer Distance
Article in January 2005 Linux journal, sorry for selfselling :slight_smile: I looked at
those code.

If I get some source code, certainly my job would be lot easier, but I can
not vouch for others.

Now if Alberto steps in, and starts preaching for Open source, I will have
to have him house arrest :-).

-pro

----- Original Message -----
From: “Michal Vodicka”
To: “Windows System Software Devs Interest List”
Sent: Thursday, March 31, 2005 10:45 AM
Subject: RE: [ntdev] WDM and Softice

> ----------
> From:
> xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> on behalf of Calvin Guan[SMTP:xxxxx@ati.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, March 31, 2005 7:40 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] WDM and Softice
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-205209-
> > xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
>
> > savoured enough single stepping and disassembling framework/support
> > library code when I developed NDIS drivers.
>
> NT assembly code is relatively easy to read with public symbols, even
> easier
> than poorly written C/C++ code.
>
I’d agree but still source code is better. Especially when docs is missing
or wrong; there are comments, variable and parameter names etc. Sources are
important for understanding, for example FastFat source in the IFS kit is
invaluable. Quick searching can save days of debugging and disassembling.

The important part for me in WDF is power management and USB selective
suspend support. With all respect to MS developers I’d prefer to see sources
before use to avoid future problems because similar code in DDK sample isn’t
quite correct. When I examined WDF some time before it was commented out
from samples and docs were under construction. Quite discouraging if sources
are unavailable.

Finally, I see no good reason why framework sources aren’t available. MS
wouldn’t lose anything, only gain. It isn’t native part of system. BTW, was
noticed any bad effect of last year (or when in was) NT4 and w2k sources
leak?

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.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

Well, if sources are available, it is everybody’s choice if examine them or not. With source browser it is very easy to examine any code referenced from your code and this way I usually look into STL sources. When necessary and when there is a reason to do it. The same with FastFat, DDK samples etc. I have BSC database created for everything interesting and it is just few keypresses in the editor to switch to the correct project and examine what is necessary. With WDF there is no choice at all.

I mentioned leak only because I presume it can be taken as a proof that there is nothing wrong even if core OS sources are available.

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 Prokash Sinha[SMTP:xxxxx@garlic.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, March 31, 2005 9:36 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDM and Softice

I’m afraid it might take the “off topic” direction, but I was quite vocal
about supressing the leak, bad effect of leak etc., etc. So once again I
will justify my args. I dont think it was widely published. Once leaked and
captivated is bit different. If MS gives out willingly, it’s a different
topic altogether. And I completely agree that if it is not base OS, having
source is going to help. If the source is about 100,000 lines or more, I
personally dont want to base my development, at least not so easily, with
the hope that I have 100+ thousands of source. But it might be good to have
while debugging down the trees of the forest. I WOULDN’T CERTAINLY OBJECT if
someone thinks I’m overly conservative or downright stupid. But people
would loose interest in very large source code also, specially when every
two years there is a new source code associated with new architecture, and
it is just my thinking.

Lot of ( if not all ) c-runtime and c++ std codes comes with MSVC
installation, and I hardly ever looked at it. Then for an all together
different reason ( Tim, one of our fellow community member and well
respected MVP pointed me to look at it after seeing my Pointer Distance
Article in January 2005 Linux journal, sorry for selfselling :slight_smile: I looked at
those code.

If I get some source code, certainly my job would be lot easier, but I can
not vouch for others.

Now if Alberto steps in, and starts preaching for Open source, I will have
to have him house arrest :-).

-pro

----- Original Message -----
From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Thursday, March 31, 2005 10:45 AM
> Subject: RE: [ntdev] WDM and Softice
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> > on behalf of Calvin Guan[SMTP:xxxxx@ati.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Thursday, March 31, 2005 7:40 PM
> > To: Windows System Software Devs Interest List
> > Subject: RE: [ntdev] WDM and Softice
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com [mailto:bounce-205209-
> > > xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
> >
> > > savoured enough single stepping and disassembling framework/support
> > > library code when I developed NDIS drivers.
> >
> > NT assembly code is relatively easy to read with public symbols, even
> > easier
> > than poorly written C/C++ code.
> >
> I’d agree but still source code is better. Especially when docs is missing
> or wrong; there are comments, variable and parameter names etc. Sources are
> important for understanding, for example FastFat source in the IFS kit is
> invaluable. Quick searching can save days of debugging and disassembling.>
>
> The important part for me in WDF is power management and USB selective
> suspend support. With all respect to MS developers I’d prefer to see sources
> before use to avoid future problems because similar code in DDK sample isn’t
> quite correct. When I examined WDF some time before it was commented out
> from samples and docs were under construction. Quite discouraging if sources
> are unavailable.
>
> Finally, I see no good reason why framework sources aren’t available. MS
> wouldn’t lose anything, only gain. It isn’t native part of system. BTW, was
> noticed any bad effect of last year (or when in was) NT4 and w2k sources
> leak?
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.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@upek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

IMHO toolkit sources are a must. Tookit is a skeleton of your code, not the
foundation of it.

With foundation, you just need to know it is reliable. With skeleton, you
need to know all details.

Lack of WDF source will surely slow down its acceptance. People will
continue to use their own boilerplates for PnP/Power or, say, use the ones from
Walter’s book.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

Exactly Michal, I also do that BSC. Once I stepped down the iostream tree
too. And it is not too difficult to cookup a driver workspace that also can
have BSC feature. But *extra baggage* must be offloaded when we are in
doubt. Very often cmd line build gives me enough to carry on.

When I first had my test on wince 2.0 platform builder I saw there is a
quite a bit of OS code being published, and it was very easy to see that
wince 3.0 has the preemptive interrupt dispactch mechanism, if I could
recall, and it was not there on the 2.xx versions, also it was quite
interesting to see how the early stage serial debugging feature was
incorporated on New kernel code ( some of the base os code, not all since
device manage code was not published ), but for driver writing it was not
very essential, for curiosity it is fine.

I centainly dont know where I would fall, if I have to have src for
everything that is being exercised in my systems. That would be a huge
amount of information overload. In the future there would be lot of BOTS
that are network enabled, could come and go on my systems, src for them ?, I
certainly dont expect to see.

Well defined interface, sort of programming based on contract could be
something I would like.

In any case, it is MS that needs to decide what level of src should be
published for developers.

-pro

----- Original Message -----
From: “Michal Vodicka”
To: “Windows System Software Devs Interest List”
Sent: Thursday, March 31, 2005 11:50 AM
Subject: RE: [ntdev] WDM and Softice

Well, if sources are available, it is everybody’s choice if examine them or
not. With source browser it is very easy to examine any code referenced from
your code and this way I usually look into STL sources. When necessary and
when there is a reason to do it. The same with FastFat, DDK samples etc. I
have BSC database created for everything interesting and it is just few
keypresses in the editor to switch to the correct project and examine what
is necessary. With WDF there is no choice at all.

I mentioned leak only because I presume it can be taken as a proof that
there is nothing wrong even if core OS sources are available.

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 Prokash Sinha[SMTP:xxxxx@garlic.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, March 31, 2005 9:36 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] WDM and Softice
>
> I’m afraid it might take the “off topic” direction, but I was quite vocal
> about supressing the leak, bad effect of leak etc., etc. So once again I
> will justify my args. I dont think it was widely published. Once leaked
> and
> captivated is bit different. If MS gives out willingly, it’s a different
> topic altogether. And I completely agree that if it is not base OS, having
> source is going to help. If the source is about 100,000 lines or more, I
> personally dont want to base my development, at least not so easily, with
> the hope that I have 100+ thousands of source. But it might be good to
> have
> while debugging down the trees of the forest. I WOULDN’T CERTAINLY OBJECT
> if
> someone thinks I’m overly conservative or downright stupid. But people
> would loose interest in very large source code also, specially when every
> two years there is a new source code associated with new architecture, and
> it is just my thinking.
>
> Lot of ( if not all ) c-runtime and c++ std codes comes with MSVC
> installation, and I hardly ever looked at it. Then for an all together
> different reason ( Tim, one of our fellow community member and well
> respected MVP pointed me to look at it after seeing my Pointer Distance
> Article in January 2005 Linux journal, sorry for selfselling :slight_smile: I looked
> at
> those code.
>
> If I get some source code, certainly my job would be lot easier, but I can
> not vouch for others.
>
> Now if Alberto steps in, and starts preaching for Open source, I will have
> to have him house arrest :-).
>
> -pro
>
> ----- Original Message -----
> From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Thursday, March 31, 2005 10:45 AM
> Subject: RE: [ntdev] WDM and Softice
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> > on behalf of Calvin Guan[SMTP:xxxxx@ati.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Thursday, March 31, 2005 7:40 PM
> > To: Windows System Software Devs Interest List
> > Subject: RE: [ntdev] WDM and Softice
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com [mailto:bounce-205209-
> > > xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
> >
> > > savoured enough single stepping and disassembling framework/support
> > > library code when I developed NDIS drivers.
> >
> > NT assembly code is relatively easy to read with public symbols, even
> > easier
> > than poorly written C/C++ code.
> >
> I’d agree but still source code is better. Especially when docs is missing
> or wrong; there are comments, variable and parameter names etc. Sources
> are
> important for understanding, for example FastFat source in the IFS kit is
> invaluable. Quick searching can save days of debugging and disassembling.>
>
> The important part for me in WDF is power management and USB selective
> suspend support. With all respect to MS developers I’d prefer to see
> sources
> before use to avoid future problems because similar code in DDK sample
> isn’t
> quite correct. When I examined WDF some time before it was commented out
> from samples and docs were under construction. Quite discouraging if
> sources
> are unavailable.
>
> Finally, I see no good reason why framework sources aren’t available. MS
> wouldn’t lose anything, only gain. It isn’t native part of system. BTW,
> was
> noticed any bad effect of last year (or when in was) NT4 and w2k sources
> leak?
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.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@upek.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

Yeah, that make sense.

-pro
----- Original Message -----
From: “Maxim S. Shatskih”
To: “Windows System Software Devs Interest List”
Sent: Thursday, March 31, 2005 12:22 PM
Subject: Re: [ntdev] WDM and Softice

> IMHO toolkit sources are a must. Tookit is a skeleton of your code, not
> the
> foundation of it.
>
> With foundation, you just need to know it is reliable. With skeleton,
> you
> need to know all details.
>
> Lack of WDF source will surely slow down its acceptance. People will
> continue to use their own boilerplates for PnP/Power or, say, use the ones
> from
> Walter’s book.
>
> 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@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

WDF is not a toolkit in the sense of ‘a skeleton of your code’. It is most
simply a new ‘higher level’ and ‘more coherent’ DDK API. It is not
impossible to understand or use WDF without the source code. Peter has done
it, I have done it, others outside of Microsoft have done it. It is simply
more difficult than it should be because of the fact that the source code is
not available, and this is especially grievous due to the lack of good
documentation.

People will indeed continue to use their own or Walter’s boilerplate code. I
have my set of stuff, you probably have yours, and there are probably (100,
1000, N) other variations on this theme out there in use right now. Most
likely each of them is broken in some unique and horrible way. As I’ve said
repeatedly, and as I’m going to say once more: the real value to me in WDF
is the ‘boilerplate code’ is now almost all inside the WDF api. It is now
Microsoft’s problem to get the Pnp/PowerManagement driver boilerplate code
correct and keep it correct across releases and bugfixes. I think I’ll get
on that train.

=====================
Mark Roddy

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Thursday, March 31, 2005 3:22 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDM and Softice

IMHO toolkit sources are a must. Tookit is a skeleton of your code, not
the foundation of it.

With foundation, you just need to know it is reliable. With skeleton,
you need to know all details.

Lack of WDF source will surely slow down its acceptance. People will
continue to use their own boilerplates for PnP/Power or, say, use the ones
from Walter’s book.

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@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

I concur with Mark, and yes for drivers that are close to the samples I have
been successful. My real complaint is that on things outside of the
samples, but still within what I thought were the capabilities of WDF, I
quickly got lost and stated reverting to a lot of WDM code that I didn’t
think I should need. At the present time I find WDF to be more useable as a
library for getting rid of the pnp/power boilerplate (in a manner similar to
wmilib did for WMI) than a new set of kernel API’s


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Roddy, Mark” wrote in message news:xxxxx@ntdev…
> WDF is not a toolkit in the sense of ‘a skeleton of your code’. It is most
> simply a new ‘higher level’ and ‘more coherent’ DDK API. It is not
> impossible to understand or use WDF without the source code. Peter has
> done
> it, I have done it, others outside of Microsoft have done it. It is simply
> more difficult than it should be because of the fact that the source code
> is
> not available, and this is especially grievous due to the lack of good
> documentation.
>
> People will indeed continue to use their own or Walter’s boilerplate code.
> I
> have my set of stuff, you probably have yours, and there are probably
> (100,
> 1000, N) other variations on this theme out there in use right now. Most
> likely each of them is broken in some unique and horrible way. As I’ve
> said
> repeatedly, and as I’m going to say once more: the real value to me in WDF
> is the ‘boilerplate code’ is now almost all inside the WDF api. It is now
> Microsoft’s problem to get the Pnp/PowerManagement driver boilerplate code
> correct and keep it correct across releases and bugfixes. I think I’ll get
> on that train.
>
>
>
> =====================
> Mark Roddy
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
> Sent: Thursday, March 31, 2005 3:22 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] WDM and Softice
>
> IMHO toolkit sources are a must. Tookit is a skeleton of your code, not
> the foundation of it.
>
> With foundation, you just need to know it is reliable. With skeleton,
> you need to know all details.
>
> Lack of WDF source will surely slow down its acceptance. People will
> continue to use their own boilerplates for PnP/Power or, say, use the ones
> from Walter’s book.
>
> 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@stratus.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>

Michal Vodicka wrote:
>

Well, if sources are available, it is everybody’s choice if examine them or not.

And I agree with Michal. I’d feel a LOT damn better if the source code
were released with the kit.

Last I heard, the WDF team planned to make their sources available if at
all possible. This isn’t confidential – It was mentioned at the last
WinHEC.

Now, of course, it remains to be seen whether they’ll be able to
successfully negotiate the quicksand filled pit that is the Microsoft
Legal and Corporate Affairs department. For that, we’ll all just have
to wait and see.

And I very much liked Mark Roddy’s comment:

“[With the advent of WDF…] it is now Microsoft’s problem to get the
Pnp/PowerManagement driver boilerplate code correct and keep it correct
across releases and bugfixes. I think I’ll get on that train.”

With WDF, you get to replace all the power management code in a driver
that’s power policy owner drvier with ONE LINE:

WdfDeviceInitSetPowerPolicyOwnership(&DeviceInit, TRUE);

And even THAT’s optional (cuz it’s the default).

Peter
OSR

> With WDF, you get to replace all the power management code in a driver

that’s power policy owner drvier with ONE LINE:

WdfDeviceInitSetPowerPolicyOwnership(&DeviceInit, TRUE);

Can I customize the default power policy owner implementation?

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

What do you want to customize it?

You can idle out in S0 w/your own timeout value. You can pick the Dx
state if you want. You can choose to idle out and not arm for wake (ie
software driven wakeup), or idle out and arm the hardware for wake
(software or hw driven wakeup). You can also enable USB SS as well for
wake from S0.

You can arm yourself for wake from Sx if your hw supports it, specifying
the Dx state if you want.

All of this is hooked up to device manager UI automatically (you can
disable this).

This is all discussed at WinHEC 2004, see
http://www.microsoft.com/whdc/driver/wdf/default.mspx

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Friday, April 01, 2005 11:01 PM
To: Windows System Software Devs Interest List
Subject: Re: Re:[ntdev] WDM and Softice

With WDF, you get to replace all the power management code in a driver

that’s power policy owner drvier with ONE LINE:

WdfDeviceInitSetPowerPolicyOwnership(&DeviceInit, TRUE);

Can I customize the default power policy owner implementation?

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

Max, let me ammend Doron’s statement. Yes, you can customize it. You can
set all the various constraints that Doron listed, and probably a couple
that he forgot. If that doesn’t do what you need, you can set callbacks on
any state transition and do whatever you want there. If even that isn’t
enough, you can tell WDF to step out of the way and handle your own power
policy.

If you find yourself needing to replace WDF’s power policy implementation,
however, please let us know why, including the goals that it’s not meeting
for you. This is very complex code and we’d like to make sure that most
people don’t need to mess with it.


Jake Oshins
Windows Kernel Group

This posting is provided “AS IS” with no warranties, and confers no rights.

“Doron Holan” wrote in message
news:xxxxx@ntdev…
What do you want to customize it?

You can idle out in S0 w/your own timeout value. You can pick the Dx
state if you want. You can choose to idle out and not arm for wake (ie
software driven wakeup), or idle out and arm the hardware for wake
(software or hw driven wakeup). You can also enable USB SS as well for
wake from S0.

You can arm yourself for wake from Sx if your hw supports it, specifying
the Dx state if you want.

All of this is hooked up to device manager UI automatically (you can
disable this).

This is all discussed at WinHEC 2004, see
http://www.microsoft.com/whdc/driver/wdf/default.mspx

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Friday, April 01, 2005 11:01 PM
To: Windows System Software Devs Interest List
Subject: Re: Re:[ntdev] WDM and Softice

> With WDF, you get to replace all the power management code in a driver

> that’s power policy owner drvier with ONE LINE:
>
> WdfDeviceInitSetPowerPolicyOwnership(&DeviceInit, TRUE);

Can I customize the default power policy owner implementation?

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

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Peter Viscarola (OSR)[SMTP:xxxxx@osr.com]
Reply To: Windows System Software Devs Interest List
Sent: Saturday, April 02, 2005 12:30 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDM and Softice

Last I heard, the WDF team planned to make their sources available if at
all possible. This isn’t confidential – It was mentioned at the last
WinHEC.

Good to hear, thanks for the info.

Now, of course, it remains to be seen whether they’ll be able to
successfully negotiate the quicksand filled pit that is the Microsoft
Legal and Corporate Affairs department. For that, we’ll all just have
to wait and see.

We can always hope :slight_smile:

And I very much liked Mark Roddy’s comment:

“[With the advent of WDF…] it is now Microsoft’s problem to get the
Pnp/PowerManagement driver boilerplate code correct and keep it correct
across releases and bugfixes. I think I’ll get on that train.”

If life is so easy… When a customer encounters a problem, it is my responsibility to fix it regardless of what really causes it. Complaning about MS is so overused that even if it is perfectly true, it wouldn’t be taken well. Even if customers trust me, they’d want working version ASAP. I’m affraid I couldn’t wait until MS fixes it and releases a new WDF version. Yet another reason why sources should be available.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

Availability of source does not mean you can distribute your version of
it, just like the latest src licence for MFC. Now, I have no idea
about the src licence that will come with WDF, but the possibility of
read only/no distro is there.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Monday, April 04, 2005 7:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice


From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Peter Viscarola (OSR)[SMTP:xxxxx@osr.com]
Reply To: Windows System Software Devs Interest List
Sent: Saturday, April 02, 2005 12:30 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDM and Softice

Last I heard, the WDF team planned to make their sources available if
at
all possible. This isn’t confidential – It was mentioned at the last

WinHEC.

Good to hear, thanks for the info.

Now, of course, it remains to be seen whether they’ll be able to
successfully negotiate the quicksand filled pit that is the Microsoft
Legal and Corporate Affairs department. For that, we’ll all just have

to wait and see.

We can always hope :slight_smile:

And I very much liked Mark Roddy’s comment:

“[With the advent of WDF…] it is now Microsoft’s problem to get the
Pnp/PowerManagement driver boilerplate code correct and keep it
correct
across releases and bugfixes. I think I’ll get on that train.”

If life is so easy… When a customer encounters a problem, it is my
responsibility to fix it regardless of what really causes it. Complaning
about MS is so overused that even if it is perfectly true, it wouldn’t
be taken well. Even if customers trust me, they’d want working version
ASAP. I’m affraid I couldn’t wait until MS fixes it and releases a new
WDF version. Yet another reason why sources should be available.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.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

> ----------

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: Tuesday, April 05, 2005 6:04 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDM and Softice

Availability of source does not mean you can distribute your version of
it, just like the latest src licence for MFC. Now, I have no idea
about the src licence that will come with WDF, but the possibility of
read only/no distro is there.

I expected WDF isn’t distributed separately but compiled/linked to driver instead, so modifying it shouldn’t cause more harm than modifying a DDK sample. If developer creates a bug there, it would be the same problem as if there is a bug in the driver written without WDF. But it is technical point of view and lawyers can see it differently. Let’s wait until src licence is available. Hopefully such scenarios will be considered.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]