/build/static/layout/Breadcrumb_cap_w.png

Driver Feed problem

I wanted to test out the driver feed feature of the K2000. I installed the window 7 driver for the Dell 2100. It worked OK for this machine... The problem is it blows up my windows 7 install on many previously working machines - including VMWare fusion. Should adding 1 workstations drivers do this? It's not like I went and added a buunch. Removing the drivers and recaching resolves this issue.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: cserrins 13 years ago
Red Belt
0
ddevore,

Even before the driver feed, conflicting drivers are known to cause issues such as you explained, it is probably the storage, chipset or video driver causing the issue. We are working on a way to help resolve this through the driver feed.
Posted by: dchristian 13 years ago
Red Belt
0
ddevore,

In the mean time you might want to add this driver as a post-install task.

Just treat it like any other piece of software and add it to your scripted install / image.
Posted by: ddevore 13 years ago
Fourth Degree Green Belt
0
Thanks for the replies - I've gone back using the post installs. I'll try back with newer versions.
Posted by: dyehardfan 13 years ago
Second Degree Blue Belt
0
I am assuming at some point the driver feed was actually tested against the Dell computers that it shows available drivers for? I backed up my Driver share, deleted all contents, turned on driver feed for ONE machine type and ONE OS version, recached drivers and started a scripted install. Setup can not continue as one or more boot critical drivers are missing.

Driver Feed = Broken.

edit: Win7 x86 on a Latitude 6510
Posted by: ncsutmf 13 years ago
Green Belt
0
This has already been discussed some in another topic, linking here for reference:

http://itninja.com/question/adobe-acrobat-7.0.1-combined-with-admin-install2&mpage=1&key=&#

From what I have seen, I have optiplex 780, 760, 755, 745, and GX620 machines to test with. Out of those, the driver feed, at least at the time, had 760s and 780s, as well as 960s and 980s. Any one of those driver feeds alone would break installs on any of the other model machines. I believe having both the 760 and 780 feeds installed broke the install for all of them. I was able to track an error down to a tcm.inf driver and have not tested yet after removing that driver manually to determine if there are any other errors. That particular driver is considered a boot critical driver, yet it has no device PnP IDs listed in it as best I can tell.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ