prathapml

A nice thing indeed! Just wanted to mention that you wouldn't be able to use the above, if you're not logged-in to MSFN before using that SearchURL.

On SP2 RC2, I removed firewire drivers and had no problems. Prolly it is messing up elsewhere? In any case, it looks like RC1 onward has deliberately crippled support for firewire - so that you don't use on a long-term basis.

If nowhere else, it most certainly must be available on BitTorrent. If even that doesn't help, try warez sites or on P2P networks.

OK then, please go ahead and make your voice heard! Vote for "Others". I hope everybody who drops by this thread will vote.

Exactly! They will stop with the testing today, and rename (if all goes well) that same day's build as SP2 final.

Yes, you need to extract the .NET framework (downloadable executable) using winrar (or anything else), and you'll find some files contained within. Have the entire folder, and when you install, use the .MSI with the "/QB" switch. Here's where the above process is mentioned : .NET Framework Start from the beginning by having a look at MSFN's official unattended guide here, if the process is too complicated.

Nopes! I do the same thing - slip-streamed SP4 and no updates beyond that.As a matter of fact, i got the errors you describe when I used to install directX from cmdlines/svcpack.inf. Then, I moved away the dX install to GUIrunonce, and all is fine now.

@all- Do make your opinion count with the poll above (even those of you who have posted already). And voice your impatience (if so) about the late release of localised versions of SP2. It'd be nice to know how many of us use the plain/vanilla English (US/UK/Australia/etc.) version of winXP. How many use the languages which are covered by the first wave of release (german, japanese will get released alongwith English). And how many use the other 25 localised language editions for which it will take upto 2 months for an SP2 release (spanish/dutch/french/italian/mandarin/arabic/etc.).

Its a known fact that winamp can listen to streamed audio - no add-ons required at the client side, just a plug-in (200 KB) required at the "streamer source" site. As for video, I don't know what you could do other than what I suggested above.

I use XP normally, or win2k at the least; but the oldest _running_ OS that I'm supporting is Windows ME. AAAARGH!!! (so that is where that 1 vote for winME came from)

Ha ha ha....... Isn't it such an irony that we are being slowed down by the Americans? (no offense meant, they normally are the quickest ones). We are waiting while the US time-zone is still indicating the previous day's "time to sleep". BTW, could you share that "nice bottle of Heineken" with us all, who are shivering in the night, keeping a candle-vigil?

good news! You can junk all your hot-fixes, and svcpack.inf fiddling, and all the head-aches of testing after that. SP2 for winXP is getting released in a few hours. Just slip-stream that into your XP install source, and you'll be OK. No hot-fixes/updates/add-ons needed.

No!The .NET framework will only be installable via the autorun function (same as in SP1) on XP Pro/Home Editions. The "netfx=yes" component entry is for MediaCenter/TabletPC editions of WinXP (I think - correct me if I'm wrong).

Nopes!from the looks of pre-release versions of XPSP2, there are no additions to MassStorage device drivers (which is what SATA/IDE/SCSI are). MSFN - Registered members: 22864 And only (hmmmm.....) 6 have posted here?

Here's the info that I got from elsewhere: So, I suppose, you can actually call your $OEM$ as Any_Folder, and specify that in the winnt.sif? And it will work?I've seen that the above mentioned entry actually refers to the SystemDrive, not the CD (i.e., OemFilesPath="..\My_Folder" would make setup search for a folder by that name on C:\, and not on the CD as desired). As for the "OemPnPDriversPath" entry, it is a certain fact that setup searches for the directories mentioned here on the SystemDrive (partition on which you installed windows, i.e., C:\) only, and there's no way to make it look anywhere else.

Hey, carry on folks. We'd like to make this the definitive thread for eve-of-SP2 butterflies in the stomach. You can talk of abstract feelings, non-technical matters related to this, whatever!

checked out KiXtart - looks good. My view on why CMDs are better: 1. Batch-files are processed by a native part of the OS, and as such, are very deeply tied in to the system and are very powerful. 2. KiXtart is too 'Unix'y to appeal to micro-softies. 3. KiXtart looks like more of a scripting and programming language, unlike the simple and easy to understand batch-files. 4. Lastly, those who want a good-looking front-end move out of batch-files and into GUI tools, not another script-based tool.

OK, everybody. #clap clap clap - to get attention# Here we are, with just about 24 hours left (I think) for the RTM of Windows XP's Service Pack 2. Let's keep a candle-light vigil, waiting for it. And let me see how many more people join in. The aim? This is the thread you'd find the first (on MSFN) link to SP2 final. We'd like to make this the definitive thread for eve-of-SP2 butterflies in the stomach. You can talk of abstract feelings, non-technical matters related to this, whatever! Here's the siren going off, for all those excited about SP2 to start posting about their feelings, on the eve of its release.

So, I suppose, you can actually call your $OEM$ as Any_Folder, and specify that in the winnt.sif? And it will work? I've seen that the above mentioned entry actually refers to the SystemDrive, not the CD (i.e., OemFilesPath="..\My_Folder" would make setup search for a folder by that name on C:\, and not on the CD as desired).

Interesting calculations there, by /\/\o\/\/. I just hope those don't become true, because they are frightening. I'd like to be able to still run LH on my current PC, alongside the newer one (which I'd most certainly have to get, to run newer apps/OSes optimally). Moreover, there's XtremeMaC's post also, which has already said what I would like to say.

So, officially the scheme is closed to me.BTW, if I'd known that it was only open to US residents, I'd have been saved some time participating in it. Oh well, a learning experience never hurt anybody.

Please read the entire thread, with attention to all the big (if not the little) details. It is clearly mentioned, that you need to make an Administrative Install Point of your CD, before using the shrinker.

Yes. The process, and all other resulting installation media are very much the same for a DVD, as for a CD.

That's true (I think).With my current AthlonXP 2400+ (non-mobile), I am able to overclock the FSB (which is potentially dangerous if you have low-quality components) to raise the speed from its native 2 GHz to a frequency of 2340 MHz. Imagine then, the possibilities with an Athlon XP-Mobile!

Not exactly. Solution posted in the right thread.