I have been wondering, why do some programs have a single driver for multiple operating systems? I didn’t think this was possible. It’s a virtual driver but I thought you had to compile for a single operating system.
Is it possible for me then to compile one driver for multiple operating systems? I.e. 32bit and 64bit Windows XP/Vista/7 operating systems.
I have been wondering, why do some programs have a single driver for
multiple operating systems? I didn’t think this was possible. It’s a virtual
driver but I thought you had to compile for a single operating system.
Is it possible for me then to compile one driver for multiple operating
systems? I.e. 32bit and 64bit Windows XP/Vista/7 operating systems.
Yes, you need different .SYS for NTx86, NTamd64 and NTia64 (hopefully built from one set of source files), but they can all be referenced and installed from one .INF and covered by one .CAT. Look at the samples in the WDK.
Tim Green
Development Engineer
DisplayLink (UK) Limited
Registered in England No. 04811048
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-398898- xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: 01 February 2010 14:14
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Virtual Driver
Are you sure it is a single *implementation*?
The INFs for 32-bit (NTx86) and 64-bit (NTamd64 or NTia64) will be
different.
The CATs will be different.
The .SYS will be different.
They might not have names that are different across the platforms because
the package for platform X is not going to install on platform Y anyway.
Are you sure that you have found a package with a single driver for both x86
and amd64 platforms?
I have been wondering, why do some programs have a single driver for
multiple operating systems? I didn’t think this was possible. It’s a virtual
driver but I thought you had to compile for a single operating system.
Is it possible for me then to compile one driver for multiple operating
systems? I.e. 32bit and 64bit Windows XP/Vista/7 operating systems.