Unattended monitor driver install [winxp_sp2]

[the_doc735]

Preamble:

I hope this works successfully for everyone, just as it has for me?

Unfortunately the methods outlined by: PhreeZ, Fonceur, Tyke, bonedaddy, cydine, hp38quser, etc etc didn't quite work for me, but here's the variation for anyone whose having 'trouble'.

Requirements:

Use notepad to edit the inf files and create batch files/runonceex.cmd.

Makecab and expand (command-line tools) should be in your system! If they are not then do a google search and download them and place them in the system, (makecab/expand.exe are incase you want to edit your own MONITOR.IN_ file).

Carry out "the-same" instruction for 'devcon' or go here: http://support.microsoft.com/kb/311272.

Here's 'the-thing' about "make'n'expand": http://unattended.msfn.org/unattended.xp/view/web/16/

Devcon.exe: Device Console Utility

This command-line tool brings many of the functions of Device Manager to the command window. Devcon enables, disables, installs, configures, and removes devices on the local computer and displays detailed information about devices on local and remote computers.

devcon [-r]update (Updateni = no interaction!!) <inf> <hwid>

Update drivers for devices.

This command will only work for local machine.

Specify -r to reboot automatically if needed.

<inf> is the .INF file you want to use to install your monitor.

All devices that match <hwid> (hardware ID) are updated. In this case "*PNP09FF". ("Plug and Play Monitor").

'Walk-through':

1. OK, lets go to the I386 folder in your working windows copy.

2. Search for monitor.inf (.IN_) files: 2,3,4,5,6,7,8. Delete these as they are useless!

3. Now go to DOSNET.INF file and use find to locate the same file references therein and delete them!

4. Now go to txtsetup.sif file and use find to locate the same file references therein and delete those too!

5. Now overwrite the monitor.in_ file in the I386 folder with the one attached herewith.

DON'T PANIC!! - after this (in a working setup) you would see: "other devices-monitor?" in device manager - but that is exactly what we want, so that 'our' driver is (in-effect) detected as a 'better' and more compatible match! (see attached screenshots).

6. Create a folder path in your working windows copy [root] like so:

- XPCD\$OEM$\$1\Install\<your monitor> (I named mine "LG").

- (see attached screenshots).

7. Place your monitor driver files in this folder. (.INF, .ICM, .CAT, etc).

8. Create a batch file, name it after your monitor model, (I named mine <L1915S> "L1915S.CMD").

9. Place this in your "$OEM$" folder.

10. Copy this code in the file:

cmdow @ /hid

@echo off

title <your monitor make/model>

start /wait devcon update %systemdrive%\Install\<your monitor make/model>\<your ".INF" file> *PNP09FF

exit

11. Save and close that file.

12. Create a cmdlines.txt file.

13. Place it in the "$OEM$" folder.

14. Copy this code in the file:

[Commands]
"<your batch file name>.cmd"

15. Save and close that file.

16. Open your .INF file in notepad.

17. Find your <HWID> (as an example mine is: "Monitor\GSM4A90") - i.e. Monitor\<something>.

18. Now, replace each instance of this text with "*PNP09FF" (without quotes).

19. Then add this code:

[version]
DriverPackageType=PlugAndPlay

20. Then overwrite this section:

[ControlFlags]
ExcludeFromSelect.NT=Plug and Play Monitor
ExcludeFromSelect=Monitor\Default_Monitor

21. Save and close that file.

22. Don't forget to include this code in the WINNT.SIF file (in> I386 folder) as the '.cats' probably won't work as a result of mods. to the '.INF' files:

[Unattended]
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore

23. Save and close that file.

7z:

I have included a couple of screenshots for the device manager and color management to illustrate what it looks like after setup finishes as well as those showing the folder structure of a working XP resource and what happens in device manager 'BEFORE' your monitor driver is installed. There is also some tools and a copy of the setupapi.log as well as the modified 'monitor.in_' file.

For a 'runonceex' method go here: http://unattended.msfn.org/unattended.xp/v...2669b042ed6e98/

For a [guirunonce] method go here:

http://unattended.msfn.org/unattended.xp/view/web/81/

GOOD LUCK!!

You are quite welcome to improve on this method, if you so wish!

monitor_method.7z

Edited October 14, 2006 by the_doc735

[The Glimmerman]

Maybe a stupid question.

But when you use this code it also works.

devcon update Your.INF *PNP09FF

Or is it just luck for me.

[the_doc735]

Maybe a stupid question.

But when you use this code it also works.

devcon update Your.INF *PNP09FF

Or is it just luck for me.

@glimmerman

I'm glad that you have found a method that works already! I don't know if you were lucky or not but I've just spent 4 weeks on and off with this problem.

I had left plenty of posts before I discovered my method, asking for help from anyone with any idea. If you had told me this 4 weeks ago I would have certainly tried it out for myself, but as it is - it's too late for me personally, but no doubt others will try it - now that you have mentioned it!

WELL DONE!

[the_doc735]

Just a quick thought:

...with your modified driver.inf file and my modified monitor.in_ file it may be possible to use either:

1. rundll32.exe (the install feature)

"rundll32.exe setupapi,InstallHinfSection DefaultInstall 132"

http://msdn.microsoft.com/library/default....hinfsection.asp

http://www.computerhope.com/issues/ch000570.htm

http://www.robvanderwoude.com/rundll.html

2. DPInst (a DIFx feature)

http://msdn.microsoft.com/library/default....0bec3a7.xml.asp

http://msdn.microsoft.com/library/default....335312e.xml.asp

http://msdn.microsoft.com/library/default....de0e60b.xml.asp

Please let me know if you try this and tell me how you get on?

Edited October 14, 2006 by the_doc735

[the_doc735]

At this point there are no monitor 'drivers' loaded:

...then the hardware is auto detected when the cmd file is executed:

...once the hardware 'driver' is installed you can view its details from the device manager:

Here are 'the events' as they are logged:

Edited October 14, 2006 by the_doc735

[The Glimmerman]

I'm going to try this DPInst.

For people who want to try this out also.

I think I found the link

[0d14r3]

What is the vantage from Personal Monitor ( LG FLATRON L1750, example only) upper Monitor Plug and Play?

What is the difference for me?

[the_doc735]

What is the vantage from Personal Monitor ( LG FLATRON L1750, example only) upper Monitor Plug and Play?

What is the difference for me?

@0d14r3

System-Supplied Device Setup Classes:

Monitor:

Class = Monitor

ClassGuid = {4d36e96e-e325-11ce-bfc1-08002be10318}

This class includes display monitors. An INF for a device of this class installs no device driver(s), but rather specifies the features of a particular monitor to be stored in the registry for use by drivers of video adapters. (Monitors are enumerated as the child devices of display adapters.)

OSR online

Edited October 15, 2006 by the_doc735

[0d14r3]

@the_doc735

the features of a particular monitor to be stored in the registry for use by drivers of video adapters.

My monitor is normal 1280x124 no widescreen and do not rotate, no flicker at 75 hz - Plug and Play.

I do not understand what is your point. For your monitor what is a real advantage ?

Be more especific.

Thanks.

[pmshah]

Perhaps the answer I am looking for may be found in this thread.

I am working on a 200 mb unattended mini xp installation. I have afncy for these 8 cm pocketable CD media. Space wise I can include all the drivers I want on this Cd after creating self extracting cab executables, with space to spare.

Now my questions are...

1. Where can I get the list of <hwid> like *PNP09FF.

2. Will this work with unsigned drivers?

Any help would be appreciated.

[the_doc735]

1. Where can I get the list of <hwid> like *PNP09FF.

2. Will this work with unsigned drivers?

Any help would be appreciated.

1. .INF files have <hwids> and devcon lists them; maybe other ways too?

2.yes.

[Unattended]
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore

[pmshah]

Some of the hardware have hwid list 6-7 lines long. Should I just pick the compatible one with the least number of " arguments !"