MHz

Try this: REG ADD %KEY%\022 /VE /D "Norton Internet Security 2006" /f REG ADD %KEY%\022 /V 1 /D "%systemdrive%\Install\Norton\SYMSETUP.EXE /qn /norestart" /f Note: Msiexec does not have a /noreboot switch so your command would fail and that is even if those switches are passed to the msi itself which the executable may do.

Have a look at the Guide: http://unattended.msfn.org/unattended.xp/view/web/15/ Create your ISO 1st, then use Roxio to burn the ISO to CD or DVD. This prevents issues such as $OEM$ to _OEM_

Thanks, there are tricks to doing alot of tasks. Just need to learn and make good use of them where suitable. @hevnbnd The posted script may work fine with WinMove(), with it's current syntax. Here is a little sample code that can show how WinMove() simply does hide the window off screen. Run('notepad') WinWait('Untitled') Sleep(1000) WinMove('Untitled', '', @DesktopWidth, 10) Sleep(1000) Send('did I work ok') Sleep(1000) For $i = @DesktopWidth To 0 Step -10 WinMove('Untitled', '', $i, 10) Sleep(10) Next Sleep(3000) WinKill('Untitled')

Send() requires an active window, so WinSetTrans() could be used to make the installer window invisible. If you use Control*() functions instead of Send(), then you can use WinMove() to move the 1st installer window off screen, then the remaining windows should also open offscreen. Another option could be to use WinSetState() though it is not as good as you would need to use it on each window that appears. Use WinWait() when using Control*() functions as windows do not need to be active to automate them.

2 different parts of the Winnt.sif. 2 of the same section headers may confuse the interpreter into producing an error. BTW, the Winnt.sif posted would have looked good in [ Codebox ] ... [ /Codebox ] without spaces in the tags.

No problem. That is what I would use if I used Acrobat. Hmm, someone who does not not me well, lol. I like using AutoIt as in general scripting. I must admit that automating some installs can be a pain. Probably about 20% of my installations are automated and the rest are done by silent switches. I used to automate them all, but got tired of the extra effort needed to do it and update them. 100% of my scripts are AutoIt and no need for any CMDOW, Taskkill or any other 3rd party commandline tool that needs to be used with a cmd file. As for seeing any automation of installers is not seen as I use AutoIt to cast a full screen picture on a AllWaysOnTop Gui at T-12 as seen here. No tricks, as only AutoIt scripting. InstallRite seems to give good results for what I have done with it, by means of testing. But I prefer to keep the installer original as the author intended, as it saves doubts as to whether the software will work as to expectation. I have repacked a few installers with Inno Setup. One installer I have, uses Inno Setup v1.2, but is still a good software. Since it has not been updated for about 5+ years, I repacked it as it did not support silent install. No matter what happens, I still use AutoIt to handle the installation. If you want a good helper with dealing with installers, then I recommend CMenu (yeah well, promoting my own product) . This shell extension is made for helping with installations, even if you do not use AutoIt. It also makes template AutoIt scripts for the installers. All of my installation scripts are CMenu created. The scripts are self contained to install silently with switches if identified, shortcut folder moved to a catagory folder and unnecessary shortcuts removed. You can add your own code to add or remove files and every other task imaginable. As you seem to not want to exert yourself into scripting in general, then most above maybe just something to read, but well, I guess someone may enjoy reading about my methods. Oh, don't forget, unattended projects are endless projects as for updating and changing of software ... so learning some scripting will certainly be needed at some point.

InstallShield Tuner 7.0 for Adobe Acrobat may help to achieve your goal with Acrobat Standard. Installers can vary with options available via commandline use, so I think you already realize that snapshot installation packages maybe the only method if you aim too high. There is no single answer that can cover all installers. They all are mostly different and may require different methods to make them install close enough to your expectations. Some members have used programs like InstallRite and have seemed happy. I use AutoIt scripts, others use may purely repacking. I use Inno Setup for repacking into a new installer. The options are available in different forms and there is no real correct or best way to fully have a customed installation of all your software. You perhaps already understand what I have said already, but there is no magic wand for Software Installers that I know of. Sometimes a compromise is needed with Software Installers.

Outlook express shortcut seems to be created at 1st Active Desktop logon. I use a script from HKCU RunOnce to clean up these shortcuts. This is no environmental variable for the Administrator's profile. The code below should do it. %AllUsersProfile%\..\Administrator

Using correct syntax normally helps in any situation. An MSI is not an executable file, so you cannot call it direct. Msiexec runs MSI files so you just need to call Msiexec to achieve the task as shown below. You were missing an "i" in Regedit. Specifing a fullpath to the MSI files is needed as the files are not relative to Cmdlines.txt or in the systems path. If you want to make use of DOS variables such as %SystemDrive%, then add the MSI files into a batch file and execute from Cmdlines.txt.

ideas, which thread should the members post an answer into ? http://www.msfn.org/board/index.php?showtopic=66322&hl= http://www.msfn.org/board/index.php?showtopic=66323&hl= http://www.msfn.org/board/index.php?showtopic=66326&hl= http://www.msfn.org/board/index.php?showtopic=66329&hl= http://www.msfn.org/board/index.php?showtopic=66327&hl= http://www.msfn.org/board/index.php?showtopic=66330&hl=

AutoIt uses DriveGetDrive() to retrieve drive letters. Here is a User Defined Function that will provide the path to the $OEM$ folder on a CD in $variable. $variable = _Drive() MsgBox(0, 'Drive Letter', $variable) Func _Drive() $drive = DriveGetDrive('CDROM') If Not @error Then For $i = 1 To $drive[0] If FileExists($drive[$i] & '\WIN51IP.SP2') Then Return $drive[$i] & '\$OEM$' Next EndIf EndFunc More examples of DriveGetDrive() are available if searched.

Yeah, to scout is baxically to search, but that is fine. I do not believe that I or anyone else has explained the working directory to a meanful concept. I use the working directory and change directory often in scripts to make handling tasks easier.

%AllUsersProfile%\..\ Perhaps this may fulfil your wish.

Thanks. But last time I checked my project folder, my scripts are plain text files also. As for changing name, simple: _NetUser('MHz', '', '', 1) I think you misjudged, I compile nothing.

Indeed scout is recommended, as I tire of giving the same good responses over and over. Thanks, I will accept your last line as a nice compliment. @bigbroantonio You should set your 2nd parameter with a macro as well. Just incase the path can be different for some reason. example: FileCopy(@ScriptDir & "\setup\file.exe", @SystemDir & '\')

Sounds to me that the Working Directory is not the Script Directory, so your relative paths are failing. When working relatively, you should check your Working Directory first before using the relative paths. FileChangeDir() can set your Working Directory. As below, the script checks if the Working Directory is different to Script Directory, and if it is, then change Working Directory to the Script Directory. If @WorkingDir <> @ScriptDir Then FileChangeDir(@ScriptDir) FileCopy("setup\file.exe","C:\windows\system32\") Or you can simply use the @ScriptDir macro. This is the fullpath to the script as shown below. FileCopy(@ScriptDir & "\setup\file.exe","C:\windows\system32\") If @ScriptDir is "E:\folder" then the 1st parameter would evaluate to "E:\folder\setup\file.exe"

Nice. I see it looks tidy, organized and correct. Good to see the Set command being used to benefit the script. I do an all in one function in AutoIt as well. Why not indeed. Func _NetUser($name, $password = '', $groupname = '', $autologon = 0) If $groupname = '' Then $groupname = 'Administrators' Local $key If Not FileExists(EnvGet('AllUsersProfile') & '\..\' & $name) Then RunWait(@ComSpec & ' /c ' & _ 'Net User ' & $name & ' ' & $password & ' /add &&' & _ 'Net LocalGroup ' & $groupname & ' ' & $name & ' /add &' & _ 'Net Accounts /MaxPwAge:UnLimited', '', @SW_HIDE) If $autologon Then $key = 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' RegWrite($key, 'DefaultUserName', 'Reg_sz', $name) RegWrite($key, 'DefaultPassword', 'Reg_sz', $password) RegWrite($key, 'AutoAdminLogon', 'Reg_sz', 1) EndIf EndIf EndFunc

You basically understand the procedure. Some installers can be done silently, some can be silent with some automation assistance and some down right need to be fully automated. If automation is needed, then options are available to hide (i.e. move window off screen) the windows if needed, but can be dependant on the installer. AutoIt is a high level basic language so it can cater for almost any event. Automation is just one of it's strengths. AutoIt can be downloaded here. Scite4AutoIt3 can be downloaded here (if you have no good editor already with tools onboard preset for AutoIt3)

Works for me...

Ensure you have OEMPreInstall=Yes in your Winnt.sif. Installing AutoIt requires a capital S as NSIS installers are case sensitive. If those au3 files fail to execute, then you may need to specify for AutoIt3.exe to run the scripts like shown below. Add this to top of ROE: SET A3=\"%ProgramFiles%\Autoit3\AutoIt3.exe\" Then use Reg Add as below: REG ADD %KEY%\010 /V 1 /D "%A3% %PP%setup_wrar351.au3" /f

I would assume that you are invoking RunOnceEx to execute from GuiRunOnce. You can add the AutoIt3 installer to RunOnceEx. The installer uses /S to silently install. If you want to use Au3 scripts during Windows setup then you can add AutoIt3.exe to $OEM$/$$/System32 to make it in the system path or any other place suitable. I have AutoIt3.exe next to Cmdlines.txt, which is used by the Au3 script next to it which runs each and every Au3 script in the software subfolder. Syntax for executing an Au3 script: AutoIt3.exe path/script.au3 or you can compile the scripts into executables. Here is my basic concept of using AutoIt3 to manage my UA Windows Installation. If you do not have a good programming editor then I would recommend Scite4AutoIt3. Uses /S as well to silently install.

ScriptLogic Installer Design Studio has started it's life as of version 3 but was acquired from masai solutions and used to be called Masai Installer. The program did not get to version 3 overnight . Just thought you would like to know.

Install Textpad: txpeng473.exe /v"/qn" (no recording available for textpad as it is MSI based) Record Flash MX: (based on 2004 setup if same) Flash_MX.exe /a /r /sms /f1"c:\setup.iss" (get setup.iss from C:\ drive root) Install Flash MX: Flash_MX.exe /s /a /s /sms /f1"%~dp0setup.iss" /f2"%temp%\FlashMX.log" (this will read the setup.iss in the scripts directory and record the log in the temp directory.) Someone else may help you with Corporate Time. Or you could try to help yourself with this program, which is a very quick way to Identify an Installer and give advice and actions.

%cd% is a poor method to rely on for being the scripts directory as it is the current (working) directory. A batch file called from the registry, as RunOnceEx does, will return C:\ as the current directory. The best solution was mentioned earlier but %~dp0 has a trailing backslash included, so adding another backslash made it fail. Add the below into a batch file and run it and you will show your solution. @echo off cd /d c:\ echo. echo Current Working directory is : "%cd%" echo. echo Script directory is : "%~dp0" echo. echo Parent of Script directory is : "%~dp0..\" echo. pause REM ~ Open explorer in the script's parent directory. explorer.exe "%~dp0..\"

I accept and value what you have sincerely stated. I indeed admire your words. You are indeed truely, a person of good understanding.