MHz

Try these switches: xcopy /e /i /y %systemdrive%\install\Applications\mIRC "%ProgramFiles%\mIRC"

Welcome to MSFN, All that, wow, alot to do. It would be quicker if you read the guide instead of referencing the forum. You will have it done in a small portion of the time and have it done by a set method when using the guide. If you have done this before as stated, then you should be better this time round. Your current problem is...? The noob guide is the MSFN Unattended CD Guide. Various forums can help with the various areas of problems that you may encounter, if you even receive any problems. Use the forum search feature to find any solutions to your presented list can help. Good luck with your project.

Nice explain Joe User 99, except for using RunWait. The vast majoity of scripts in the pinned AutoIt thread do not use RunWait as the following functions cannot interact during the installation. Using Run and ProcessWaitClose is another option instead of using RunWait. This can allow you to insert code between these 2 functions to address issues. ProcessWaitClose is not required if good blocking functions like WinWait etc are used to control the install if it is a gui driven install. RunWait is fine to use if no interaction is needed, like a totally silent install that AutoIt can manage. AutoIt cannot continue with the script until the RunWait process has finished. To clarify, numerous blocking functions are available to control the flow of the script while the installation occurs. Loops could be considered also to help control script flow...

Glad to help. Good luck with the project.

[b]Original installer[/b] Doubleclick on the installer and a window opens with "Nullsoft Install System v2.0" on it. [b]/S[/b] is the switch to use.

Is this in VMWare? You may not have your display adapter recognized in VMWare. You have a space in your xcopy command that has no quotes surrounding it. Windows File Protection cares for these folders. Yes, search the pinned regtweaks thread. Check the 1st post for an attachment. Example: ; Disable Security Center ; ======================= [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc] "Start"=dword:00000004 Registry file should do it. Add it before installing Nero is best. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\ahead\Nero - Burning Rom\Info] "User"="x" "Company"="x" "Serial6"="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" All are MSI Installers failing except for Daemon Tools. You are calling msiexec with Daemons Tools, use it with the others.

Fast Explorer looks nice. I have a contextmenu program called CMenu. If interested, it is posted here and can be downloaded from it's Website.

Cmdlines.txt runs even without a Winnt.sif. Not sure, but I believe that SVCPACK.INF is not executed for a repair install?

I run a AutoIt script from Cmdlines.txt which adds _Startup.au3 to a RunOnce key and works for the current user and any users created in the future. It will execute when the Desktop becomes active, which starts when the startup folder is processed. This is the code that I use: RegWrite('HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce', 'zFirstLogon', 'Reg_sz', 'AutoIt3.exe "' & @WindowsDir & '\_Startup.au3"') The full script that contains this line is mentioned and attached here, if you are interested. The au3 file is given system attributes and is hidden so it will be available for each new account. And I keep AutoIt3.exe in the system32 folder to run it. Note: At Cmdlines.txt, HKCU keys are redirected to the Default User. Desktop wallpaper? You can choose a theme from Winnt.sif which will cater for the Desktop wallpaper. That is if you are using themes.

You are using the text of the parent window which is not active instead of the text of the child window which is active. Your WinWaitActive function needs the correct text to continue onwards.

You could try using fsutil to set the dirty bit to invoke chkdsk. fsutil dirty set c: You can change c: to the drive of your choice.

Regtweak: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.cmd\ShellNew] "FileName"="Template.cmd" Create Template.cmd and add to $OEM$\$DOCS\Default User\Templates. The template can be empty or preset and can also be added to All Users instead. Alternatively, use a Copy command to insert into your User Profile when it exists. Simple.

@sonic If the first parameter is not the title and does not use "" then "" is not required.

Thanks, it is easy. Just add the installer and Au3 script to the Software folder and it is done. No list to update. Identify Installer in CMenu is recommended. It is quick. If you want to do the same as my method then: Add the master script in root $OEM$ named _Deployment.au3. Create a folder in root of $OEM$ named Software. Add installers and CMenu scripts in $OEM$\Software I use the Winntbbu.dll picture added to $OEM$ root. Create Au3 files named _Prepare.au3, _Cleanup.au3 and _Startup.au3. Add AutoIt3.exe from latest Beta to $OEM$ root. Add Regtweaks.reg to $OEM$ root. Create Cmdline.txt and add this inside it: [COMMANDS] "AutoIt3.exe _Deployment.au3" "RegEdit /s RegTweaks.reg" Done. This runs from Cmdlines.txt. A small script can make it run from RunOnceEx instead. A text file of commands is a harder method to setup and maintain. Here are some silent samples but instead of using Run, you will need to use RunWait instead. $cmdfile = 'test.cmd' ; Sample 1 RunWait($cmdfile, '', @SW_HIDE) ; Sample 2 RunWait(@ComSpec & ' /c Call "' & $cmdfile & '"', '', @SW_HIDE) This would spawn lots of hidden cmd windows, but not all at once. If you are handy enough with AutoIt, then you should not need a single cmd script in your whole project. Cmd windows are not a problem when using solely AutoIt.

Glad you like it. I do not have a Windows XP X64 system to test on. I would assume that it will work, but cannot be certain of it.

Eh? Why bother. It does seem very bold to try to convert anyone from what they prefer. FireFox is definately offtopic in this thread!!!

Two RunOnce keys are available. You must be using HKLM RunOnce? HKLM RunOnce waits for completion before loading the Desktop. HKCU runs when the startup folder does, and runs while the Desktop is active. I have not registered fonts unattended, but I use HKCU RunOnce to run my AutoIt script and it does well. HKCU RunOnce also removes those shortcuts in time that are not created until the desktop is active.

Try this instead: c:\xpsp2.exe /integrate:c:\xpcd I believe you problem is simply adding I386 to the destination path when you shouldn't.

Arh, my old RunOnceEx script that the link shows. Those are all compiled scripts that RunOnceEx executes, so limitation is only the amount of code that I have within the compiled scripts. This would compare to your 2 commands as a enormous difference in function, as my scripts can have can have almost unlimited functions. Currently I install everything from Cmdlines.txt. AutoIt3.exe runs the master Au3 script, which adds paths, environment variables and services. The master script then executes a cleanup Au3 script. It then searches a software folder for Au3 scripts which AutoIt3.exe executes each in order. Logs software installation times and exitcodes while installing. The scripts will access support files whilst executing. Most software scripts are CMenu created scripts and a few are Gui driven. All this is done while a fullscreen picture on a AlwaysOnTop Gui is displayed showing the software list scrolling through as installs are working and a progress bar display. The Gui can be toggled from AlwaysOnTop setting by pressing the spacebar, incase an installation stalls. A startup Au3 script is then copied to the windows directory and the execution line is added to the HKCU RunOnce key for Desktop cleanup and shortcut removal etc. The master Au3 script can also run from RunOnceEx and resize the Gui to suit the resolution. This setup has 0 compiled AutoIt scripts which saves space and is easy to edit the scripts when needed. Display of working script _Deployment.html _Prepare.html _Cleanup.html _Startup.html For your question: Simple a change to the previous script is to alter the _Entry function with 2 lines as shown. Func _Entry($title, $file1, $file2 = '', $file3 = '') $count = $count + 1 RegWrite($key & '\' & $count, '', 'Reg_sz', $title) RegWrite($key & '\' & $count, '1', 'Reg_sz', $file1) If $file2 <> '' Then RegWrite($key & '\' & $count, '2', 'Reg_sz', $file2) If $file3 <> '' Then RegWrite($key & '\' & $count, '3', 'Reg_sz', $file3) EndFunc Then call the function like this _Entry('SmartFTP + Settings', $software & '\SmartFTP\SFTPNSI.exe /S', $software & 'SmartFTP\Settings.exe') The above modification allows for 2 extra optional parameters, so you can call 2 more items to execute under the 'SmartFTP + Settings' title. There is no set concept with unattended AutoIt scripts, just good imagination to make them. Edit: Added attachments: _Prepare.html, _Cleanup.html and _Startup.html.

This has been discussed recently http://www.msfn.org/board/index.php?showtopic=56208

1- If you have a function that looks for a certain file in the CD - $variable = FindCD('WIN51') - why do you need the DriveGetDrive function to detect the CDrom? The DriveGetDrive is a builtin function in AutoIt for locating drives. It is far easier to use DriveGetDrive rather then reproducing with it with numerous lines of code. DriveGetDrive returns an array of drives available, but some further lines of code is required to refine a match that suits our needs. This explains for the function FindCD. 2- Why doesn't the function FindCD appears in the Autoit Help file? FindCD is a User Defined Function. It exists through my creation. AutoIt users can create their own User Defined Functions and use them similar to builtin functions. For example, let us say that a script may require lots of basic MessageBox functions, but using the builtin MessageBox has too many parameters for a simple task. I could make a User Defined Function (UDF) as below: Func Message($text) MsgBox(0, '', $text) EndFunc Now I place the above UDF at the bottom of the script and call the function as below: Message('This is easier') The above single line will execute the Message function. $text parameter will be replace with the string 'This is easier'. Imagine that this is what the function looks like when called: Func Message('This is easier') MsgBox(0, '', 'This is easier') ;<-- This will popup a MessageBox. $text is replaced with the string. EndFunc 3- Why is a third variable - $i - needed? $i is a variable used for storing the loop count for the For Next loop. It is self declared and a required variable for For Next loops. 4- What exactly does this line do: For $i = 1 To $cdrom[0]? A For Next loop will continue to loop through the code between the For and the Next keywords. $i stores the loop count. 1 is the start number for the loop count. $cdrom[0] stores the amount of drive letters that the DriveGetDrive function returned. If DriveGetDrive returned 2 CDRoms, then $cdrom[0] = 2. The For Next loop would loop twice. The first loop would replace $cdrom[$i] with $cdrom[1], which is the 1st CDRom letter and checks if the FileExists and return the CDRom letter if true. If false, then the 2nd loop will happen and $cdrom[$i] is replaced with $cdrom[2], which is the 2nd CDRom letter and checks if the FileExists and return the CDRom letter if true. 5- When I use the Run function, it seems that it just can run .exe files, not other type of files? Straight out of the helpfile. The full name of the executable (EXE, BAT, COM, or PIF) to run. This is a simple indicator. DLLs and others can also be included as files to run etc.

It has Skip files with extensions. Certain filetypes can be downloaded to certain folders. Plus alot more features that are not written in that page. They just did not want to bore people with writing too much in.

You ask for other. You can export your registry settings easily with Free Download Manager. It works well and is free and easy.

Driving a car from the back seat is unworkable also. Half-hearted attempts mean little. I do not call the command interpreter from the registry to run it. Find Target opens explorer to select the file that the shortcut points to. So what is the difference between the RegTweak and the one in shortcut tab in properties? It does require displaying to only *.lnk files which the RegTweak needs to be improved upon.

Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\shell\Find.Target] @="&Find Target" [HKEY_CLASSES_ROOT\Directory\shell\Find.Target\command] @="\"explorer.exe\" /select,\"%1\"" [HKEY_CLASSES_ROOT\*\shell] [HKEY_CLASSES_ROOT\*\shell\Find.Target] @="&Find Target" [HKEY_CLASSES_ROOT\*\shell\Find.Target\command] @="\"explorer.exe\" /select,\"%1\"" The long wait is over. Enjoy.