submix8c

1) http://www.ehow.com/how_8518467_upgrade-media-player-microsoft-xp.html It's in the Options. Have you "transplanted" this illegally? C:\Documents and Settings\<user-id>\Application Data\Microsoft\Internet Explorer\Quick Launch\<anyprogram>.lnk http://www.xxcopy.com/xxcopy38.htm http://ss64.com/nt/shortcut.html http://ss64.com/vb/shortcut.html Enterprise Deployment info http://social.technet.microsoft.com/Forums/en/w7itpromedia/thread/70179c16-ac44-431e-96b4-d1ee9ce86881 You now have all but #2 (NO WAY on that one). Be happy... Forgot to mention... "Quick Launch" has to be "activated" in the Task Bar. I suppose you want that too...

OUCH!!!! Totally forgot about this!

Agreed! Press "Print" Key, open the Paint program, Past the image, save it, then attach it. PLEASE be aware of the Size, else maybe on Photobucket?

http://translate.google.com/

Not from a Retail, no... But I assure you, the OEM when you buy e.g. Dell, HP, eMachine, etc., and "plug it in" you get the SysPrep stuff AND in the documentation IF it has a Recovery Partition (and most usually do) you WILL be warned to "Create Repair CD's/DVD's" and SOMETIMES you get a "Recovery CD's/DVD".I've argued this before so don't go there... I have a Dell E521 sitting here with Restore DVD's (NOT Recovery DVD's) -AND- it has a Recovery Partition. 1st came PowerQuest Images, then came Ghost images, then came SoftThink images, then came WinRE (also used on XP - see below) WIM images. The latter two appear to be widely used by OEM's for Vista/Win7. http://www.goodells.net/dellrestore/ AND an Acer that I recently "de-trojan'ed" that actually had XP-Home-SP3 WITH a Recovery Partition that had... WIM's! And HP (Win7) uses it too - ALSO gave up on De-Trojan and did... RESTORE from Recovery (complete replacement of running OS). -PRESS A SPECIAL KEY-SEQUENCE AND BOOT TO RECOVERY PARTITION (F11, F10, Alt+F10, etc) - it's either in the MBR and/or in the BIOS. You are TOTALLY misunderstanding... It's an OEM-thing, ok? P.S. Recovery Console not installed on the bad-boy's... a different "beast". PLEASE don't confuse the OP - they ARE NOT "computer literate".

Just past Patch Tuesday. http://xdot.tk/updates.html

HUH??? Do you mean the PANES (left side <-> right side) reverse when F5 is pressed, depending on NTFS-FAT32? Don't work that way here. BTW, "Correcting Sort Order" (to make sort same as 9x) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer] "NoStrCmpLogical"=dword:00000001

Well, to be sure, the "hooks" between the info is there now. I couldn't find it although I was sure it had to be there somewhere. Now YOU da man! (sorry, tomasz86, you have been dethroned. Finder still reigns but - where were you on this earlier? <-rhetorical )

I thought I specifically told you it goes DEEEEEP into the Components. 2)I thought I specifically told you it goes DEEEEEP into the Components.NOW understanding you want to "hack" Home Edition to Pro Edition. I had thought (as everyone else had) by your "specifications" that you wanted the opposite. However, you will NOT get that info here... Repeat... You will NOT get that info here Why? WE (at least MANY of us) believe it's 1) Nearly Impossible 2) Against the EULA and therefore ILLEGAL 3) Not worth the effort - Install Pro instead... re - Developer not-necessarily= Hacker Have a nice day...

EGG-ZACTLY what I was hoping you'd say! "Current User" (HKCU) in the context of the HIVEDEF apparently means "DEFAULT" at "build" time! Don't know about anyone else, but I'd say "Case Closed". OP needs tonly o add appropriate entries. THANK you tomasz86 for the "testing"! Useful! "You da man!" "No, YOU da man!" "No, YOU..."

Fine... Searching TEXT in I386 (possible relevant entries) LAYOUT.INF - productname = "Windows XP Professional" PRODSPEC.INI - ;Note to user: DO NOT ALTER OR DELETE THIS FILE. <--- See that? Most undoubtedly some reason... [Product Specification] Product=Windows XP Professional WINNT32.MSI is OBVIOUSLY "different" (see TackTech link I gave) SETUPREG.HIV is OBVIOUSLY different TXTSETUP.SIF has - "ProductType" value - NOT GOING TO GIVE VALUES [strings] wks_id = "Microsoft Windows XP Professional" <-- Used to fill in BOOT.INI There is JUST TOO MUCH! Find that "warez" program that I will NOT mention to do it. WHAT are you trying to DO? Convert Pro to Home? WON'T HAPPEN! As I said, eve that "hack" for "supposed" "Home VL" is KRAP! If someone else wants to "volunteer" have at it. I got pestered about this and refused (I'll say no more as it's against MSFN rules)... And refuse to answer again...

I am... SOOO confused! You mean that appears DIRECTLY UNDER "HKU"???My Running System: HKCU = HKEY_CURRENT_USER <- Me (Current User) HKU = HKEY_USERS <- Top-Level - Sub-"Folders" only HKU\.DEFAULT <- Contents (?) of "Documents And Settings\DEFAULT\NTUSER.DAT" - The Defaults for any New User HKU\S-1-5-18 <- Local System HKU\S-1-5-19 <- NT Authority Local Service HKU\S-1-5-19_CLASSES <- (empty) HKU\S-1-5-20 <- NT Authority Network Service HKU\S-1-5-20_CLASSES <- (empty) HKU\S-1-5-21(etc) <- Me (Current User - Administrator Account) HKU\S-1-5-21(etc)_CLASSES <-Me (Current User - Administrator Account) http://support.microsoft.com/kb/243330

Sooo... DISKPART "sees" the HDD. Does it "see" the Partition(s)? I assume that since you've done this already that you're "doing it" right. -OR- You didn't need to use DISKPART on the "other" PC's and are NOT "doing it" right?

I didn't say that. I'm fully aware of that (the "slipping" of an SP for EITHER CD was addressed based on that). You obviously (?) mean (1)Installed the CD-XP-SP2 then installed "WindowsXP-KB936929-SP3-x86-ENU.exe" onto the Running System. "Make the files"? You mean SlipStream SP3 onto the SP2 CD-Image via nLite (assuming AT WORK on the x86)? That statement makes no sense... I must "assume" you mean the nLite "run" you did with the LastSession, which MAKES NO SENSE since the nLite "run" (LastSession) says the SOURCE was SP3, and NOT an "untouched" SP2 Source. I beleive you were told that you CANNOT NLITE FROM ANYTHING BUT AN UNTOUCHED (ORIGINAL) -OR- one that was MANUALLY SlipStreamed (on HDD - many references on how-to) and NO OTHER ACTIONS. HUH??? How did you get a WINNT.SIF on it? Was that the one you "created"/slipped using nLite from WORK?I can take that EXACT SAME WINNT.SIF, stick in into I386, burn a BOOTABLE CD/Image, and Install from Boot. The ONLY thing I see different is the quotes (") wrapped around the Key - maybe that's the problem? One for my daughter (she's running it now) x86 - edit - P.S. - same thing for VirtualPC (which is what I use)

DUDE!!!! 1) - I GAVE YOU THAT and ALSO stated what Tripredacus just said. Did you look at the RTM "Differences" list Link I gave? ALSO there are MANY PLACES that it's referenced. a - under the PCHealth "SKU" entry (Professional_32) HKCU\Software\Microsoft\PCHealth\HelpCtr\UserSettings\SKU b - MANY places under "SideBySide\Installations\x86(many)\Codebases\OS" Line#1 = "Microsoft Windows XP" <-HKLM\Microsoft\Windows NT\CurrentVersion\ProductName" Line#2 = "Professional" -OR- "Home" (probably the PCHealth one? but DOUBT IT since it's in the USER hive) Line#3 = "Version 2002" - NO CLUE, dude! (irrelevant?) Line#4 = "Service Pack 3" <-HKLM\Microsoft\Windows NT\CurrentVersion\CSDVersion" -UNKNOWN whether ANY of (-B-) above has ANY effect! I REFUSE to screw up my install to test this for your CHEAT!!! YOU DO IT!!! Try VER and WINVER in a Command Prompt.

??? I think I kind of "implied" that in my post about REG.EXE??? I SPECIFICALLY remember creating a Boot Floppy with it for that exact purpose...Perhaps "Safe Mode" with REGEDIT.EXE -OR- "Safe Mode->Command Prompt"/BootFloppy with REG.EXE (same-o same-o)... Seriously... what am I missing here?

http://www.techtalkz.com/windows-server-2003/41270-unattended-winnt-sif-being-ignored-2k3-x64-cd-install-but-works-2k3-x86-cd.html 1 - DID YOU put the sample in the CORRECT FOLDER (above applies also to XP, BTW) 2 - (I asked this before...) DID YOU BOOT TO THE CREATED CD? (see my POSTS ABOVE!) Do NOT tell me this DOES NOT WORK! I ALSO stated that in order to install via WINNT32.EXE you MUST use the provided parameters (I gave links to the appropriate ones) and (not really sure about this) it MUST BE DONE FROM x64-OS/WinPE (x64 WILL NOT "UPGRADE" FROM x86)! In addition, IF you use VMWARE, then it MUST be run on an x64 OS AND it must be set up AS an x64 Machine! PERIOD! Do I REALLY have to load my Dell up to prove it (currently unhooked and loaded with OEM MCE)?

Please note that the OP wants this for ALL users (AFAICT) during "Unattended" Install. The Registry Entries the OP has listed is for CURRENT User and the OP wants it for ALL Users and WILL NOT WORK one-by-one UNTIL each user is actually DEFINED. That's why I suggested that the change be made to DEFAULT so that WHEN any given User (including the INITIAL Administrator, if kept via nLite, which the OP did NOT say they were using) the changes would be "picked up" at Logon (when the User Profile/Folder) is created. Now... in the HIVEDEF file - how would it be done (entries) for DEFAULT user based on the Reg entries given? (I really don't know myself - I linked to modding a Basic "Default" NTUSER.DAT and possibly "replacing" it during install). The MISUNDERSTANDING the OP has is that HKU is the HIVE needing changed - NOT SO! It's the INDIVIDUAL one(s) BENEATH it which ONLY "HKCU" (under the s-Value for the Given Logon - DO NOT CHANGE THAT ONE) and OR "DEFAULT" (which is NOT what one can ACTUALLY mod - the "HKU\.DEFAULT" one - ref HKU\s-Value=HKCU). It's GOT to be nodded in the NTUSER.DAT of the "Documents and Settings\Default). HTH the confusion.

HOLY CROW! I leave for a while to spar with political opposites (elsewhere) and come back to THIS? As a co-worker once said in a meeting... SHUSH!

AHA!!! The crux of the matter... AutoPatcher anyone?P.M. (post-mortem) - don't make me have to download this NOW before it goes bye-bye.

Might I suggest before anything gets "silly" that the BASIC package be offered "as-is" with BASIC optionals and any ADDITIONAL optional be placed in SEPARATE packages. It's easy enough to "add" (e.g.) IE6 after-the-fact as long as it doesn't BREAK the BASIC's. Sheesh! You could fill a whole CD with "Optional Optionals". This type of thing has occurred before with other "update" packs. (Check all of the other ones and "'order-of-install" etc.)

Off Topic. Yes, XP did. Compaq even had a Recovery Partition for Win9x-series but it didn't create a Recovery CD. You had to purchase them. They got in a LOT of trouble (even with the XP) for not providing. Yes, I have an eMachines Recovery set for an XP on CD (created with that "program"). If they have that Option I highly recommend creating the CD's/DVD's... I see your point about not wanting to "lose" programs installed. Usually folks have the Install Software (maybe CD's) and Keys handy for just such an emergency. The PITA is setting everything back up (options, updates, etc.) after Recovery. They also tend to Back Up all of their Pictures, MP3's, etc. before doing the Recovery and restore afterward. Just saying...

Somewhere (can't remember) I vaguely recollect using REG.EXE (from the Win98 Resource Kit) against the DAT files to "compress". There was some "method" to the madness... something about "creating" a new DAT file from the "exported" REG files? I could have SWORN I had used the method before... (and I could be TOTALLY wrong, so don't be too harsh)

Not necessarily OT... Some manufacturers don't supply them. There would be a "Create Recovery CD/DVD" somewhere in the "Start->Programs" structure, usually an Image Restore created from a Recovery Partition. Also, some mechanism (special Function Key sequence) to Restore the Running OS from the HDD Recovery Partition. AFAIK, eMachines may use either method. HTH

Will test "slip"/Install SP2 shortly... This "problem" makes no sense. You DID slip the x64 SP2 "Full", right? I just don't understand how the WINNT.SIF can be ignored from CD-Boot (it's right there in El-Torito Boot Image->SETUPLDR.BIN).Also please note the other post I made. x64 SP2 is more-or-less equivalent (slightly precedes) to x86 SP3 and coincides with the linked-to MS article.