mazin

@smc1979 hmmm...I just wondered why didn't you rename lusetup.exe to Lsetup.exe and put it in: ..\CommonAppData\Symantec\LiveUpdate\LuMMInst\Lsetup.exe, so that SAV installs it for you.

Oh, it's my fault, then! My normal niche is App. Sw. Forum, so I rarely read MSFN news page.

Well, I haven't seen it posted on this forum before, have you?

@smc1979 Why do you have to install LU separately? @RogueSpear Would you please explain an example of configuring those settings via GRC.DAT? I haven't read much about it. It'd be better if you could post it, here.

Official Gmail Notifier! DDL: http://toolbar.google.com/gmail-helper/GmailInstaller.exe Info: http://toolbar.google.com/gmail-helper/ CHEERS!

I'm not offended by buletov, and I think he's mature enough to understand me. Thanks prathapml.

@buletov Alright, sir! For McDonald's, I'll consult my stomach and report back!

For Acrobat, it's ISX_SERIAL not PIDKEY. However, neither of them works on the command line! And Acrobat requires /QR not /QB nor /QN. Also, the original serial doesn't work (with or without dashes) from a reg file. There should be the encrypted serial exported from the registry. This reg file should work fine on a clean machine if applied before running the MSI: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\6.0\Registration] "SERIAL"="encrypted serial exported from registry" [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Distiller\6.0\Registration] "SERIAL"="encrypted serial exported from registry" However, this is my favorite method.

I think this guide can be adapted to your language.

yeah... and won't continue without a key!!

@skeetre A search taking a few seconds can bring you an answer. @buletov Do you think your post is of any help to a person who's asking for a way to install a product? However, who can ever trust a freeware for such a critical mission of proterctng PCs against threats? Are data and accumulated work so cheap? Can you hold a free-software author accountable while you haven't paid them a penny? Actually, Symantec products are the greatest software in their field. This is accumulated experience over years. I do not trust software authors who appear suddenly with new software and then offer their products for free. They can only attract idiots who do not have real sensitive data on their PCs. And before all, they are imitators, who copy others' work and provide it for free without worrying about others' PCs. @SilverBullet The method prathapml refered to is the same and it's adapted to NAV 2005, here. I think this thread should be closed. We'd better stick to the thread above (NAV 2005) instead of repeating same instructions again and again!!!

Well, I used both and I'm satisfied with them. And there's always the opportunity cost. SAV doesn't protect a PC against malicious scripts, doesn't protect a recycle bin, isn't integrated to office applications, doesn't perform a pre-scan before installation, and doesn't create emergency disks that are a must sometimes when a PC can't start due to a virus. On the other hand, if we disabled the above features from NAV, it should be fast, too.

Your name is on the crackers list that is banned by Microsoft?! Kidding. Now, it's time for Microsoft to force peolpe change their names if they want to use MS products. Come on, Bill Gates!

Now, it's time to my 2 cents. NAV: ------ It's designed, intentionally, to protect a single PC. Being designed for this purpose, it assumes a PC user who is careless and a PC that's not connected to a server. Home users are mostly careless, as we know. They can forget to, frequently, update NAV or V.Defs or LU or whatever. Hence, there's automatic liveupdate and it's on by default. SAV: ------ It's designed, intentionally, to protect a network. Being designed for this purpose, every PC on the network gets its updates from the server. The network administrator downloads an XDB file (instead of i32) to the server. Whenever a PC on the network boots, it looks for that file on the server and takes V.Defs updates from it. Other updates are taken care for by the admin, too. So, there's no need for a client PC to update itself independently via Internet connection. Hence, there's no need to automatic liveupdate. Now, since we have the client program (the subject of this thread) installed on our single PCs (no servers), we are worried about automatic liveupdate! However, Symantec did not forget the client entirely. Still, you can schedule LiveUpdate to run automatically and silently to perform a frequent update to your client. Symantec says that it uploads a new V.Defs updater file every week. So you know how often your LiveUpdate should be scheduled to run. My own experience: ----------------------- I rarely turn my PC off, unless after an exhaustive defrag operation. So, my LiveUpdate wakes up at 03:00 AM on Thursdays (while I'm asleep), connects to the Internet, downloads what it likes to, installs it, disconnects from the Internet, then goes back to its bed. Isn't this automatic liveupdate you worry about?

Good find. Much simpler. Have you tested it? Thanks.

For the record, I recieved FOUR invites to my best friends & relatives from: - Astalavista (1 inv) - weed (1 inv) - evilkwan (2 inv) Just wanted to thank'em.

Good one!

This key isn't common on all PCs, is it?

@shaz Thanks, man!

I used this command to integrate SP2 to WinXP-Pro-SP1a with no problems: I:\XPsp2.exe /integrate:C:\XPCD, where I:\ is my CD-ROM drive.

Thanks DisabledTrucker for refering to this tool. Have you tested it yourself? Thanks again.

Due to that sentence, I understood that you didn't know it. That's it. Ah, and in the post you linked above, you talked about downloading SP1, not that one on the CD. CHEERS!

This step isn't needed by people who received an SP2 CD. SP2 CD has both files. This is a small guide for that.

SP2 CD isn't useless! You need to do the following, if you want to prepare a copy of .NET Framework 1.1 that has SP1 slipstreamed. 1- In your (shipped) SP2 CD, and in this directory: X:\DOTNETFX\, you'll find two files: DOTNETFX.EXE and NDPSP.EXE! 2- Run DOTNETFX.EXE from the CD, then go to your %TEMP% folder. From the folder "IXP000.TMP", copy netfx.msi and netfx1.cab to a safe place on your HD. Now, follow setup screens to install .NET Framework 1.1! Restart your PC if prompted. I don't remember if a restart is required, really. 3- Run NDPSP.EXE from the CD, then go to your %TEMP% folder. Wait few seconds till you find an MSP file created there. It's 18.3 MB in size. This file is the patch needed to update .NET Framework 1.1 with SP1. Copy it to the same place where you keep MSI and CAB. Cancel the setup process at this point, or complete it if you want to update the version installed in step 2. Please be informed that you MUST complete the installation process mentioned in step 2. Otherwise, you can't get the MSP file. 4- Now, create Administrative Installation Point using MSI+CAB. This is the switch you need to create AIP: netfx.msi /A Provide a path for AIP when prompted. I assume your path is C:\NET11SP1 5- Put MSP file in C:\NET11SP1\NDPSP.MSP, I assume you name it so. This is the switch you need to patch AIP: msiexec /p C:\NET11SP1\NDPSP.MSP /a C:\NET11SP1\netfx.msi After the patch operation completes, delete NDPSP.MSP from C:\NET11SP1\ as it's no longer needed. By now, you should have three objects in C:\NET11SP1\, and they are: - Program Files (folder) - Win (folder) - netfx.msi (file) They total 56.1 MB in size. You can compress them using WinRAR or whatever with the following comments: ;The comment below contains SFX script commands Setup=netfx.msi /qb TempMode Silent=1 Overwrite=1

That's what I use. Just add quotes.