I guess that’s comparable to using the InstallHinfSection() API call from a
setup program, or was that what you meant?
The MSI tables are scary…
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ted Hess
Sent: Thursday, April 29, 2004 1:26 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Installing driver with MSI
You need to create a delayed execution “Custom Action” that essentially
calls setupapi from within the MSI tables - like before StartServices would
be a good place.
Ex: “rundll32 setupapi,InstallHinfSection DefaultInstall 132
[YOURINSTALLDIR]yourinf.inf”
/ted
-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Thursday, April 29, 2004 12:24 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Installing driver with MSI
Is it possible/practical to install a driver using MS Windows Installer
(MSI)?
In my case, it’s a filter driver with no hardware component, but some
associated applications (.NET apps, to make things worse, so the CLR may
have to be installed). It’s only for Win2K and higher.
All the driver installation documentation centers around the .inf file; all
the MSI documentation describes how it’s database-driven; installing .NET
assemblies is still more different.
They seem to be mutually exclusive. Or am I staring right at it and missing
it (always a likely possibility ;-)?
Thanks,
Ken
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@livevault.com To unsubscribe
send a blank email to xxxxx@lists.osr.com
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com