prathapml

dunno...... The KB article just says that this hotfix'ed sys will fix the issue of loopback-IPs running into trouble under certain conditions.You have to download the update only if you have that issue. And you have to use the idea mentioned in this thread only if you have downloaded that update. So the reach for this one is quite limited. The rest of you who haven't had any loop-back IP problem with their XPSP2 can give this thread a miss and carry on......

Ah! Thanks for that touch-up Alanoll.... Well, there you have it people - now this topic is for those who have the problem mentioned in that MSKB link above.

The amazing thing about XP SP2 seems to be the release of two patches within a week of release, one is listed here: (the formatting is such that this page isn't able to take up the link, due to the quirks of the [url ] tags) Now, this small tip will show you how to slip-stream this update into the XP-CD.If you read the MS Knowledge Base article above, you see that the only file updated/replaced/changed is TCPIP.SYS - that is the only modification it does. Now, not all of us might need this latest patch, but having it applied would always be better. Now, many of us have a hacked TCPIP.SYS in our uA XPSP2 CDs, to allow for better performance in file-sharing apps. So, if you applied the above patch, your painstakingly hacked TCPIP.SYS will get replaced back with a stock version of the updated one. Now, if you took the new patched TCPIP.SYS after applying the above update, and then hacked it for the "connection tweak" (event ID 4226), you wouldn't anymore need to update it. You are patched to all the latest hot-fixes, AND you also have a patched TCPIP.SYS which behaves the way you want it. Then put this file after CAB-ing it into the CD (I386 folder) to replace the older TCPIP.SY_ file. If anyone has read this who is able to understand this and put it in simpler words, please do - I was pretty excited when I wrote this. And yes, if this tip is interesting or useful to you, please post back about how you did it, and suggestions if any.

bartPE WAS a grey area legally, not anymore.... Anyway, its upto you to choose. Just a tidbit I saw somewhere - It looks like a PE windows (winPE/bartPE/ERDcommander) will reboot every 24 hours - it looks like that's MS' way of preventing usage of PE as your main OS, instead of the recovery/install tool it is supposed to be.

Open the "Regional Settings" Control Panel, and set everything to the way you want them. Then export the registry key below (I apply this at T-13, that way it applies to all users) : ; Sets "Location" to India [HKEY_CURRENT_USER\Control Panel\International\Geo] "Nation"="113" ; India-specific Regional settings [HKEY_CURRENT_USER\Control Panel\International] "iCountry"="1" "iCurrency"="0" "iDate"="1" "iLZero"="1" "iMeasure"="0" "iNegCurr"="0" "iTime"="0" "iTLZero"="0" "Locale"="00000409" "s1159"="AM" "s2359"="PM" "sCountry"="United States" "sCurrency"="Rs." "sDate"="-" "sLanguage"="ENU" "sShortDate"="dd-MMM-yyyy" "sTimeFormat"="h:mm:ss tt" You could customize that to leave only what you want, its my comprehensive set for regional settings - you may not want to have such a big list of modifications.

Very promising indeed, RichWargo. Welcome to MSFN.

Oh my GAWD !!!!!! Simply fantastic - my next upgrade to my PC at home.... I know how its gotta be now

LOL Interesting to think of........ But that would surely be a sad day for the industry - despite all the barbs against him.

Don't give up so easily. 1. Download "lusetup.exe" from the link above (given by techguy). 2. Then, go into your NAV2003 folder. 3. Browse to the "SUPPORT\Lupdate" folder within the NAV2k3 install. 4. Replace the "lusetup.exe" which you find there with the new one. 5. That's all. Easy? Now go and buy yourself some sweets, because you have got it updated. The best part about this update is that the new LiveUpdate component installer (lusetup.exe) is smaller than the old one by 2 MB - so you save space on CD. You can update everything in the NAV-install this way - the LiveReg, the Virus Definitions, the SEVinst, and so on...... Please post back on whether it worked for you, or not. ++++++++++++++++++++ BTW, you guys might have noticed that NAV 2003 is detected by XPSP2's new "Windows Security System" but not perfectly as to monitor it. OK, the installable (slip-streamable) update patch (an MSI) that fixes it (so that WSC no more complains about an NAV which is in-communicado) is being issued through LiveUpdate. But you would like to have it already integrated, right? I have the update in slip-streamable form. It is about 1.8 MB, and anyone who wants to host it (and has the bandwidth) for download by other MSFN members can reply. I'll send it thru email, and you've got to honour your promise of putting it up for download.

Even if you haven't enabled "OEMPre-install" in winnt.sif, your $OEM$\cmdlines.txt will ALWAYS be parsed. Now that can be a good thing or bad depending on what you are trying to do. As for now, your best solution is to make yet another set of winxp install on the CD, without a $OEM$\cmdlines.txt file.

I found its new look pretty good - worth checking out. Although the interface is a bit cluttered up at first-run, and you need to configure it (cleaning up toolbars) before you'll be able to do anything. Could someone please clarify this for me? I noticed that it seemed a lot like MyIE2, Maxthon, Avant Browser, etc. in terms of interface design choice and options offered, and the display of pages. It looks like an IE-based browser. In other words, it uses the IE-engine (not its own, so its not independent) to render HTML/other pages, and has all/most of the functionality of IE. It is only as secure as the version/patch of IE that you have installed on disk. And if you have ripped out IE-core using nLite, SlimBrowser (or the other ones mentioned above, for that matter) won't work. Are these inferences of mine correct?

How would you have Slim Browser v4.00.2 (listed on MSFN front-page right now) installed unattended? ---- NEVER MIND ---- Found the answer myself. I'll anyway be posting the info for others who might want this: It uses an NSIS v2.0 installer (same as winamp). Just run "sbsetup.exe /S" (note the capitalising of the switch) to install it silently.

Please check if you changed the colours used to display the progress-bar - or whether you have left it at defaults.

Well, no sadly! The version of nvidia drivers included in XPSP2 is v56.73 - so to install your own drivers and CPL, your driver-version should be both higher than that (30.xx is lower) and also be WHQL'ed.

He's talking about his own web-site which is linked from the first-post.

There is a tool developed here (on mSFN) to make runonceEX easier. Yes, CDimage doesn't have a GUI boot-maker, and needs a command-line switch to operate to make optimised CDs. Its a tool leaked from MSDN.

Ah sorry..... I only mentioned the max. it could go there - my normal res. is here. BTW, all the points you make regarding the LCD: I'd like to voted Birbal style - get both. While the facts are good, its not fully so to everyone. But it simply isn't cheap enough (in my country) to buy them, and high env. conditions. Given that a large LCD would be cost about 4 times the size of a lower-end version, and far more than a very big HDD. somethings are differently favoured by me.

Hey dudes, sorry to spoil the party...... Windows XP SP2 (which everybody is gotta install sooner or later) already has Windows Media Player 9 integrated (just like the gold release of XP had WMP8). And its a fact that the methods described here don't work to disable the first-run and other prompts of WMP9. In any case, all of us can get an easier way to get-around that issue - see this thread. I suppose simply needing to use registry hacks alone, will be a lot easier......

I believe this is what will enable it back: REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom] "Start"=dword:00000002What had happened was that the service had been set to "disabled". Now, the above will set it to "Automatic" start - i.e., on demand. Do post back on whether it works or not.

Its possible that an update you recently got, or a BHO (like yahoo toolbar) went in and replaced system files, with its own versions - which can lead to plenty of conflicts and errors. Try this: format your C:\ drive, then install WinXP, then install Service Pack (released recently).

You could download the bartPE (a variant of winPE) from http://www.nu2.nu/pebuilder/. Then, use it with your XP CD to make a WinPE bootable CD. Use any plugins you want to, I never forget the XPE plugin (for explorer-style interface). Then, you'll see an option in the bart-menu that offers to install bartPE to hard-disk. Follow the prompts (which disk/partition, etc.) and you're done. It took me exactly 45 mins. for the whole process on one PC - after that, installing the bartPE on each machine is a 30-second job, so its good. It does work, believe me (I've done it, as have many others here) its very simple and you can't mess up your experiment by much, even if you wanted to. BTW, if at first you don't succeed, try again - with a slight variation this time.

Is your drive properly defragmented? Have you enabled DMA for it? Or have the drivers for the MoBo chipset got corrupted in anyway? Also, see in System Properties whether windows is accessing your HDD in LBA mode (which is _extremely_ slow). Welcome here Stanislavs!

Well, I seem to be the first _posting_ here, that I'll prefer the HUGE HD - never mind if its PATA or SATA, my MoBo can handle either. Reason? I have a good enough monitor (CRT, 17", can do 1400x1050@60Hz) which has sharp display - and there's still reasons why LCDs aren't as good as CRTs. But I keep adding to the data on my HDD at the rate of, like probably 5 GB a week - and I can't keep all of that, nor burn to CDs. Now, your HUUUUUGE disk here will help me. Whaddya say?

Well, if the statements coming out of Redmond are to be believed, the answer to your question would be "never", I suppose.

Make a thread and I'll sticky. FAQ I hope you like it.