MadCat1968

Here's my current Install.cmd file (@T-12) for installing ATI AIW display drivers. It also shows how I load the sound and an alternate display drivers too. Found out that for proper operation, I need to insert a little bit of a delay between installs. It seems the most natural way to install the display driver set distributed by the vendors. I just don't like to whack my brain and wonder if I've installed everything or not using the PnP method. REM cmdow @ /HID @echo off set ONE_MATCHES="s/.* matching device(s) found./set deviceInstalled=yes/" set NO_MATCHES="s/No matching devices found./set deviceInstalled=no/" echo Installing DirectX9 HOTFIX ... start /wait %systemdrive%\Install\DirectX90-KB839643-x86-ENU.EXE /Q /O /N /Z sleep 2 echo Installing Windows Media Encoder... start /wait %systemdrive%\Install\Multimedia\WMEncoder\WMEncoder.msi /qn sleep 2 set DEVICE_ID="PCI\VEN_8086&DEV_24D5&SUBSYS_1021147B" devcon find %DEVICE_ID% | sed -e "/^PCI\\VEN.*/d" -e %ONE_MATCHES% -e %NO_MATCHES% >%systemdrive%\Install\deviceCheck.cmd call %systemdrive%\Install\deviceCheck.cmd if %deviceInstalled% == yes ( echo Installing Realtek Audio Driver... start /wait %systemdrive%\Install\Audio\Realtek\setup.exe /s sleep 2 ) set DEVICE_ID="PCI\VEN_10DE&DEV_0200&SUBSYS_064E10B0" devcon find %DEVICE_ID% | sed -e "/^PCI\\VEN.*/d" -e %ONE_MATCHES% -e %NO_MATCHES% >%systemdrive%\Install\deviceCheck.cmd call %systemdrive%\Install\deviceCheck.cmd if %deviceInstalled% == yes ( echo Installing NVIDIA GeForce Display Driver... start /wait %systemdrive%\Install\Video\NVIDIA\61.76_winxp2k_english_whql\setup.exe /s sleep 2 echo Installing NVIDIA WDM VIVO Capture Driver... start /wait %systemdrive%\Install\Video\NVIDIA\2.20_wdm-vivo\setup.exe /s sleep 2 ) set DEVICE_ID="PCI\VEN_1002&DEV_4E48&SUBSYS_4F721002" devcon find %DEVICE_ID% | sed -e "/^PCI\\VEN.*/d" -e %ONE_MATCHES% -e %NO_MATCHES% >%systemdrive%\Install\deviceCheck.cmd call %systemdrive%\Install\deviceCheck.cmd if %deviceInstalled% == yes ( echo Installing ATI Radeon Display Driver... start /wait %systemdrive%\Install\Video\ATI\wxp-w2k-8-03-040610a-016126c\setup.exe /s sleep 2 echo Installing ATI Radeon Control Panel... start /wait %systemdrive%\Install\Video\ATI\control-panel-8-03-040610a-016126c\setup.exe /s sleep 2 echo Installing ATI Radeon WDM Capture Driver... start /wait %systemdrive%\Install\Video\ATI\tv-capture-wdm-6-14-10-6240\setup.exe /s sleep 2 echo Installing ATI AIW Radeon DAO/MDAC... start /wait %systemdrive%\Install\Video\ATI\mmc-9-1-0-0-dao-mdac\setup.exe /s sleep 2 echo Installing ATI AIW Radeon Multimedia Center... start /wait %systemdrive%\Install\Video\ATI\mmc-9-1-0-0\setup.exe /s sleep 2 echo Installing ATI AIW Radeon DVD Decoder... start /wait %systemdrive%\Install\Video\ATI\DVDDcdr\setup.exe /s sleep 2 )

Figured out a Win32 application to dismiss the rogue dialog box that pops up on successful install of the 3ware RAID driver at T33 minutes ("3wareAcknowledge.cpp"): #include <windows.h> int WINAPI WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { HWND hwnd = NULL; while (hwnd == NULL) { hwnd = FindWindow (NULL, "Installation Complete"); Sleep (1000); } SendMessage (hwnd, WM_CLOSE, 0, 0); return 0; } Compiled "3wareAcknowledge" binary takes only 36KB of disk space. Here's my mt39 script: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <mt39> <version>0.3.1</version> <item> <program>%systemdrive%\3wareAcknowledge.exe</program> <arguments>bogus</arguments> <hide>0</hide> <wait>-1</wait> </item> <item> <program>%systemdrive%\Drivers.exe</program> <arguments>-y /q /r:n</arguments> <hide>0</hide> <wait>0</wait> </item> </mt39> When the 3ware "Installation Complete" dialog box pops up at T33 minutes, the "3wareAcknowledge" program, which was spawned off as a background process by mt39, kicks in and dismisses the dialog box automatically. You may have a bug with null argument processing with mt39 (haven't tried your latest version yet). I had to pass a bogus argument for "3wareAcknowledge" to prevent mt39 from crashing (see script above). Thank you for the mt39 utility!

I'm not running a "setup.exe". I'm just trying to keep the dialog box from popping up when the RAID driver comes "online". This is just the normal INF detect and install. I'm installing the 3ware RAID device driver via "OemPnPDriversPath" method. I could install the 3ware driver via the setup.exe method at t12 where the jscript environment is present. But I'm trying to do it the right way via the "OemPnpDriversPath" method.

I did something like (didn't save the actual script so typing out from memory): "%systemdrive%\WINDOWS\System32\wscript.exe %systemdrive%\3wareCheck.js" The JS script works fine from a full blown windows installation, but not from a Windows pre-install environment at t39. I'm going to try to create a Win32 application that performs the same tasks as the following jscript (3wareCheck.js): function getWin(win, inc) { while (!WshShell.AppActivate(win)) { WScript.Sleep(inc); } return true; } var WshShell = new ActiveXObject("WScript.Shell"); getWin("Installation Complete", 5000); WshShell.SendKeys ("{ENTER}"); WScript.Sleep(100); WScript.quit(); I've been studying the Unattend Install link for the last two weeks. I believe this window pops up for normal F6 installs of 3ware drivers anyway (IIRC). Attached is my attempt to invoke the jscript interpreter at t39 (The 3ware script has been spawned off into the background; mt39 is waiting for the 7z extraction task to complete):

I did get mt39 to work. I had to re-download the package to get the updated version of mt39. My copy was corrupt or something. I'm excited by the potential of this utility and learned something new in the process. Unfortunately for me, I found that jscript can't execute that early so I can't put this utility to good use until I find another way to dismiss the rogue dialog box that pops up on succesfull install of 3ware RAID driver. Not really unattended install until I resolve this problem.

Using the mt39 method, my SFX archive fails to extract and it does not pop up any window indicating % extraction completed. The old way works: [GuiUnattended] AdminPassword=* AutoLogon=Yes OEMSkipWelcome=1 OEMSkipRegional=1 TimeZone=35 DetachedProgram="%systemdrive%\Drivers.exe" Arguments="-y /q /r:n" But not the mt39 way: [GuiUnattended] AdminPassword=* AutoLogon=Yes OEMSkipWelcome=1 OEMSkipRegional=1 TimeZone=35 DetachedProgram="%systemdrive%\mt39.exe" Arguments="%systemdrive%\default.xml" <?xml version="1.0" encoding="UTF-8" standalone="no"?> <mt39> <version>0.3</version> <item> <program>%systemdrive%\Drivers.exe</program> <arguments>-y /q /r:n</arguments> <hide>0</hide> <wait>0</wait> </item> </mt39> Did I do something wrong here? I hope to employ the mt39 method to add more commands later to take care of rogue dialog boxes that may pop up on some vendor driver installs (3ware RAID drivers in particular). This is for home use. Thanks!

Is there a way to keep the unattended install from hanging when a driver install pops up an "OK" input dialog box? (I have to click "OK" before installation can continue pass that point.) Window Title: "Installation Complete" Message: "The 3ware Escalade Service has now been successfully installed." Button: "OK" Tried to work around the problem using the following scripts via the "cmdlines.txt" method, but it hangs the MSDOS command line interpreter when the wscript command is executed: $OEM$\cmdlines.txt [COMMANDS] "Install.cmd" "RunOnceEx.cmd" $OEM$\$1\Install\3wareCheck.js function getWin(win, inc) { while (!WshShell.AppActivate(win)) { WScript.Sleep(inc); } return true; } var WshShell = new ActiveXObject("WScript.Shell"); getWin("Installation Complete", 5000); WshShell.SendKeys ("{ENTER}"); WScript.Sleep(100); WScript.quit(); $OEM$\Install.cmd REM cmdow @ /HID REM @echo off REGEDIT /S %systemdrive%\Install\RegTweaks.reg start /wait %systemdrive%\Install\Audio\Realtek\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Video\wxp-w2k-8-03-040610a-016126c\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Video\control-panel-8-03-040610a-016126c\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Video\tv-capture-wdm-6-14-10-6240\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Multimedia\WMEncoder\WMEncoder.msi /qn sleep 1 start /wait %systemdrive%\Install\Video\mmc-9-1-0-0-dao-mdac\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Video\mmc-9-1-0-0\setup.exe /s sleep 1 start /wait %systemdrive%\Install\Video\DVDDcdr\setup.exe /s sleep 1 wscript %systemdrive%\Install\3wareCheck.js start /wait devcon install %systemdrive%\Install\3ware\oemsetup.inf PCI\VEN_13C1 sleep 1 The 3wareCheck.js script works ok from a user MSDOS shell environment, but not from inside an unattended install MSDOS shell environment.