neophyte

I had been privately discussing how to install WiMP 9.0 through the SVCPACK.INF method with AaronXP, and he mentioned that it would give an error regarding the System Restore service. He mentioned something about /DisallowSystemRestore as a switch for the installer program, but it didn't work. Is there any possible way to tell WiMP 9.0 to not set a system restore point?

Doesn't the $OEM$ folder get placed in the root of the distribution source when using a CD? I've tried it as a sub folder of i386, but it just doesn't work.

Oh boo. Stupid me misread the guide. Move on. Nothing to see here. *neophyte slaps head for being blind

If you wish to use $OEM$\Textmode, you must use this: So yes, you can use the Textmode directory

If you've copied wpa.dbl after activation, and restore it to the same computer after a fresh install, and there has had no hardware changes, the same CD key used, etc, will work. This has been around since (as far as I can remember) RC1.

Yes, you can delete the DriverSigningPolicy line, as the drivers are WHQL certified. However, you should leave it there if you have other drivers that aren't signed.

You're actually incorrect with your first statement. Windows XP Unattended install allows you to complete the first part of the text installer manually. [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" By using that, you are telling it to not auto-partition, thus, you can choose which disk to install to (as well as muck around with the partitions).

Wouldn't it just be simpler to copy the drivers for the chipset that you need? The intel installer is intelligent enough to simply extract the drivers for the chipset that you are running on (for instance, on my machine, it only fully extracted all the ICH5 drivers, as my chipset is the ICH5R). Then simply copy the XP folder into the appropriate folder, and rename it.

Reading the updated hotfix guide left me pondering, is it possible to install Windows Media Player 9.0 and Windows Messenger 5.0 through the Update Rollup method as shown here? Cheers.

Whilst you've been fairly clear on what files point to what parts of the registry etc, you haven't been as clear on just exactly what to edit/how to edit. For example, searching through the relevant hive file for the messenger service yielded no results, and was in fact, quite confusing. For the time being, I'll be sticking to my reg files. Unless of course, we can just simply append (to the bottom) the appropriate registry entries (in the correct manner) to the appropriate files, and leave it at that.

I know this is an old thread, but it came up whilst I was searching these forums, and I noticed a mistake in the original thread. Folders located within $OEM$\$1\ are not copied over when the Start Menu is being configured, but rather, are copied during the initial text based part of the XP installation process (right after all the files are copied from the i386 directory as a matter of fact). Sit down and watch it

General License Grant to Install and Use Software Product. You may install and use one copy of the Software Product on a single computer, device, workstation, terminal, or other digital electronic or analog device ("Device"). You may make a second copy of the Software Product and install it on a portable Device for the exclusive use of the person who is the primary user of the first copy of the Software Product. A license for the Software Product may not be shared. An excerpt from the Office XP Retail EULA agreement.

I personally would like to have a downloadable ISO which has all the appropriate hotpatches ready for slipstreaming into an XP cd, with all the appropriate files (such as dosnet.inf or whatever the heck it is). Frankly, the MS TechNet guide is to mind boggling.

I personally want a pure slipstreamed CD. However, I also think its high time Microsoft developed a hotfix installer that catered for slipstreaming hotfixes into the CD, and creating appropriate markers so that Windows Update would recognize the appropriate updates. This would be a universal installer, that would work for Windows and Internet Explorer critical updates, as well as for programs such as Media Player, Direct X, and Messenger.

If thats the case, my apologies.

As far as I can tell, these forums condone illegal activity. I guess posting that link directly into the forums wasn't such a good idea, and should have been relegated to the Private Message feature of this board. While people can use it on legitimate copies of software, it is still illegal (as far as I know, reverse engineering of MS products still isn't allowed in any MS eula's I'm aware of). Please remove it yourself, or perhaps a mod will.

I actually am not a "newbie" (simply because I've only joined here recently, and happen to use "neophyte" as my nick doesn't make me a computer n00b). I have been around computers for longer than some people here have been breathing, and know my way around various platforms. In fact, I've been using Windows XP since before some people knew it existed. If your post wasn't aimed at me, then ignore the above text.

From what I can gather, the safest method is to stick with the WHQL certified drivers if you wish to use the PnPOEMDrivers routine. The simple reason is, they are the WHQL certified drivers (remember, Windows XP does prefer these drivers). If you wish to use other drivers that aren't WHQL certified, then the $oem$\$1\install\ route is far better. I personally use the $OEM$\$1\install\ route, as I know what's going on, and can easily fix it.

Handy hint, use a CDRW for testing these CD's before you commit to a CDR.

Thanks for clarifying the Intel64Bit version thing up.

This is a nasty hack, but why not make a registry file and put it in your startup directory? Then it won't matter. *Edit* Don't forget to use /S with the regedit command to silently merge it. Be warned, it is a very nasty fix.

Office XP is easily fixed as well. Look for the file MSO.dll and make a backup of that (its in the C:\Program Files\Common Files\Microsoft Shared\ folder in one of the office folders). I've not heard of a product key being blacklisted either. If you have proof of purchase, and are willing to show MS it, there is nothing to be afraid of. People are making a bigger fuss out of something that isn't really that much of an issue.

Windows XP Corporate != 64Bit Windows XP Windows XP Corporate is the common term for the VLE of Windows XP. Windows XP currently only has one 64Bit edition (for Intel 64Bit cpu's), and I don't think that is even out for RTM yet. AMD64 Beta's of XP are out and about.

A license applies to you whether you read it or not. However, there is a lot of controversy about licenses that are only able to be read by opening the shrinkwrap (called shrinklicensed) or by clicking (clicklicense) a button. On one hand, they are applicable, as they do dictate the terms of the copyright "license", yet on the other, they could be considered invalid, as they were not seen at time of purchase. However, we shall ignore those petty arguments, and assume that the license is applicable. If you've read it, or haven't, you are still bound by the copyright license, and "required" to follow it. Whether you do is up to you, but if caught, you can be prosecuted (as according to the law).

Oooer. Maybe now we can properly slipstream it. *Edit* Oh boo. You can't.