MHz

Nullsoft ® Installer /D="x:\dirname" Install program to path.

I notice that some entries allow for a higher process priority, overwise no.

Dotnet is not account related. User privilages are to be considered with installers. Runas may have to be considered, to install some programs, as no user is logged on at t-13. Depends on the type of software, it requirements and what the system will allow.

Some programs can apparently can be installed from Cmdlines.txt. These are programs that are not account related or such. But, still, most user related programs are done after reboot, to do the installations at first logon. This reboot after that is perhaps needed and a good recommendation. I would not be concerned over trying to save a reboot. The system may still run fine, without it. But is it worth the risk?

Sorry, I have to say this but... Absolutely not. You are creatimg a dos variable, that last as long as the batch or dos window session. In this instance, breifly, as long as this dos window is open. Try this, what does the messagebox say ? AutoItSetOption ( "ExpandEnvStrings", 1 ) RunWait(@ComSpec & " /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WIN51 set CDROM=%%i:", "", @SW_HIDE) ; This will fail. Sleep(1000) $result = EnvGet('CDROM') MsgBox(0, '', 'CDROM = ' & $result) ; This will work. Sleep(1000) $result = EnvGet('WINDIR') MsgBox(0, '', 'WINDIR = ' & $result) @ScriptDir work's perfectly everytime. Anyone who doubts this, has not enough experience with AutoIt. As MAVERICKS CHOICE has stated, the AutoIt forum is also a great resource for learning. I'm regularly there to help. And again MAVERICKS CHOICE is right about toying with it. Over 300+ imbuilt functions within AutoIt, there is alot to test and learn. It's a feature rich basic language, better then others, that i know. I believe I have enough confidence with AutoIt, I should have, with making scripts that go up to 3000 lines long. Use of multidimentional array's etc. And well, some basic knowledge in DOS, definately helps also. Sorry Siginet, I mean no hostility. I just like to help. Here is my runonceex, with my CDFind() function. RunOnceEx.html

run("myfile.msi") does not work at all. You need to call msiexec or use @ComSpec to run it. run("msiexec /i myfile.msi") You are calling msiexec, which is in the system directory. How is msiexec, supposed to know, where to look for myfile.msi, unless you specify it. You are lucky when this runs in a Win32 environment, as you are only feeding msiexec a filename, with no address. You should specify: Run(@SystemDir & '\msiexec /i "' & @ScriptDir & '\myfile.msi"') Run(@ComSpec & ' /c "' & @ScriptDir & '\myfile.msi"', '', @SW_HIDE) You could probably, get away without using @SystemDir, as the system path should be available for msiexec location.

I do not think you can mix variables with 8.3 format. If you cannot do it from a cmd prompt, then it will not work in a batch file. They use the same interpreter. Use this: Del "%APPDATA%\Microsoft\Internet Explorer\Quick Launch\Ad-watch.lnk"

; Installation file paths. $installerpath = @ScriptDir & "\klmcodec.exe" $inipath = @ScriptDir & "\klmcp.ini" Run($installerpath & ' /loadinf="' & $inipath & '"') You need to wrap the double quotes, for the parameter, if it has spaces. For this use single quotes. I use single quotes by default, so when you come across a line like this, it seems simpler to wrap. ' " ' = wrapped double quotes.

The only way you can install all programs to "D:\programs\" is to change the %ProgramFiles% directory location in Winnt.sif. Most installers install to %ProgramFiles%, whether you like it or not. Only other chance of doing this, is using AutoIt to control the installation in gui mode. That is if, all these installers support changing installation directory during this mode, which some will not.

Is that a question ? I an unsure of it reference. But most use something to execute the *.exe, during unattended install of windows.

Just makes changes to the script as author has specified, then compile it into an executable. Then you should normally put this file in the same directory, as your installer, then add it from your runonceex script, or whatever. It should not require any switches, unless specified. AutoIt 3.1.0 or 3.1.1 should be the required version to compile.

I do not disagree. Adding a *.reg file is far easier for doing this OS tweak.

True, and thanks to it even I have managed to create some "crude" working scripts that run fine - (no, effectively!) - from within Win envir. Its just my 100% failure rate from within RunOnceEx that has daunted me. Since you have mentioned line errors. Hopefully you are using a editor that has the tools on board, to help you with your code. Scite4AutoIt3 is a nice editor for creating AutoIt scripts. It has in it's Toolbar, a Tools dropdown, which contains SyntaxCheck. This will validate your lines of code. It also has a program called AutoItMacroGenerator. This tool creates a draft install script for you. Plus all the other tools onboard. If you are not using an editor like Scite4AutoIt3, then you are just making life hard for yourself.

Yes. Au3 file converted to .exe file in same folder as app I'm trying to install. So I can just call <au3-converted-to-exe> in my RunOnceEx without any switches? And the first line of my script doesn't need to have ANY path in it? Have I finally understood this correctly? Cant find this info anywhere on forum. Thousands of scripts, yes, but not found anything on their implementation of any use to me. Perhaps if some guidelines were "Stickied" it wouldn't make AutoIt so scary to use as I've shyed away fro it for ages. Not because of the commands because the Help files are superb from within the app, but because of how to use the app in conjunction with RunOnceEx. Thanks nologic for all your help, too. <{POST_SNAPBACK}> Using Autoit during the RunOnceEx period is the same as using it on the desktop. Only difference that I have found, is you may need to use WinClose() twice, instead of once, on a open window. Look in the Autoit helpfile for Tutorials -> WinZip Installation. Everything in it relates to making a script for desktop use or RunOnceEx. The last line of it, you can do twice for RunOnceEx. e.g: WinClose("WinZip (Evaluation Version)") WinClose("WinZip (Evaluation Version)") Or you can use a loop for WinClose() Example to try 5 times to close it: For $i = 1 to 5 WinClose("WinZip (Evaluation Version)") If Not WinExists("WinZip (Evaluation Version)") Then Exitloop Sleep(1000) Next The help is there in the manual. With the first line, is fine to use. Run("winzip90.exe") If you want Autoit to only search for the file in the directory, rather then the directory and the system path, then you could use: Run(@ScriptDir & "\winzip90.exe") @ScriptDir is the current directory, of the script/compiled exe. AutoIt has a excellent helpfile. People who read this Helpfile fully, are the one's who will succeed with AutoIt. I know it is hard to first start out with any programming language, but we all have to endure it to enjoy the experience of the benefits. Yours sincerely, Another AutoIt fanatic

Use /silent with Astalavista's installer above. /? for available switches.

99% chance that it is the media is at fault. You can change burners, but the performance of the media is the same. For media: Some brands last reasonably. Some brands, burn today, data gone tommorrow. Some brands fail burn process everytime. I would recommend CDCheck.

Log path. No. It is not a archived file, that writes a log file. So should not be needed. Just run the Autoit file, and it should work hopefully.

Try feeding the full address to msiexec. Run('msiexec /i "' & @ScriptDir & '\AdobeIllustratorCS2.msi"')

TweakUI does this.

But the boot files are on the 1st drive.

I am impressed BoardBabe. Very nice to know someone with good Autoit skills. Windows do not need to be active for Control*() functions though. I have changed alittle of your script to reflect on how I would handle it. This will give you another view of how it can be done. Illustrator_CS2.html

Well, not silent, but close. Try this Autoit Script. _HotkeyMaster.html

XP does not like packet writing software, so I hope you are not installing. For Nero, it's called InCD. Easy CD Creator has DirectCD. and so on. Registry corrupted sounds bad. A clean install maybe the fix ? You could try this fix. Can help fix lost CDRoms if these entries are present. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}] "LowerFilters"=- "UpperFilters"=-

Opt("WinWaitDelay", 400) Opt("WinTitleMatchMode", 2) Run ("SETUP.EXE -s") Opt("MouseCoordMode",0) WinWait("Crossword Maestro","FolderView"); Added also. WinActivate("Crossword Maestro","FolderView") WinWaitActive("Crossword Maestro","FolderView") Send("{ALTDOWN}f{ALTUP}{DOWN 5}{ENTER}") Certainly I can. Opt() just is added to the top of the script as shown.

WebPackage record: Whatever.exe /a /r Unpackaged: setup.exe /r setup.iss will be recorded in %windir% - nVidia has it's own setup.iss in the Webpackage, so just unpack it, make a recorded install, then just pack it with WinRAR. And use WinRAR to execute in the SFX: setup.exe /s If you use the webpackage from cd. you would need: (Rename setup.iss, and put it in $$ directory) whatever.exe /s /a /s /f1C:\Windows\setup.iss /f2C:\install.log /a is admin install, so any switches passed after it, will be passed to setup.exe.