submix8c

Not sure about XP-Mode on Win-7 - BUT... Using VPC2007 on an XP/2K3 Host and NOT using Bridge (it allows for giving a SEPARATE IP directly to the Host NIC) AND installing VPC Add-On (not sure if there's something like that for Win7 XP-Mode) AND Directly Sharing the Folders (NOT via "Shared Folders") it runs just fine! Notice that "Shared Folders" is DEFINITELY slower (goes through an interface) as is Bridges (goes through an interface). I stopped using Bridges and "Shared Folders" a loooong time ago...

Allow me to help you create a Clean XP Home SP3 CD (without Dell stuff and Older Drivers).1 - Make a Folder (any name) on your HDD 2 - Sort the CD Contents by Date and copy ONLY those Files NOT dated (MM-DD-YYYY) 08-04-2004 3 - Create a NOTMS.CMD file (using Notepad) as follows: dir "x:\Folder\*.*" /OD > NOTMS.TXT Where "x:\" is the HDD and "folder" is the name of the folder you created. Save using "Save As" and "All Files" with the name given in your "My Documents" folder. 4 - Open "My Documnts" folder and double-click on the "NOTMS.CMD" 5 - Compress/ZIP the resulting "NOTMS.TXT" and upload it here (it will be very small). The point of this is to distinguish WHICH files you DO need (by removing any "extra" that will be in the list) to create a Clean XP Home SP3 CD as a running starting point without the additional (and unnecessary) Files/Folders. Note that the "NOTMS.TXT" does NOT reveal any "secret" or Proprietary information. Your option as to doing it or not, but I guarantee that you have unnecessary "junk" on your newly created CD. I've already prepared the procedure. I just need the List...

Yes... it's called "OEMSETUP.EXE"... An OEM "bootable" CD has the necessary Boot Image embedded in the CD... It ONLY recognizes IDE (PATA, with a size limitation), and NOT SATA.

OK... let's get this straight... Your "built" in VisualStudio "SETUP.EXE" is POINTING AT THE WRONG PLACE (folder) !!! Got it? It's the SETUP.EXE!!! Please NOTICE that "Documents and Settings" are in an ENTIRELY DIFFERENT PLACE between XP and Win7!!! OK???Microsoft USUALLY creates a SFX package that GENERATES a COMMON FOLDER NAME in the ROOT directory of the "Largest Free Space HDD" BEFORE the "Setup" program is executed and SETUP uses THAT folder name, UNLIKE 7ZIP!!! Either CHANGE THE SETUP.EXE program -OR- CHANGE THE CONFIG.TXT to create a SPECIFIC folder in the ROOT and Run from THERE! Did you even READ the DETAILS on parameters in the LINKS given? GO DO SOME READING and TRY it.... DUDE!!! edit - and the suggestion of using a CMD (EXAMPLE GIVEN) was to "beat" it! Learn a little CMD Scripting as well... edit2 - a little info on Folder Names / Junction Points

Did you open the VPN Ports on the Router (Port Forwarding)? The same applies for a Web Server (forward Ports 21/80) through a Router. The Router is apparently NOT forwarding the Requests. Note also that a Router serves as an INDEPENDENT "firewall" and the OS will ALSO have a "firewall" that will ALSO have to have the ports "opened".

Heh!!! Get some rest, -X-, you're slipping! The code change for the newer version is the next post below that one. The subsequent post is to "correct" the folder-name problem. Just never re-uploaded the "fixed" CMD file (assuming the changes would be incorporated) - been busy with daughter's PC (cloning HDD's etc).

Hmmm... I just realized something. You are using a Dell XP Home OEM w/SP2. I have a Dell XP Pro w/SP3. There is (or may be) an "$OEM$" folder on it in the ROOT as well as a preexisting "WINNT.SIF" in the "I386" folder. Also, there MAY be some added/changed files in the "I386" folder (in my case for SATA drivers among other items). This MIGHT cause you some problems.

OK... let's clarify some things... Mobo's SOMETIMES require the RAM Speed to match the CPU FSB speeds. The one I noted above was due to the Processor FSB speed. Yes, it worked with faster RAM AFTER the RAM Speed was reduced to match. It wasn't the mismatch of RAM, it was what the FSB speed required. @pointertovoid - check that CPU speed - bet it's a 333... Put a 400 CPU in it and watch it work with DDR400!

Well, to be fair, the (fairly) new Lenovo Windows 7 AMD x64 Desktops are pretty awesome. Cousin bought one for his daughter last year and it rocks!

Explorer->Tools->Folder Options->File Types Find the "bad ones", click once on it/them, click Advanced->Change Icon For "TXT" the Standard Icon is in "C:\WINDOWS\system32\shell32.dll" For "AVI" it's "C:\Program Files\Windows Media Player\wmplayer.exe" For that "AVS" it could very well be inside the Program in question. IF "AVS" isn't there, I couldn't tell you... that program probably should have been Installed to "create" that type. You "copied" the folders and expected the Registry to be updated. I'm really unsure if there are actually other files necessary.

BUT... it's in the OS "WINDOWS\SYSTEM32" folder (W32TM.EXE). Put it and all dependencies in your PE Build. Haven't tried it (this), but I have inserted EXPLORER in it before (and dependencies). Use Dependency Walker to find all dependent models. Put all of them (if they are not there) in SYSTEM32 of the PE. Should work...

@-X- Not sure if this would "fix" it... 1 - Download this instead (it's GNU Unix Port to Windows of "split.exe" so it's distributable). Put in the folder. 2 - Remove these PARTCOPY references :: KEEP THIS ZIP FILE!!! MAY BE HARD TO GET AGAIN!!! :: if exist pcopy02.zip del pcopy02.zip if exist partcopy.exe del partcopy.exe if exist pcopy02.zip goto GOTSPLIT ECHO Downloading PARTCOPY from Web Archive... :: --- UNDEPENDABLE! :: wget -nc "http://web.archive.org/web/20010116021600/http://users.erols.com/johnfine/pcopy02.zip" :: --- Use this instead... wget -nc "http://www.brokenthorn.com/Resources/Programs/pcopy02.zip" :: --- OR this instead... :: wget -nc "http://geezer.osdevbrasil.net/johnfine/pcopy02.zip" :GOTSPLIT 7za.exe e "%~dp0pcopy02.zip" -o"%~dp0" partcopy.exe -y3 - Replace PARTCOPY code :: NOTE! This MUST use 8.3... I DID NOT prefix filenames with "%~dp0"... partcopy WUAEXE.EXE 0 8A00 WUSFX.SFX :: The Install is no longer needed... del "%~dp0WUAEXE.EXE"with SPLIT code :: Original Hex-8A00=Dec-35328 split -b 35328 wuaexe.exe wuaexe :: output: wuaexeaa wuaexeab etc... ren wuaexeaa wusfx.sfx del wuaexe*.*"SPLIT -HELP" displays syntax. edit - and BETTING that using the "%~dp0" code would work...

Are you telling that it is not possible to verify the correct drivers installation with any virtual machine? Really? I guess because drivers integration is a very very easy to success process in nlite; maybe is this the reason?Anyway I verified in NLDRV folder there're all the subfolders and files drivers-named like For last question I'd want to ask if there're critical/favourite/interesting tests to carry on within the virtual machine to ensure the nlited windows copy works properly and gets no bad surprises for the real one. how do you test it? Explanation - VM's create/utilize "fake computers" of which are NOT the same hardware as the "real computer".For "fake computer" (in VM eg. Virtual PC or VirtualBox or ANY OTHER TYPE SOFTWARE) you need to ADDITIONALLY add Drivers for THAT VM'S "FAKE HARDWARE"! The REAL Drivers will NOT be used in a VM/VPC and will NOT SHOW IN DEVICE MANAGER (they don't exist)!!!! The REAL drivers SHOULD (mind you SHOULD if CORRECT ONES for REAL COMPUTER) be used AND the Hardwre WILL BE IN DEVICE MANAGER! Clear explanation?

Maybe -X- does, I don't I use MS' VPC2007 (I said that). Again, your Integrated Drivers will ONLY install if the Hardware is There/Defined (else they are ignored). Alternatively, go the the Website I gave for VMware Player "Documentation" and Get-Those-Drivers and integrate them ADDITIONALLY (they interface to your REAL HOST OS Hardware+Drivers). Additionally, you can ONLY install an X64 system on X64 Hardware REGARDLESS of whether you "define" the Machine as X64 (unless VMWare "emulates" one). VPC2007 does NOT do X64 Machine at all! My CD's install XP 32-bit just fine in VPC2007... There is absolutely NO reason that XP 32-bit will be "not able to install"... you MUST be doing something wrong!!!edit - OHHHH! Sorry, you are referring to being unable to install VMWare Player on your Host!!! Here are the PDF docs. It SHOULD install... Err-maybe not (see the "Getting Started With" PDF). Your Dimension 4600 is 32-bit only... It APPEARS that v2.5 will install/run... v2.5.5 and drivers (documents for v2.5 in above link).

BWAHAHAH!!! McRip was not for them... almost sorry I gave that post link. I had found another place that did very similar. Here is an example CMD. @echo off pkgmgr /ip /m:WUClient-SelfUpdate-ActiveX-x64.cab /quiet pkgmgr /ip /m:WUClient-SelfUpdate-Aux-TopLevel-x64.cab /quiet pkgmgr /ip /m:WUClient-SelfUpdate-Core-TopLevel-x64.cab /quiet EXITThese 3 files are NOT for XP/2K3/(maybe 2K) and the Installer will detect that. Apparently, the CMD is to "insert" it into the Install (?) or maybe "after" install (as one of the post-install scripts?). See this. So, this is semi-irrelevant to the Topic but the Files (these are the 3 cabs I had initiall had in question - thx, ricktendo64) are "necessary" to make a Complete Package usable on all versions XP(2k?)->Win7. Will download samples from ricktendo64's newer packages and inspect them. You will have the option of using This Built Package (specifically for -X-' methods) or the Pre-Built Packages by ricktendo64. If I have time, I will investigate the "new links" given (note that the WU link remains but redirects to MU). Side note... Just went to MU/WU (already had MU installed) on 2K3 and it offered a DIFFERENT "?99999" MU-appendage that is STILL v257! (?1340464593891) One might ask - WHY is that appendage (redirect) different TODAY (other link was running XP)??? Is it "dependent" on the OS? (BTW, SAME CAB!) Addendum Microsoft Update Catalog v7.4.7057.249.- https://catalog.update.microsoft.com/v7/site/ClientControl/en/x86/MUCatalogWebControl.CabDoesn't appear to need the "HTTPS" where it was offered. Please note that I did NOT have the latest MU/WU installed on this setup. Will check on the one that does... edit - it APPEARS that you have to have Temp IE files "deleted" to cajole MU/WU to "update". I had cleared before shutdown yesterday and got "offered" today BUT when going again - it does NOT offer. Yes, folks, it appears to be RANDOM!!!

Let's simplify - If you ever used XP, the differences between OEM and Retail and Upgrade are... Retail and Upgrade have a "Retail/Upgrade" key associated with the CD you purchased. You must Phone In for product activation. For OEM, there is a SLP key internally used with a special set of OEM-Specific files that when used causes Pre-Activation and an External (COA sticker) that you CAN use but it reverts to Phone In (as if you purchased an OEM-Generic files CD package). IF you use the COA key and NOT use the Internal Key PLUS the OEM-Specific files, you will WIPE access to the Internal Keys, hence the reason to FIRST get the INTERNAL key and the OEM-Specific files FIRST!!! The concept is called SLP. The same concept is applied to Vista/2k8/Win7 except with a different OEM-Specific File(s) (uses NOT BIOS SLP but SLIC). All other answers to the OP have been given in preceding posts with appropriate links.

BWAHAHAHAH!!!! You manually slipstream'd SP3 onto a pre-SP3 XP, right? Wonder how many other duplicates you have (compressed vs uncompressed)? nLite when SLIPSTREAMING A SERVICE PACK ONLY would have "cleaned up" for you... edit - or... maybe not. I will say that XP SP2 is 5.1.2600.2180. Better check your SOURCE!!! Something is not right... edit2 - see this as well - TWO of you with same problem? http://www.msfn.org/board/index.php?showtopic=156382&view=getnewpost I'm now bowing out... -X- this is your baby from now on...

Revision as follows - Get the CMD above and change wget -nc http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x86/Other/wuweb.cabto wget -nc http://www.update.microsoft.com/microsoftupdate/v6/v5controls/en/x86/client/wuweb_site.cab?1340383010227 ren "%~dp0wuweb_site.cab@1340383010227" wuweb.cabNotice the Rename? Odd how the filename was created, BUT that's how it works... Will update later (maybe here after removing older download). "Gots da-kidds" pestering... Played heck digging into this. And thx, dencorso, for the "hints" - that's what prompted the "experiment". Reminder - WU is not, repeat NOT the same as MU and MU is not part of this. I have absolutely no clue as to how to create a package for MU. For the purpose of Windows-only "-X-" packages it is irrelevant since it's for "other than Windows Updates" (e.g. Office, etc.)... OK, folks, I'm not sure we can get any better/newer than this. 5eraph or ricktendo64 can chime in anytime for any further info on MU or errors (or even hints on the v257 thing...). Happy WU-ing!!!

Hate to burst your bubble - but WU is Windows Update (the "built" files) and MU is Microsoft Update (not part of the "Windows Update Agent"). MU only happens when you "Get Microsoft Update Today!". I had previously done that and had "turned it off" (Custom settings in MU to use only WU) after updating with the New Package (7.6.7600.256). Notice that it (AFAIK) "uninstalled/removed" "Windows\Downloaded Program Files\MUWebControl Class". Really unsure if that was exactly what happened - I fiddled so much... Then I "Uninstalled" the (only and can't remember which one) the Class from "Downloaded" folder. I subsequently RENAMED WUWEB.DLL and got the Newer MUWEB stuff. However, I could NOT "Get MU" (IE CLAIMED the ActiveX was "missing"). I then COPIED MUWEB.DLL from 5eraph's links to MUWEB.CAB/DLL (from another thread? can't remember) v7.6.7600.256. I could NOW "Get MU" and the results are...The "Windows\Downloaded Program Files" now contains - WUWebControl Class - WUWEB.DLL v7.6.7600.257 MUWebControl Class - MUWEB.DLL v7.6.7600.257 <-now again active in IE The Download Address (in IE TempFiles) has an entirely different ?9999-series than the prior version. Very confusing what I did and not sure I can replicate. Put this in your Web Browser - hXXp://www.update.microsoft.com/microsoftupdate/v6/v5controls/en/x86/client Add this to the end - muweb_site.cab?1340383010227 It's v257 of MUWEB.CAB (with INF and CAT). I'm willing to bet that if you "Remove" "MUWebControl Class" (maybe use the Custom option to "Use only WU" in The Update Website screen?) then go BACK in (since you now have MUWEB.DLL v257) and go BACK to Windows Update, request "Get MS Update" that you will get a brand spanky new WUWEB.DLL "Dowloaded"/installed.

Back to KB949104... How odd! It implies that if you opt into Microsoft Update (the MUWEB.DLL from MUWEB_SITE.CAB) as opposed to Windows Update (the "normal" path that we've been discussing) that you should get it if you have AU turned on (see my SUS vs WSUS link). Not sure I want to "flood" my VPC test bed with Updates...

Gigabyte using DDR - Insert 400 - set in BIOS to 333 - save - shut down <--as Tripredacus said (BIOS support) Insert 333 - both running at 333 If put both in before BIOS SET, fails (tries to use 400)... (for said MoBo) Point of note - I believe the CPU FSB speed has/had something to do with "default" DDR speeds... (can't remember) JFYI/HTH

? Isn't there a different one for OEM's? If it's an OEM install, you want a different file and the actual internal key, in which cas "backing up the tokens" is irrelevant... (that's as far as I go with that...)

Well, in THAT case, you may want to DIRECTLY integrate SP2 into EACH image separately first (you can use nLite for that but JUST the SP2). Use the Unattended guides to DIRECTLY integrate Drivers. THEN go to "flyakite" to create the AIO. Your making this complex and it isn't. This would keep nLite "out of the loop" (so to speak)... edit - nLite doesn't make AIO's - it's an "integration/tweaker/remover/make-unattended" (not exactly the same as the Unattended guide, but VERY close).

? Never having one or any general knowledge of it, I found this - http://www.overclock.net/t/906194/how-does-sandy-bridges-gpu-work DVI Connector... the CPU does the work instead of a separate Chip - utilizes (shares) the L3 Cache.

??? Build an AIO (by whatever method of -booting- the selected version). Usually, this involves a completely independent set of Folders with a "hacked" file to point to the correct "hacked folder name". The FULL ISO contents of each is usually stored also in a SEPARATE folder. nLite will require that you COPY that FULL ISO contents to HDD before nLiting (or just point to that folder). I really don't want to go into AIO building just now. AND... you've mixed two different subjects - AIO and nLite... Can you indicate (tell us) how the AIO is built and the directory structure?