prathapml

I believe the guide clearly states that this is the switch to use, it is: /qb-

IEXPRESS won't work for this package. WinRAR works perfectly. Also, following the guide above EXACTLY will give you successful results. Also, using the installer as it is will make your .NET framework install extremely time and space-consuming. You will have to have 23 MB for the v1.1 setup, and 11 MB for the SP1 update. Whereas, the slip-streaming will drastically reduce space taken (from 34 MB to just 12.2 MB), and also the slip-stream/admin-install-point procedure will quicken your setup.

The procedure is all the same as for office. Look here at the MSFN unattended guide for detailed, step-by-step instructions - http://unattended.msfn.org/xp/officexp.htm.

If the setup.exe was got after extracting from the original DOTNETFX.exe (I haven't yet received my SP2 CD), then just use "/QB" for silent install. Otherwise, use "/s /v/qb" switch. LOL, this question has already been answered before. Our concern is that it takes up too much space on the distribution media.

@drthawhizkid You could try this in the CMD window: msiexec /a whatever.msi Might work that way (same was the case with .NET framework). Also, if you have the original licensed package, you will be able to run "/A" with no problems. The warez download sites seem to give out a single-file installer which is pretty problematic as mentioned by you.

No, you can pre-order it right now. And the one many are already having is licensed too (v9.0.338). So there's no difference in the two. Licensed and "ours" is the same. Also, maybe symantec will release a patch for upgrading to v9.0.1 once its finalised. Because it is not a new version (like v8.1 was to v8.0), a patch SHOULD be available - I'll wait and get that instead of running to buy a pre-packaged version of the updated SAV. BTW, what I meant was "All-in-what????". I mean, what word that starts from letter "P". Sheesh, this is getting a bit funny now...... might be wiser to finish up with it.

Check your personal messages (under the MSFN toolbar on top). Been sent one. Enjoy Gmail!

Yes, and the procedure is described here : netfx. You'll have to adapt it slightly to suit the slip-stream method. Enjoy!

Nopes, I wasn't kidding. In fact, that sentence (quoted here) looked like an abbreviation for something else. I'd heard of AIO's (All-in-one), but not of anything like All-in-P?????. Hence my question. (its late night now, so maybe I'm getting a bit slack in mind).

I'd be happy to see that as well in your guide. I really don't know what an AIP (as in the context of your post) is, LOL. But I do know that my original intention in this thread was to have all necessary updates for SAV9 in one guide (that includes LU 2.5). Any more additions that I haven't mentioned are welcome too. Any cautions/notable-things to check on while making the SAV9 combined would be good too. Any more ideas/notes would be good. Basically, EVERYTHING that there is to be about SAV9. Thanks for taking the time to put together that guide mazin!

Sent an invite to you too, check the mailbox address that you gave in your PM to find it.

Thanks for that addition - updated!

OK, I'll check "before" and "after" version numbers once again, I guess.... Also, the easiest way to check if the SP1-slipstreamed version is properly made/installed is to simply visit Windows Update, and check if it offers the SP1. I found that the method given by RyanVM (and posted in my post) kept windows update happy - it said I already have .NET SP1 installed - nice! So here's your confirmations dudes. Let the slogging (for all you who HAVE to stay with the latest) begin to have .NET+SP1 together, LOL. You've got the necessary guide above. @RyanVM Updated my step-by-step post above to reflect your most recent post (the switches /XP and /C).

The planned method has been posted in previous post. Does anyone know if there is any way to check if the now installed version of .NET is really the 1.1+SP1 version? Because the main file (mscoree.dll) in the "\Win\System" folder shows the same version, before and after the SP1 refresh (i.e., the version 1.1.4322.2032). @RyanVM All credits go to you for the above step-by-step description of the process.

Not all of us want to hear music wherever we go - in that case an iPod has no relevance, a PC suffices. But there are the music enthusiasts among us, I accept - who'd hate to be out of hearing range of good music throughout their wakeful hours. This device makes a lot of sense to them.

That's odd, it didn't work before for me...... Anyways RyanVM gave me the courage, and here's the steps (given by him): 1. First download the .NET framework v1.1 re-distributable package, and run "dotnetfx.exe" with the "/C" switch (to extract contents). 2. Then download the .NET fw v1.1 SP1 update, and run "NDP1.1sp1-KB867460-X86.exe" with the /XP" switch (to extract contents). 3. A dialog box asking you where to save the MSP (update patch) comes up, choose where you want to save it (size 18,760 KB). 4. Rename that MSP to SP1.MSP, and place the extracted contents of dotnetfx.exe (.NET framework installer) in the same directory. 5. Clean the directory so sp1.msp, data1.cab, and netfx.msi are the only files (3 files) in the directory. 6. Run the following commands (from a command prompt): msiexec /a netfx.msi TARGETDIR="c:\netfx" msiexec /p sp1.msp /a c:\netfx\netfx.msi These commands created an admin-install point and patch-updated it to .NET SP1 respectively. 7. Your c:\netfx directory should have 3 items in it after this operation: 2 directories - Program Files & Win, and netfx.msi. 8. Now you can compress it to SFX (if compressed it will be just 12.2 MB, if left uncompressed it is 56.2 MB). And set it to silently extract. 9. And install your newly created ".NET Framework v1.1 slip-streamed with SP1" package during XP/win2k setup with the "/QB" switch.

That's cool. Could you describe what you did to merge it in?

That is described in detail here: Command-Line Switches for the Microsoft Windows Installer Tool MS Knowledge Base article

Just put "Warranty Terms" as the first line to be displayed, in oeminfo.ini - that's quick and simple. If you really HAVE to change the text-string on that button, then open up sysdm.cpl in Resource Hacker (or some similar tool) and do it.

Thanx a lot mazin - now we'll wait for a day or two, for additions/suggestions to your guide, then post it as the primary guide (I'll replace my instructions on first page of topic).

Well, my SP2 is faster..... Slip-stream it into your winxp CD, and then install.

So learning is a continuous process - didn't know of this previously.

Have a manually enforced policy on what should/should not be installed - all non-humanised items are ultimately not perfect.

You can prevent the creation of that folder (by Office 2003 install) by using an MS Installer property alongside other switches when you install it: LOCALCACHE=0

I doubt activation will be done away with. If anything, they may make it more intricate. And why should they eliminate activation? Its their right to prevent un-licensed usage.