this was my very first attempt. i created a image run it on several machines with different display adapters from intel, ati, nvidia and s3. i installed the drivers and on this specific machine and all the drivers work fine. (Also switching the hdd with display adapter support was smooth).
but e.g. you deploy the image on a machine with a similar but not identical graphics card the driver has to be installed again. i pretty sure this is because of not completly matching pid and vid issues. - some have x3100 or x4500, ati 4x series and so on. (as i mentioned i also tried for intel the iegd drivers, but with no luck at all.)
an absolutly not homogeneous environment.
i'm now pretty sure that dpinst will be the best solution. i can may run it as a service or at login stage.
but there is some behaviour i don't understand.
(may i should start a new thread?!)
Please forget in this szenario that i actually don't want to restart.
I need an explanation about this (for me weird) szenario - this has not that much to do with my original question.
All drivers are WHQL signed (if this is important?!)
Short version:
|Dpinst + Plug in|
1. I run Dpinst and install some drivers (let's take something easy like a usb dongle)
2. i plug in the dongle and it become to life.
- fine | Done.
|Dpinst + Restart + Plug in|
1. I run Dpinst and install the usb dongle
2. i do a restart
3. i plug in the dongle and it pops up the new hardware found wizard. (WHY IS THIS?)
- not fine | this sucks.
|Dpinst + Restart + Plug in + Dpinst|
1. I run Dpinst and install the usb dongle
2. i do a restart
3. i plug in the dongle and it pops up the new hardware found wizard.
4. i abort the wizard
5. run Dpinst again - the secound run of dpinst with inf struktur behind is very very fast (1 sec.) and the device is installed immediately.
- may can be usefull, but not the best solution.
now my imagination would be.
1. install all drivers with dpinst in the first run. "seal" it. done.
2. and then let the driver install automaticly with the deposited drivers.
- but for now it will pop up the damn found new hardware wizard. or the device is found with an exclamation mark in device manager. (and then the very fast secound run of dpinst can fix this).
i want to avoid processes to run if they don't have to.
Last edited by pferd5 (2010-05-04 02:34:24)