Dear List,
I have builded the USB driver given under WDK\src. Since it is an User Mode Driver the output was dll file. I successfully installed the this driver along with inf file and supported co-installer dlls in Windows XP but I am unable to install the same in Vista platform.
The New Hardware Found wizard says:
“Windows found the driver software for your device but encountered an error while attempting to install it. The parameter is incorrect.”
Can somebody provide a hint about the meaning of the error. I think the same build environment (Vista and Server 2008 Checked Build) of WDK can be used to build the drivers for both XP and Vista.
Regards.
Given that you’re saying it’s a user mode driver, and it works on XP, I guess you mean one of the UMDF drivers. Is this correct? If so, which one? Installing on Vista generally kind of sucks, because as you’ve encountered, the error messages are completely useless, and sometimes just misleading. In any case, the first place to check is \windows\setupapi.log. On Vista, this will refer you to another file, the name of which I do not recall. Look for the information for your driver, and see if there is anything further in there that is worth posting. Another thing to check is the actual INF you are using that is generated from the INX file, perhaps running ChkInf. Make sure both that whatever UMDF needs in the way of a coinstaller (if any; I don’t know) is a real file name and present.
This is not really my thing, but the setupapi.log file is certainly worth checking, and I’m sure that someone else will be along shortly to give to you more complete advice.
On a final note, while it is possible that UMDF drivers are supposed to be built under the Server 2008 environment no matter what platform on which they will run, as some drivers and windbg extensions work this way, I kind of doubt it in this case; that is, Server 2008. The WDK for Server 2008, to the best of knowledge, produces KMDF drivers that will only install on Server 2008, and perhaps Longhorn. I don’t know if this applies to UMDF as well, but it might be worth checking.
Good luck,
mm
To be specific, the example is wdk-src-umdf-usb-fx2_driver-step1. The glance at \windows\setuplog.api was completely clueless. It shows the new location as D:\Windows\INF whereas my system has a single partitioned C: only.
Then I interpreted it as C:\Windows\INF and moved there. The INF of the sample is there and the corresponding DLL file is copied in C:\Windows\System32\Drivers\UMDF.
One more point which is worth for posting it, inorder to make the driver installation as the first time device attached behaviour under XP I used to delete the keys at the following location:
HKLM-Microsoft-Software-WindowsNT-CurrentControlSet-System-Enum-USB-device VID & PID.
In XP I used to delete it by changing the permissions with regedt32. But in Vista, it gives error message saying that access is denied.
I tried all possible ways of changing permissions, ownership, advanced permissions, running regedit as an administrator but cannot overcome this error.
Regards.
Not entirely sure what is going on with D:\Windows\INF.
Although I can’t say that I have ever played with installing the UMDF version of OSRUSBFX2 on Vista, I did do the same with the KMDF version, and had all sorts of problems, that, unfortunately I addressed basically the way you did - delete everything in the registry; I also deleted the INF and image as well, and I want to say that Vista had an INF that new about this driver out of the box, so I killed that one as well; that may be wrong, and does sound suspicious. I believe that the easiest general answer to the access problem is to add yourself (via “Advanced”) and grant yourself full permission, after unchecking the box about “inherit from parent” (then choose “remove”); whether or not this is a good idea, I don’t know, but as you are going to delete it anyway, I suppose why not, assuming that you are OK with the former. It sounds like you already tried this, so I’m not sure what to tell you.
mm
xxxxx@evitechnology.com wrote:
On a final note, while it is possible that UMDF drivers are supposed to be built under the Server 2008 environment no matter what platform on which they will run, as some drivers and windbg extensions work this way, I kind of doubt it in this case; that is, Server 2008. The WDK for Server 2008, to the best of knowledge, produces KMDF drivers that will only install on Server 2008, and perhaps Longhorn.
“Server 2008” is the new name for the system that used to be called
“Longhorn”…
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thanks for all those attempts to understand what is happening acutally.
I did not overcome the problem but approached it from entirely different angle. I wanted to install my driver in Vista because of problem with Windows DTM with XP.
Now I am able to use DTM with XP and hence reverted back from Vista to XP to install the driver.
But this must be a problem at any given time. If somebody is able to delete registry keys in Vista, please respond with the procedure. The point is we are able to delete the keys at the following location:
HKLM-Microsoft-Software-WindowsNT-CurrentControlSet-System-Control-Class
but we are unable to delete at the location mentioned in the previous posting.
Regards.
xxxxx@gmail.com wrote:
But this must be a problem at any given time. If somebody is able to delete registry keys in Vista, please respond with the procedure. The point is we are able to delete the keys at the following location:
HKLM-Microsoft-Software-WindowsNT-CurrentControlSet-System-Control-Class
but we are unable to delete at the location mentioned in the previous posting.
The official word, of course, is “don’t do this”. You aren’t supposed
to dink with the Enum tree of the registry directly.
However, it certainly is possible to do so. Bring up regedit as
administrator (note that this does not merely mean “when logged in as
administrator”, unless you turned off UAC), and take ownership of the
key (and possibly its parent). Then you can change the permissions to
assign yourself full control. Then you can delete it.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.