USB WDM driver working on 2000, XP and 2003, but not 98

Hi all,

as the title says: I have developed an USB driver which works fine on
all platforms but 98 (I don't know about Me: not tested).

Is there any DDK tool that can check for Windows compatibility?

Thanks!

Bill
Wed Jul 21 14:34:01 CDT 2004

No not really. There is a handy tool available on Walter Oney's website
called WdmCheck which will check to see if your binary is attempting to
import functions which the platform does not export.

Check it out, you will very likely be glad you did: www.oneysoft.com

--
Bill McKenzie
Software Engineer - Prism 802.11 Wireless Solutions
Conexant Systems, Inc.


"Guillaume" <youbet@rideabike.biz> wrote in message
news:utLXiezbEHA.636@TK2MSFTNGP12.phx.gbl...
> Hi all,
>
> as the title says: I have developed an USB driver which works fine on
> all platforms but 98 (I don't know about Me: not tested).
>
> Is there any DDK tool that can check for Windows compatibility?
>
> Thanks!

Jesse
Wed Jul 21 15:44:11 CDT 2004


> No not really. There is a handy tool available on Walter Oney's website
> called WdmCheck which will check to see if your binary is attempting to
> import functions which the platform does not export.

(pardon spellings, shaved fingertip off in bektsander last weekend)
Exactly as Bill said, WDMCHECK will check a druver for missing imports.
Yoiu should copy the driver to your 98 system and run WDMCHECK. WDMCHECK
will indicate that yer driver calls unsupported finctions. Then get
WDMSTUB. It might support these functions. Add WDMSTUB.sys to yor driver
package.

Jesse O. Glidden
------------------
USBDevWare.com
Low-cost, high-speed
USB development hardware

Guillaume
Wed Jul 21 16:10:41 CDT 2004

> No not really. There is a handy tool available on Walter Oney's website
> called WdmCheck which will check to see if your binary is attempting to
> import functions which the platform does not export.

Thanks, I think it'll do the trick! I'll try that tomorrow.

Meanwhile, I don't have a Windows 98 machine at hand right now, so could
you tell me whether the fact my driver has a WMI interface could
possibly make it fail under Win 98 (I'm sensing that it would)?

Guillaume
Wed Jul 28 14:55:56 CDT 2004

Hi again,

well, it still won't load on Windows 98:

- wdmcheck said there was no missing import links.
- I disabled WMI support, just to make sure, and it still won't load it.

This driver is based on the "bulkusb" sample in the Windows DDK 3790.
Is there any reason why this driver wouldn't work on Windows 98
(and it doesn't work on Win Me either, I tested it...)?

Is a recompilation necessary (if so, with which DDK? The Windows 2000
DDK didn't seem to compile it properly using the Win Me build
environment, and I can't get ahold of an older DDK)?

martinbo
Wed Jul 28 16:30:00 CDT 2004

------=_NextPart_0001_0619E99C
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I think it's possible you're running into a problem with changes in ordinal
and hint numbers in USBD.LIB between the Win98 version and and the 2K/XP
version. Walt Oney discussed a workaround for this in the following
posting:


http://groups.google.com/groups?q=oney+and+usbd.lib&hl=en&lr=&ie=UTF-8&oe=UT
F-8&selm=3CD1443B.9C4E7104%40oneysoft.com&rnum=1

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_0619E99C
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 I think it's possible you're running into a problem with changes in ordinal and hint numbers in USBD.LIB between the Win98 version and and the 2K/XP version. Walt Oney discussed a workaround for this in the following posting:
\par
\par http://groups.google.com/groups?q=oney+and+usbd.lib&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=3CD1443B.9C4E7104%40oneysoft.com&rnum=1
\par
\par Thanks,
\par Martin Borve [MSFT]
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_0619E99C--

Guillaume
Thu Jul 29 13:14:20 CDT 2004

> I think it's possible you're running into a problem with changes in ordinal
> and hint numbers in USBD.LIB between the Win98 version and and the 2K/XP
> version. Walt Oney discussed a workaround for this in the following
> posting:

Ok, that could be. But wouldn't have "wdmcheck" found missing links
in that case? This is confusing.

martinbo
Thu Jul 29 17:58:13 CDT 2004

------=_NextPart_0001_0B911A0D
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

>> Ok, that could be. But wouldn't have "wdmcheck" found missing links
>> in that case? This is confusing.

You'd have to ask Walt Oney about WDMCHECK, as it's his tool.

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_0B911A0D
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 >> Ok, that could be. But wouldn't have "wdmcheck" found missing links
\par >> in that case? This is confusing.
\par
\par You'd have to ask Walt Oney about WDMCHECK, as it's his tool.
\par
\par Thanks,
\par Martin Borve [MSFT]
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_0B911A0D--

Walter
Fri Jul 30 19:46:55 CDT 2004

Guillaume wrote:
> Ok, that could be. But wouldn't have "wdmcheck" found missing links
> in that case? This is confusing.

Yes, it would have. The naming problem Martin is referring to definitely
shows up with WDMCHECK.

Another useful tool to try is DEPENDS, which comes with Visual Studio.

--
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com