[Fonceur]

Thanks to this site my unattended CD is almost done and I just need to iron out some little problems here and there...

My first problem is that Windows XP corp installs a Plug and Play monitor instead of the monitor file that I put in my driver folder (.inf file that I created with Powerstrip for my HDTV). Is there any way to force it to use that monitor file instead? By searching the forums all I could find was someone thinking about doing that, but not actually doing it...

[Bâshrat the Sneaky]

I'd like to know this too!

[my2001]

(removed)

[Fonceur]

my2001, on Jun 21 2004, 12:05 PM, said:

But did you test your CD using VMWare or VirtualPC?

I am doing an actual installation on a spare drive, since it is so easy with a CD rw... I just don't like getting stuck with 720x480 until I load the monitor .inf file myself...

[my2001]

(removed)

[Fonceur]

my2001, on Jun 21 2004, 12:40 PM, said:

Do you use a D-SUB-cable, i.e. not BNC?

I am connected by a DVI cable... I know that there is no way for Windows to check that specific monitor file and say "oh, that monitor would go well with that driver file", which is why my question is about a way to force a driver install for a specific hardware (my monitor)...

[Tyke]

I use the following to update my monitor:
"devcon update "D:\drivers\sony\sonylcd.inf" "Monitor\SNY0280"
This line is in my cleanup.cmd file, and the devcon.exe file is in the system32 folder. Works a treat!

[PhillTheChill]

Fonceur could you elaberate.
What does the "Monitor\SNY0280" part do where is it? what is it?

TIA
Phill

[PhillTheChill]

Also how do you install the icm file?

[TechTalker]

I assume that the correct settings would be used automatically at installation time if you put the monitors INF, ICM and CAT files into the OEMPnPDriversPath.
The monitor needs to support PnP for this to work.

To update the driver after installation you can use devcon.exe as mentioned by Tyke. If you need to detect the device automatically you could also delete the device and have Windows detect it. This may also be done with devcon. You need to put the driver files in OEMPnPDriversPath first.

I didn't try this with monitors yet but it works with other devices. So why not with monitors?

[bonedaddy]

Here you go try this works

every time for me and the

Gentleman who posted it "Cydine"

I edited monitor.inf in I386 and commented out the line:

%*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

then added my monitor driver via OemPnPDriversPath.

This way drivers are installed whether signed or not.

Cydine

good luck

bonedaddy

[Fonceur]

Tyke, on Jun 23 2004, 01:20 AM, said:

I use the following to update my monitor:
"devcon update "D:\drivers\sony\sonylcd.inf" "Monitor\SNY0280"

Thanks Tyke, that method did the trick! I got the devcon file from MS site and the .inf monitor file had the internal model name of the monitor. So I ended adding this to my cleanup.cmd (the start /wait is probably overkill for that but...):

start /wait %CDROM%\Apps\devcon update "%CDROM%\Apps\Hitachi_50v500.inf" "Monitor\HTCD7A6"

I tried the bonedaddy/Cydine method but it did not work in my case.

[Bâshrat the Sneaky]

And how could you do this in a universal way? Instead of specifying a monitor I mean...

[Fonceur]

Bâshrat the Sneaky, on Jun 23 2004, 12:38 PM, said:

And how could you do this in a universal way? Instead of specifying a monitor I mean...

If you are sure to include all the right monitor drivers that you might need, I guess you could use the method mentionned by bonedaddy and maybe remove even more default/plug and play monitor detection... This way it would have to fall back on your new drivers instead. It would probably be tricky to find out what to remove though...

[Sgt_Strider]

Hi guys, I am interested in this method as well. I have a LG Flatron 915FT Plus and do I need to specify the monitor like what you guys just did? Thx

[Bâshrat the Sneaky]

Fonceur, on Jun 23 2004, 10:12 PM, said:

Bâshrat the Sneaky, on Jun 23 2004, 12:38 PM, said:

And how could you do this in a universal way? Instead of specifying a monitor I mean...

If you are sure to include all the right monitor drivers that you might need, I guess you could use the method mentionned by bonedaddy and maybe remove even more default/plug and play monitor detection... This way it would have to fall back on your new drivers instead. It would probably be tricky to find out what to remove though...

Could it perhaps be possible to entirely REMOVE monitor.inf?

[Fonceur]

Bâshrat the Sneaky, on Jun 24 2004, 02:44 AM, said:

Could it perhaps be possible to entirely REMOVE monitor.inf?

Hmm, I guess that might work... Your best bet is probably to ask the people that made reducing tools like nLite and the other batch files about it. Who knows, they might be interested to adding that too if they see some interest...

[Sgt_Strider]

Just wondering has anything changed regarding installing a monitor driver unattended? Thx

[Bâshrat the Sneaky]

Unfortunately I haven't done any further research on this topic. Maybe in the future... But it's not a priority to me.

Bâshrat the Sneaky

[prathapml]

Sgt_Strider, on Oct 10 2004, 06:14 PM, said:

Just wondering has anything changed regarding installing a monitor driver unattended?

Please see the devcon command described above.

As for my own adventure:
I did see that when I used the drivers on the floppy-disk that came with my Samsung monitor, it did install that one unattended. But what use is this:

SyncMaster 703(M)s/ 753(M)s/750(M)s/753(M)v, MagicSyncMaster CM173A(M)

Ha ha.... That's what the INF contained, and that's what the monitor name in display properties showed up as.

So I changed the monitor name in the INF to have the name of my monitor alone, and not the entire product segment. But, as is obvious, that broke driver signature, and the .CAT of the driver could not validate it anymore. Installing it manually works now, with a dialog about non-WHQL driver, but unattended has been no go.


Other than that, I have a few things that I'm yet to try out myself. So the below is untested ideas:
Maybe deleting monitor.inf and replacing it with your own monitor's INF file - and if it contains associated DLLs/ICMs you need to have it copied over to the system as well (txtsetup.sif).
Or... disabling driver signing.
Or... Make your own INF and your own .CAT (this one is highly improbable, I think).