Back to the past i.e. VISTA

NTDEV
1

Both 32 & 64-bit versions of our WDM driver are working on Win7/8. However,
rebuilding the same source for VISTA-64 yields a non-working driver. I
originally suspected interference from the LSI driver that ships with VISTA
(but not Win7/8). However, that is disabled. A further oddity is that I
can set breakpoints in WinDBG but no breaks occur - ?. The driver installed
but has a yellow ‘!’.

I know I haven’t supplied any real clues but can anyone venture a (WA)guess
as to what step(s) I’ve missed by going back to VISTA-64? Most of my
customers did not like VISTA; so I started the porting process of our
original driver at Win7.

Even though disabled could the LSI driver be reserving my PCI hardware?

TIA,

Bill Casey

ASC

2

Probably a missing import that doesn’t exist on vista. Run depends.exe on the binary on a vista system or you can do it at load time, http://blogs.msdn.com/b/doronh/archive/2006/03/13/550844.aspx

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Bill Casey
Sent: Friday, July 19, 2013 1:06 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Back to the past i.e. VISTA

Both 32 & 64-bit versions of our WDM driver are working on Win7/8. However, rebuilding the same source for VISTA-64 yields a non-working driver. I originally suspected interference from the LSI driver that ships with VISTA (but not Win7/8). However, that is disabled. A further oddity is that I can set breakpoints in WinDBG but no breaks occur - ?. The driver installed but has a yellow ‘!’.

I know I haven’t supplied any real clues but can anyone venture a (WA)guess as to what step(s) I’ve missed by going back to VISTA-64? Most of my customers did not like VISTA; so I started the porting process of our original driver at Win7.

Even though disabled could the LSI driver be reserving my PCI hardware?

TIA,

Bill Casey
ASC

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

@Doron,

Considering that he is building the src against vista x64. Shouldn’t the missing API problem be trapped at build itself?(by some unresolved linker error). Also the loader should throw an error when loading a binary with missing imports. shouldn’t it?

Aditya

4

Depends on how well the APIs are marked with NTDDI_VERSION. If improperly marked, the build will succeed. Also, if you build for a newer OS and want to load on an older OS, you need to manage this aspect yourself. The loader stopped putting up a dialog on missing export after Win2k (IIRC), now it just fails to load and you have to debug it.
d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Sunday, July 21, 2013 10:27 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Back to the past i.e. VISTA

@Doron,

Considering that he is building the src against vista x64. Shouldn’t the missing API problem be trapped at build itself?(by some unresolved linker error). Also the loader should throw an error when loading a binary with missing imports. shouldn’t it?

Aditya

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

5

Doron:
I did my build for VISTA-64. Also, per your suggestion I ran
‘depends.exe’ and saw no issue there. I think the main problem is the
standard Windows driver for the chip on my board. How can I permanently
remove this driver? I’ve tried with no luck. It does not exist on Win7 or
8 and my 7/8 driver works fine in both those environments. FYI: the
following (with the _WIN32_WINNT & NTDDI_VERSION defines) was in the
‘buildfre_wlh_amd64.log’ file:

/D_WIN32_WINNT=0x0600 /DWINVER=0x0600 /D_WIN32_IE=0x0700
/DWIN32_LEAN_AND_MEAN=1 /DDEVL=1
/D__BUILDMACHINE__=WinDDK /DNDEBUG /D_DLL=1 /DNDEBUG
/DNTDDI_VERSION=0x06000100 /DRUN_WPP /I.\inc

Again, I suspect the standard (boot) driver that comes with VISTA is
stealing my resources - even though disabled.

Bill Casey
ASC

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, July 22, 2013 12:52 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Back to the past i.e. VISTA

Depends on how well the APIs are marked with NTDDI_VERSION. If improperly
marked, the build will succeed. Also, if you build for a newer OS and want
to load on an older OS, you need to manage this aspect yourself. The loader
stopped putting up a dialog on missing export after Win2k (IIRC), now it
just fails to load and you have to debug it.
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Sunday, July 21, 2013 10:27 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Back to the past i.e. VISTA

@Doron,

Considering that he is building the src against vista x64. Shouldn’t the
missing API problem be trapped at build itself?(by some unresolved linker
error). Also the loader should throw an error when loading a binary with
missing imports. shouldn’t it?

Aditya

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

6

Sorry to harp on this VISTA-64 problem but we need a solution. Our adapter
board uses the same chip as the chip manufacturer uses on their boards. In
XP we could supplant their driver with ours (read: load before) by making
ours also a BOOT driver and placing our custom ‘Group’ ahead of the
manufacturer’s in the ‘List’ of ServiceGroupOrder. This worked nicely. For
our updated PnP driver version on VISTA-64 we tried doing this procedure -
doesn’t work L. Can anyone suggest another way to if not remove the
manufacturer’s driver, at least get ours to load AHEAD of theirs?

Bill Casey

ASC

From: Doron Holan [mailto:xxxxx@microsoft.com]
Sent: Monday, July 22, 2013 4:34 PM
Subject: RE: Back to the past i.e. VISTA

You can’t get rid of the driver behind the OS’s back. You would need to go
call into setup to remove the driver package. The effectiveness of that
action on XP is clearly up for debate and with XP about to go out of
support, not something I would think you get traction on if the built in
remove doesn’t work the way you want

d

7

Is this for installs on a running system, or as part of a system install?
It almost sounds like the latter, but it could be the former.

Don Burn

Windows Filesystem and Driver Consulting

Website: http:</http:> http://www.windrvr.com

Blog: http: http://msmvps.com/blogs/WinDrvr

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Casey
Sent: Friday, July 26, 2013 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Back to the past i.e. VISTA

Sorry to harp on this VISTA-64 problem but we need a solution. Our adapter
board uses the same chip as the chip manufacturer uses on their boards. In
XP we could supplant their driver with ours (read: load before) by making
ours also a BOOT driver and placing our custom ‘Group’ ahead of the
manufacturer’s in the ‘List’ of ServiceGroupOrder. This worked nicely. For
our updated PnP driver version on VISTA-64 we tried doing this procedure -
doesn’t work L. Can anyone suggest another way to if not remove the
manufacturer’s driver, at least get ours to load AHEAD of theirs?

Bill Casey

ASC

From: Doron Holan [mailto:xxxxx@microsoft.com]
Sent: Monday, July 22, 2013 4:34 PM
Subject: RE: Back to the past i.e. VISTA

You can’t get rid of the driver behind the OS’s back. You would need to go
call into setup to remove the driver package. The effectiveness of that
action on XP is clearly up for debate and with XP about to go out of
support, not something I would think you get traction on if the built in
remove doesn’t work the way you want

d

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer</http:>

8

Don - a running system in which our board may or may not be installed. I’ve
tried installing our driver first and then adding the board to the system -
doesn’t matter. The Windows-supplied driver takes over and we’re left
holding nothing. In the enum for our driver it shows: Root\UKNOWN\0000.
On Win7/8 (no driver from the manufacturer included) we have not trouble at
all. Somehow their driver takes precedence in VISTA. I just need the trick
to get around this.

Bill Casey

ASC

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, July 26, 2013 6:00 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Back to the past i.e. VISTA

Is this for installs on a running system, or as part of a system install?
It almost sounds like the latter, but it could be the former.

Don Burn

Windows Filesystem and Driver Consulting

Website: http://www.windrvr.com http:</http:>

Blog: http://msmvps.com/blogs/WinDrvr

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Casey
Sent: Friday, July 26, 2013 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Back to the past i.e. VISTA

Sorry to harp on this VISTA-64 problem but we need a solution. Our adapter
board uses the same chip as the chip manufacturer uses on their boards. In
XP we could supplant their driver with ours (read: load before) by making
ours also a BOOT driver and placing our custom ‘Group’ ahead of the
manufacturer’s in the ‘List’ of ServiceGroupOrder. This worked nicely. For
our updated PnP driver version on VISTA-64 we tried doing this procedure -
doesn’t work L. Can anyone suggest another way to if not remove the
manufacturer’s driver, at least get ours to load AHEAD of theirs?

Bill Casey

ASC

From: Doron Holan [mailto:xxxxx@microsoft.com]
Sent: Monday, July 22, 2013 4:34 PM
Subject: RE: Back to the past i.e. VISTA

You can’t get rid of the driver behind the OS’s back. You would need to go
call into setup to remove the driver package. The effectiveness of that
action on XP is clearly up for debate and with XP about to go out of
support, not something I would think you get traction on if the built in
remove doesn’t work the way you want

d

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

9

Don - a better way of stating the problem is that during PCI enumeration the
HardwareID for our device is being associated with the chip vendor’s driver
not ours. As I said earlier, in XP we changed from ‘System’ to ‘Boot’,
added a ‘Group’ in our driver’s registry entry and then placed that Group
name ahead of the group-name used by the chip vendor’s (BOOT) driver.
Doesn’t work in VISTA L.

Bill Casey

== VirDISR & VirtualSCSIT Target Mode Solutions ==

Advanced Storage Concepts, Inc. (409) 762-0604

2200 Market Street, Suite 810 xxxxx@virtualscsi.com

Galveston, TX USA 77550-1532 www.virtualscsi.com
http:</http:>

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, July 26, 2013 6:00 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Back to the past i.e. VISTA

Is this for installs on a running system, or as part of a system install?
It almost sounds like the latter, but it could be the former.

Don Burn

Windows Filesystem and Driver Consulting

Website: http://www.windrvr.com http:</http:>

Blog: http://msmvps.com/blogs/WinDrvr

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Casey
Sent: Friday, July 26, 2013 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Back to the past i.e. VISTA

Sorry to harp on this VISTA-64 problem but we need a solution. Our adapter
board uses the same chip as the chip manufacturer uses on their boards. In
XP we could supplant their driver with ours (read: load before) by making
ours also a BOOT driver and placing our custom ‘Group’ ahead of the
manufacturer’s in the ‘List’ of ServiceGroupOrder. This worked nicely. For
our updated PnP driver version on VISTA-64 we tried doing this procedure -
doesn’t work L. Can anyone suggest another way to if not remove the
manufacturer’s driver, at least get ours to load AHEAD of theirs?

Bill Casey

ASC

From: Doron Holan [mailto:xxxxx@microsoft.com]
Sent: Monday, July 22, 2013 4:34 PM
Subject: RE: Back to the past i.e. VISTA

You can’t get rid of the driver behind the OS’s back. You would need to go
call into setup to remove the driver package. The effectiveness of that
action on XP is clearly up for debate and with XP about to go out of
support, not something I would think you get traction on if the built in
remove doesn’t work the way you want

d

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer