Hi,
I have a problem installing my virtual serial com port driver on few computers, on XP and Vista.
after installation with devcon finished successfully, In device manager the driver has the error :
This device cannot start. (Code 10)
in setupapi.log i get this error:
Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
I think it’s something with the port being used, although I see that it gets the next unused port.
One more thing, when building the driver (with build -ceZ) on the computers it does work there are not warnings, but on the ones it does not work on, there is a warning but it does not create .wrn file (How is that possible??).
xxxxx@gmail.com wrote:
One more thing, when building the driver (with build -ceZ) on the computers it does work there are not warnings, but on the ones it does not work on, there is a warning but it does not create .wrn file (How is that possible??).
What warnings, exactly?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim,
As I said there is no .wrn file so I don’t know what is the warning. devcon does not show any details about this warning, just tells there is one.
Sorry, I meant the compilation( build -ceZ) not devcon (which finishes with no error or warning).
xxxxx@gmail.com wrote:
Sorry, I meant the compilation( build -ceZ) not devcon (which finishes with no error or warning).
How about cutting-and-pasting the results from “build -ceZ” and “dir”,
and maybe the contents of “sources”?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
What’s the difference between the two build windows? Is one amd64 and one x86? One checked and one free?
-p
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Thursday, May 21, 2009 3:15 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] UMDF: “Device not started” Error after installation
xxxxx@gmail.com wrote:
Sorry, I meant the compilation( build -ceZ) not devcon (which finishes with no error or warning).
How about cutting-and-pasting the results from “build -ceZ” and “dir”,
and maybe the contents of “sources”?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Peter, they are exactly the same, both x86 and both free, I’ll make sure though …
Tim, I’ll cut-and-paste it here on Sunday (not at work now).
Have you checked %windir%\setupact.log? Does the coinstaller log say anything about requiring a reboot?
Also, you can try using “devcon -r”, which will automatically reboot your system, if it’s required and see whether the driver is working after the reboot.
Ilias
From: xxxxx@lists.osr.com [xxxxx@lists.osr.com] on behalf of xxxxx@gmail.com [xxxxx@gmail.com]
Sent: Friday, May 22, 2009 2:58 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] UMDF: “Device not started” Error after installation
Peter, they are exactly the same, both x86 and both free, I’ll make sure though …
Tim, I’ll cut-and-paste it here on Sunday (not at work now).
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer