SRJ

Hi, If you search Trend Micro's website you'll find information pertaining to their setup.ini file. This is where you place the switches (and I don't think there are many of them). Here's a copy of the one I use to silently install Internet Security 2007 (without the serial number of course ). To install it I simply run setup.exe. Give it a go and let me know how things turn out. [Product] Version=15 [SETUP] Lang=en RollbackInfoURL=http://www.trendmicro.com/support/consumer/ Toolbar=0 DesktopShortcut=1 ShortcutName=Trend Micro Internet Security 2007 Silent=qn [CustomerInformation] Skip=0 Serial=XXXX-XXXX-XXXX-XXXX-XXXX USEBLANKTRIAL=N [NetworkType] Skip=1 ONLINE=1

Found a bug... when you select 'Above Normal' priority the priority combo box disappears entirely. If you select High or Normal it remains as expected. Haven't checked the lower priorities yet.

Updated to v1.43 - Apologies for taking so long to do it!

I think what you're after is the FileInstall() function in AutoIt. This allows you to include files in the .exe AutoIt produces and then use them. Here's a cut & paste from the AutoIt help file... [b]FileInstall [/b]-------------------------------------------------------------------------------- Include and install a file with the compiled script. FileInstall ( "source", "dest" [, flag] ) [u][b]Parameters [/b][/u][i]source [/i]The source path of the file to compile. This must be a literal string; it cannot be a variable. [i]dest[/i] The destination path of the file with trailing backslash if only the directory is used. This can be a variable. [i]flag [/i][optional] this flag determines whether to overwrite files if they already exist: 0 = (default) do not overwrite existing files 1 = overwrite existing files [u][b]Return Value[/b][/u] Success: Returns 1. Failure: Returns 0. [u][b]Remarks[/b] [/u]The FileInstall function is designed to include files into a compiled AutoIt script. These included files can then be "extracted" during execution of the compiled script if the statement is executed. Keep in mind that files such as images can greatly increase the size of a compiled script. The source file must be a string and not a variable so that the compiler can extract the filename to include. The source cannot contain wildcards. When this function is used from a non-compiled script, a copy operation is performed instead (to allow for easy testing pre-compilation). Files maintain their original creation/modification timestamps when installed.

FYI , v1.8.2 (1002) is out.

Don't have much time but try this: REGEDIT4 [HKEY_CURRENT_USER\Software\Microsoft\Driver Signing] "Policy"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing] "BehaviorOnFailedVerify"=dword:00000000

Okay... Have you read this post? Under the section unsigned drivers it discusses the method it uses for getting around the driving signing issue. I use this method myself for installing drivers from a CD/DVD and have had no issues with installing Realtek drivers. Note the commentary near the end of the post about resetting the signing policy so that in the future, unsigned drivers throw the dialog box. Give it a go and let me know how things turn out.

This can be tricky as the /D option you've been using is actually for a silent install of 7-zip itself not 7-zip created SFX's. Here's what I'd use for your situation: Your_7-zip-SFX.exe -y -ao -o%programfiles%\Utilities -y -> 'Yes' to any dialog boxes that may appear -ao -> Overwrite all files -o -> Directory you want the archive to extract to

You can install all Realtek Audio drivers through RunOnceEx using the silent switch. Here's an example: REG ADD %KEY%03 /VE /D "Realtek High Digital Audio R1.57" /f REG ADD %KEY%03 /V 1 /D "\"%CDROM%\Applications\Realtek High Definition Audio Drivers R1.57\setup.exe\" -s -f2\"%systemdrive%\realtek.log\"" /f The -s tells InstallShield to do a silent install (it uses setup.iss) whilst the -f2 is required for silent installs as they generate log files (you must save the log to a HDD or you'll have problems).

The problem I have with the Flags method is that it removes the Status Dialog. Users are then left with a blue screen until installation's complete. THe outcome of this is that some users will believe installation has stalled or has a problem and interrupt it unnecessarily. What are Microsoft doing about rectifying this problem?

Okay I've done some more testing and the problem remains unless you either: a. replace iernonce.dll v7 with v6 OR b. use the Flags RunOnceEx indicator which turns off the Status Dialog (ie. REG ADD %KEY% /V Flags /T REG_DWORD /D 128 /F). Has anyone gotten RunOnceEx to work correctly with ieronce.dll v7 and the Status Dialog? I prefer to install with the status dialog so users know what's happening. Option B above does not give this (despite everything installing correctly). So... I'll throw together a AddOn that needs to be installed post KB928090 and post it for others to use.

Latest (x32) nLite/RVMIntegrator Unattended Integration SPTD Driver [v1.43] can be downloaded from here. Older versions: SPTD Driver v1.42 SPTD Driver v1.42 Beta SPTD Driver v1.40

Okay I've just checked and KB928090 installs v7.0 of iernonce.dll. When I swap this file out (with v6) RunOnceEx executes correctly, when its left in it doesn't. As nLite leaves iernonce.dll at v6 when it integrates Internet Explorer v7 it must be KB928090 that's to blame given none of the other 13 Feb 07 updates contain iernonce.dll. Did I try it? I feel like being somewhat facetious due to the question but I won't be given the number of people who are quick to the draw in the forums. Yes I did try it because that's how I discovered it broke my UAE installation. I also note that I'm not the only one who's noticed this (refer this post) Of those who you say KB928090 fixed their RunOnceEx issues, were they using nLite or RVMIntegrator? Given this broke my installation, I'm a wee bit perplexed why it would fix theres. I can check this further if need be by simply taking a vanilla SP2 install disk and swapping out just iernonce.dll (ie. swap v6 with v7). Happy to do that if you'd like confirmation this way... Okay, I've just found another post (remembering I'm integrating not installing IE7 via RunOnceEx) that suggests using the Flags entry. I'll give that a go and see what happens and if I have egg on my face I'll be the first to apologise.... and here's another one for unattended installations (suggesting the work around I used which is replacing iernonce.dll v7 with v6 as KB928090 breaks RunOnceEx).

Word of warning: Whilst nLite integrates IE7-WindowsXP-x86-enu.exe correctly (ie. it does not allow ieronce.dll (v6) to be overwritten with ieronce.dll (v7) thereby allowing RunOnceEx to work), the IE7-KB928090-WindowsXP-x86-enu update breaks RunOnceEx again as nLite integrates ieronce.dll (v7) without realising it . I intend on releasing a quick fix to this via an AddOn but not tonight... Something to keep in mind if your slipstreamed install suddenly doesn't run RunOnceEx correctly! SRJ.

@biatche - this is what I do (the script is a smaller version of the one done here); $cdrom = DriveGetDrive("CDROM") RunWait($cdrom[1] & "\Applications\Daemon Tools v4.08.0.0\daemon408-x86.exe /S") ; Delete spyware installer. RegDelete("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run","DaemonTools_WhenUSave_Installer") If FileExists(@ProgramFilesDir & "\DAEMON Tools\SetupDTSB.exe") Then FileDelete(@ProgramFilesDir & "\DAEMON Tools\SetupDTSB.exe") EndIf ; Kill the spyware process and its application If ProcessExists("DaemonTools_WhenUSave_Installer.exe") Then ProcessClose("DaemonTools_WhenUSave_Installer.exe") EndIf DirRemove(@ProgramFilesDir & '\' & "DaemonTools_WhenUSave_Installer",1) Things to note: This is an AutoIt script I run this script from RunOnceEx (ie. after SPTD is loaded) The script will remove the spyware process if its running, the spyware application itself and related registry keys. The script is designed to install SPTD from the first CDROM For those interested, here is the unattended integration file for SPTD v1.42 Beta: SPTD v1.42 Beta Unattended Installation File SRJ.

Here's an unattended installation version of SPTD 1.40. It will install quietly and prior to RunOnceEx and GUIRunOnce so you can then install the remainder of Daemon Tools without any further hassle! [url=http://home.people.net.au/~srjohnson/SRJs_SPTD140_Addon.7z]SPTD v1.40 Unattended Integration File Enjoy!

The issue is that nLite does not support all the directives RVMIntegrator does. In this case the [WINntsif] directive.

Nuhi, I've rewritten the VCPack entries.ini file so that it works with both RVMIntegrator and nLite (refer this post). Is it possible to get nLite to bring up a text box (as used to happen) to state this AddOn pack requires the Unattended option to be selected? Otherwise, will you place a new flag that forces creation of the Winnt.sif file ? Cheer, SRJ.

When did nLite stop supporting Siginet Integrator's [WINntsif] entries.ini directive? Have I missed something here?

The only thing that comes to mind is to use a scripting language such as AutoIt and script the entire installation. That way you can control % installed for each application include the total installation package. The question you would then have to answer is whether you increment the % completed based on files installed or actual time. If its time then you're going to have to measure it somehow (good luck!)... files installed won't be time accurate... is it worth the hassle? I would say no! Sit back and enjoy watching your unattended installation work without you!

NOD32 will require you to use an AutoIT script (or similar)... far too many options that need setting.

Is anyone else having this problem: Selecting 'Notify before downloading' (or any other selection actually) under Automatic Updates on the Unattended Tab doesn't change Windows' behaviour. The default setting (download and install) is always set. I'm a thinking this is a bug (did a search and can't find anyone else has raised this). SRJ.

For those who don't know how to install Quicktime v7.1.3.x silently here's how: Unpack QuicktimeInstaller.exe using an application like 7-Zip or Universal Extractor. You will see that three (3) files have been extracted. The only one of interest to us is Quicktime.msi. You can DELETE the others as they're not required. As this is an .msi, we can simply use Microsoft's msi switches (refer code box below). I use '/passive /qb /norestart' Windows ® Installer. V 3.01.4000.1823 msiexec /Option <Required Parameter> [Optional Parameter] Install Options </package | /i> <Product.msi> Installs or configures a product /a <Product.msi> Administrative install - Installs a product on the network /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>] Advertises a product - m to all users, u to current user </uninstall | /x> <Product.msi | ProductCode> Uninstalls the product Display Options /quiet Quiet mode, no user interaction /passive Unattended mode - progress bar only /q[n|b|r|f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI (default) /help Help information Restart Options /norestart Do not restart after the installation is complete /promptrestart Prompts the user for restart if necessary /forcerestart Always restart the computer after installation Logging Options /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile> i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options /log <LogFile> Equivalent of /l* <LogFile> Update Options /update <Update1.msp>[;Update2.msp] Applies update(s) /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode> Remove update(s) for a product Repair Options /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode> Repairs a product p - only if file is missing o - if file is missing or an older version is installed (default) e - if file is missing or an equal or older version is installed d - if file is missing or a different version is installed c - if file is missing or checksum does not match the calculated value a - forces all files to be reinstalled u - all required user-specific registry entries (default) m - all required computer-specific registry entries (default) s - all existing shortcuts (default) v - runs from source and recaches local package Setting Public Properties [PROPERTY=PropertyValue] Consult the Windows ® Installer SDK for additional documentation on the command line syntax. Copyright © Microsoft Corporation. All rights reserved. Portions of this software are based in part on the work of the Independent JPEG Group. There are also two properties you can change DESKTOP_SHORTCUTS and QTPROGRAMMENUFOLDERNAME. They are self explanatory but in case you're still bewildered here's what they do and their options: DESKTOP_SHORTCUTS - Determines whether a desktop shortcut will be installed or not - FALSE/TRUE QTPROGRAMMENUFOLDERNAME - Determines where the Quicktime menu shortcuts will be placed under the START menu - Whilst I haven't done this, I don't believe you need to place the location surrounded by quotes So here's how the final installation line looks on my UAE disk:

Dangerzone: Here's an AutoIT script I use to install SetPoint silently: $cdrom = DriveGetDrive("CDROM") Run($cdrom[1] & "\Applications\Logitech SetPoint v3.1.16\setpoint310.exe") WinWaitActive("Logitech Software Setup","") ControlClick("Logitech Software Setup","","Button3") WinWaitActive("Logitech Software Setup","Select Language") ControlClick("Logitech Software Setup","Select Language","Button3") WinWaitActive("Logitech Software Setup","Destination Folder") ControlClick("Logitech Software Setup","Destination Folder","Button3") WinWaitActive("Logitech Software Setup","Software License Agreement") ControlClick("Logitech Software Setup","Software License Agreement","Button21") ControlClick("Logitech Software Setup","Software License Agreement","Button3") WinWaitActive("Logitech Software Setup","Access and modify settings") ControlClick("Logitech Software Setup","Access and modify settings","Button3") WinWaitActive("Logitech Software Setup","No. I will restart my computer later") ControlClick("Logitech Software Setup","No. I will restart my computer later","Button26") ControlClick("Logitech Software Setup","No. I will restart my computer later","Button3") The script is designed for installing from the first CD/DVD Drive. Enjoy!

I'm more than happy to post a AutoIT script that I wrote for Agnitum Outpost - is that what you're after?