From: Pavel A. on

The INF name and section of installed driver can
be obtained with SetupDiGetDriverInfoDetail.
I don't know how to get the list of files from there.
Maybe need to parse the INF section manually,
find all CopyFiles referenced by it, etc.

--PA


Kerem Gümrükcü wrote:
> BTW, Don, do you know a way, how i can get all
> the drivers(filesystem locations) and the inf-files for the
> drivers with SetupDI* or CM_* PNP functions? Or
> is there any other way to get them, to get them completely
> and reliable?
>
>
> TIA,...
>
> Regards
>
> Kerem
>

From: Stefan Kuhr on
Kerem,

Kerem G�mr�kc� wrote:
> Hi Don,
>
>> Well if you look at the sample in the SDK it is an LPVOID array. Using a
>> DWORD will get you in serious trouble on 64-bit.
>
> yes, you are right, thats why i wrote a wrapper arround the function, some
> call that first checks the size of the DWORD representation on the platform
> and then uses the right mannaged type to return the values,...
>

There is no need to check for the size of a DWORD, it is 4 Bytes on both
x86 Windows and x64 Windows.

--
S


From: Kerem Gümrükcü on
H i Stefan,


>There is no need to check for the size of a DWORD, it is 4 Bytes on both
>x86 Windows and x64 Windows

ok thanks, but i will remain on the wrapper, who knows what
the future brings,...


Regards

Kerem

--
-----------------------
Beste Gr�sse / Best regards / Votre bien devoue
Kerem G�mr�kc�
Latest Project: http://www.codeplex.com/restarts
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."
"Stefan Kuhr" <kustt110(a)gmx.li> schrieb im Newsbeitrag
news:%23qXV0aI$IHA.1016(a)TK2MSFTNGP03.phx.gbl...
> Kerem,
>
> Kerem G�mr�kc� wrote:
>> Hi Don,
>>
>>> Well if you look at the sample in the SDK it is an LPVOID array. Using
>>> a
>>> DWORD will get you in serious trouble on 64-bit.
>>
>> yes, you are right, thats why i wrote a wrapper arround the function,
>> some
>> call that first checks the size of the DWORD representation on the
>> platform
>> and then uses the right mannaged type to return the values,...
>>
>
> There is no need to check for the size of a DWORD, it is 4 Bytes on both
> x86 Windows and x64 Windows.
>
> --
> S
>
>

From: Kerem Gümrükcü on
Hi Don,

>I do not know how to do it (never spent the time to figure it out) but it
>can be done, since the driverquery command does exactly that.

i run driverquery and it display the drivers name, its display name, its
type
and some time stamp information, but nothing for a INI, the drivers
path,etc,...

EnumDeviceDrivers returns all Drivers on the System, but how will i get the
INI for that,...

Regards

Kerem

--
-----------------------
Beste Gr�sse / Best regards / Votre bien devoue
Kerem G�mr�kc�
Latest Project: http://www.codeplex.com/restarts
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."
"Don Burn" <burn(a)stopspam.windrvr.com> schrieb im Newsbeitrag
news:ePKlGLI$IHA.4816(a)TK2MSFTNGP06.phx.gbl...
>I do not know how to do it (never spent the time to figure it out) but it
>can be done, since the driverquery command does exactly that.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> "Kerem G�mr�kc�" <kareem114(a)hotmail.com> wrote in message
> news:%23OayBHI$IHA.2216(a)TK2MSFTNGP06.phx.gbl...
>> BTW, Don, do you know a way, how i can get all
>> the drivers(filesystem locations) and the inf-files for the
>> drivers with SetupDI* or CM_* PNP functions? Or
>> is there any other way to get them, to get them completely
>> and reliable?
>>
>>
>> TIA,...
>>
>> Regards
>>
>> Kerem
>>
>> --
>> --
>> -----------------------
>> Beste Gr�sse / Best regards / Votre bien devoue
>> Kerem G�mr�kc�
>> Microsoft Live Space: http://kerem-g.spaces.live.com/
>> Latest Open-Source Projects: http://entwicklung.junetz.de
>> -----------------------
>> "This reply is provided as is, without warranty express or implied."
>>
>>
>
>

From: Kerem Gümrükcü on
Hi Pavel,

yes SetupDiGetDriverInfoDetail seems to be a option, but
i get always Wrong Parameter or unknown error results
from the call to that function, The point is that i run this
not from C/C++ but from managed C# via Pinvoke.
Something seems to be wrong either on my declarations
or on the buffers size i pass to the function. I could
not figure it out whats the thing that does not work, but i will
find it by time....



Regards

Kerem


--
-----------------------
Beste Gr�sse / Best regards / Votre bien devoue
Kerem G�mr�kc�
Latest Project: http://www.codeplex.com/restarts
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."
"Pavel A." <pavel_a(a)NOfastmailNO.fm> schrieb im Newsbeitrag
news:eZZT1aI$IHA.4124(a)TK2MSFTNGP05.phx.gbl...

The INF name and section of installed driver can
be obtained with SetupDiGetDriverInfoDetail.
I don't know how to get the list of files from there.
Maybe need to parse the INF section manually,
find all CopyFiles referenced by it, etc.

--PA


Kerem G�mr�kc� wrote:
> BTW, Don, do you know a way, how i can get all
> the drivers(filesystem locations) and the inf-files for the
> drivers with SetupDI* or CM_* PNP functions? Or
> is there any other way to get them, to get them completely
> and reliable?
>
>
> TIA,...
>
> Regards
>
> Kerem
>