MHz

Could very well be a corrupt install. Maybe a reinstall may fix? You are not giving enough information for anyone to give any good advice.

That is not an error msgbox, that is a question msgbox. You could try to create one and copy it over when you install office?

If you are having problems installing an application, then the Applications Forum seems to be correct forum to post? Here is a link to the post in the Applications Forum for anyone who can help bigbroantonio.

OEMPreInstall is listed twice in your Winnt.sif. Once as yes and once as no. Only OEMPreInstall = yes is what you want.

This is a trick that I use to stop any spyware or pest installs. 1. Create a null file. (A new text file with extension removed) 2. Name the file google as in this case. 3. Copy it to program files as in this case. Now when google goes to install itself. it is block by the null file as it tries to install to the google folder. The google installation will abort. Done. No google installation.

$Title was not declared before the WinExists function? You must declare or assign a value to a variable before using it, else you will receive the error as you display. Edit: Allow me to give example. ; Declare a variable Global $Title ; Assign a variable $Title = 'Here is a string'

If you want to use AutoIt to make some silent installs, then use CMenu. Identify Installer within CMenu can create template AutoIt scripts for you. It will make it easy for you. AutoMacroGenerator is rough but quick at creating an automated script. It is fine if you are not concerned for it's output. Checking and editing can be a post operation. Post #13 has some scripts added if you want a look. The prepare, cleanup and startup scripts are mostly custom to my needs, but you may see something to learn from. Are you refering to silent install scripts or automated scripts? There is a WinZip tutorial in the AutoIt helpfile. The automated example uses WinWaitActive and Send. WinWait and ControlClicks are more reliable to use if possible. Always use the Au3Info tool to supply you the information for using the function parameters. Let me know what you do not understand and which type of install, whether silent or automated.

Just to confirm that Control*() functions do not require active windows.

I fail to see the reason why you want the windows to be active. The Control*() functions directly operate the controls. You should try to use the text parameters if able to, if needed to prevent a similar window with the same title being recognized incorrectly. The Splash Screen may not be a problem then, as the script is not concerned if a window is active or not. Just change all the WinWaitActive() functions to WinWait() functions in your script. Then give it a test.

Here is a function that dynamically changes a bitmap wallpaper. You nay not need the DllCall() from cmdlines.txt but the registry entries show the values to change. ; Courtesy of ezzetabi at AutoIt Forum. ; The BMP Wallpaperchanger Function. ; Example usage. _ChangeWallpaper('C:\WINDOWS\Web\Wallpaper\Windows XP.bmp', 3) Func _ChangeWallpaper($sFile, $iType) ; $iType: 1 = Tiled, 2 = Normal size, 3 = Stretched. If Not FileExists($sFile) Then Return 0 If StringTrimLeft($sFile, StringInStr($sFile, '.', 0, -1)) <> 'bmp' Then Return 0 Select Case $iType = 1 RegWrite('HKCU\Control Panel\Desktop', 'TileWallpaper', 'reg_sz', '1') RegWrite('HKCU\Control Panel\Desktop', 'WallpaperStyle', 'reg_sz', '0') Case $iType = 2 RegWrite('HKCU\Control Panel\Desktop', 'TileWallpaper', 'reg_sz', '0') RegWrite('HKCU\Control Panel\Desktop', 'WallpaperStyle', 'reg_sz', '0') Case $iType = 3 RegWrite('HKCU\Control Panel\Desktop', 'TileWallpaper', 'reg_sz', '0') RegWrite('HKCU\Control Panel\Desktop', 'WallpaperStyle', 'reg_sz', '2') EndSelect RegWrite('HKCU\Control Panel\Desktop', 'Wallpaper', 'reg_sz', $sFile) DllCall("user32", "int", "SystemParametersInfo", "int", 20, "int", 0, "str", $sFile, "int", 0) Return 1 EndFunc

I currently use NVU as it is light on system resources. I would say it does well for it's small size.

What was the command that the final window gave when you made the MST? Example picture of the final window with command Edit: more info Slipstreaming into Office. Note the admin install to get the files from the cd. That should leave you with a MSI as the main installer file?

Do you have oempreinstall in your winnt.sif set to yes? [Unattended] OemPreinstall = Yes

[quote name='a06lp' date='Oct 2 2005, 11:53 PM']any way to disable the picasa system tray thing? [right][post="397920"][/post][/right][/quote] By which method. The Inf that asbsamsf displays uses TASKKILL and removes the Run registry entry. The AutoIt script I posted blocks the process and removes the Run Registry key. If you use a DOS cmd then TASKKILL and Reg delete. The system tray thing you mention is PicasaMediaDetector.exe.

Try using the Start command. If you do not use the Start command, then window will remain until the executed process finishes.

Within the header of a file is a checksum. If you modify a file, you are changing the size of that file. If the checksum says 500 kb and the file is 600 kb then you will get an error when setup expands it. Use ModifyPE to correct the checksum to receive no errors. Then use MakeCab to compress the file. It is not needed if you do not alter contents of the file in the first place. Compression bin is just a front end for doing the 2 commands of ModifyPE and MakeCab.

Could be a bad driver, but it could be a bad piece of hardware that the driver is trying to initialize. I would do as rjz has mentioned and disconnect or remove hardware until it is bare and see if the OS can boot at that.

Au3 Advantages No Compiler Directives used. No Compiling needed. Easily viewed for checking and updating. No re-compiling needed for edits. Save Space: 1 AutoIt3.exe + 50 scripts = 400Kb, 50 compiled scripts = 7500Kb. Script and Installer in one location. Hardlink friendly. Can use a master Au3 script to execute each Au3 script in a selected folder without disturbing other executables as mentioned here. Less headaches Compiled Advantages Easy to execute. Security as compiled to hard to read. (Alternative: A3x in beta is encrypted script only) Perhaps missed a few advantages? My complete UnAttend project is AutoIt driven. I used to compile the scripts. Had a Compiler Directive to copy the compiled file to the software folder and all the other Compiler Directives to recognize exe version etc. Sometimes compiling a 2nd time, if I was not sure of compiling the 1st time. Now I do not compile and I find it as much easier to manage all the scripts. Your UnAttended project is a resource that can be updated occasionly to update as software changes etc. If your project layout is good, then you should be able to constantly improve on it. If it is easy to maintain, then it is less time consuming and more extendable. The more Au3 scripts that you have, the better the uncompiled concept is to manage.

Thanks totoymola, The Image File Execution Options concept that you shared with us may come in handy for certain problematic installations. Edit: As a reference, the functions above are generic code and can be used in other scripts also.

Not yet heard of it. A few weeks ago, AVG was removing AutoIt compiled scripts from user systems as it was stating that they were viruses. Most other AV programs have done this erratic behaviour also. All compiled AutoIt scripts use a common bin file when compiled. This is the internal interpreter used. AV programs continually seem to identify the executable code by the bin file code. This is ignorant of them to punish all AutoIt users for the sake of possibly one id*** who creates a malicious AutoIt script. The id*** may have simply made the script as a joke gone bad, but if the reciprient sends the file to their AV company, then...? I say id***, as all AutoIt users can have all their compiled scripts put at risk by the AV program. You should never setup your AV to autodelete. AV programs get it wrong too often. We need AVs programs though to warn us of real baddies.

[quote name='totoymola' date='Sep 29 2005, 03:17 AM']MHz is the AutoIt master here. Maybe he has a dirrerent method of doing this. [right][post="396341"][/post][/right][/quote] Ok, that sucked me in. I do not even have an interest in this program but I did a script showing your process block method totoymola. Let me show the code that does the blocking. This variable contains the processes to block: [code]; Block list for annoying processes. Delimiter is |. $processblock = 'Picasa2.exe|PicasaMediaDetector.exe|notepad.exe|iexplore.exe|firefox.exe'[/code] The Install() function will call the _ProcessBlock() function if processes are assigned to the $processblock as above. If the above line has processes listed, then it will call this function and add each process into the Image File Execution Options registry key. [code]Func _ProcessBlock() ; Add process block for select processes Dim $processblock Local $key, $command If Not @OSTYPE = 'WIN32_NT' Then Return $processblock = '' If $processblock <> '' Then $key = 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options' If @Compiled Then $command = '"' & @ScriptFullPath & '" /dummy' Else $command = '"' & @AutoItExe & '" "' & @ScriptFullPath & '" /dummy' EndIf If StringInStr($processblock, '|') Then $processarray = StringSplit($processblock, '|') For $i = 1 To $processarray[0] RegWrite($key & '\' & $processarray[$i], 'debugger','Reg_sz', $command) Next Else RegWrite($key & '\' & $processblock, 'debugger','Reg_sz', $command) EndIf EndIf EndFunc[/code] Blocked Processes will execute the AutoIt script with the /dummy switch and that script execution will immediately exit. This line exits if /dummy switch s used: [code]; Exit if executed a 2nd time by blocked process. If StringInStr($cmdlineraw, '/dummy') Then Exit[/code] Picasa should install silently without annoying processes. Once the script exits, it will call the inbuilt Autoit function OnAutoItExit. OnAutoItExit will remove the registry entries that were added previously. [code]Func OnAutoItExit() ; Blocked processes will be unblocked. Dim $processblock, $silenterror Local $key, $exitcode If @OSTYPE = 'WIN32_NT' And $processblock <> '' Then $key = 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options' If StringInStr($processblock, '|') Then $processarray = StringSplit($processblock, '|') For $i = 1 To $processarray[0] If RegDelete($key & '\' & $processarray[$i]) = 2 Then $exitcode = 1 If Not $silenterror Then MsgBox(0x10, 'Error', 'Registry key for ' & $processarray[$i] & ' still exists', 2) EndIf EndIf Next Else If RegDelete($key & '\' & $processblock) = 2 Then $exitcode = 1 If Not $silenterror Then MsgBox(0x10, 'Error', 'Registry key for ' & $processblock & ' still exists', 2) EndIf EndIf EndIf EndIf If $exitcode Then Exit -1 EndFunc[/code] Full script attached. [attachment=12119:attachment] Using Adlib or OnAutoItExit would perhaps be my usual method to close these processes, but I find AutoIt is quite flexible as to problems so methods may vary. [b]Edit:[/b] Added script update to attachment. Up to date script has OS check etc.

@Mikeboy Yes, you have to AutoIt3.exe where the files is. My small example could have mentioned path to the au3 file. Corrected the example previous. It may have misled you.

Interesting concept totoymola. Have you any good links that can explain the operation of this registry key

True. As Joe User 99 is trying to mention. If the AutoIt script finishes before the installer does, then the next command in start.cmd would start. This fails the wait between installs. To comfirm: If the Compiled AutoIt script waits for te installer to finish, then Start /Wait will perform as expected with waiting between executions. Tip: If alot of AutoIt scripts are being used, then an alternative can be to add AutoIt3.exe into the system path (i.e. System32 folder) and call the AU3 script as below: Start /Wait AutoIt3.exe Path\Script.au3 Can save space, easy to edit and no compiling issues. Edit: Added path to example.

A file called Winnt.sif is added into the I386 directory. It is an answer file that windows setup accesses to get retrieve preset data to automate the installation process. Using Deployment tools cab from Microsoft has all the information for creating answer files and the link below shows information also. More Winnt.sif information: http://unattended.msfn.org/global/reference.htm