Registered member login:
Register Now
Altirigos » Homepage2

» Current Poll
Do you leave the Aclient enabled?
YES - 82.31%
107 Votes
NO - 17.69%
23 Votes
Total Votes: 130
You may not vote on this poll.
» Stats
Members: 9,496
Threads: 11,750
Posts: 55,298
Top Poster: Nick (4,981)
Welcome our newest member, JessicaD
» Online Users: 46
0 members and 46 guests
No Members online
Most users online at once 294, 06-30-2007 at 12:24 PM.
» March 2010
S M T W T F S
28 1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31 123
View Single Post
Old 11-21-2008, 07:10 AM   #18 (permalink)
Keslaa
 
Keslaa's Avatar
 
Status: Super Altiris Admin
Join Date: 05-19-2005
Location: Minnesota, USA
Age: 45
Posts: 114


Thanks to rlgura, I got the fix. The change in the .INF file is to add the line

%USB\VID_0A5C&PID_5800.DeviceDesc%=cvusbdrv.Dev, USB\VID_0A5C&PID_5800

under the Device Section. After that, no more hardware bangs!

UPDATE: In using the changed .INF file, I am able to step through the New Hardware Wizard without a problem. However, when used within our HII, the device is not enumerated in the Device Manager. I can step through the wizard, but the point is to NOT have to do that.

As a side note, on a couple of the devices (IDT High Def Audio and Intel Integrated Video) the Found New Hardware wizard pops up until after the app for the hardware is installed. The drivers are exactly the same but for some reason they are not registered until later. Any ideas on that front?

Last edited by Keslaa; 12-01-2008 at 12:38 AM..
Keslaa is offline   Reply With Quote
 
Powered by vBadvanced CMPS v3.0 RC2

All times are GMT -4. The time now is 02:25 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
vB.Sponsors
Altirigos