[jds]

PROBLEMCHYLD, on 21 February 2012 - 03:31 PM, said:

I contacted Walter Oney about updating WDMSTUB.SYS and he says, it has to be an .SYS instead of .VXD for universal purposes.
He also said the source code is included in his book which I don't mind buying but I don't know how to program.

If you download and update per the first posting, you will also have the source code.

PROBLEMCHYLD, on 21 February 2012 - 03:31 PM, said:

He also said if one was to update WDMSTUB.SYS to change the name to avoid confusion.

Interesting. This is quite different to his published advice on these matters. Yet, if we can modify and distribute under a new name, that will do for our needs! Are you able to post (quote) the relevant text from Walter?

Joe.

[PROBLEMCHYLD]

jds, on 21 February 2012 - 05:58 PM, said:

Interesting. This is quite different to his published advice on these matters. Yet, if we can modify and distribute under a new name, that will do for our needs! Are you able to post (quote) the relevant text from Walter?

Joe.

No because he contacted me by email. Its personal and I will not share my emails on the internet. (You are more than welcome to hack it though).
I have better things to do then to lie about what people have sent me via email. If my word is not Good, then all I do is a lie. And I'm not a liar.
And besides, how would I know the source code is offered with the book if I don't own it.

This post has been edited by PROBLEMCHYLD: 21 February 2012 - 06:37 PM

[jds]

PROBLEMCHYLD, on 21 February 2012 - 06:26 PM, said:

jds, on 21 February 2012 - 05:58 PM, said:

Interesting. This is quite different to his published advice on these matters. Yet, if we can modify and distribute under a new name, that will do for our needs! Are you able to post (quote) the relevant text from Walter?

Joe.

No because he contacted me by email. Its personal and I will not share my emails on the internet. (You are more than welcome to hack it though).
I have better things to do then to lie about what people have sent me via email. If my word is not Good, then all I do is a lie. And I'm not a liar.
And besides, how would I know the source code is offered with the book if I don't own it.

Eh? Nobody is calling you a liar. Why would you think that???

It's simply a legal formality. The published license for WdmStub specifically says it cannot be redistributed except by explicit permission of Walter Oney. That's where we stand legally, unless we can prove otherwise, eg. to the people running MSFN. Only the relevant portions of the e-mail, plus the time/date information, should suffice.

As for the source code, you can either get it on the CD-ROM if you buy the book, or you can download it as described in the first posting. Of course, the benefit in buying the book is that all the stuff is explained, otherwise you have to figure it out yourself.

Joe.

This post has been edited by jds: 21 February 2012 - 07:31 PM

[rloew]

I bought the book years ago at a used Book Store. The Source code I have is version 4.20

I have written my own VXD File to add other functions, not in WDMSTUB.

This post has been edited by rloew: 21 February 2012 - 11:16 PM

[dencorso]

That's great news!
What do you think about the question of whether is it preferable to have the WDM Function/Stub provider as a .SYS or as a .VxD which I've raised some posts above?

[PROBLEMCHYLD]

jds, on 21 February 2012 - 07:00 PM, said:

Eh? Nobody is calling you a liar. Why would you think that???

It's simply a legal formality. The published license for WdmStub specifically says it cannot be redistributed except by explicit permission of Walter Oney. That's where we stand legally, unless we can prove otherwise, eg. to the people running MSFN. Only the relevant portions of the e-mail, plus the time/date information, should suffice.

As for the source code, you can either get it on the CD-ROM if you buy the book, or you can download it as described in the first posting. Of course, the benefit in buying the book is that all the stuff is explained, otherwise you have to figure it out yourself.

Joe.

Maybe I misunderstood you or vice versa. I posted what he sent me via email. I wasn't trying to be an a** about things. Sometimes my comprehension is off.

dencorso, on 21 February 2012 - 11:39 PM, said:

That's great news!
What do you think about the question of whether is it preferable to have the WDM Function/Stub provider as a .SYS or as a .VxD which I've raised some posts above?

rloew, on 21 February 2012 - 11:14 PM, said:

I bought the book years ago at a used Book Store. The Source code I have is version 4.20

I have written my own VXD File to add other functions, not in WDMSTUB.

From: "PROBLEMCHYLD" <>
> Do you think its possible to update WDMSTUB.SYS with the missing exports,
> and convert it to WDMSTUB.VXD.

There is no point to having a VxD -- WDMSTUB was designed for the single
purpose of allowing WDM drivers to work across platforms, and it has to be a
.sys file to perform that function. Anyhow, the source code for WDMSTUB came
with the book. That means you can use the code as a base to build something
of your own with a different name.

--
Walter Oney, Esq.
267 Pearl Hill Road
Fitchburg, MA 01420
Tel.: 978-343-3390
http://www.oneylaw.com

This post has been edited by PROBLEMCHYLD: 22 February 2012 - 07:58 AM

[rloew]

dencorso, on 21 February 2012 - 11:39 PM, said:

That's great news!
What do you think about the question of whether is it preferable to have the WDM Function/Stub provider as a .SYS or as a .VxD which I've raised some posts above?

I personally prefer the VXD as it is always there just like the NT/2000/XP NTKERN.VXD that it is trying to emulate.

PROBLEMCHYLD, on 22 February 2012 - 07:47 AM, said:

rloew, on 21 February 2012 - 11:14 PM, said:

I bought the book years ago at a used Book Store. The Source code I have is version 4.20

I have written my own VXD File to add other functions, not in WDMSTUB.

From: "PROBLEMCHYLD" <>
> Do you think its possible to update WDMSTUB.SYS with the missing exports,
> and convert it to WDMSTUB.VXD.

There is no point to having a VxD -- WDMSTUB was designed for the single
purpose of allowing WDM drivers to work across platforms, and it has to be a
.sys file to perform that function. Anyhow, the source code for WDMSTUB came
with the book. That means you can use the code as a base to build something
of your own with a different name.

--
Walter Oney, Esq.
267 Pearl Hill Road
Fitchburg, MA 01420
Tel.: 978-343-3390
http://www.oneylaw.com

What he says would be true only if he expects WDMSTUB to be used on an NT platform to support a later version.

It appears that he is not claiming ownership of the source code, only the name WDMSTUB, so it should be OK to use it and extract the later Code.

This post has been edited by rloew: 22 February 2012 - 11:37 AM

[PROBLEMCHYLD]

rloew, on 22 February 2012 - 11:35 AM, said:

What he says would be true only if he expects WDMSTUB to be used on an NT platform to support a later version.

It appears that he is not claiming ownership of the source code, only the name WDMSTUB, so it should be OK to use it and extract the later Code.

Thanks for explaining it a little better. As I said earlier, sometimes my comprehension is off. I hope I didn't offend anyone. If so please forgive me.
Thanks.

[dencorso]

rloew, on 22 February 2012 - 11:35 AM, said:

I personally prefer the VXD as it is always there just like the NT/2000/XP NTKERN.VXD that it is trying to emulate.

So we do agree on this point. BTW, v. 4.20 is still a VxD, right? It's from before he moved on to .SYS.

rloew, on 22 February 2012 - 11:35 AM, said:

What he says would be true only if he expects WDMSTUB to be used on an NT platform to support a later version.

Sure, I think that's what he meant, too. And it may be needed for XP/2k sooner than anyone expects... (But I'll let this discussion for a new thread in the apropriate forum, later on).

rloew, on 22 February 2012 - 11:35 AM, said:

PROBLEMCHYLD, on 22 February 2012 - 07:47 AM, said:

Anyhow, the source code for WDMSTUB came with the book. That means you can use the code as a base to build something of your own with a different name.

--
Walter Oney, Esq.
267 Pearl Hill Road
Fitchburg, MA 01420
Tel.: 978-343-3390
http://www.oneylaw.com

It appears that he is not claiming ownership of the source code, only the name WDMSTUB, so it should be OK to use it and extract the later Code.

Yes, that's how I understand it. And he *is* a lawyer, besides being a programmer, so I think he meant precisely what he said. I *think* that using another name, and printing a message telling something like "based on WDMSTUB, by Walter Oney", should be all that's needed.

PROBLEMCHYLD, on 22 February 2012 - 11:45 AM, said:

I hope I didn't offend anyone. If so please forgive me.

You rock, PROBLEMCHYLD!
Your iniciative in contacting W. Oney was great, timely and enlightening.

[jaclaz]

PROBLEMCHYLD, on 18 February 2012 - 04:42 PM, said:

@ jaclaz
Do the drivers you listed work with any bluetooth or are they specific to its own devices.

I have no idea.
I simply gave a possible answer to dencorso's question.
I am "The Finder", AND NOT "The Low Level Device Programmer" .

jds, on 20 February 2012 - 01:27 AM, said:

No worries, your English is usually exemplary (if I were more proficient in Portuguese, I might have figured out what you meant).

Just for the record (and to stir a bit the pot ) *any* latin language may have done :
Portuguese: dispositivo
Spanish: dispositivo
Italian: dispositivo
French: dispositif
Romanian: dispozitiv

This post has been edited by jaclaz: 22 February 2012 - 05:19 PM

[LoneCrusader]

dencorso, on 21 February 2012 - 04:44 PM, said:

PROBLEMCHYLD, on 21 February 2012 - 03:31 PM, said:

He also said if one was to update WDMSTUB.SYS to change the name to avoid confusion.

Of course he shall have his wish respected. I propose the updated version, if and when we arrive at that, should be named "NUWDMST".

Why not "WDMSTUBX" for "WDMSTUB eXtended/eXtender?" I think the name should be as close to the original as possible while fulfilling Oney's wishes.

This post has been edited by LoneCrusader: 22 February 2012 - 05:22 PM

[rloew]

dencorso, on 22 February 2012 - 02:03 PM, said:

rloew, on 22 February 2012 - 11:35 AM, said:

I personally prefer the VXD as it is always there just like the NT/2000/XP NTKERN.VXD that it is trying to emulate.

So we do agree on this point. BTW, v. 4.20 is still a VxD, right? It's from before he moved on to .SYS.

The source code is for a VXD. I don't see any for a SYS File.

[jds]

PROBLEMCHYLD, on 22 February 2012 - 07:47 AM, said:

Walter Oney said:

Anyhow, the source code for WDMSTUB came with the book. That means you can use the code as a base to build something of your own with a different name.

Thanks, PROBLEMCHYLD, you've done well! This gives us the green light!

BTW, can you also give us the time/date of the e-mail? Probably not important, but it helps with traceability.

In case you haven't seen it, below is the notice that comes with the WdmStub code. So you can see why it was important to get more up-to-date permission for what we're wanting to do here :

Quote

Redistributing WDMSTUB

WDMSTUB is an exception to the blanket license to use the sample programs for this book. The author will grant a royalty-free license to anyone to redistribute WDMSTUB as part of a WDM driver package. The license will, however, include conditions designed to insure the consistency and quality of WDMSTUB on end user machines. Send e-mail to waltoney@xxxxxxxx.xxx for information about obtaining this conditional license.

Note: A special license is required even if you ship WDMSTUB under a different name. This driver includes special checking to make sure that it does not unload while some other vendor’s driver might be using it, and the special license will insure that you preserve that checking.

Joe.

This post has been edited by jds: 23 February 2012 - 06:27 PM

[dencorso]

PROBLEMCHYLD, on 20 February 2012 - 07:51 PM, said:

dencorso, on 18 February 2012 - 01:58 PM, said:

Wishlist for a next version of WDMSTUB:

_vsnwprintf
HidNotifyPresence
InterlockedPopEntrySList
InterlockedPushEntrySList
TdiCopyBufferToMdl
TdiCopyMdlToBuffer
ZwDeleteValueKey

Here's two more that might come in handy in the future.

WdfVersionUnbind
WdfVersionBind

And yet some more:

KeReadStateEvent
InterlockedExchangeAdd
KeQueryActiveProcessors
RtlUpcaseUnicodeString <-- although I reckon this one may not be feasible

[PROBLEMCHYLD]

You guys are aware his book has an Second Edition.

[rloew]

PROBLEMCHYLD, on 23 February 2012 - 08:14 AM, said:

You guys are aware his book has an Second Edition.

My copy is clearly the first.

[PROBLEMCHYLD]

jds, on 22 February 2012 - 10:26 PM, said:

BTW, can you also give us the time/date of the e-mail? Probably not important, but it helps with traceability.

Feb 20, 2012 06:28:41 PM

LoneCrusader, on 22 February 2012 - 05:22 PM, said:

Why not "WDMSTUBX" for "WDMSTUB eXtended/eXtender?" I think the name should be as close to the original as possible while fulfilling Oney's wishes.

That would be a great name for it.

This post has been edited by PROBLEMCHYLD: 25 February 2012 - 12:26 PM

[jds]

I have been wondering about the three different versions 5.00.006 of WDMSTUB.SYS (that we know of, so far), and what may be different between them. Anyway, when I opened them with Dependency Walker, it reported the following dependencies :

Oneysoft version => ntoskrnl.exe, HAL.DLL
Garmin version => ntoskrnl.exe
NUSB30e version => ntoskrnl.exe

Digging deeper with Dependency Walker revealed these dependencies :

ntoskrnl.exe => bootvid.dll, HAL.DLL, kdcom.dll
HAL.DLL => ntoskrnl.exe
bootvid.dll => ntoskrnl.exe, HAL.DLL
kdcom.dll => ntoskrnl.exe, HAL.DLL

So, all three versions ultimately show the same dependencies, but only the Oneysoft version shows a direct dependency on HAL.DLL (and is also noticeably larger than the other two, more recent, versions). I'm not sure, but that suggests to me that there may be functional differences between these three versions, despite the identical version numbering.

The other notable thing, is that these apparent dependencies are not provided by W98SE. I searched around to find these versions of said files, before Dependency Walker was fully satisfied with WDMSTUB.SYS :

bootvid.dll = 5.1.2600.0 (xpclient.010817-1148)
HAL.DLL = 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
kdcom.dll = 5.1.2600.0 (xpclient.010817-1148)
ntoskrnl.exe = 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)

Now I wonder, are these extra modules sometimes needed for WdmStub to do its job on W98, or are they only used on say, W2000?

Joe.

[dencorso]

Dependency Walker gives false results for WDM drivers on 9x/ME. It'll always show dependencies to one of or both hal.dll and ntoskrnl.exe, which are NT-OS only files.

There are four known compilations of WDMSTUB.SYS v. 5.0.0.6, AFAIK:

1) PE TIMESTAMP Wed Jun 11 22:05:16 2003 (3EE7D1CC), 20480 KiB, MD5 69309403061DD2953D402015B6E4EFB1 is a debug build compiled from the source provided with W. Oney's Service Pack 3 to the WDM book 2nd Ed. (released June 12, 2003);
2) PE TIMESTAMP Wed Sat Mar 15 09:16:46 2003 (3E7319AE), 11520 KiB, MD5 3AA89DDB2B5FE621E0EB11F9D1FFBD39 is a release build that comes with some Honeywell drivers;
3) PE TIMESTAMP Wed Thu May 22 10:55:15 2003 (3ECCD6C3), 11520 KiB, MD5 1D7284E0F3CB98A189F0AC17C3F13337 is a release build that comes with the Garmin USB GPS drivers;
4) PE TIMESTAMP Sun Sep 24 19:05:20 2006 (45170120), 12767 KiB, MD5 9AA0AEA685F135C9D1409F8E3E5ADD10 is a release build that comes with NUSB30e.

While the first three are functionally identical, despite being clearly different compilations, with some different optimizations, the fourth is an updated version that exports one more function. It is the one in general use and it is the most up to date one that I know of, and, of course, it shouldn't be versioned 5.0.0.6...

And to answer the question you posed: yes, they're only used in NT-OSes.

[rloew]

NTOSKRNL.EXE and HAL.DLL provide the Core functionality for WDM Drivers on NT OSes. When Microsoft ported WDM to Windows 9x they put most of the Functions in NTKERN.VXD and a few in other VXDs. The normal Export/Import model cannot handle this configuration, so Microsoft provided a way to Export Functions under the name of Modules other than the ones hosting them.
These Exports are published via Kernel calls, not by PE Export tables. This is why Dependency Walker cannot follow Imports back to these Exports. In addition more than one Module can add Functions under the same Module name. WDMSTUB adds it's functions under the Module name NTOSKRNL.EXE on top of the ones already defined, replacing a few of the existing ones.
VXDs can only add Functions in this manner as they do not have Export Tables.