submix8c

An explanation or two is in order. Yes. Amazon? eBay? That's the COA key for that particualer Vista Edition. There's another internal one inside the Registry. But that's (kind of) irrelevant. You *do* have the Restore Disks, for it, right? And per your link - That means your currently installed Windows 7, which you don't have but wish to upgrade to. In other words, you have to have a Full/Upgrade Install Product Key that you bought with your Windows 7. They changed the rules even for that, in that you can't even get an ISO with a Windows 7 OEM (COA) Key. And the direct links to them (useless since you don't even have a legal Full/Upgrade Product Key) have been pulled by MS requiring you to go to the MS Website and enter a key. If you want Windows 7 that badly, I'd recommend getting ASAP a legally purchased one (DVD and Key of Full/Upgrade) for the best price you can. Bear in mind, if you purchase an OEM System Builder version you won't be able to Upgrade as those are strictly for Clean Installs (no prior OS). HTH ( and sorry... )

See this - http://www.msfn.org/board/topic/175080-driver-packs-from-driverpacksnet-in-a-customized-winxp-cd/ Let's keep our questions together so we'll all have the big picture. Yes, I made a cross-post between them, and "generally" answered you there. HTH

Closely related topic by you. One was enough. http://www.msfn.org/board/topic/175079-windows-xp-pro-sp3-drivers-to-remove-and-keep/ Seems you want to remove some but add some others. In addition to adding Post-Install Software. http://www.msfn.org/board/topic/174919-applications-to-remove-and-replace-with-addons/ On that note, I'll agree - go with a DVD if this is for "newer hardare". Be aware that "newest hardware" may or may not work for XP.

AFAICR, there's a file on any given XP system that *if* you back it up and for *that* PC somewher off the computer(s) when you Reinstall the Activation is restored without calling again. Read these carefully. The MS one expains what happens and why/how/under-what-condtions requiring reactivate. https://support.microsoft.com/en-us/kb/305356 If you follow the above rules, this one explains how to retain activation. http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/UserTips/Miscellaneous/BackupRestoreXPActivation.html Note that the first one is talking of Hardware Changes. Exceed them and you *will* have to re-activate. However, if the hardware does *not* change for *that PC and it's corresponding file* then the second one will avoid that nasty reactivate call. Here's the process to Activate By Phone. (Then perform the second link's instructions/) http://www.windowsnetworking.com/articles-tutorials/windows-xp/wxpactiv.html HTH

Sadly, VPC's use the Host OS Date/Time, so that doesn't work. It actually gets set in the VPC's BIOS (AFAICR). Time server on the Guest has nothing to do with it. To my knowledge there's no way around that. Best go with the XP-Mode one (no expiry). Bad part is it's much larger and you have to extract it *but* it will function. (Not to self - see if the EXE one has a full I386...) (but probably not...) Google this. "virtual pc" BIOS timeTherein lies the rub. (and I'll say no more - just google that)

Well, not knocking the Product, but in WSUSoffline you can see that it's using the CAB files (links in the XML's) and in WUD you can directly see the compiled (also through great effort) list (inside the XML). IOW, the ULZ used by WUD have undergone great effort to maintain just as the Product that you tout has. You won't deny that, right? So, which one?

Well, yeah, probably. Just that you can't create an Integrated CD/DVD from it. The major difference between it and a Full OEM/RTL is 1 - Just the basic "extras" in the I386 (anything in Add/Remove). All else is removed. 2 - OEMBIOS.xxx are MS-specific "OEM" as is the Internal Key. 3 - Additional Drivers to allow for drag-and-drop and USB access (among other things) 4 - There are a couple of "fixes" already installed. Chances are the one jaclaz linked to is probably the same type of VHD. Nonetheless, either should be usable for the OP's purposes.

Tell ya what... Download *the* latest Z-Zip to unzip EXE's. Some will be un-zippable, others will not. Some EXE's will have a different verrsion of a "stub" to Unpack them Try opening a CMD Prompt, navigate to your Download folder, for one (a copy maybe) and run "NAME.EXE /?" and see if it gives extraction options. You may/may not see a CAB, MSP, or MSU. You could also (maybe) get the latest Reshacker, open the EXE, and literally (maybe) see the Extraction instruction. And like I said, *some* files can *not* be Directly Integrated. Curious - did you read the link? Or even try the ULZ there? http://www.wincert.net/forum/topic/12103-8-juin-2015-update-list-gdr-pour-windows-7-sp1-x86x64-fr-en-de-es-it/ It's in English part way down (a bit of information re: Integration). Oh, and the mentioned WinToolkit is just another Integrator (like nuhi's nLite/vLite/NTlite). It's not an OS Hack. Wincert is legit. Google on the last KB you gave above, I found this yuck. http://answers.microsoft.com/en-us/windows/forum/all/update-kb-3004375-and-kb-3031432-windows-7-keeps/28eee421-2491-4470-bb3d-9325f076da34?auth=1 Here's another. http://forums.mozillazine.org/viewtopic.php?f=37&t=2920727 Here's the actual KB, which lists Version/Date for all the Files inside the Package(s) - https://support.microsoft.com/en-us/kb/3031432 Here's the one preceding it (another yuck!) http://windowsitpro.com/patch-tuesday/patch-tuesday-kb3033929-causing-problems The KB article with warnings - https://support.microsoft.com/en-us/kb/3033929 And that very one links to the MS# https://technet.microsoft.com/en-us/library/security/3033929 ..which tells you that it Supercedes anothe one. Did you install/integrate the older one? (An example of the below Process.) Sometimes it's good to Google the KB's before assuming they're a good thing and/or not Superseded and/or have no Prerequisites. There have been cases where Fixes actually broke stuff (as seen above). I will repeat that getting *all* MS Catalog files for the purpose of Integration is not necessarily a smart thing. The usual method of someone that actually builds *correct* lists is to - 1 - Install the OS 2 - Go to Windows Update and get the list but DO NOT install 3 - Go to the KB Articles (one by one) referenced and get the file(s) from the Download(s) link given. 4 - Integrate and reinstall 5 - Go to #2 until no more Updates show (then proceed) 6 - Get that god-awful list and work your way BACKWARDS through it, eliminating *all* Superseded. 7 - Integrate and reinstall to confirm you have Just The Correct Ones. If not, try to figure out where you went wrong. I should point out that integrating out-of-date-order can possibly cause problems as well. We discovered that for nLite for XP and went "safe bet" order by old-to-new. Indeed, some Fixes have Prerequisites and installing out-of-order *may* goof up the Integration. HTH

Depends on the Driver type as to whether it will work in Win95. This - https://en.wikipedia.org/wiki/VxD -vs- this... https://en.wikipedia.org/wiki/Windows_Driver_Model (Yeah, Wiki - ugh!)

Yeah, it bites... Can we can back On Topic now? We have fish to catch and fry.

Maybe so, but are they coming directly from MS Servers or somewhere else (illegally)? I have heartburn over that.

Can you? Let us know if it works.

Seems they shipped with Windows XP (AFAICT. Not so sure that (even if no *USB Legacy* in BIOS) the OS wouldn't recognize it. Isn't that the point? http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&lc=en&product=81295 Your main problem is getting USB KB/Mouse to work in DOS. That's what (hopefully) an Adapter would do. How about Fn Keys? Seems HP doesn't have an actual Manual available. Found this for External Monitor. http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00213448&tmp_task=useCategory&cc=us&dlc=en&lc=en&product=81295 edit - FWIW - zt1000 Series. http://www.hp.com/ctg/Manual/lpi05595.pdfHTH

(sigh...) An EXE may *very well have* an MSU *inside* it! Also note *some* updates do *not* directly Integrate and *must* be installed via a Command Script (the OEM way). Is there some reason you don't wish to get the ULZ from WinCert and note the very specific information (that you *can* read)? I *suppose* I could get the latest, do the downloads, and give you a full list to compare to, but I'm rather busy with another project. As an *alternative* I could get the ULZ, and strip out everything but the KB# and Description. I will *not* post it (complete) here as the project is over *there* and some of the forums have a mutual respect for one anothers' efforts. If they *wanted* to share it here they would *post* it here, but the people would have to sign up *here* to download, same as WinCert. edit - I will *again* note that MS Catalog will give you Superseded updates, whic you do NOT want a a *newer* Fix will simply *overwrite* it! http://www.merriam-webster.com/dictionary/supersede KB#123 has abc.sys in it. KB#456 is newer and has abc.sys in it. Forget KB#123 because KB#456 replaces it in its entirety. Trust me on this, I've done some merry chases eliminating older updates for XP via KB articles. ------------------------------ EDIT#2 - Apparently, the OP is in need of explanation. If I sounded rude, my apologies. I just hate to see someone repeat the efforts that other noble contributors have already done (wherever). I will agree that the OP probably has quite a bit of experience, but (no offense) it may be a bit shy of what a lot of "Been There, Done That" folks have experienced. Addendum - Want to *really* get confused? Use "WSUS Offline" and compare results to WUD (using the latest ULZ) results. It's not pretty, due to the fact that "WSUS Offline" isn't as exacting as WUD ULZ (latest) is. And trust me on this... "Been There, Done That". HTH Side note - We know that WSUS and WUD get Updates directly from MS, as opposed to "Encrypted" download lists/locations (even though they *nay* get them direct.) Just sayin'....

I say *again* that MS has two separate repositories, one for Windows/Microsoft Update and one for Downloads (manual). If you get one of the ones from WU and get the same KB# from Downloads (using the KB#) you'll find they have different dates. HOWEVER, they *should* be identical. The Catalog (as well as WU/MU) uses a different repository (WSUS Server). This is the same method Big Corporations use to roll out Updates instead of allowing Users (employees on the LAN) to go to MU/WU. Does this clarify your post #6 (which is a wrong assumption)? You'll find, if you look in a Log file (?can't remember the name) it will give where WU got it from. It will *not* be the same place as getting it from the KB#. Hint - when going to the KB# Download, right-click on the "If your download didn't start..." link, copy it, and paste it into Notepad. Those are the Links that are used for WUD ULZ files, not the ones from WU. It's called (loosely described) Sub-Domains. HTH (again...)

Just want to point out (and the XP VHD is still fully functional) that the OS inside does *not* contain a complete I386 folder, so don't depend on "creating" an XP CD from it. It also has some "special" Drivers to allow USB Support and drag-and-drop (among other drivers). JFYI...

o_O So... good thing I didn't go ahead and download yet? (Rats!) Thanks for the heads up, harkaz! edit - But *will* (as soon as time permits) get the last v2 packages.

This one (Windows 8?) - https://www.asus.com/Notebooks/X45C/ The manual doesn't say anything about how "up to 4gb DDR3 video memory" applies. It says if you have problems remove added components to see if it boots properly. I will say this as a possible - Starting at 2gb, upgrade by adding another 2gb, then blowing up at 2gb -may- be some kind of ideosyncracy in the "sleep" (aka Suspend To Ram?) or the Hibernate(?Suspend To Disk?) and the OS using the old info? The Manual just says "put the RAM in and it works!" (paraphrase). It doesn't have much in the way of BIOS settings. I can say this - the Asus Laptop I have disassembled (AFAIK) used to work before it stopped powering up and was brought to me. Maybe Asus is making crappy Notebooks? (The one I have has 4gb SOLDERED in!) It's an X55C, so... Curious - what speed/type RAM was in there originally? Maybe a timing/mismatch problem? A dump would help and Trip (and others) know how to quickly read them and isolate the problem (not me, though), so... (Done chiming in...)

I have a boxfull of them, sound cards, modems, and a number of video cards. Soon they will all get recyled or sold on Cragslist.

Agreed. I've recycled more PC's than I can count. (Thanks, Brothers Chris and Joel, for dumping them on me into giant stacks in my work room.) Goodwill or nearly any large thrift store may have some. Of course, they're getting scarce around my neck of the woods. Got lucky on a $25 Dell Vostro 200 SFF (all SATA, Core2Duo + 4GB DDR2 Ram, DVD burner, no HDD, no PS/2). Needs a dang PSU (odd size) as well, but tested with an extra standard size and it works.

Pick an ULZ. Copy it to a different folder (to retain the original). Rename to xxx.ZIP. Extract the UL. Rename to xxx.XML. Open it. You'll see that the files come directly from MS. WUD simply facilitates the display/download of the contents. The format of the UL is very specific. Indeed, it "could" be used to download just about anything that has a direct (and GOOD, mind you) link. Bad file links will cause a HALT of the WUD awaiting a response. HTH

Krud! XP and up. Oh well, I have 2 more empty slots so a PCI NIC Add-In is in order, I guess. Oh, well, I usually have the On-Board plus one Add-In anyway. Yeah, and I planned on eventually getting a nVidia PCI-e (the "shorter" one is reserved for USB-3 Add-In). If *only* the Chipset drivers work. We shall see, time permitting. http://www.msfn.org/board/topic/163405-slipstreamable-intel-chipset-inf-drivers/

Boo-boo (the year) in the Components PDF. Back To The Future! Am I understanding correctly the Legacy v2 "false positive" is fixed? Also does it include everything *except* POSReady? (That's a bit unclear.)

Hmmm... http://serverfault.com/questions/749761/corrupt-excel-xls-file-ole-header-corruption

Thx, LoneCrusader. Haven't considered the 98SE on my "new" Asus yet. It has Gigabyte (Marvell) NIC. And the BIOS has option of HD or AC97 sound, so yay! I've also inserted an nVidia PCI video card so I guess I may be good to go (depending on the SATA). Good news is it has one PATA connector. Maybe I'll get lucky?