I think driver and laptop detection in dos would be too complicated to setup and then keep up to date. Where I work we have a PnP drivers directory per PC model (stored as a zip file). Build engineers pick the PC model from a list (enumerated on the fly) before Windows is installed. This way we know throughout the rest of the build the make (eg IBM) and model (eg ThinkpadT20) of PC. The fact that the PC is a desktop or laptop is also determined from this selection. The vendor's PnP drivers for the model (ripped from factory image) are unzipped and environment variables set eg:
set make=IBM
set model=IBMT20
set deskorlap=laptop
Sent this before but here's our tool for making per model pnp zip files containing make, model and desktop/laptop info for pre Windows install pick list.
Your development seems to be headed towards master scripts and subscripts to support organisations with several different configurations of PCs based around a single 'standard'.
We have 4 groups of apps/installs
- Core apps (for eveyone, eg Office, acrobat reader, winzip)
- Department apps (per department, eg Traders, Accounting, IT)
- DeskorLap (desktop apps or laptop apps eg VPN client, RAS dialler, Safeboot HD encryption, offline e-mail config)
- Vendor apps (make model specific apps and non PnP drivers eg Thinkpad utils, Compaq Management agents, HP keyboard)
BTW I think this unattended list is great. I borrow loads of great scripts and ideas from it. Please keep it up!
Alex
Want to chat instantly with your online friends?�Get the FREE Yahoo! Messenger
