mazin

@Randy Rhoads Same method works for Windows Me, too. However, I had a problem with that method. When I used msbatch.inf, everything went well, except that Windows diplayed the screens of CD-Key, user name and organization name. They were written for me, but I had to hit "Next". That happened with some but not all copies of Windows I installed. Do you have suggestions? Thanks.

Well! Now the beast is under control! Watch for news. EVERYTHING is solved. Another Symantec product is smashed by mazin©. WOOHOO.

Good news. I'll give it a go and post back when ready. Thanks.

Let me check the MSI first. Or it may be written to the registry bu LiveUpdate package? Let me check that, first. Thanks. EDIT: Well! Thanks. I recieved your PM about that.

Is this key supposed to be the same on all PCs?

If you slipstreamed patches, then you've done AIP. So, you can't use setup.ini. Instead, you use the MST you've created, supposedly.

Well! Then, there's one attempt. I suggest you run the MSI like this: publisher.msi /QB PIDKEY=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Hope it works.

Unless you need to slipstream patches (MSPs), you don't need to do admin install. But, you can customize your installation using setup.ini along with setup.exe.

An unlicensed copy is legal, I know. Probably, I've been confused by this post: http://www.msfn.org/board/index.php?showto...ndpost&p=178184

Do you have a file named setup.ini? I think you should have it on your CD.

I think this is the licensed version, not ours! Am I correct?

AIP is a documented abbreviation on Microsoft sites, not my invention really. And P <> P????, hah, naughty boy!

@prathapml AIP? HUH? Kidding? Nice joke, really. Well, I'll consider adding LU 2.5 to my guide. I'll see if it can be made via the same batch above! If can't, I'll do it manually. Thanks. EDIT: @RyanVM That guy is kidding.

@prathapml Well! As for LU 2.5, I'm using the same idea of killerbee. But, since it becomes about 10 MB after extraction, I suggest you create a SFX for it with the same switch integrated inside the SFX, you know. The new SFX size is 3.25 MB only. This was tested and worked for me. It runs unattendedly, you know. I didn't add it to my guide because I thought it was off the course of AIP. Thanks.

So, you have got Publisher 2002 as a separate application?

My Useless Guide for SAV's AIP Before you use this guide, make sure SAV isn't installed on your system. Otherwise, you'll get errors when creating the Administrative Installation Point. Create a folder anywhere on your hard disk and name it whatever you like. I'll assume you name it "SAVSource". Copy the following files into "SAVSource": 1- 0x0409.ini (for French version, you need 0x040c.ini, instead) 2- Setup.ini 3- setup.exe 4- Data1.cab 5- Symantec AntiVirus.msi Those 5 files are copied from your CD (of version 9.0.0.338), of course. 6- SAVCE_9.0.0.1400_AllWin_EN .msp This file is extracted from SAVCE_9.0.0_mp2.zip (3 MB) downloadable from here. (for French version, you download this, instead.) 7- yyyymmdd-###-i32.exe It's usually 5+ MB in size and can be downloaded from here. The file I'm using in this guide is named 20040828-003-i32.exe! (for French version, you start here, instead.) 8- lusetup.exe It's 2.5+ MB in size and can be downloaded from here. 9- remote.cmd The following quote shows the contents of remote.cmd! Before you run remote.cmd, make sure you put sleep.exe in your system32 or Windows folder. After remote.cmd exits, you should have your AIP created (ready steady) as a folder in your system drive and named SAV91400. Now, delete "SAVSource" folder, as it's no longer needed. To install SAV using your AIP, add these lines to your batch file:

BTW, you don't need install.exe if you run netfx.msi!

If you are new to SFXs, you can read this post: http://www.msfn.org/board/index.php?showto...ndpost&p=132110

ThanksGiving Day times: USA: November. Canada: October.

Sure, I will, soon! B) @drthawhizkid Thanks. I hope Cee-Kay has got enough time to improve it.

i32 worked fine for me, too. Thank you all. I think the guide on the first page must be updated now. Updates should be: - Use i32 not x86. - Overwrite not delete then extract. @killerbee You can enhance extraction process to be short and completely silent: NB: I created a batch file to do all the job silently. B) - Creating AIP. - Patching AIP. - Extracting V.Defs to AIP directly.

Exactly!

Yes! It's a good method and you'll have ITW, too.

WOW! This should be the best idea ever, if it's always possible.

http://rinkworks.com/stupid/cs_online.shtml You'll laugh to your extent. The original thread is here: http://www.msfn.org/board/index.php?showtopic=2112 But gamehead's joke was never matched!