DH> Did you run stampinf with the correct cmd line?
good hint, I have never used stampinf before … all by hand …
OK, now is successfully. I have used version info 1.0.0 and
entrys with “WUDFUpdate_01005.dll” in my hand edit inf file. Not
so good combination.
But the other question, why the WUDF service is not started
automaticly after using
Did you follow the instructions for building and installing the sample driver in the readme files for the samples? See src\umdf\readme.htm for the top level file.
You shouldn’t download the UMDF Install Kit anymore - the latest version comes with the WDK and that’s the one you should use.
How do you try to install the WDK sample driver?
-p
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of MailingList
Sent: Monday, September 24, 2007 10:49 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] UMDF Driver Installation
Hello,
I have had not luck to install a UMDF driver on Windows XP SP2
computer.
I assume I must download the UMDF Install Kit for Windows XP and
install it. After that the WUDF service is not running.
OK - I have used
NET START wudfpf and
NET START wudvsvc
To minimize my errors I try to install the WDK sample driver.
But no success. Everey time I got an Error 0xE000203.
So my question, the sample INF files use a catalog wudf.cat.
Where is it ?
Is this a right entry in INF file, or must I insert the right version
?
[CoInstallers_AddReg]
HKR,CoInstallers32,0x00010000,“WUDFUpdate_$UMDFCOINSTALLERVERSION$.dll”
What is rigth way to install UMDF on a custom computer for Windows XP
SP2 ?
“The right way” to install a WDF driver is to include the appropriate INF sections and directives for UMDF and/or KMDF, including the coinstaller-related directives, and then to make sure the appropriate coinstaller binary (or binaries if you are using both UMDF and KMDF in a package) is an integral part of your “driver package”.
If by this question you mean to ask “can I extract that program and run it directly?”, the answer is definitely “NO”.
I assume you mean “DIFx”. The answer is “Yes”, but you have to preinstall the entire package, and (as I said above) that INCLUDES the appropriate coinstaller. The same applies to DPInst.
FINALLY- to get back to your first question- if you have the correct INF directives and you are invoking the coinstaller, then the services you need for UMDF will start when they are needed.
The place to start with installation failures is pretty much the same for WDF as it is for any WDM driver- %windir%\setup*.log (setupapi and setupact). The coinstallers will leave some tracks there if and when they install the framework. If those “tracks” are missing, go back to your INF file, because invocation of the coinstaller is the ONLY way we support installation of the framework.
General INF guidelines for UMDF (straight from the WDK docs, BTW):
(1) use the coinstaller
(2) add the reflector service (associate it with the device if it is the function driver, but not if it is a filter).
(3) use the appropriate WDF directives
(4) make sure the driver binaries get copied to drivers/umdf (typically using the 12,umdf notation in the [DestinationDirs] section.
If you used a broken INF before, you should clean everything up before you use the fixed one (system restore points are handy for this)- or at least keep a close eye on the setup logs and ensure installation is using your new package and not the previous, broken one.
all by hand …