submix8c

Points - UDC website has all the links to the KB's in question to get the French version (just change the language). No, UDC doesn't download any language files other than English with the stipulation that SOME of them are language-independent.

The (usually lame) Wiki - http://en.wikipedia.org/wiki/Pre-shared_key

I honestly can't say about whether XP can "detect" DDR4. Obvoiusly, your talking about a brand spanky new MoBo, of which XP already has some heartburn with the latest (already out) MoBo's with DDR3/EFI/Chipset/CPU/(etc.). Don't depend on using XP on a TOO new MoBo - stick to the newest that has Drivers for your OS, otherwise double-trouble. Wherever you seen "isn't backwards compatibe", well, that's true. the Slots are entirely different between ALL of the DDRn sticks. You can't stick DDR3 into a DDR2 slot, any more than you can stick SDRAM into a DDR slot (and vice-versa).

Wikipedia is wrong. It should be changed. http://thestarman.pcministry.com/asm/mbr/W7VBR.htm Same goes for a Vista one. As for "second stage", I guess they're talking about the MBR code being the first stage? The last link is most accurate. See Starman link. Someone should clean up that "disinformation". edit - DOH! Also see jaclaz' post below.

XP x64 EOL isn't the same as XP 32-bit. http://support.microsoft.com/lifecycle/search/default.aspx?alpha=windows+xp Support doesn't end for another year for x64 (AFAIK). Same for Server 2003. As for "DDR4", that would probably be irrelevant . What you'll run into is not finding drivers for the Chipset and associated Hardware.

Hmmm... this may or may not work to isolate what it is. I say that only because I'm not sure how "up to date" it may be for your hardware. Chances are, it will work fine. http://www.majorgeeks.com/files/details/everest_free_edition.html

DOS 1.1? DOS 2.0? Wouldn't you have to do massive mods to it? AFAICR, it has some hard-coded HDD for the "ancient" disk access, correct? (I had an IBM 5150 at one time.) Also, limited the FDD size. Guessing that at least the code could be used to get an idea of how MS envisioned the OS. Edit - Ehhh, downloaded and "looked" at it.

VST Plug-Ins - http://bedroomproducersblog.com/2011/03/03/bpb-freeware-studio-best-free-parametric-equalizer-vst-plugins/ You're wanting for "any media player". I'm not really sure that's possible? Again, probably depends on the Hardware and the Player in question.

Not really sure if this is may fit the bill. What your asking for is a simple intermediary (at final output stage) Parametric EQ and it -may- depend on your particular hardware and the "player" software you use. http://audacity.sourceforge.net/about/features edit - there's this (with stipulations) - http://sourceforge.net/projects/equalizerapo/ Try this - google "parametric equalizer" softwareSorry, can't help more than that. Depends on whether you want to fork over $ or want "free" and (maybe) the hardware (etc.).HTH

+1 And if the poster is REALLY slick they could prepare some sort of recovery scenario. Bear in mind (if said Dells are set up the way I believe them to be) they already have the Recovery Partition setup on them which -may- have to be "cleaned" (ref. Goodells website). That is -if- the are indeed "identical".

Mmmm - maybe not be able to use it YOURSELF and "refurbish". From the License The best I can suggest is that you just "refurbish" all of them with that source (legality is on your/your comapny shoulders). Provide the recipients with clear instructions on what to get from where with a "how to" and allow them to make their own if they so desire. Have you considered WPI (Windows Post-Install Wizard) for the Updates? You can always get all the Updates and distribute that as an "extra" CD. edit (I'm going to choke myself for suggesting this) - You could also use Autopatcher and put on a separate CD. Bear in mind, the contents may/may not be accurate (like -X- list is) but you could always "clean" the superfluous stuff out, if you're slick enough to understand and us -X- list to do it with. Note that -X- is VERY good (IMHO) at ensuring superseded stuff is removed and -some- items may not be in Autopatcher. I leave the methods of Ethical Distribution to you.

If the "pk" is from a single COA, then yes. Each Dell PC should already have that COA for that OS on it. As I stated, there is an INTERNAL key. Generally, this should NOT be used if "distributing" to "friends". In additions, what do you MEAN by that? MSFN'ers have suggested "borrowing" a friends CD before, but (AFAICR) never has anyone here suggested "warezing" it out. You're treading on thin ice... Now... what do you mean "hypothetical list"? Either you can DIR it or not DIR it. And please don't PM me - here or nowhere. It's simply for confirmation of "clean source" (i.e. what is "dross/modified" and what is not). Thank you. edit - (sigh...) I believe I may have that CD sitting right here (Dell XP Pro SP3). Yes, you may have a problem if it's the same as mine. It's "altered" (betting yours is too). -IF- so -AND- you were to keep yourself -LEGAL-, you will still have to "de-alter" it to make it "clean".

(jeez - banging head on desk...) Can you PLEASE specify WHICH MS VM? There are SEVERAL variations! Give the LINK to the one you installed and THEN we may help you. PLEASE answer just a FEW basic questions? Reading, then seeing questions, and giving NO answers (what you are doing) is NOT going to allow any of us to help you AT ALL!

Like Ponch said - UNLESS those are your Personal Computers, you may NOT use nLite. Yes, there is a EULA and you agreed to it when you installed. Now, -assuming- that those are your PC's, your Dell Restore CD does, in all probability, have a WINNT.SIF file already there and contains the "generic OEM key" which doesn't require Activation. I'm -not- really sure if nLite handles that as I -always- ensure I have a -totally clean- source (i.e. NO Winnt.SIF at start of nLite). -IF- you input the Key when you used nLite then... It will -NOT ask for it (it's been embedded into WINNT.SIF). Now... you are using a DELL Restore CD, of which may or may not be totally -clean-. This subject has been visited many times that OEM (e.g. Dell, HP, etc) Recover CD's have a nasty habit of "altering" the Source to include "other" software -or- insert "additional fixes". Could you attach a zipped Directory Listing to confirm that it will -work- with nLite? I'm thinking it won't since it already has SP3. -IF- it had SP2 and you slipped SP3+Updates then the SP3 Integration would have "wiped" the "Dell junk" out and ths "superfluous" would have been ignored. Houston, you -may- have a problem.

Thanx, jaclaz for a reminder/link. Gatecrash away! @LostInSpace2012 - Did you miss the post I made before yours? Using the Boot Disk (It's called an Emergency Boot Disk aka EBD) I was fully able to both FDISK and FORMAT. The PROBLEM appeared to make a SYS'ed one. So, your statement is, errr, erroneous. Yes, I have Windows ME and used it "for a while". My main heartburn with it was driver availability - you sometimes had to "argue" with Win98 ones to work.

This I was not aware of - http://support.microsoft.com/kb/254959/EN-US FORMAT.COM is in EBD.CAB, so... ..and SYS.COM is as well, so... Booting to the EBD with a "new" HDD, I 1 - use FDISK and reboot (naturally) 2 - In the D-Drive (whichever is the RamDisk) is FORMAT and SYS 2a - Format C: - fine 2b - SYS is giving me fits. IO.SYS is Hidden/System and is "not found" somehow. ATTRIB will not reset it. DISKCOPY.EXE has always been an independent program. Not sure what you mean by "go into DOS" (you mean Command Prompt?). I've never been aware of it doing anything other than "cloning" Floppy->Floppy. http://www.computerhope.com/diskcopy.htm So, until I have time to dink with it, I'll have to revistit this topic. l8tr...

??? That's what has been said. I only point out that since the OP has an UPGRADE (Retail, obviously) that simple slipping of the SP3+Fixes should be all that's needed since the Key will -only- work with Upgrade (with valid old OS media). Further, changing a RETAIL Upgrade to FPP will not work with that key. The problem is that the OP has "somehow" failed in installing on an unnamed VM and assuming it has to do with SATA Drivers, etc. This (slipstreaming) should work in a VM but using AHCI on the REAL Hardware would need the additional step of repeating the nLite and integrating the TextMode drivers. And yes, the OP apparently is not answering questions, just posing more and/or doing "other" things rather than following simple instructions.

Having a Dell Reinstall Disk myself (MCE) I would say you -could- get the internal key with a keyfinder and use it instead (preactivation) and slipping post-SP3 updates -shouldn't- be a problem.

"version.data" may be unrelated to the XP and -may- be related to the Third Part Add-Ons (you never said what) maybe WinRAR? Curiosity - was this message issued DURING Text Mode? You were unclear on that. The reason I said it -may- be related to the OEM XP is becuase I believe I -may- have a Compaq (?) CD somewhere that has that file on it but don't remember that it was actually referenced or a clean install. WHAT is the brand of Notebook (you also never said, any more than providing a Directory Listing of the CD)? You might try inspected the XP CD for that file and if not there then the individual Add-Ons (before you created them). Doesn't make sense... edit - AHHH! "version.dat" -could- be on a Recovery CD Set (additional software?). Which could explain a lot. That "Directory Listing" of your CD would sure help isolate errors. After all, no "secret info" would be revealed.

??? WinME "System Disk"??? You're referring to the EBD then. I see no problems with FDISK and FORMAT unless you're talking about HDD sizes. As for Floppies, really? A problem using COMMAND.COM+FORMAT? (SMH...) What kind of -general foppy disk "stuff"- would you mean? Could you elaborate by listing the missing/failing features?

This is what you stated in Post#1 JFYI, "version.dat" sounds a lot like an OEM CD, supplied by the OEM Manufacturer. The Volume Label of your CD should (generally) be one of the following: VRMHFPP = Full VRMHCCP = Upgrade VRMHOEM = System Builder OEM ...with a "_xx" of something appended indicating the Language (e.g. "_EN"). Going back to my Post #13, you responded with at Post#15 (partial quote). Trust me, even though you SAY it's "Retail", how do you know? Any Volume Label OTHER than above is an OEM "altered" CD (see next link for COA's, which you said you had). I can't seem to find the link to the CD Image, but here is the COA images (archived) - http://web.archive.org/web/20081015211434/http://www.microsoft.com/resources/howtotell/en/coa.mspx Note that this info has been "scrubbed" from the current MS site (or at least I can't find it). All that shows is Windows 8, so I got the Archive link above... Please note that IF that file is part of an OEM-Altered Source CD, then theoretically it shouldn't matter. Can you provide a Directory Listing of the CD or at least confirm your COA? Something doesn't sound right (you're confused and are confusing us).

Sadly, the path to making an Upgrade into a Full wouldn't really make any difference unless you have a Full key. An Upgrade key fully well works on a Full cd (AFAICR) but not vice-versa. I "obtained" and Upgrade key at one time and used it with the "borrowed" Full version (from a friend). Both keys worked. However, I did NOT "change" anything (certain file/files) to "create" an Upgrade version. The tacktech links in the first link jaclaz gave (scroll down in that thread) will show you the difference between Upgrade and OEM. OEM's (e.g. Dell/HP Specific) has (-may- have) other "certain files" that are even more different and is irrelevant in this case as they are for using the "internal" (OEM-Specific) Key along with SLP, although the Key on the PC will work with it (it's your personal OEM Key). A "hint" is here - http://wiki.lunarsoft.net/wiki/Product_IDs The "ExtraData" part is irrelevant in your case, as it's the same (should be) between them for SP2 Source. Basically, what I'm saying is, even if you "changed" it into Full, you STILL only have an Upgrade Key which will determine the "type" (Upgrade, not Full/OEM) of Install. Therefore that "change" is totally irrelevant. The "basic" problem still lies with Slipstreaming whatever is necessary and installing in a VM and the TRYING on the real PC. Side note - ALL files on your XP SP2 CD should be dated 08/04/2004 (Aug 4, 2004) - if not, you have an "altered" one somehow. HTH

Both of the XP Drivers are at that link (see this link to topic and my response). You're welcome, LeakHunter... http://www.msfn.org/board/topic/124459-ich8m-driver-for-windows-2000/

Well, then a suggestion - tie the three together with cross-links in the other two? Intel->nVidia->AMD nVidia->Intel->AMD (AMD not yours, so...) With a short explanation to avoid confusion as to which Drivers are for which Base Controllers (apparently some folks don't realize). You HAVE loaded this Topic with useful Drivers/Mods for AMD...

@Fernando 1 - why is this Topic not Stickified? The Intel and nVidia ones are.