Menu
▾
▴
libusb-win32-devel
|
From: Ekkehard <edo...@ad...> - 2011-12-20 12:10:41
|
Thanks Pete, this is a nice idea! I just checked this file(s) on my PCs - very informative! As soon as I have the clients file with more detailed information, I will post again. Greets Ekkehard -- View this message in context: http://libusb.6.n5.nabble.com/Driver-installation-failed-Error-39-Vista-64-bit-tp5088225p5088685.html Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |
|
From: Xiaofan C. <xia...@gm...> - 2011-12-22 14:11:15
|
On Thu, Dec 22, 2011 at 1:46 AM, Travis <lib...@gm...> wrote: > On 12/21/2011 12:52 AM, Xiaofan Chen wrote: >> On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen<xia...@gm...> wrote: >>> You may want to check if that Vista 64bit machine has been set up >>> to block unsigned driver package? > > I'm not sure this is even possible. An invalid .cat file should cause > windows to display the signed driver warning prompt. I cannot find any > policy settings that change this behavior is Vista or 7. Did you have > something specific in mind? > I forgot where I read it. It might be some posts in the OSR ntdev mailing list and might involve some 3rd party software management package. But I could not find anything now. Maybe I mixed it up with something else. -- Xiaofan |
|
From: Travis <lib...@gm...> - 2011-12-22 20:45:10
|
On 12/22/2011 6:11 AM, Xiaofan Chen wrote: > On Thu, Dec 22, 2011 at 1:46 AM, Travis<lib...@gm...> wrote: >> On 12/21/2011 12:52 AM, Xiaofan Chen wrote: >>> On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen<xia...@gm...> wrote: >>>> You may want to check if that Vista 64bit machine has been set up >>>> to block unsigned driver package? >> I'm not sure this is even possible. An invalid .cat file should cause >> windows to display the signed driver warning prompt. I cannot find any >> policy settings that change this behavior is Vista or 7. Did you have >> something specific in mind? >> > I forgot where I read it. It might be some posts in the OSR ntdev > mailing list and might involve some 3rd party software management > package. But I could not find anything now. Maybe I mixed it up > with something else. > > I assumed there was a policy for something like this as well. I've only found this: http://technet.microsoft.com/en-us/library/cc785800%28WS.10%29.aspx ..this is not supported on vista and seems to have no effect. I believe this to be for older operating systems that allow an unsigned "driver.sys" by default. There are also policies to prevent/allow device installations by class and/or deviceID but I doubt this is the problem. You can review these policies by launching "mmc" and adding the Group Policy Editor snap-in but it is not available in home premium editions. Regards, Travis |
|
From: Ekkehard <edo...@ad...> - 2011-12-23 10:49:18
|
Its running now, but why?
It's a bit like the 4 states of an instrument given by Murphy:
- State 0: Everything is running and you know why
- State 1: Something is broken, but you know what/why
while you attempt to repair the state is changed to
- State 2: The thing is running, but you *dont* know why
and the last and finite state is waiting
- State 3: Something is broken, and you dont know what/why
So we reach state 2!
What I have done was using Zadig and transforming the (not running)
installed libusbK driver into a WinUSB driver. This approach yesterday
failed with a timeout ("and how was your day...") and an uncontrolable Zadik
sw.
Today everything went well, and the WinUSB driver was installed and
successfully started.
Next I installed a driver from the Devicemanager from the list (a libusbK
based made by Zadig) this runs as well, and to the end I installed my
original driver (probably one with cat file commented out in the inf file,
but I am not sure), which runs also well (after a long delay in the install
procedure).
Now the device is installed and running - if I can communicate with the
device is not clear, but probably beyond the scope of this topic.
Thanx for helping!!!
Happy xmas for all of you wishes Ekkehard
--
View this message in context: http://libusb.6.n5.nabble.com/Driver-installation-failed-Error-39-Vista-64-bit-tp5088225p5096868.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
|
|
From: Pete B. <pe...@ak...> - 2011-12-23 13:47:49
|
On 2011.12.23 10:49, Ekkehard wrote:
> Its running now,
Great!
> but why?
>
> What I have done was using Zadig and transforming the (not running)
> installed libusbK driver into a WinUSB driver. This approach yesterday
> failed with a timeout ("and how was your day...") and an uncontrolable Zadik
> sw.
I'll see what I can do to investigate/reproduce the uncontrollable
Zadig, because I thought I had taken steps to make sure it never
happened. If there's additional information you can provide on that,
don't hesitate to mail me.
Now, I did once get a timeout with Zadig, on a Vista 64 bit machine that
had a large disk, the first time I ran a driver installation with Zadig
there, and this was due to the creation of a restore point taking too long.
By default, Windows initiates the creation of a restore point when
installing a new driver, which is an operation over which we have no
control and which may actually fail. Windows does define a 5 minutes
timeout before it gives up on the restore point.
The second time I ran Zadig, the restore point creation completed within
the 5 minutes allocated, and I haven't been able to reproduce the issue
since, which is quite similar to what you've been experiencing below. I
think it may have been due to the machine having ran a very long time
without creating a restore point, and the disk being rather large.
Unfortunately, Windows doesn't provide any info on what happens during
the restore point creation or any form of progress report, so it's hard
to tell what's going on.
> Today everything went well, and the WinUSB driver was installed and
> successfully started.
> Next I installed a driver from the Devicemanager from the list (a libusbK
> based made by Zadig) this runs as well, and to the end I installed my
> original driver (probably one with cat file commented out in the inf file,
> but I am not sure), which runs also well (after a long delay in the install
> procedure).
The long delay could be due to the creation of another restore point,
though, if you installed a driver before, the creation of new restore
points is supposed to be faster, not slower.
Also the driver installation process is supposed to disable the creation
of restore point whenever possible, unless there's a policy setting that
prevents it. It would look like this is also the the case on your
machine. I think Zadig will report whether it was able to disable
restore point creation with debug logging turned on.
> Now the device is installed and running - if I can communicate with the
> device is not clear, but probably beyond the scope of this topic.
>
> Thanx for helping!!!
> Happy xmas for all of you wishes Ekkehard
Merry Christmas to you too!
Regards,
/Pete
|
|
From: Xiaofan C. <xia...@gm...> - 2011-12-28 13:00:09
|
On Thu, Dec 22, 2011 at 10:11 PM, Xiaofan Chen <xia...@gm...> wrote: > On Thu, Dec 22, 2011 at 1:46 AM, Travis <lib...@gm...> wrote: >> On 12/21/2011 12:52 AM, Xiaofan Chen wrote: >>> On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen<xia...@gm...> wrote: >>>> You may want to check if that Vista 64bit machine has been set up >>>> to block unsigned driver package? >> >> I'm not sure this is even possible. An invalid .cat file should cause >> windows to display the signed driver warning prompt. I cannot find any >> policy settings that change this behavior is Vista or 7. Did you have >> something specific in mind? >> > > I forgot where I read it. It might be some posts in the OSR ntdev > mailing list and might involve some 3rd party software management > package. But I could not find anything now. Maybe I mixed it up > with something else. > I think this comes from Windows XP. Under Windows XP, there is a setting to block unsigned driver software. During hardware installation, Windows might detect software that has not passed Windows Logo testing to verify its compativility with Windows. (Tell me why this testing is important). What action do you want Windows to take? Control Panel -- System -- Hardware tab -- Drivers -- Driver Signing 1) Ignore - Install software anyway and don't ask for my approval 2) Warn - Prompt me each time to choose an action 3) Block - Never install unsigned driver software -- Xiaofan |
|
From: Travis <lib...@gm...> - 2011-12-23 14:02:53
|
On 12/23/2011 2:49 AM, Ekkehard wrote:
> Its running now, but why?
> It's a bit like the 4 states of an instrument given by Murphy:
> - State 0: Everything is running and you know why
> - State 1: Something is broken, but you know what/why
> while you attempt to repair the state is changed to
> - State 2: The thing is running, but you *dont* know why
> and the last and finite state is waiting
> - State 3: Something is broken, and you dont know what/why
>
> So we reach state 2!
>
> What I have done was using Zadig and transforming the (not running)
> installed libusbK driver into a WinUSB driver. This approach yesterday
> failed with a timeout ("and how was your day...") and an uncontrolable Zadik
> sw.
I hate not knowing what happened!
Occasionally, my host controller malfunctions and causes problems
similar to this. I must *cold* boot my machine before it works
correctly again. Could it have been something like this?
> Today everything went well, and the WinUSB driver was installed and
> successfully started.
> Next I installed a driver from the Devicemanager from the list (a libusbK
> based made by Zadig) this runs as well, and to the end I installed my
> original driver (probably one with cat file commented out in the inf file,
> but I am not sure), which runs also well (after a long delay in the install
> procedure).
lol.. At-least everything is working now; you probably couldn't
reproduce this error if you wanted to. ;) I know I couldn't.
> Now the device is installed and running - if I can communicate with the
> device is not clear, but probably beyond the scope of this topic.
>
If it says it's functioning properly, then the driver has already sent
several control transfers and selected config #1 successfully.
Probably, everything is A-OK.
> Thanx for helping!!!
> Happy xmas for all of you wishes Ekkehard
>
Ho-Ho-Ho Merry Christmas,
Travis
|
|
From: Xiaofan C. <xia...@gm...> - 2011-12-23 14:16:00
|
On Fri, Dec 23, 2011 at 10:02 PM, Travis <lib...@gm...> wrote: > On 12/23/2011 2:49 AM, Ekkehard wrote: >> Today everything went well, and the WinUSB driver was installed and >> successfully started. >> Next I installed a driver from the Devicemanager from the list (a libusbK >> based made by Zadig) this runs as well, and to the end I installed my >> original driver (probably one with cat file commented out in the inf file, >> but I am not sure), which runs also well (after a long delay in the install >> procedure). > > lol.. At-least everything is working now; you probably couldn't > reproduce this error if you wanted to. ;) I know I couldn't. If there is still something suspicious, then it will probably be better to check if the cat file is commented out in the inf file or not. If it is commented out, then maybe it is worth checking whether it works or not if uncomment it. > >> Thanx for helping!!! >> Happy xmas for all of you wishes Ekkehard >> > > Ho-Ho-Ho Merry Christmas, Merry Christmas to all! It is quite nice to have a long year end vacation, my vacation starts on 22-Dec-2002 and will only need to be back to work on 3-Jan-2012. :-) -- Xiaofan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X