AlBundy33

At first I would suggest to change %CDROM% to %ROOT% because %ROOT% is the upper-level of the WPI-folder. With this setting you can start WPI from every place. If you want to start WPI from a network-share you can use this batch-file @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET SHARE= IF NOT "%~1"=="" SET SHARE=%~1 IF "%SHARE%"=="" ( TITLE Running local WPI... PUSHD "%~dp0" CALL :RUN POPD ) ELSE ( TITLE Running WPI from "!SHARE!"... PUSHD "!SHARE!" ECHO.Mounting "!SHARE!" to "!CD!"... CALL :RUN ECHO.Unmounting network-drive... POPD ) GOTO :END :RUN PUSHD WPI ECHO.Starting WPI... START /wait "%WINDIR%\mshta.exe" wpi.hta POPD GOTO :END :END Put this file in your share-folder (where wpi, i386, applications, ... exist). If you start this batch file locally it will start you wpi. if you start it from the share it should start wpi from the share - if there are problems copy the file to the remote-pc and change the line SET SHARE= to SET SHARE=\\YOUR_SERVER\YOUR_WPI_SHARE and it should work. Al

Type2-Hotfixes (that with the yellow icon - e.g. WindowsXP-KB923789-x86-DEU.exe) can be extracted with 7-Zip Command-line version (not 7za.exe). This command-line version is included in the installer - you'll need 7z.exe, codecs-, formats- and lang-folder (just put them into HFTOOLS). Syntax is the same like 7za.exe but it can extract more archives (e.g. the Hotfixes, RAR, ...). It's also possible to extract the Type1-Hotfix but the result is a set of _sfx_00xx._p files. Maybe we'll find a way to use 7z.exe to extract the hotfixes - I think this would be a good solution to fix the focus-"bug". Al

#1. located #2. Looks good - I will test it. #3. And what about the ISO-output-folder? In Version 1.4.2 I tried ISONAME=..\HFSLIP.ISO but this doesn't really work. #4. works #5. Hope that somebody will find a solution. [EDIT] To #5: What about cmdow.exe? Maybe it's enough to start the hotfixes with ... cmdow /RUN /HID %%I /Q ... It should be enough to to something like IF EXIST HFTools\cmdow.exe ( SET RUNHIDDEN=HFTools\cmdow.exe /RUN /HID ) ELSE ( SET RUNHIDDEN= ) and start the hotfixes with ... DO %RUNHIDDEN% %%I /Q... [/EDIT] Al

Could you please describe what you want to do? Al

Ok it's no problem remove the "I HAVE..."-dialog but I think this is a good "expert"-setting for people who know what they are doing. It's also no problem when all have to use the SOURCESS-folder but I think that a configurable ISO-output-folder is a good thing. I tried to put my folders (DOCS, SUPPORT, ...) to the SOURCE-folder and it really works - they are also in SOURCESS. To #5: I already said that this is a strange thing. Al

First: REALLY COOL PIECE OF CODE My first way to integrate the hotfixes was during T-13 with svcpack.inf but this takes a lot of time to install - the hfslip-way is definitely the best way. But I have some wishes for the next release: 1. please add a setting tt HFANSWER.INI to suppress the "I HAVE READ THE INSTRUCTIONS"-"dialog" 2. I need also an option like CREATEISO in HFANSWER.INI to enable or disable the iso-building - I have cdimage.exe in my HFTOOLS-folder an so HFSLIP builds everytime the ISO 3. it would be very nice to set the output-path for the SOURCESS-dir (btw. what means the SS in the dir-name?) and for the ISO-output-folder 4. an extra folder like ROOT would be very nice to put some files on the cd-root (I want to add DOCS, SUPPORT, DOTNETFX and so automaticly on the the image - just to create an orignal xp-cd) 5. this seems to be a strange thing but I hope that there is a solution: If I start hfslip.cmd the console-window grabs sometims the focus and this is really bothering if I want to use another program. Is there a way to keep all hfslip-actions in background? These are my ideas for the next version. Did I mentioned before that hfslip is really great?!? Greetings Al

This is my Autoit-Code to install ProgDVB - this code works also if the setup-window hasn't the focus. ; ---------------------------------------------------------------------------- ; ; AutoIt Version: 3.1.1 ; Author: Hawk ; ; ---------------------------------------------------------------------------- ; Script Start - Add your code below here AutoItSetOption("TrayIconDebug", 1) AutoItSetOption("WinWaitDelay", 500) AutoItSetOption("SendKeyDelay", 50) $PID = Run("ProgDVB4.83FullInstall.exe", @ScriptDir) WinWait("Installation ProgDVB ", "Select language :") ControlClick("Installation ProgDVB ", "Next", "Button1") WinWait("Installation ProgDVB ", "Destination directory :") ControlSend("Installation ProgDVB ", "", "ComboBox1", "{END}") ControlSetText("Installation ProgDVB ", "", "Edit1", EnvGet("PROGRAMFILES") & "\ProgDVB\") ControlClick("Installation ProgDVB ", "Next", "Button1") WinWait("Installation ProgDVB ", " Timeshift ") ControlClick("Installation ProgDVB ", "In file", "Button6") ControlClick("Installation ProgDVB ", "Next", "Button1") WinWait("Installation ProgDVB ", " Modules ") ControlClick("Installation ProgDVB ", "Next", "Button1") WinWait("Installation ProgDVB ", "Installation successfully completed.") ControlClick("Installation ProgDVB ", "Run ProgDVB", "Button5") ControlClick("Installation ProgDVB ", "OK", "Button2") ProcessWaitClose($PID) Al

You can use this code instead: SET CDDRIVE=%~d0 :DONECD If the script is on the cd it gives you your cd-drive-letter. You can also get a path relative to the script-path. ::set a path relative to the script SET DIR=%~dp0..\Anwendungen ::create the absolute path PUSHD "%DIR%" SET DIR=%CD% POPD ::output absolute path ECHO %DIR% Greetings Al

Idea to use vars like %ROOT% in Batch-files: To use wpi-vars in own batch-files WPI should create an WPIVars.cmd on a specified folder (o.g. in options dialog set the path to %USERPROFILE% or %TEMP% or ...) And add the SET-commands (SET ROOT=...) for all WPI-vars to it. On own batch-file we can call this file and access all WPI-vars in it (e.g. %ROOT%\Tools\myTool.exe). Al

If you have white-spaces in your path to you bat-file you should use this batch-file: @ECHO OFF PUSHD "%~dp0" ECHO Installing the K-Lite Mega Codec Pack start /wait klmcodec159.exe /verysilent /LoadInf="klmcp.ini" /MERGETASKS="icons_mpc\desktop,icons_mpc\quicklaunch,speaker\stereo" ECHO Done! POPD Greetings Al

@mritter: My screen resulution is only 1280x1024. Any news about WPI Pro? Al

Where did you download the cabs?!? 7Zip, Acrobat Reader etc. are coming as a standard setup-routine by default. Did you use HFSlip? --> If so, you need to place the cabs into a folder called HFAAO under HFSlip-folder (klick). BTW: cab is an archive-format from microsoft. You can extrac these files with WinRAR, extract.exe and maybe with 7Zip. Al

All of the commands are windows-commands. Here is my last version of the script: @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET SHARE= IF NOT "%~1"=="" SET SHARE=%~1 IF "%SHARE%"=="" ( TITLE Running local WPI... CALL :RUN ) ELSE ( TITLE Running WPI from "!SHARE!"... PUSHD "!SHARE!" ECHO.Mounting "!SHARE!" to "!CD!"... CALL :RUN ECHO.Unmounting network-drive... POPD ) GOTO :END :RUN PUSHD %~dp0WPI ECHO.Starting WPI... START /wait wpi.hta POPD GOTO :END :END I tested it only on Windows XP - don't know if it work on 2k but think that it works von windows server 2003. TITLE can be removed it doesn't work. PUSHD is very important because it does the same like cd but has UNC-support START should be available on all sindows-os - you can try to replace it by mshta.exe. For this method I I don't know if the script waits until WPI has finished. SETLOCAL could eventually removed - but then you have to replace !SHARE! and !CD! by %SHARE% and %CD% If you change the script as mentioned aove you should have this code (not tested): @ECHO OFF SET SHARE= IF NOT "%~1"=="" SET SHARE=%~1 IF "%SHARE%"=="" ( CALL :RUN ) ELSE ( PUSHD "%SHARE%" ECHO.Mounting "%SHARE%" to "%CD%"... CALL :RUN ECHO.Unmounting network-drive... POPD ) GOTO :END :RUN PUSHD %~dp0WPI ECHO.Starting WPI... mshta.exe wpi.hta POPD GOTO :END :END Don't know if this work but you can try it. Or better: write what error you get by the original script. Greetings Al

AUTOINSTALL is NOT %CDROM%\AUTOINSTALL - AUTOINSTALL is %WPIPATH%\AUTOINSTALL or %CDROM%\WPI\AUTOINSTALL. Maybe this was your problem. [EDIT] Sorry have not seen you modified post. I tihnk on older WPI-versions %WPIPATH% was not implemented. Hava a look into WPI_log.txt (by default on your desktop as far as I know) why install failes. Are you shure that %CDROM% has the correct value? My suggestion is: 1. Don't use own environment-variables in WPI (%WPIPATH%, %CDROM% and some more are created directly in WPI). 2. download the latest WPI and don't modifiy any files on it 3. use your config.js with commands like %WPIPATH%\\AUTOINSTALL\\... 4. test if this configuration works. [/EDIT] Al

Why didn't you use %CDROM%\AUTOINSTALL if %AUTOINSTALL% is the same? If this works the problem is to get the value behind %AUTOINSTALL% - maybe it's an Windows-Problem or an WPI-problem. Where did you set this environment variable? --> %CDROM% is only defined in WPI If you define %AUTOINSTALL% before running WPI I think it's an Windows-problem. I think this would work if you set %AUTOINSTALL%, restart Windows and run WPI. But if you only need %AUTOINSTALL% for WPI you can also use %CDROM%\AUTOINSTALL (this is my prefered solution). Al

Some ideas: 1. Instead to use a fixed numbers of commands replace cmd1-6 with an dynamic array and the 6 inputfields with an textarea (one command per line) - so there is no need to use batch-files. 2. Is it possible to set temporarily some varaibles in the user-environment (e.g. %WPIDIR%, %ROOT% etc.) and set some directories temporarily to the path-variable (e.g. %WPIDIR%\Tools). With the extended path-variable we have access to all programs in %WPIDIR%\Tools directly in WPI and in batch-files. 3. A Keyboard shortcut to invert the selection would be very nice. If WPI runs unattended after XP setup with defaults checked and I want to install the rest I have to click on all checkboxes. [EDIT] 4. Short summary in WPI_Log.txt at the end of the file. Just a short overview how many apps could be installed successfully and how many error occurred. [/EDIIT] Al

At first you should try the following command %SYSTEMROOT%\System32\mshta.exe "%CDDRIVE%\WPI\WPI.HTA" options=useroptions.js config=config.js check=Corporate_Build timer=30 (removed the \ after WPI.HTA) If this doesn't work you could try the following way to start WPI via RunOnceEx Create WPI_RunOnceEx.cmd in that directory where WPI exists. Add the following line to this file: REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\999" /v 1 /d "%~dp0WPI\WPI.hta" /f And add the following lines to your cmdlines.txt in $OEM$-directory. [COMMANDS] "\path_to_cmdfile\WPI_RunOnce.cmd" Good luck. Al

But if wmp11.exe and the manual way works why you want to use setup_wm.exe?!? Maybe this is your problem: If you have a look into wmp11.exe you will see that there is a control.xml which setup_wm.exe assumes in C:\DOCUME~1\SUPER-~1\LOCALS~1\Temp\tmp41546.WMC but if you have extracted wmp11.exe the file only exists in your extracted directory and not in your temp-directory. So I think that setup_wm.exe wants to download the file - maybe there are more errors because setup_wm.exe don't find it files. Al

Did you have the problem if you are running wmp11-windowsxp-x86-enu.exe and setup_wm.exe or only if you use setup_wm.exe? Can you install WMP11 manually or does it also terminate? Al

@Super-Magican: Are all post SP2-hotfixes installed on your system? If not you can try the update-pack from winboard.org Al

I think it's not possible with WPI (for now) but you can start the setup from a vbs-file. Create a vbs-file, make your query and if manufacturer is vmware you can run your setup with these lines of code: Dim shell Set shell = CreateObject("WScript.Shell") 'Syntax: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/wsmthrun.asp shell.Run "notepad.exe", 1, 1 Set shell = Nothing I'm also interessted on your script if it works. Al [EDIT] I tried to create my own script and here is the result: strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_DiskDrive",,48) insideVMware = false path = WScript.ScriptFullName path = Left(path, InstrRev(path, "\") - 1) For Each objItem in colItems If InStr(1, objItem.Model, "VMWare", vbTextCompare) Or InStr(1, objItem.Caption, "VMWare", vbTextCompare) Then insideVMware = true Next If insideVMware Then Set objShell = CreateObject("WScript.Shell") objShell.Run "msiexec /i """ & path & "\VMware Tools.msi"" ADDLOCAL=ALL REBOOT=ReallySuppress /passive /norestart /qb", 1, true End If It was really hard to find the right query. Just add this command to WPI wscript "path_to_script\install.vbs" If you don't use wscript and start directly "path_to_script\install.vbs" you will be asked if you really want to start this script (for security reasons). Please try it an tell me if it works for you. Thanks Al [/EDIT] [EDIT2] The script menitioned above works but VMWare Tools shows an error during install. I created the following script which work without error-message. checkifInsideVMware.vbs strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_DiskDrive",,48) insideVMware = false For Each objItem in colItems If InStr(1, objItem.Model, "VMWare", vbTextCompare) Or InStr(1, objItem.Caption, "VMWare", vbTextCompare) Then insideVMware = true Next 'set ERRORLEVEL (0 = true, -1 = false) WScript.Quit(insideVMware) setup.cmd @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION PUSHD "%~dp0" CSCRIPT /nologo checkifInsideVMware.vbs IF %ERRORLEVEL% LSS 0 ( ECHO Inside VMware. Starting setup... START "" /wait Setup.exe /S /V"REBOOT=ReallySuppress /passive /norestart /qb /log ""%SYSTEMDRIVE%\VMwareTools.log""" ) ELSE ( ECHO Not inside VMware. ) POPD ENDLOCAL Just call setup.cmd in WPI to install VMWare Tools. You can set VMWare Tools to your default selection because they where only installed inside VMware. Al [/EDIT2]

I don't know if setup_wm.exe creates a log file - but you can check your %WINDIR%, %WINDIR%\Temp or %TEMP% if such a log exists. And you should take a look into your event log - maybe the error is listet there. Al [EDIT] It's not exactly your problem but maybe this blog can help you: http://blogs.msdn.com/astebner/archive/200.../29/682936.aspx [/EDIT]

what did you mean with terminates? Did you mean that you fall back to the user prompt or that setup_wm.exe is not listed in taskmanager? If you only fall back to user prompt have a look into the taskmanager if setup_wm.exe-process exists or try this command. start /wait setup_wm.exe /Q /R:N /NoMigrate /P:#e /DisallowSystemRestore If setup_wm.exe really terminates after some seconds try to start only setup_wm.exe to see if it shows an error-message. Al

No problem but whats your problem with setup_wm.exe?!? If you extract wmp11.exe and use setup_wm.exe from command line you only have to use the command inside the quotes from /C:-param. setup_wm.exe /Q /R:N /NoMigrate /P:#e /DisallowSystemRestore The /Q means that the setup will run quiet - so I don't understand what's your problem with this command. If this is not your problem could please explain what you mean? Al

I've copied the command from my svcpack.inf which is 100% working. Of course you have to replace my wmp11-setup-filename with yours (because I have the german version). If you want to try this command line in a shell "wmp11-windowsxp-x86-DE-DE.exe /Q:A /C:""setup_wm.exe /Q /R:N /NoMigrate /P:#e /DisallowSystemRestore""" you have to remove the outer " and replace the "" with " to have this new command line for your shell wmp11-windowsxp-x86-DE-DE.exe /Q:A /C:"setup_wm.exe /Q /R:N /NoMigrate /P:#e /DisallowSystemRestore" Hope this helps. If not you should tell us, what error-message you get. Al