prathapml

Basically, the reboot is a Windows Installer property, not a switch. So, wherever you have an MSI setup, the correct way to reject a reboot is REBOOT=Suppress (note that there was no "/" preceding it). Moreover, some installers want the property to be all capitals, which is why I have it that way above ("REBOOT" and not "Reboot"). Also, some I've seen some setups needing REBOOT=ReallySuppress (that switch to reject a reboot, instead of the one to simply "suppress" above)

Here's how to pre-set the default wallpaper: this thread

Hiya both of you! Welcome to the MSFN forums.

Use WinPE, or make a bartPE from XP install source - for more full-featured access to the network.

I prefer XHTML any day. If you are anyway intent on using server side scripts to serve up data from a DB, I'd say go for ASP.

That's right - and you can also search google for "resource editor" to turn up more similar programs.

diskpart scripts are run from a winpe environment, normally. Here you go for the nvidia drivers issue: 1. nv1 2. nv2 That's two of 'em. Hoping this helps....

Maybe you filled it up with too many events listed. (just kidding, of course)

Hey all of ya there..... Nice discussion you have going here, but please don't start taking comments personally and make this topic into an argument. And yes, an amazing thing was the release of a patch within a week: you can find it here (the formatting is such that this page isn't able to take up the link) So is it time now, to start a "Hotfixes for Windows XP SP2" thread yet?

<never mind> Well.... well, turbomcp above has said most of what I was about to. In the job-market, your certification of MCSE 2003 does not count nearly as much as the effort that you're understood to have put-in towards getting it, and the experience that you're likely to have after that course. So, its really an indirectly valued cert. Experience always counts more, people pair it with a certification to really prove that..... That's all I can say, and good luck to you.

I don't exactly remember if it was related to the user-creation page, but there was a switch or a setting in the INI, which did it. EDIT: Ran a "/?" on the exe, and saw the "/UseCurrent" switch. I suppose that is the one to directly go to software installs.

why not just follow what flyakite's multi-boot DVD guide says? He says: NOTE: I modified the quote slightly to make the instructions more generic.So that is all there really is - in other words, don't try manually editing at all - simply give the task to the "Find and Replace" function.

Did you rename it (the new file which you copied) to ntoskrnl.exe ? Moreover, replacing by hand can be dangerous. StyleXP will keep your current kernel and add a BMP of your choice to the boot-screen - try it. Or try bootskin by StarDock.

You can continue using commands for changing passwords, and deleting users, but the best way to create administrative users on windows XP setup is this one over here - oobeinfo.ini

Hmm..... when you know what you are doing, and there's no chance of you needing to Restore, yes - remove SR. Also, it sometimes comes in the way when you are trying to replace protected DLLs in the system directories.

Thanks for the tip edbro - that looks like a better thing to do, than a registry tweak that applies to "Users" individually. Will check it out, and post back on how it goes.

It is OK, office2k3 install doesn't over-write the values. That's the place to put it.

There won't be development anymore, of the DOS version - so it will fall behind, in terms of hardware recognition and chipset compatibility. The windows version is well, and good.

The residual incompatibilities and flaws are most probably those that MS did not or could not do anything about. The need to prevent a re-release was what was served, right when MS had programs of betas and RCs for testing by the public in the real world conditions.

Not when it is hard-earned, and you are going to pay for licenses of what you use!

The CD you have got is not exactly a legit one - the shop has given you a pirated CD. Use only licensed versions of software, to prevent problems like this. Or, ask the shop to give you a new SP2-compatible key.

For your second question, nothing can be done. One option you can try is using WinPE, but that is *EXTREMELY* painful the first time - not worth the effort for you as of now. For your first question, please search before asking anything - there's right now 3 threads running with the EXACT SAME issue - we'd rather not repeat the same thing for the fourth time. FYI, it is not difficult at all, it has been solved.

There's no need to ignore driver signing - forceware 61.76 is WHQL'ed, and installs perfectly fine for me. The one with SP2 is v56.73. So, if you have a signed (also called WHQL) driver of a version higher than this, it installs fine with no problem. Try checking if your OEMpnpDriversPath is properly listing the path to the folder that contains the nVidia-gfx INF files.

Apply it through cmdlines - that will make it applicable to all new users created.

What key are you talking about? A registry key, or a product key, or what? And at what stage of usage? If this is related to being able to use WXP without a proper license for it, be aware that this topic will be closed.