Prev: Wi-Fi Driver development for WINCE OS
Next: XPSDrv Font Subsetting
From: CoolSun20 on 23 Jun 2010 14:12
I am porting my legacy 32 bit driver to AMD64 and I came across
HalGetInterruptVector API which I am finding unsupported.. What are my
options.. My driver currently installs as a service no inf file..

Any advise..

Thanks in advance..
From: Doron Holan [MSFT] on 23 Jun 2010 14:48
you need to convert your driver to a pnp driver (use KMDF, it will make your
life simpler) and install via an INF

d

"CoolSun20" wrote in message
news:23B1CBD7-FD8D-4E74-BB92-CCFCDD741D48(a)microsoft.com...

I am porting my legacy 32 bit driver to AMD64 and I came across
HalGetInterruptVector API which I am finding unsupported.. What are my
options.. My driver currently installs as a service no inf file..

Any advise..

Thanks in advance..

From: Don Burn on 23 Jun 2010 14:48
You have a non-PnP driver, to reliably support hardware from XP onwards
you have to support PnP. Basically, at this point your best option is to
start over with a KMDF driver that supports PnP and Power management for
you.


Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr




> -----Original Message-----
> From: CoolSun20 [mailto:CoolSun20(a)discussions.microsoft.com]
> Posted At: Wednesday, June 23, 2010 2:12 PM
> Posted To: microsoft.public.development.device.drivers
> Conversation: HalGetInterruptVector
> Subject: HalGetInterruptVector
>
> I am porting my legacy 32 bit driver to AMD64 and I came across
> HalGetInterruptVector API which I am finding unsupported.. What are my
> options.. My driver currently installs as a service no inf file..
>
> Any advise..
>
> Thanks in advance..
>
>
> __________ Information from ESET Smart Security, version of virus
> signature
> database 5223 (20100623) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

 | 
Pages: 1
Prev: Wi-Fi Driver development for WINCE OS
Next: XPSDrv Font Subsetting