Welcome to the Applications Installs forum. Make sure you read the forum rules before you start posting.
Links/Requests to warez and/or any illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated.
We try our best to keep this forum clean of illegal content. If you see any illegal activity use the "report" button you find in every post to report the specific post to the moderators. If you ignore any of the rules you will be banned without notice.
Read Forum Rules
![]() ![]() |
Jan 24 2008, 01:36 AM
Post
#1
|
|
|
Newbie Group: Members Posts: 42 Joined: 3-November 06 Member No.: 114702
|
hi there, I´ve been trying to get the nod32 v3.0.621 silent install with WPI running but with no success, here is the code I use:
QUOTE msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qb /cfg=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml if anyone can tell what am I doing wrong would vey much appreciate it. thanks. PS first I get the windows installer window which shows me the aveilable commands (I tried most of them, nothing happens), then WPI just quits giving an error report about the install process I also tried the /silen /passive switches with no success... |
|
|
|
Jan 30 2008, 05:06 AM
Post
#2
|
|
|
Group: Members Posts: 4 Joined: 24-October 07 Member No.: 159464 OS: none
|
You should use /qn instead /qb.
|
|
|
|
Jan 30 2008, 05:12 AM
Post
#3
|
|
|
Newbie Group: Members Posts: 42 Joined: 3-November 06 Member No.: 114702
|
|
|
|
|
Jan 30 2008, 05:34 AM
Post
#4
|
|
|
Group: Members Posts: 4 Joined: 24-October 07 Member No.: 159464 OS: none
|
I don't know what happening when you run your command. Do you get any error message?
To find out which step(s) in installation process fail I would try to run this MSI in 3 steps: 1. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" (without any switches) if it works, go to step 2. 2. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qn. if it works too, go to step 3. 3. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qn /cfg=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml If it still doesn't work, put </l* c:\eavbe.log> in the end of your command to find out what's happening when Msiexec.exe trying to install that MSI-file. |
|
|
|
Feb 1 2008, 08:32 AM
Post
#5
|
|
|
Group: Members Posts: 1 Joined: 31-January 08 Member No.: 174548 OS: XP Pro x86
|
I've exactly the same problem.
It looks like the installer doesn't like the \cfg command... |
|
|
|
Feb 1 2008, 08:45 AM
Post
#6
|
|
|
Newbie Group: Members Posts: 42 Joined: 3-November 06 Member No.: 114702
|
|
|
|
|
Feb 1 2008, 08:53 AM
Post
#7
|
|
|
WPI Guru Group: Software Developers Posts: 5901 Joined: 18-September 03 From: Pocatello, ID Member No.: 6960 OS: Vista Ultimate x86
|
I have I install my Nod32 with just the /qn switch
This post has been edited by Kelsenellenelvian: Feb 1 2008, 08:54 AM |
|
|
|
Feb 1 2008, 09:35 AM
Post
#8
|
|
|
Newbie Group: Members Posts: 42 Joined: 3-November 06 Member No.: 114702
|
|
|
|
|
Feb 1 2008, 03:41 PM
Post
#9
|
|
|
Junior ![]() Group: Members Posts: 64 Joined: 30-November 04 From: A+ IT Professional Member No.: 37630 OS: none
|
I am using the same your NOD32 version, if you're already extracted EXE to MSI, using nod32.msi /qn switch is correct. It will not REBOOT
|
|
|
|
Feb 1 2008, 07:25 PM
Post
#10
|
|
|
WPI Guru Group: Software Developers Posts: 5901 Joined: 18-September 03 From: Pocatello, ID Member No.: 6960 OS: Vista Ultimate x86
|
cmd1[pn]=['"%wpipath%\\Install\\Nod32av.msi" /qn'];
Is my WPI command. |
|
|
|
Feb 1 2008, 10:12 PM
Post
#11
|
|
|
Newbie Group: Members Posts: 43 Joined: 25-June 07 Member No.: 144401 OS: XP Pro x86
|
|
|
|
|
Feb 1 2008, 11:07 PM
Post
#12
|
|
|
Group: Members Posts: 3 Joined: 4-January 08 Member No.: 169726 OS: XP Pro x86
|
The switches for NOD32 changed from version 2 to version 3.
I asume that this should work: msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qb! ADMINCFG=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml Here is the RunOnceEX commands I use. REG ADD %KEY%\100 /VE /D "ESET NOD32 Smart Security 3.0.621" /f REG ADD %KEY%\100 /V 2 /D "%systemdrive%\install\ESET\ess_nt32_enu.msi /qb! REBOOT=ReallySuppress ADMINCFG=%systemdrive%\Install\ESET\gbmNOD32v3settings.xml" /f QUOTE Parameters for ESET Smart Security and ESET NOD32 Antivirus should be typed after the name of the MSI installation package (e.g. ea_nt64_ENU.msi /qn): • /qn Quiet installation mode – no dialog windows are displayed. • /qb! No user intervention is possible, but the process of installation is indicated by a progress bar. • REBOOT="ReallySuppress" Suppresses restart after the installation of the program. • REBOOT="Force" Automatically reboots after the installation. • REBOOTPROMPT ="" After the installation, a dialog window prompting the user to confirm rebooting is displayed (can’t be used along with /qn). • ADMINCFG=”path_to_xml_file” During the installation, parameters defined in the specified XML files are applied for the client solutions ESET. The parameter is not required for remote installation. Installation packages contain their own XML conigurations, which are applied automatically. QUOTE Insert the desired XML configuration created in the ESET Configuration Editor and named cfg.xml to the directory where the downloaded installer is located. If you run the installer, it will automatically adopt configuration from cfg.xml. In case the XML configuration file has a different name, or it is located somewhere else, the parameter ADMINCFG=”path_to_xml_file”can be used. (for example ess_nt32_enu.msi ADMINCFG=”\\server\xml\settings.xml” to apply configuration stored on a network drive).
|
|
|
|
Feb 3 2008, 03:52 AM
Post
#13
|
|
|
Senior Member ![]() ![]() ![]() ![]() Group: Members Posts: 666 Joined: 30-November 06 From: Behind you Member No.: 117138 OS: Vista Ultimate x86
|
msiexec.exe /i %AppsRoot%\Install\WPI\install\NOD32\nod32.3.0.msi /qn
taskkill /IM egui.exe /F Works fine |
|
|
|
Feb 5 2008, 08:33 AM
Post
#14
|
|
|
Newbie Group: Members Posts: 42 Joined: 3-November 06 Member No.: 114702
|
thanks everyone, I finally got it working, the tested syntax is this:
CODE msiexec.exe /i %WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi /qb! REBOOT="ReallySuppress" ADMINCFG=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml thanks again |
|
|
|
Mar 25 2008, 03:40 PM
Post
#15
|
|
|
Junior ![]() Group: Members Posts: 75 Joined: 15-December 05 From: Romania Member No.: 82557 OS: XP Pro x86
|
THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!
THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO! |
|
|
|
Jun 8 2008, 02:45 PM
Post
#16
|
|
|
Advanced Member ![]() ![]() ![]() Group: Members Posts: 362 Joined: 31-July 03 From: Midlands Member No.: 5331 OS: XP Pro x64
|
you dont need admincfg=<path to xml> if your xml is called cfg.xml and resides in the same dir as the installer.
|
|
|
|
Jul 7 2008, 09:20 AM
Post
#17
|
|
|
Newbie Group: Members Posts: 12 Joined: 2-July 08 Member No.: 199091 OS: Vista Ultimate x64
|
Um, and what would be the layout of such an XML file? Can't seem to find it anywhere :s
|
|
|
|
Jul 7 2008, 07:11 PM
Post
#18
|
|
|
Junior ![]() Group: Members Posts: 52 Joined: 24-April 04 Member No.: 18457 OS: none
|
|
|
|
|
Aug 16 2008, 12:36 PM
Post
#19
|
|
|
Junior ![]() Group: Members Posts: 75 Joined: 15-December 05 From: Romania Member No.: 82557 OS: XP Pro x86
|
Regarding custom silent installation of Nod32, is it possible to install it silently with all the up to date virus definition files? I tried this some time ago, by extracting the msi and copying the updated *.nup files to APPDATADIR\Updfiles, but it failed to install the signature database.
|
|
|