|
This Question is Answered
1 "helpful" answer available (10 pts)
Found ONE instance of this problem with E6400's ..
Interestingly enough the person affected was able to get the machine's mouse and keyboard to responds once it booted into safe mode and to load the drivers there manually.
The agreement was made that the person in question would try to reconfigure the sysprep to include additional drivers for the Dell E6400 laptop chipset - that seems to have fixed them. Looks like this particular critter's not as straight forward as many of us would like 
Hope this helps.
Paul Hoffmann
LANDesk EMEA Technical Lead
My problem with the new Dell E6400 series is, that the driver-installation is not working properly!
I use N-Light to include all drivers into the Windows XP Prof.-Image and deploy it with LanDesk Provisioning.
Everything seemed to be perfect, but I have to klick ones on a driver-detection. 
( "driver succesfully installed" )
... that mask interrups my OSD-Task
The rest is working silently with no user interaction ... ( formating, OS and a lot of software in about 46 Minutes)
greetz from vienna
This may appear a strange idea, but maybe keeping a driver-friendly PCMCIA NIC on the backburner for those models where you must get "more creative" may be a bit of a band-aid. At least until you can convince your OEM to provide you proper drivers (not much we can do there ourselves - sorry) 
.
At least that way, you can get an OS imaged down on the machines in question, and that's half the battle won.
Paul Hoffmann
LANDesk EMEA Technical Lead
You forgot to attach the files mate
I don't see why there should be a problem with us keeping a driver here (it's not like those get charged for normally), unless this is maybe some obscure "we charge you if you want the non-exe form driver" scheme by Dell in this case (though that would be new to me).
So unless there's any directly chargeable thing, I'd say we should be OK. If we should get contacted by a disgruntled Dell in the future about it, we can remove it then without an issue of course (though - again - since it's "just a driver" and not any kind of "here's software you have to pay for, for free" scenario, I don't see that happening).
So once you attach the zip, this should be good to go. Thanks also for the steps & instructions -- great of you to share
Paul Hoffmann
LANDesk EMEA Technical Lead
I didn't forget, i tried but the proxyserver i sit behind failed to allow the uploads. 
I will email them home and upload them from there, should be done by the end of the day
<EDIT>
Files should now be uploaded
Message was edited by: drew Mackay - Uploads Added
Wow - that's a bastard of a place to freeze up in .
scratches beard
I don't even have a single bit of material on how to diagnose/troubleshoot that stage ... you had any luck on MS forums for this? If you at least can find out why it's hanging at that stage, then you stand a reasonable chance of finding out what's causing it (i.e. "it doesn't like the driver for component X" or such) ..?
Paul Hoffmann
LANDesk EMEA Technical Lead
Here is the solution to my problem:
The Image was made on a HP desktop with both SATA and IDE hardware.
In some way, files from the SATA driver, or the driver itself caused problems when trying to deploy a H/W independent image.
We called Dell and they put us on the track of the solution.
The result was making a new image on the Laptop, because there was no time left before going live. 
Now we have 2 H/W independent images, So we have still some work to do.
Next thing up is to uninstall some drivers, deleting registry keys or whatever we find. Later.
| ||||||
