jrf2027

Save yourself a trip to the store - just go to the Webroot home page (http://www.webroot.com/). It has the most up-to-date version, you'll have it in about a minute, and you won't have to pay tax. As far as the definitions...I thought that too, until looking at a friend's system that had 2.6 on it and seeing that it was infested with spyware. The program would delete it, but the stuff had edited itself into the startup routine, so that it would re-install upon reboot. Man, this stuff is getting nasty!

Definitely get the newer version. Some of the more nasty, newer spyware and malware cannot be removed with anything less than 3.0. 2.0 does not have the ability to prevent programs from re-installing themselves at startup, whereas 3.x does. Plus, the newer version is an Inno Setup, so it's fully silent.

No...most likely, your machine came with a pre-activated version of XP. Quite common, actually - for instance, all Dell OEM XP Professional install disks have the same product key in the winnt.sif on the CD, be it from original XP, SP1, SP1a, SP1a plus updates, or SP2. As long as your machine has a sticker with a product key on it, you have a valid copy.

Same switches as before for .msi-based install? I won't be able to test for about four more hours. (Grabbed the .msi from temp folder while installing on my work machine.) I'll edit to post results after I test it. EDIT: Yeah, the same switches work in this version as worked in the original 5.0 install.

@Kamil: Administrative install, or non-admin install using the .msi and the data1.cab file?

You don't even need to install the program. Just double-click the AdbeRdr70_enu_full.exe file. It automatically extracts the msi and the data1.cab file to %programfiles%Acrobat 7.0. Just dig through the folder levels and you'll find it. Then cancel the installation before it installs anything. (Don't know if you can use WinRar to extract the files - I don't have it at work.) You can also make an administrative install of it. I changed the name of the .msi file to acrobatreader.msi (for compatibility with my existing RunOnceEx file), then ran the following command: msiexec /a (Pathtothefile)\acrobatreader.msi It creates an administrative install. (7.0 gained about 20 megabytes over 6.0!) Then, just use WinRar or another compressor program to save space, and you should be able to install it using /qb (haven't been able to test this yet and won't be able to for about four more hours, so don't quote me on this!)

Won't have a chance to play with this until this weekend...but is it possible to run the 6.0.3 update on an administrative install of Adobe Reader already updated to 6.0.2? If the installer is MSI-based, it sounds like it should be... EDIT: My bad - installer is MSI, not MSP...found some free time and was playing with it... if it weren't for the two .rtp files, the update would be as simple as replacing one file...I wonder if there's a way to do an admin run of the program needed to update the plugins.

Just a thought here... Of the several of you who are having problems with the symlcrst.dll file...how are you grabbing the file? Are you installing and activating NAV, then deleting it and retrieving the file, or are you booting into Windows using safe mode and retrieving the file? Are you installing symlcrst.dll to the expected location before or after NAV is installed? Also, as far as the activation date for the new installation being the same as the original activation date, is this on a new, clean installation of Windows, or reinstalling NAV on a Windows installation where it was once before installed? My personal experience shows that if it's a clean install of Windows, you get another full 366 days, but if it's a reinstall, you only get the 366 from the original date of activation. Perhaps Symantec found out we cracked the unattended installation, and has NAV modify the symlcrst.dll file after first download of updates to prevent future cracking...in which case the smiley is appropriate...but as for my own trials, it's always worked (so far)... which means the B) smiley is more appropriate for me...

Buy the firewall as a standalone, instead of NIS.

Buy the firewall as a standalone, instead of NIS.

Delete your product key from your post!!!

@ToBe: This works for me in RunOnceEx: REG ADD %KEY%\270 /VE /D "Norton Internet Security 2005" /f REG ADD %KEY%\270 /V 1 /D "REGEDIT /S D:\Install\NIS\NIS.reg" /f REG ADD %KEY%\270 /V 2 /D "D:\Install\NIS\NIS.exe" /f REG ADD %KEY%\270 /V 3 /D "D:\Install\NIS\NIS2005.exe" /f REG ADD %KEY%\270 /V 4 /D "%systemdrive%\SFXTemp\NIS2005\SYMSETUP.EXE /O REBOOT=ReallySuppress /QB" /f How are you adding the registry entry - are you running regedit in RunOnceEx, or are you directly entering the registry entry in RunOnceEx? In the above code, NIS.reg is a file directly exported from the registry which contains my product key. I know it's a little backward, but try entering your product key through regedit to see if that works for you.

@Astalavista: For NIS 2005, follow "my" earlier posts. For all: From what I can tell, be it NAV or NIS, the important steps, and the order in which they must be done, is as follows: 1. Get the symlcrst.dll file from a currently activated copy of the program you're looking to use. Ideally, this would be from the same computer on which you plan to reinstall the program. You cannot just copy this file, because as long as NAV/NIS is installed on the computer, the symlcrst.dll file is protected from copying or deletion. Copying the file can be done in two ways: a. Install the program, activate it, then uninstall it. The file symlcrst.dll is found at %systemdrive%\Program Files\Common Files\Symantec Shared\CCPD-LC\symlcrst.dll and will be the only file left in the folder after uninstallation of the program. b. Install the program and activate it. Then log into your computer in safe mode and copy symlcrst.dll from the above path. 2. Make a registry entry to automatically enter your NAV/NIS product key. The only thing you need in the registry entry is the actual entry with the product key. This is best found by installing and activating the program, then entering regedit and doing a search for your product key. Once the product key is found, export that registry key and name it navreg.reg, nisreg.reg, or whatever-else-you-want.reg. 3. When installing on a clean system, install the following things in the following order: FIRST, regedit registry key you just created (with your product key in it) into the registry. SECOND, install symlcrst.dll to %systemdrive%\Program Files\Common Files\Symantec Shared\CCPD-LC\symlcrst.dll. This can be accomplished in several ways - you can create a SFX to do it automatically, you can xcopy the file there, you could put it in your $OEM$ file, whatever...symlcrst.dll just needs to be in this exact location before the last step. THIRD, install the program. The install routine must look to see if symlcrst.dll is preloaded, and if it is and it matches the version which it was expecting to find, it manually activates the installation of NAV/NIS, with the 366 days of complimentary updates commencing on the date the program is first run. This should work for NAV and NIS (don't know about the Pro versions yet). It can be run from both RunOnceEx and start.cmd. The order is the most important. Remember, 1. Regedit the registry key containing your product key into the registry. 2. Copy symlcrst.dll to the above location. 3. Run the install for the program. Heck, you can probably even copy symlcrst.dll before running regedit, just as long as both are done before installation of the program starts.

@ToBe: The values in my posts, at least all but the last one, are for Norton Internet Security 2005. (I borrowed the values from DLF's earlier post for NAV in my last post.) I assume that NAV will have a certain value, NAV Pro will have a certain value, NIS will have a certain value, NIS Pro will have a certain value, etc. That's why it's probably best to first install the software and look at the registry to see what the actual registry values are for your program. The "best" way to get the correct registry: Install and activate the software, open Regedit, go to "Find...", and type in your product key. When the registry entry with the product key is found, export it as "navreg.reg" or whatever, and use that for installation.

@www2000: Pardon my free association answers to your post. First thing I see is, you are using the registry entries for Norton Internet Security 2005. If you are installing Norton AntiVirus, the registry entry is different. Look at jbright's and DLF's posts for the registry entry for NAV. Also, the only thing you would really NEED is the line with your key. I recommend cutting the rest out, so that the only line is as follows: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000082\0000000f\0000001b] "Key"="XXXXXXXXXXXXXXXXXXXXXXXX" Yes, the XXX's are where you put your registry key. In my registry entry, I have the dashes included in the key, and it works. You may not need them, but it works if they are there. (Any reason you don't want to include them? You don't save that much space by not using them. ) Should work, as long as you've copied the contents of your NAV CD (minus the things which can be deleted, see other posts for that info) to %systemdrive%\Install\NAV\. Yeah, the virus def stuff is optional, it is nice to already have them installed but it's not necessary, and it can be a pain to continually update your SFX with the newest defs. Here's a suggestion I have for your RunOnceEx file: REG ADD %KEY%\010 /VE /D "Installing NAV 2005" /f REG ADD %KEY%\010 /V 1 /D "REGEDIT /S %SystemDrive%\Install\NAV\NAV.reg" /f REG ADD %KEY%\010 /V 2 /D "%SystemDrive%\Install\NAV\NAV.exe" /f REG ADD %KEY%\010 /V 3 /D "%systemdrive%\Install\NAV\NAVSETUP.EXE /O REBOOT=ReallySuppress /QB" /f The time spent running regedit and the SFX with your symlcrst.dll file is so small, I recommend just saving the screen space. But that's your personal choice, whatever you like is the best thing for you. Good luck!

I did this a while ago with a Dell OEM CD. Like sleepnmojo said, delete the hotfixes. There will also be a bunch of files in the I386 folder that need to be deleted - they all begin with either KB###### or Q###### (# indicating the wildcard is a number). You also have to clean up svcpack.inf to remove references to the hotfixes, and then makecab the cleaned svcpack.inf back to svcpack.in_. From my experience, SP2 won't update the files if svcpack.inf is expanded, but once it's cabbed, it will. There may also be some stuff in the $OEM$ file that needs cleaned. I THINK this is what I did, I'm at work now and can't remember exactly...I can look when I get home.

@jbright: I was working on it apparently at the exact same time you were. You beat me to the post, obviously, because while you were posting the first post in the thread (at 11:58 a.m. on 11/13/04) my install was running (as evidenced by the time stamp in my last post re: my ez-log.html file and the fact that currently my local time, Central Standard Time, is the same as MSFN posting time). After I confirmed my install method would work on a clean install of Windows (which was accomplished between 12:15 p.m. and 1:05 p.m. 11/13/04), I posted my instructions as an alternative/clarification to yours at 1:20 p.m. As my computer was not connected to the Web during my install attempts (I use a second hard drive to test my installs) I didn't even know about your install attempts until after I had confirmed my attempts worked. After I read about your method, I did not test yours to see if yours would work or not, I just knew from my previous attempts a couple of days earlier that a similar attempt I had made, that is, installing symlcrst.dll to the CCPD-LC file after installation of Norton Internet Security, did not work for me. And I knew that what I had done earlier that day - installing the CCPD-LC folder with symlcrst.dll inside prior to installing Norton Internet Security - did work for me. I don't need credit for it, and I'm not trying to steal credit from you. I was distinguishing the method in "my" posts from the method in "your" posts, which obviously other people were trying and not having success. Heck, there were other posts I had read prior to my attempts that led me to which files to use, so I highly doubt that either of us are the first human beings on Earth to accomplish this. Isn't the important thing here - the reason you posted your findings, the reason I posted my findings, the reason those before us posted their findings - that we've made installs of these programs a heck of a lot easier for many others?

I can confirm that the install program (for NIS, at least) does NOT overwrite the symlcrst.dll file. At first, I thought it would, but I tried it just to see if it would work. In fact, the program does a manual activation based on the presence of the symlcrst.dll file - here's the text of my ez_log.html file from the CCPD-LC folder: 13.11.2004 11:58:56:499 580 Manual mode enabled. 13.11.2004 11:58:56:499 580 Executing version 1.8.54.478 of C:\DOCUME~1\Jason\LOCALS~1\Temp\SymLCSVC.EXE 13.11.2004 11:58:56:499 580 Commandline = "C:\DOCUME~1\JASON\LOCALS~1\TEMP\SYMLCSVC.EXE" INSTALL /MANUAL 13.11.2004 11:58:56:499 580 NT based operating system detected. 13.11.2004 11:58:56:499 580 Installation initiated. 13.11.2004 11:58:57:50 580 Deleting file C:\WINDOWS\system32\symlctnk.dll 13.11.2004 11:58:57:50 580 Deleting file C:\WINDOWS\system32\symlcnet.dll 13.11.2004 11:58:57:50 580 Deleting file C:\WINDOWS\system32\symlcsvc.exe 13.11.2004 11:58:57:80 580 Writing file C:\Program Files\Common Files\Symantec Shared\CCPD-LC\symlcnet.dll 13.11.2004 11:58:57:110 580 Writing file C:\Program Files\Common Files\Symantec Shared\CCPD-LC\symlctnk.dll 13.11.2004 11:58:57:130 580 Relaunching the installer from the correct location. 13.11.2004 11:58:57:150 580 Installation complete. 13.11.2004 11:58:57:170 1432 Manual mode enabled. 13.11.2004 11:58:57:170 1432 Executing version 1.8.54.478 of C:\Program Files\Common Files\Symantec Shared\CCPD-LC\symlcsvc.exe 13.11.2004 11:58:57:170 1432 Commandline = "C:\PROGRAM FILES\COMMON FILES\SYMANTEC SHARED\CCPD-LC\SYMLCSVC.EXE" INSTALL /MANUAL 13.11.2004 11:58:57:170 1432 NT based operating system detected. 13.11.2004 11:58:57:170 1432 Installation initiated. 13.11.2004 11:58:57:180 1440 Start service initiating. 13.11.2004 11:58:57:631 1432 Deleting file C:\WINDOWS\system32\symlctnk.dll 13.11.2004 11:58:57:631 1432 Deleting file C:\WINDOWS\system32\symlcnet.dll 13.11.2004 11:58:57:631 1432 Deleting file C:\WINDOWS\system32\symlcsvc.exe 13.11.2004 11:58:58:662 1432 Installation successful. 13.11.2004 11:59:00:665 1440 Service started. I started the unattended installation around 11:57 or so, I didn't track the exact time. The computer was not connected to the Internet at the time, so it couldn't do an online activation. My method has worked twice for me, both installing on a Windows installation with a previous installtion deleted and then reinstalled, and also on a fresh Windows installation. Interestingly enough, when reinstalled on a system with a previous install deleted, the 366 days started at the time the program was originally installed on the system, but on a clean Windows install the 366 days starts the day the program installs. I had tried before the copy the CCPD-LC file after installation, but the copy always failed. In fact, with a current installation of NIS on the computer, the only way I was able to copy symlcrst.dll was to go into safe mode. And copying the symlcrst.dll file from an activated installation to an unactivated installation did not work. Follow mine, it works, I guarantee it. If it doesn't, I'll pay back every cent you paid me for the information. B)

I don't know if it does, and I'm not going to find out. If you only have one license, you can only install it on one machine. Anything above and beyond that is piracy.

Use RyanVM's Update Pack. Here's the URL: RyanVM's Windows XP SP2 Update Pack It contains what you want, as well as all other updates to Windows XP since SP2 was released. Just follow the instructions. Details are also in this thread: RyanVM Windows XP SP2 Update Pack

I was working on the same thing this morning for Norton Internet Security. The procedure should be similar for NAV 2005. Here's what worked for me: First, I deleted my current installation of NIS 2005. After the deletion process is done, the following folders are left in C:\Program Files\Common Files\Symantec Shared\ (or wherever you've installed the program files): CCPD-LC (contains symlcrst.dll) VirusDefs (contains the latest virus defs downloaded and installed) I then made a WinRar SFX archive (called NIS.exe) to extract these files back to their original positions. The advantage of including the VirusDefs is that when you run LiveUpdate, the virus definitions are current. Total size of the archive is about 4 mb, as long as you've cleaned out all but the most current virus defs - but don't delete the BinHub, Incoming, and TextHub folders or the two .dat files as they are important for later updating. Here's the comment from my archive: ;The comment below contains SFX script commands Path=%programfiles%\Common Files\Symantec Shared SavePath Silent=2 Overwrite=1 Next, I created a registry file called NIS.reg, with the following text: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000083] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000083\00000028] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000083\00000028\000000d8] "Key"="INSE-RTYO-URKE-YHER-E123-4567" [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\InstalledApps] "AVENGEDEFS"="C:\\PROGRA~1\\COMMON~1\\SYMANT~1\\VIRUSD~1" [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs] [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedDefs\MicroDefs] "LastBinUpdate"=hex:01,00,00,00 "LastTextUpdate"=hex:01,00,00,00 [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SharedUsage] You probably don't need all this, but it's what is left after the original installation is deleted and the cleanup is complete. After all, by bypassing the activation, we're trying to fool the installer to think it's performing a reinstallation to the same machine which originally had the program, which, technically, you are doing if you reformat your drive and reinstall Windows and the programs. I had previously created a WinRAR SFX archive of NIS 2005 (called simply enough NIS2005.exe), which extrated the files to %systemdrive%\SFXTemp\NIS2005\. Here's the text of the comment for that archive: Path=%systemdrive%\SFXTemp\NIS2005\ SavePath Silent=2 Overwrite=1 Title=Norton Internet Security 2005 Unattended Setup I put NIS.reg, NIS.exe, and NIS2005.exe all into a file called "NIS" in my install folder. Now, here's my code for RunOnceEx.cmd: REG ADD %KEY%\270 /VE /D "Norton Internet Security 2005" /f REG ADD %KEY%\270 /V 1 /D "REGEDIT /S D:\Install\NIS\NIS.reg" /f REG ADD %KEY%\270 /V 2 /D "D:\Install\NIS\NIS.exe" /f REG ADD %KEY%\270 /V 3 /D "D:\Install\NIS\NIS2005.exe" /f REG ADD %KEY%\270 /V 4 /D "%systemdrive%\SFXTemp\NIS2005\SYMSETUP.EXE /O REBOOT=ReallySuppress /QB" /f (I install all my programs from a second partition on my hard drive which is not reformatted during Windows installation. If you use a CD, substitute "%cdrom%" for "D:\". ) First, the registry entry is run. Then, the NIS.exe file runs, which extracts the files to Symantec Shared, including the symlcrst.dll file to CCPD-LC. Next, NIS 2005 installation begins. By putting the symlcrst.dll file in its expected location BEFORE running the installation program, the installation program automatically activates the program during the installation. I'd run into problems before trying to copy symlcrst.dll to CCPD-LC after installation was run, also. This setup works flawlessly for me.

Ditto here, just did it an hour ago, in fact.

If you used nLite, it may have accidentally edited something out. I'm betting that something was taken out of the txtsetup.sif file, based on the error message you received. Just run nLite again, on a clean install point, and that should fix the problem if nLite did edit too much. You may want to ask about this in the nLite forum, I don't use it much myself.

Could you post your winnt.sif file? (Don't forget to edit your product key out!) Otherwise we can't see what the problem is. EDIT: Is this error even in winnt.sif? Could be in txtsetup.sif, based on the fact that it's looking for [sourceDisksFiles]. Have you edited any files yourself, or are you using nLite to integrate updates?

Well, my attempts at integrating WMP10 directly into the installation failed, and I've resigned myself to just adding the WMP10 KB887078 hotfix after WMP10 is installed. Oh well, can't win 'em all...