MHz

I use msiexec /i "Path to File\daemon.msi" /qn /norestart That is the command that I use to install Daemon's Tools.

You only need quotes for strings with spaces. Very few entries would need quotes.

Just use Regsvr32 on the self registering dlls. Some of the powertoys are not as user friendly to setup. The ones I list are simple. Just add to $$ folder and register them later in windows setup.

You have your titles set for full path to be shown. So I will use a substring option to cater for it Opt("WinTitleMatchMode", 2) For $i = 1 To 2 Run('explorer ' & @WindowsDir) Sleep(20000) WinClose('WINDOWS') Next For $i = 1 To 2 Run('explorer ' & @WindowsDir & '\Fonts') Sleep(20000) WinClose('Fonts') Next

It is called Sysprep. It is preparing, creating an image, and burning to cd/dvd. The ref.chm in deployment tools.cab has details on setting up such a process.

For $i = 1 To 2 Run('explorer ' & @WindowsDir & '\Fonts') Sleep(20000) WinClose('Fonts') Next

Using a For loop to open and close Windows folder twice For $i = 1 To 2 Run('explorer ' & @WindowsDir) Sleep(20000) WinClose('WINDOWS') Next

An example: Master.cmd for %%a in ("Files\*.cmd") do Call "%%~a" The above will execute the *.cmd files in the files directory, next to the script. Create a folder called files and create a cmd script with below in it. Slave.cmd @echo off echo. echo everything is working ok echo. pause Now run the Master.cmd and you will see it execute the Slave.cmd. If you had other *.cmd scripts in files folder, then they would be executed also. If you type cmd /? in the command console. It will tell you what /c does. But as I have stated. Call is the best command for this purpose.

Get the msi files from the folder in the windows directory, then use a admin install on them. Example: "msiexec /a file.msi" to retrieve the files. I use these: Background switcher. BgSwitch.dll BGSwitch.exe Magnifier. Mag.dll Virtual Desktop. Msvdm.dll Image resizer. PhotoToys.dll

Normally, you just need AutoIt v3.1.0 or higher to compile the script. Keep the script in the same directory as the installer. Execute the compiled AutoIt like any other installer. You should not need switches, as the AutoIt file will execute the installer as required. To the question of nLite, unsure of it's operation, as I do not use nLite.

I will help answer that query. Call is internal method to a execute a batch file. The batch file will pause, until the Call to the executed batch ends. The same instance of %ComSpec% does the operation for the entire loop. %Comspec% is executing cmd.exe externally. This means that %ComSpec% is started For each loop. This is by far the slowest and inefficient method.

The msi files are cached in a folder in the windows directory. The files are installed into the system directory.

Consider using [ CODEBOX ] lots of code... [ /CODEBOX ] tags for large display of code. Lots of tweaks in the pinned topic of this forum.

Set AutoPartition=0 or omit it. Repartition will format the 1st drive. If C:\ is correctly setup as your first drive, then D:\ should be safe.

VideoLAN uses the NSIS Installer. NSIS supports /S, /D=InstallPath or /NCRC for no crc checking. Unless the author adds more switches to the NSIS Installer, which is rare, then that is it.

That release should be fine. That has the latest Scite v1.66 that was released on the 26.08.05. Well, that was certainly released quick. Download Scite4AutoIt3 and enjoy.

With your sound scheme entries. You should be able to use "@=-" instead of "@=""". This will set the default value to nil.

Hi xtremexxx, Glad to see your interest with AutoIt. I have been using it for years. It will cover almost any scripting need that you may have. Do not use notepad though, use Scite4AutoIt3. It has all the tools onboard. Au3Recorder and AutoItMacroRecorder to do the recording you mention. A new version of Scite4AutoIt3 should be released possibly this weekend. Give it time, and you will learn it. AutoIt is a nice adventure indeed. And getting better all the time with it's active development.

As mentioned a couple of posts back. Just file and folder handling. That is the limitation of it. Sounds nice, but the editor will not be changed. Look in the help guide under Installation topic. This was added some versions ago. This has a connection to the 2nd request, as I did not create the editor nor the shell extension dll that allows CMenu to operate. Unless Revenger.inc decide to upgrade them, then this is best result available. I will not alter either of these 2 files. Thanks for the idea's though. And I liked your can of.... line.

Your RunOnceEx.cmd cmdow @ /HID @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\005 /VE /D "Adobe Reader 7" /f REG ADD %KEY%\005 /V 1 /D "%systemdrive%\install\AR7\AR7.exe" REG ADD %KEY%\015 /VE /D "Installing GDI Detection Tool" /f REG ADD %KEY%\015 /V 1 /D "REGEDIT /S %systemdrive%\install\GDI\gdi.reg" /f REG ADD %KEY%\015 /V 2 /D "REGEDIT /S %systemdrive%\install\GDI\KB873374.exe /Q:A /R:N" /f REG ADD %KEY%\020 /VE /D "Winodws Genuaine Advantage" /f REG ADD %KEY%\020 /V 1 /D "REGEDIT /S %systemdrive%\install\GWVT\GWVT.exe" /f REG ADD %KEY%\025 /VE /D "Installing Java Runtime Env" /f REG ADD %KEY%\025 /V 1 /D "REGEDIT /S %systemdrive%\install\JRE\j2re.exe" /f REG ADD %KEY%\030 /VE /D "Installing MSN Messenger 7.5" /f REG ADD %KEY%\030 /V 1 /D "REGEDIT /S %systemdrive%\install\MSN\msnmsg75.exe" /f REG ADD %KEY%\035 /VE /D "Installing Windows Installer 3.1" /f REG ADD %KEY%\035 /V 1 /D "REGEDIT /S %systemdrive%\install\WinInst\winins31.exe" /f REG ADD %KEY%\040 /VE /D "Installing Windows Update V6" /f REG ADD %KEY%\040 /V 1 /D "REGEDIT /S %systemdrive%\install\WU6\WU6.exe" /f EXIT Your 1st program is installed as it does not have RegEdit doing it. The rest of the installation commands have RegEdit doing it? RegEdit is not an installation command. RegEdit /s will just do the *.reg files for you. Edit: wow, codebox strips empty lines.

Installing Internet Explorer 6 should reinstall Outlook Express as it is in the installer package. Check the Microsoft download site for the installer of Internet Explorer 6.

Just file and folder handling. That is the limitation of it.

Compiling to exe file? AutoIt is my total solution, and not a single script is compiled. I use the interpreter AutoIt3.exe to run the Au3 files, like you would run CScript.exe to run VBS files. I use a main script with a For loop to execute each script in the software folder, one after the other. Writing a log file recording start and finish times of each install, as well as the exitcode. I would consider VBScript could do this as well. I also put up a full screen popup window, that displays a picture on it, with a scrolling list of software and a progress bar. VBScript can do the same. Here is it running a T-12 And you are going to retool about a third of your scripts. I have done mine countless times.

Have XP replace the files for you. Open a command console and type sfc /scannow This will check the protected files on your pc and replace any that require it. It may or not solve your problem, but is good to rule out.

Regmon. This show the read/writes in realtime.