mazin

RunOnceEX is slightly different. Here's an example:

Thanks for confirmation. CHEERS!

$OEM$ folders are copied to your PC before RunOnceEX runs. So, you'd better create SFXs (or use COPY command) that run via your RunOnceEX. And you put those SFXs in a later phase after original programs are installed.

This works for 4.8.2: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Yanicsoft\WinXP Manager] "Date"="type your serial here" "Name"="type your name here" "CreateSR"="True"

I'm not sure if this works, but you can try it: - Extract the main EXE, then run pcc.msi with /qn. Or, without extraction, you can run the main EXE with /S /v"/qn". You can use /qn REBOOT=ReallySuppress or /S /v"/qn REBOOT=ReallySuppress" if you know that the app requires your PC to restart. - Use this reg key to register: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillin] "register no."="xxxx-####-####-####-####"

@prathapml For those who are interested, my method of NAV is adapted for NIS by other guys here.

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000082\00000002\00000002] "Key"="xxxxxxxxxxxxxxxxxxxxxxxx"

This can be done via cmd(Z)!

Updated Sir! Thanks. Wish you good luck with PMI files.

Thank you Thauzar! I added the French links you PMed me for people who are interested. Just a stupid question, is there a French version for LU 2.5, too?

You can use /qn instead of /qb to hide progress bars. Keep up the good work. When oaom asked, I searched using Norton Internet Security as a keyword. I didn't find any topic for it. I hope that this thread will be the official guide, now. I think it could be found via a search.

Error 1603 means Fatal error during installation.

hmmm... So you are all talking about Cyber-For-Love all the way. All singles? No business opportunities? Wish you good luck!!! B)

I told him. But he believes that the packager of 8.1 can work for 9. I'm not sure if this is possible, however. @drthawhizkid HUH? Do you have good news about that? I didn't try it.

So sorry. I don't have any packager.

A download manager can do the job, I think.

@drthawhizkid Yes, just renaming. No extraction required. @big poppa pump So, no more investigation about switches. @Cee-Kay Thank you very much for your time trying to help. Now, it's much easier. Stay for harder missions.

I'm still waiting for SP2 CD. I hope I can help when I recieve it. Or, maybe, I'll ask like you. Who knows. EDIT: Did you try this solution?

It should work this way unless some files or folders inside driverz are in use by your system: move %systemdrive%\driverz %systemroot%

@Thauzar So far, this guide has been talking about unlicensed version of SAV. If you've got the licensed version (Business Pack), then you need to download an MSP that's different from what we talked about here. For anyone who wants to determine which version is installed on his PC, please read this. And from there, you'll know what to download to update your product.

Guaranteed!

As I read on some threads, v9.0 has no packager. But you can check the guide here if it could help you.

WOOHOO! Thanks for your confirmation. Actually, this is what I meant by this party: I'll update my guide, soon. Thanks again.

MSIs in this location c:\windows\installer are needed for uninstall/repair/reinstall operations.

Thanks for confirmation. Now, I've got a new idea, tested it, and worked very well. I need feedback so that LU issue is over. I renamed the downloaded lusetup.exe lsetup.exe and put it in ...\CommonAppData\Symantec\LiveUpdate\LuMMInst as a replacement. I ran SAV.msi and LU 2.5 installed automatically! May someone try it? Thanks.