InstDrv Plugin: InstallDriver: E0000203

atlastraeger · 25th January 2007, 05:24

Hi everybody,

I'm trying to use the InstDrv plugin to install a custom driver on an XP system, however, I keep getting the error

Quote:

InstallDriver: E0000203

CreateDevice was called before, and returned 0.

Does anybody know this error message? I tried to find the error code in MSDN, however, I didn't find it.

Any help appreciated.

Thanx in advance!

Takhir · 25th January 2007, 07:03

E:\WINDDK\3790.1830\inc\wnet>findstr /i 203 setupapi.h
#define ERROR_NO_DRIVER_SELECTED (APPLICATION_ERROR_MASK|ERROR_SEVERITY_ERROR|0x203)

atlastraeger · 25th January 2007, 10:46

Hello,

thank you for your quick reply. I googled for ERROR_NO_DRIVER_SELECTED, however, I still don't know how to avoid this error.
Perhaps I should download the source code for the InstDrv plugin and debug it, so that I can see where this error occurs exactly.

So nobody has ever had this error before?

Thanx again..

onad · 29th January 2007, 16:47

Well I did, but I always know *I* was wrong somewhere, so yes get the source and let the debugging quest begin, if you persist you will solve the issue you have, I feel it...

Ocrana · 23rd April 2007, 02:21

Hi,
did you solved the problem? I run into the same problem but cannot find a solution.

Ingo

arrow15 · 20th July 2007, 03:30

So I was looking over the plug-in today, and I found what I suspect might be the issue in create device. There is a fundamental flaw in the current code, in that for SetupDiCreateDeviceInfo, DICD_GENERATE_ID is sent as a flag.

MSDN: http://msdn2.microsoft.com/en-us/library/ms792966.aspx
WINSETUPAPI BOOL WINAPI
SetupDiCreateDeviceInfo(
IN HDEVINFO DeviceInfoSet,
IN PCTSTR DeviceName,
IN LPGUID ClassGuid,
IN PCTSTR DeviceDescription, OPTIONAL
IN HWND hwndParent, OPTIONAL
IN DWORD CreationFlags,
OUT PSP_DEVINFO_DATA DeviceInfoData OPTIONAL
);

DICD_GENERATE_ID
If this flag is specified, DeviceName contains only a Root-enumerated device ID and the system creates a unique device instance key for it. This unique device instance key is generated as:

Enum\Root\DeviceName\InstanceID
where InstanceID is a four-digit, base-10 number that is unique among all subkeys under Enum\Root\DeviceName. Call SetupDiGetDeviceInstanceId to find out what ID was generated for this device information element.

Essentially, by having this flag in the call to SetDiCreateDeviceInfo, the plug-in is limited to generic device names like "foobar123". Specifying the PnP enumeration is NOT possible (eg: "USB\foobar123").

Sorry I didn't fix the bug, but I haven't really had time. Maybe someone else can see if they can fix this problem and upload a new version of the plug-in?

~Arrow15

29th January 2007, 16:47	#4
onad Senior Member Join Date: Dec 2004 Location: Turkey Posts: 447	Well I did, but I always know I was wrong somewhere, so yes get the source and let the debugging quest begin, if you persist you will solve the issue you have, I feel it... "Just do it"

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

25th January 2007, 07:03	#2
Takhir Major Dude Join Date: Feb 2004 Location: Moscow, Russia Posts: 1,222	E:\WINDDK\3790.1830\inc\wnet>findstr /i 203 setupapi.h #define ERROR_NO_DRIVER_SELECTED (APPLICATION_ERROR_MASK\|ERROR_SEVERITY_ERROR\|0x203)

25th January 2007, 10:46	#3
atlastraeger Junior Member Join Date: Jan 2007 Posts: 2	Hello, thank you for your quick reply. I googled for ERROR_NO_DRIVER_SELECTED, however, I still don't know how to avoid this error. Perhaps I should download the source code for the InstDrv plugin and debug it, so that I can see where this error occurs exactly. So nobody has ever had this error before? Thanx again..

23rd April 2007, 02:21	#5
Ocrana Junior Member Join Date: Nov 2006 Posts: 27	Hi, did you solved the problem? I run into the same problem but cannot find a solution. Ingo

20th July 2007, 03:30	#6
arrow15 Junior Member Join Date: Jun 2007 Posts: 4	So I was looking over the plug-in today, and I found what I suspect might be the issue in create device. There is a fundamental flaw in the current code, in that for SetupDiCreateDeviceInfo, DICD_GENERATE_ID is sent as a flag. MSDN: http://msdn2.microsoft.com/en-us/library/ms792966.aspx WINSETUPAPI BOOL WINAPI SetupDiCreateDeviceInfo( IN HDEVINFO DeviceInfoSet, IN PCTSTR DeviceName, IN LPGUID ClassGuid, IN PCTSTR DeviceDescription, OPTIONAL IN HWND hwndParent, OPTIONAL IN DWORD CreationFlags, OUT PSP_DEVINFO_DATA DeviceInfoData OPTIONAL ); DICD_GENERATE_ID If this flag is specified, DeviceName contains only a Root-enumerated device ID and the system creates a unique device instance key for it. This unique device instance key is generated as: Enum\Root\DeviceName\InstanceID where InstanceID is a four-digit, base-10 number that is unique among all subkeys under Enum\Root\DeviceName. Call SetupDiGetDeviceInstanceId to find out what ID was generated for this device information element. Essentially, by having this flag in the call to SetDiCreateDeviceInfo, the plug-in is limited to generic device names like "foobar123". Specifying the PnP enumeration is NOT possible (eg: "USB\foobar123"). Sorry I didn't fix the bug, but I haven't really had time. Maybe someone else can see if they can fix this problem and upload a new version of the plug-in? ~Arrow15