prathapml

I'd better warn you in advance..... (someone here -me- wants them, LOL) Keep an eye on those, or soon you'll find some of them missing from where you left them.

Many of these problems come up, even if you have done everything right. There's just too many things to keep track of. Just pick up your original WXP CD, slip-stream SP2 into it - and burn a new CD. Install it from that, and things will be fine.

No, not needed for auto-update, its needed for SFP and system-restore - both of which aren't really needed if you know what you are making the machine do. So...... Disable System Restore!

I really don't know - 'coz I haven't merged 2 Office CDs of different languages. But I'd guess you can just make 2 directories: Office_EN Office_AR On the root of the CD, then copy over their respective contents. Then, you could use the cdimage (v2.47, tool by MS) command-line utility to optimize the resulting ISO-9660 image. Then burn the image to a CD.

I've used my current CD-RW for atleast 150 writes, I'd say. It now looks pretty old, but survives. My other discs have been similarly used as well - you can expect atleast 100 writes, if you maintain/store that disc with proper care.

moved to hardware hang-out

Have you both tried checking if the original CD (from which you sourced the I386 for the update to SP2)? Was it scratched or unreadable in any other way - in short, are you sure of the integrity of the CD you updated?

Yes, just use the standard batch-file. Where you'll have a problem though, is to fit both win2k and o2k on one CD (if you install from CD). The switch is "/QB". The first time you start any app from the suite, it will ask you for the key. Sufficiently unattended for office2k - OXP and O2k3 have more advanced unattending features.

Hmm.... I suppose if it shows up during your testing in normal windows mode, it would do the same during uA setup as well. I would gladly use the update with /Q switch, but my only gripe with it is that it would end up swelling the size of my CD - so I prefer to replace the existing defs with new - which Symantec still isn't satisfied with - I suppose it thinks we are a bunch of lying kids, so it asks its mother and confirms the news.

OK, understood what the problem is. (you can now edit out those screenies) The SAV isn't ever satisfied with what is already there (even if it is the latest already) - it necessary always wants to go out and download the latest updates - I saw this being discussed somewhere - there's probably a registry entry, or a file signature somewhere which we aren't able to update when we merge the newest virus definitions. Well, no probs as long as you can manually deny it permission to update itself, when you already *KNOW* that it has the latest it could get.

Man..... not bad at all.

Advertising your site on the *FIRST* post, is not exactly the best thing to do. The main purpose you registered on MSFN wasn't to spam, was it? Stay around, for a bit, participate in the other discussions going on, then post an ad about your website as an aside, not as the *MAIN* and only post you have ever made. BTW, your site is inaccessible on first try, takes some extra hops for your DNS to be seen, maybe. Might like to change your DNS provider to a faster one. And always see that you don't commit the cardinal sin of having a website that a browser with images turned off can't make head or tail of. Fortunately, your page hasn't made that sin, so your site is OK.

Could you please mention which ones those are?

Since the last few days, there has been a spurt in the number of reports saying that the first screen of GUIsetup appears before carrying on with uA install. Fine, I shall do a bit of looking under the hood, and post back (if I'm able to reproduce the same error), on what could have gone wrong.

Hey! Now that's *REALLY* odd as you said. OK, from now on I know to look out for them, and try getting from their server.

More details about updating distribution-source, and silently installing SAV9 can be found here: http://www.msfn.org/board/index.php?act=ST&f=80&t=23991

More details about updating distribution-source, and silently installing SAV9 can be found here: http://www.msfn.org/board/index.php?act=ST&f=80&t=23991

That's great news! You find the warez which already have the build1400 update integrated. How they do it is described below. Slipstream SAV9 Update 1. Run a setup.exe /A (admin install point) 2. Get AV-defs (get the i32 version) from here 3. Save it in a folder, and then change into that directory using the command-prompt. Create a new folder called "updts". 3. Extract the above-mentioned exe using "/EXTRACT .\updts" switch, and in the admin-install folder, over-write files in "\program files\Symantec AntiVirus\Virus Defs" with all files from the extracted i32 update. 2. extract "SAVCE_9.0.0.1400_AllWin_EN .msp" from the update (see previous post) .zip and place it into the SAV9 admin/server-image install dir. 3. Open a command-prompt into that directory, and use the following command: msiexec /p "SAVCE_9.0.0.1400_AllWin_EN .msp" /a "Symantec AntiVirus.msi" /QB So there it is, AV-updates and latest SecurityCenter patch merged into the distribution source. Now, can we have more details from ppl who have successfully pre-configured their SAV? I mean, how to: 1. Disable the LiveUpdate that comes up at the end of install? 2. Disable Automatic updating 3. And whatever else, interesting things you ppl have found out.

Somewhere in the menus, there is a listed "CD drive". Then you'd find an option called "Capture ISO image" which when you click brings up an "Open" box where you select location of your ISO. Then, just click "power-On" and everything will start up just as in a real PC and setup will start. BTW, if you are new to Virtual PC, it'd be rather helpful to have a read of the in-program "Help" - it contains a good manual of what/how to do things.

ROFL...... Yup! we are all friendly here. Welcome to the MSFN forums.

Hey to you too! Welcome to MSFN forums.

Yeah, the stereo-typed stuff here..... Vote for F1, fave is Schumacher (but don't keep myself updated with latest developments in the field).

OK, that's cool then! I suppose we know what that means (unless your logs were lying or your eyes didn't search properly) - it was successful.

OK, that's fine - sufficient. Now try downloading something (umm.... something popular which lots of people have shared - ah, why not download XP SP2 itself) for 5 minutes. By this time, the needed results have come. Stop the download and check for EventID 4226 (hopefully that hadn't appeared ).

Nice fix you got there! Gotta use it myself too - was looking around for a solution for this since the beginning.