prathapml

So here I seem to be scurrying about my job, busily resurrecting threads from the stone age ( , 2003 already seems stone age to me, don't know 'bout you). Cool!

Yes, for sure. And what's more - XPSP2 contains an updated version of WMP9 (integrated, just like how WMP8 was into XP-classic) than what is otherwise downloadable.

The same incompatibilities as were known to exist from RC2 - some get fixed, the others will not, coz the responsibility is on the makers of the app to fix badly coded apps which end up being incompatible with SP2.

There's nothing wrong with what you have done. The fact is, having a winnt.sif itself rules out any possibility of the option to use the recovery console being presented to you. Go here and make an optimized ISO9660 CD-image with 2 BOOT folders - one should contain winnt.sif, and the other not - and I386 folder shouldn't have a winnt.sif at all now (after making your CD a multi-boot as described above).

encore from me, here! And yeah, I voted for "both are equal" - equally DIRRRRRTY that is!

The next time I trot up to a shop which stocks gfx cards, I'd buy a card based on an nVidia GeForceFX 6800 GT, AGP 8x. Why? It's available for a reasonable price (considering its monstrous capabilities). Its not a top-end card retailing upwards of $500, it is a main-stream one - available from different makers at different price-points. It has enough of VRAM onboard (256 MB), and would most certainly have features like TV in/out, with channel surfing and PVR functions. Also, since I already have quite a high-end MoBo with AGP-8X support, it makes sense for me to go for one with that feature - PCI-X is useless with my MoBo (I don't say the technology is bad, just that I won't have an option of using it) for another year atleast.

Yep! The price/performance ratio makes the Athlons winners.

Marathi That's supposedly my native language. But I end up talking/communicating with people (online, as well as real-life) in English more often than not (90% of the time). So I can't really claim to know my Mother Tongue very well (I know as much as I learned of it in my infancy, I suppose). Marathi is one of the many, many languages spoken in India. I vote for Asian group of languages.

It would be nice to know how many of those on the forums are speakers of a particular language. Do vote, and then post (if possible) the specific language you speak as your Native-language (also called Mother Tongue), and any extra info you might want to add.

Open Windows Explorer (just view My Computer, or something). Tools >> Folder Options >> View >> (uncheck) Use simple file-sharing

Yes, I'm interested - how would I do that (enabling LZX) ?@BeenThereB4- Yes, that is an expected error entry.

Yes.

Yes, you got it right. Its not possible to change the name of the $OEM$ folder, atleast, not when you don't want to carry out the $OEM$ folder's funtionality manually!

You'll find that info as well (its a small .reg file) in that thread, just try. Or, use "search" in the Application Switches forum (yes, here itself).

They won't because that will bloat their OS further. Also, all they really need is "drivers", not all the CPLs which just give an interface to fine-tune it - that's a function left to manufacturers. When I bunched 62.76 with RC2, things worked out just fine - you might want to do that. If dX9c support is *SO* important (which gfx card? GeForce FX6800? lucky!) that you *HAVE* to use 62.77, you still need to wait for a new WHQL'ed release, or install 62.77 manually.

This is *THE* definitive thread for what you want - discussed method is quite the same for older versions too! NAV2004 Do try searching first, because it will save you sometime in waiting for an answer.

You could do it like this: 1. Delete all files\folderrs in \VIRUSDEF folder. 2. Then, extract the newly downloaded AV-update into that folder. You'll find the replaced files are almost same, but larger now. So now, you are installing with the new virus definitions, by default.

Nothing special to be used. Just the standard MSI switches. Use "/QB" switch on the setup.exe or the MSI inside some folder.

Remote desktop and terminal server (service) should be on. And then use ;Concurrent Sessions /w SP2 for 2 users - one at console, and 1 remote ;[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core] ;"EnableConcurrentSessions"=dword:00000001 Of course, remove the commenting when using, its just commented above so you don't accidentally enable when you cut-and-paste.

Prolly you got used to 60Hz - I won't, cause I love my eyes. Do please have concern about your eyes, because 60 Hz is actually quite strainful for them (ask any doctor). Health-care is a booming industry now, and we wouldn't like to add to their profits, just not right now . A display frequency of 50Hz for a TV is very good - you view it from a distance. A CRT monitor, on the other hand, is stared/drooled-at from very close by! OK, I've gone sufficiently off-topic, out of concern for you, lets get back please.

Nice info. Thanks for sharing it with all.

There's lots of discussion taken place about that. Do as MCT says! As for your first proposal, I'd say remove a few things from your CD to cut-down the size. Then try compressing everything one by one (inc. drivers). Then, if nothing else helps, use winPE to install over the network. interesting option - superbikkel's screenshots (second post there) will hook you, I'm sure - and you'll want to know more about it. You might like to check out the WinPE sub-forums : MSFN -> Unattended Windows Discussion & Support -> Windows PE

Well, this one's been a fairly irritating thing about nV drivers (ForceWare) right since the betas. You know what? nVidia releases a driver, and MS takes it and releases it (within the driver SP2.cab) as driver_version+0.01. So, (most recent example) when nV brought out the detonators 56.72, SP2_rc2 had 56.73. Now, when windows decides on which driver to use, it sees 2 factors - WHQL signing, and version. If a driver is signed, and has a higher version than what it already has in its own install source, that will be used. If it has a higher version, but is unsigned, you need the driver signing off in winnt.sif. In your case, windows thinks it has the newer drivers, and gets an additional reason to beat you with a stick - 62.77 (which is what I think you are really referring to, that version's main advantage over 62.76 is that it is dX9c supportive) is not WHQL signed/approved yet. So don't cast doubts on your ability to have those drivers installed automatically, or the integrity of the drivers - you are doing fine, MS/nV are at fault. Just wait for a signed release (which might come out with a higher release version) - or do what you already are doing (install the newer version post-install) manually.

That would be absolute sacrilege, if such a thing were to be possible in NT4, forget about XPSP2.

That's what I mean to say, too! It look ok if you were an active member on MSFN (or atleast notched up 5 posts), and then felt like advertising your own home-page/forum. But here, you see his first-post itself is self-promotion, and nothing else has he ever posted after that. It simply looks like he registered to "blatant"ly promote himself with the high-volume MSFN boards, and is doing (learning/helping/etc.) nothing else.