MHz

Good to hear.

It is possible with some installers to wait for a window and set it as invisible but normally this needs to be done with each window and Control* Functions are required to be used. It is not a good solution as the time it takes to hide the window, could have been used to click to progress to the next window. Another concept is to move the 1st installer window off screen and each window will open off screen. Some installers are hardcoded to use the screen centre so can fail with those. Again Control functions are required for this concept. I sometimes choose to let the windows quickly go through the cycle and hide the install progress window which tends to be visible for awhile sometimes. When Automation is required when no silent installation options available, then you can just do what is best for each installer. Either that or just go without.

Create a cmd file and have the new Help.exe next to the cmd and execute. Del /q %SystemRoot%\System32\DllCache\Help.exe Del /q %SystemRoot%\System32\Help.exe Copy /y Help.exe %SystemRoot%\System32\Help.exe pause The pause is just so you can see the result. A few seconds later, Windows will ask about inserting the Windows CD to restore the file, so just click cancel.

If the cmd files did not exist then an AutoIt fatal error would occur as you have taken no steps to suppress it. The code you display is working code so you must have a mistake in your cmd file which is not adding the registry entries ? Perhaps if you want to attach or post your cmd scripts, then the problem could be recognized.

Now called Installer Design Studio. It is not a freeware product either.

Very good bobthenob. Just some tips. This line is hard coded to only C: drive. Use macros to improve chances if Program Files is else where. Run(@ProgramFilesDir & "\Ahead\Nero\nero.exe") A little optimize trick for you. Your code below can be made easier. It can be transformed into this: WinWaitActive ("New Compilation") Send('{tab 4}{Enter}') They both do the same but the change is only 2 lines without the extra repetition. The Send() page in the helpfile has a number of tricks to learn.

v4.01 is the 64bit version. The AutoIt script I created that muiz links to is for the 32 bit v4.00. I cannot install a 64 bit program on a 32 bit OS to create an install script for 64 bit users.

No Reboot script Added No Reboot script also to AutoIt thread.

Using Send() is just emulating the keyboard. I think it is the Tab key and Arrow up key to switch radio buttons for Nero. Try it manually with the keyboard to check. Send('{TAB}{UP}')

Nice extensive explaination, Nologic. Would recommend hiding those cmd file windows for better presentation ? If @OSVersion = "WIN_XP" Then Run ( @HomeDrive & "\Install\RunOnce32.cmd", "", @SW_HIDE ) Else Run ( @HomeDrive & "\Install\RunOnce64.cmd", "", @SW_HIDE ) EndIf Exit The more up to date AutoIt Beta has @ProcessorArch which returns one of the following: "X86", "IA64", "X64". That could be also an option. A 64 bit OS also has a WOW64 key in registry that could be checked for existance. Perhaps for a DOS solution is %OS% ? XP 32 here is set at "Windows_NT". I do not know the XP 64 value atm. Type set in a command window to find out on a XP 64 OS.

Here is an AutoIt script that can change working directory and then execute specified files or all files of a given extension. Examples: HideCmd "Software" "1" "2" Will change working dir to "Software" folder and execute 1.cmd amd 2.cmd in sequence. HideCmd "Software" Will change working dir to "Software" and execute each cmd file in sequence. HideCmd "" Execute each cmd file in sequence within current dir. Plus: HideCmd sleep 10 Will sleep for 10 seconds. HideCMD.html

[size=3][b]DivX Bundle 6.4[/b][/size] [url="http://www.divx.com/divx/"][color="#6633FF"]Homepage[/color][/url] [b]Comments:[/b] Choose components and shortcuts within the script to keep or remove. Toolbars and downloads processes are prevented from any operation or installation tactics. An opening internet browser will be closed amongst other needed actions to make installation without hassles. [b]Download Install Script:[/b] [attachment=15161:attachment]

Defrag.exe is not too verbal for even the AutoIt Beta stdio to get information from. You could try to automate the Defrag Gui. Here is some code to get you started. Run(@SystemDir & '\mmc.exe dfrg.msc', @SystemDir) If WinWait('Disk Defragmenter', '', 10) Then ControlFocus('Disk Defragmenter', '', 'SysListView321'); Focus drive selection. ControlSend('Disk Defragmenter', '', 'SysListView321', '{DOWN}'); Next Drive. ControlClick('Disk Defragmenter', '', 'Button1'); Analyze. ;~ ControlClick('Disk Defragmenter', '', 'Button2'); Defrag. EndIf The above will analyze D: drive.

@muiz I see you used the debug script. Only the script in the AutoIt thread has the latest change. I see from the log that the toolbar installer did get deleted from the HDD before it could do anything. Above quoting myself from AutoIt thread. When installed at RunOnceEx, the script will do the reboot for you when the desktop is active so I do not know why you are using the systems Shutdown.exe to also do the reboot ?If you want to increase the timeout then look at this line: This is a 15 second Sleep before continuing with the next line of code. You can increase or decrease the 15 to a number that is more suitable for you. The other 5 seconds is used for the MsgBox(). This can be changed also if suitable. To Exit without timeout and reboot, then add an Exit after the ControlClick() and before the Sleep(). The script will Exit immediately. If you choose to use the systems Shutdown.exe, then use the Exit example above. Use the script from the AutoIt thread to install it normally without any log file and with the latest changes. Edit: Updated Debug script in 1st post.

When a user is not logged on, as such a time as Cmdlines.txt executes, then registry entries for the unloaded HKCU Hive get redirected to HKU Hive. Most entries will be accepted at that point for what HKU will handle. Another option is to add an entry for HKCU RunOnce during Cmdlines.txt, to run a reg file on the HDD for each 1st logon of each user. The latter I use for a script to run for each new account. If you do want to share all software and regtweaks then installing from Cmdlines.txt may suit you better ? I install all mine from Cmdlines.txt and it goes fine. New accounts absorb the software links and regtweaks fine. You may find some, if any reg entries may not take possibly as HKU may allow only certain entries. To get the admin desktop to a red background, you would need to use HKLM RunOnceEx or HKLM RunOnce to apply the changes. You need to logon first to enable the admin account so you can apply then. This could be ok after the Cmdlines.txt to change for everyone's accounts background. Your the best judge of what you need in the end. I can just help with some knowledge.

You do not add something to HKEY_USERS/.DEFAULT. As I stated above, at which time that you add the registry entries decides where the system will apply the registry entries into the registry. Here you state from 1st post that you want the registry-tweaks to be shared to other users which contradicts your last post of having to use RunOnceEx to apply them which will do the opposite to appling at Cmdlines.txt. You can split the registry file and apply each part at the suitable time needed to accomplish what you want. Edit: You can install software from Cmdlines.txt if that is more suitable also.

Time to add HKCU reg entries: Cmdlines.txt -> Goes to Default User (for all user accounts) Logged on as Admin -> Goes to Admin account Logged on as moeti -> Goes to moeti account.

This may work: sc config dhcp start=auto sc start dhcp

@muiz Updated the DT4 script which tests ok for me that the toolbar installer does not even appear on the HDD. Just one line added and one modded alittle. If interested, check the AutoIt thread to download.

FFdShow is a Nullsoft installer. Use a capital S. setup.exe /S

Compile a HelpEx.exe yourself from a cmd file within the zip. Just click on Compile.cmd to compile it and you can add it to the systems path and just type HelpEx to list help information to console. It is low budget Help compared to Help.exe, but may suit your needs. Download: HelpEx.zip Edit1: @VAD hehe, I guess Attrib, AT, ChkDsk, ChkNTFS, CMD, Compact, Convert, DiskComp, DiskCopy, Find, Format, Graftabl, Label, More, Print, Recover, Sort, Tree, XCopy and some of the other items listed in Help are only internal commands ? Those mentioned are command line applications. Feel the difference ? Edit2: I decided to implement the idea for my commandline tools in the systems path. It makes remembering what I have available....easier. Picture Edit3: New File Host link.

This is using commandline tools: If the executable was compiled to be used as a service, then you can use SC.exe to create the service. If the executable was not compiled to be used as a service, then you can use Instsrv.exe and Srvany.exe from one the latest Resource Kit Tools from Microsoft, which will create the service as Srvany.exe will act as a kind of wrapper for your executable. More details can be found here.

Burning at high speeds is known for corrupting compressed files. The more compressed the data that you burn, the slower you should burn for success. Low quality CD media can also cause some problems.

A very mild understatement. I would not support any anyone who acts so pathethic as starting a thread with this kind of behaviour. This is totally inconsiderate, unhealthy behaviour and should not be allowed. 2/2 posts of sick behaviour, period.

You could preselect the users. Oobeinfo.ini may still work fine and there is always Net User. Have a look in the Unattended Guide for more details.