Molecule

Thanks jaklaz! As usual you find the good references ... I tried everything, to no avail. So I figured the DVD CD-ROM drive itself was dead, and bought a new one. While removing the old DVD, I noticed that the SATA cable connection at the back had somehow worked loose. Perhaps slowly over 5 years of fan vibrations or whatever ... In any case restored the SATA cable connection, and the DVD is back. So, here is the wierdness ... this means that the SATA cable connection was NOT sufficient for Windows XP to recognize the device, but it WAS sufficient for the BIOS to recognize it. With the loose connection, the BIOS recognized the DVD, but XP wouldn't. Tightened up the connection and XP recognizes the DVD. Maybe BIOS needs only 3 of 4 wires, while XP needs all 4. Thanks again, bro!

running a 2008 intel mobo with XP sp3 w/ POS Ready thru last year +/- only one DVD/CD-ROM is connected to the mobo BIOS sees DVD/CD-ROM on Sata 1 as HL-DT-ST BD-RE WH14NS40, DMA Mode is auto when Windows XP boots it doesn't see the DVD drive device manager devmgmt.msc doesn't show a box for DVD/CD-ROM drives thus I don't have an option to change drive letter, or delete the device so that it can be re-recognized on XP reboot under Hkey Local Machine / Systen / Current Control Set / Control / Class / {4D36E965 E325 11CD BFC1 08002BE10318) there are 24 items only the first one is for DVD/CD-ROM drives it has three sub folders -- 0000 and 0001 and Properties in 0000 and 0001, the LowerFilters key value is PxHelp20 --- any thoughts on how I can get my DVD drive back?

Hi -- been a while -- seems simple things get complicated as I get older (arghh) I'm running XPsp3 with POS updates thru approx Aug 2015. For browser, I'm running Firefox 38.1.0 esr. It's running the flash plugin 21b197. I'd like to update FF. Does anyone know if latest FF (45.6.0esr) runs OK in XPsp3+POS? And now for the dumb question (sorry) ... do I need to uninstall the old FF 38.1.0 first? Or, just launch the new exe installer, and install on top of the old installation? or ...? I'd like to save passwords, download history and settings etc if possible. The FF exe installer is available here -- https://ftp.mozilla.org/pub/firefox/releases/45.6.0esr/win32/ Also, the flash archives now include a new file which I can't find any information on ... it's a xxx_winpep.exe, for example "flashplayer23_0r0_207_winpep.exe" Does anyone know what this file does? Searching "winpep.exe" on adobe forum and here return empty. I see it's now included in the flash archives back to v.20, maybe earlier. The adobe archive containing the flash plugin exe installer and this ?-new winpep.exe file is found here -- https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html Merry Christmas! and Happy New Year!!

sorry if my observations are totally noob and a little out of sync ... there's alot in this thread to catch up on this article (https://www.winhelp.us/microsoft-emet.html) claims EMET 5.2 installs and works in XP-sp3, but it requires a working .NET 4 I seem to recall prior posts talked of removing .NETs, which if that's the case that might be causing a problem with EMET 5.2 installation

@skrell -- I had looked at your final 7z addon, even did an integration and tried to setup a system with it. The setup failed, and as I remember it (http://www.ryanvm.net/forum/posting.php?mode=quote&p=139998) it was a corrupted ntkrnlmp.ex_. Having the addon 7z was of little use, because you hadn't given us the list of files that were used to build the addon, until now. Going back to the mid August issue (the list is now out of date in case anyone is checking), I built an addon with your list above using dxupac, integrated the addon with a clean XP sp3 hologram source and OnePiece's AIOv106, using RVMI in an XPsp3 system, and I get a normal ISO with a normal ntkrnlmp.ex_. I didn't try a build a system (It takes an hour since I don't have virtual machine ...), but we know that with a corrupted ntkrnlmp.ex_, the setup will fail. When I build and integrate I get a normal sized ntkrnlmp.ex_ To me, that suggests the problem may not be with the POSReady files (which until we had your list could not be excluded as a possibility), or with DXUPAC, or RVMI, but rather with your system or with your source. MD5s over at http://www.ryanvm.net/forum/posting.php?mode=quote&p=140057

@bersaglio -- how do we determine which .NETs are applicable to XP Embedded? I looked at the link you gave -- https://technet.microsoft.com/library/security/ms15-101-- but the MS lists only updates for Vista SP2, Win7, etc, but none for XP Embedded. Once you have the KB, and go to the KB page, some of them have an MD5 hash for XP Embedded, but I didn't see any links ... On the MS15-xxx bulletin page, there are also updates for different .NETs, 2 and 4 in this case, cross referenced for different security issues. Do you review each KB in detail, and see which ones have a hash value for XP Embedded -- but then where do we find the link for XP Embedded, or do you just use the .NET update for Vista or Win7 and run it in XP? Maybe if that's the way .NETs were setup it would work. just wondering ... thanks

@heinoganda and atari -- re WSUS page -- solved -- to replicate the request by MS to install some kind of new program for the catalog update page, I found out I had to log on as administrative user -- only then does MS ask to install the new program, after which the catalog update page returns the needed search box. Logon as Admin -- fixed. If I loged on as usual limited user, it gives WSUS screen without search box ... (yea ok it's stupid, but I'm still graduating from win98se, so I figured eventually I had to figure out what this new limited users thing was all about ... then I got used to it and kind of like it ... of course any competent hacker walks right past the imaginary protections ...) there are lots of people here and on ryanvm who would like to try to help skrell, but he refuses to provide the list of files (POS Ready and other) that he has been feeding into DXUPAC to create his failed addon, and of course the OS environment that he is using to run DXUPAC. The mods to DXUPAC to create an addon are very simple, and it would take only a few minutes to replicate (or not) the problem that he claims to be observing, but he refuses to provide the list of files that has been causing his problem. So far it seems there are no rogue POS Ready files, and DXUPAC continutes to work reliably in an XP pro with post-SP3 AIO update (with integration there is no need for XP Pro to spoof XP Embedded ...)

I just tried logging onto https://catalog.update.microsoft.com/v7/site/Home.aspx-- Last month, the catalog home page offered a search box, where I could enter "XP Embedded" which then returned a table which could be sorted by date, etc. Now, I get a blank screen -- edit -- meaning I get a Microsoft Update Catalog page with no search box or link or anything -- screenshot below my IE8 that is wide open (I use it only for MS) -- it wants to install something called Update Catalog (which for all I know might be free MS-10 Pentagon-NSA spyware system makeover, or whatever ...) It never did that before ... Has anybody else had this experience? MS gives me no information on what it wants to install ...

This is a thread on application of POS Ready updates to XP So far none of them have caused any problem, and a whole lot of people have tested them. That noted ... the problem with your Addon is most probably not a rogue POSReady update. (So far, there aren't any.) In other words, your problem can probably be traced to your introduction of a non-POS Ready file. Your problem cannot be replicated by creation of an Addon that uses only POS Ready updates. I've created several, using ONLY POS Ready updates, and all of them have built a stable system.

thanks for feedback w2k4eva -- I'll need some time to open the topic up again, but I wanted to say, I made the list go up and stop at EOS april 2014 because I didn't want to create an overlap with the work being done over on the POSReady thread on XP post-EOS -- also I wanted to share the find for the offline installer for the .NET 3.5 family

a batch scripting question for management of POSReady updates for XP users The MS catalog site gives us a list of "XP Embedded" update files. (BTW, I learned today that a search on "POSReady" and on "XP Embedded" return different file sets. The former returns only system updates, the latter returns system update as well as the .NET updates and some hardware files. The problem is, neither list gives us a MSxx-xxx to track the issue, or a KBnum for when a prior patch is being superceded. I was wondering if there would be a way to write a batch that could help us doign that ... Basically, put all the system-only patches (type-1) in a directory, have the batch extract the updates, read the patch inf, and echo >> the isntall data to a comma-delimited database (or other delimiter). Each file (mostly dll) would be associated with an update KBnum, and have its dll version number, file size, file date. Roll through the patches in the dir, then save the database and delete the extractions. Users could feed the delimited data into a spreadsheet, sort on dll name and then version number, and from the highest version for each dll, generate a list of hot patches, and of patches which are superceded, because the dlls or whatever have higher version numbers. I'm sure it's probably more complicated, but that might be a start, since as it is now, MS gives us nothing to go by ... Could save all of us a lot of time .. I don't know how the .NETs could be tracked, so we rely on each other I guess ... just wondering out loud ...

There's nice work being done on tracking the post-EOS, POSReady patches for XPsp3. I don't use MS update or "agent" whatever it is, so I just take the MS frog walk through Bill's patchwork paradise. In any case, for noobs like me, the problem comes up, how to get from a hologram CD to the POSReady, regarding the .NETs. So, here's the fruits of my frogwalk through the security bulletins -- starting Jan 2007 through May 2014. XPsp3 came out sometime early 2008. The latest .NET service packs about the same time. The earliest bulletin I found which includes XP SP3 was MS07-040. For the NDPs, I didn't find a bulletin which announced that the following post XPsp3, pre-EOS patches (2008 to 2014) were superceded. In other words, if you're starting with a hologram CD, they are probably still hot. MS12-035 NDP1.1sp1-KB2656353-X86.exeMS13-052 NDP1.1sp1-KB2833941-X86.exeMS10-041 NDP1.1sp1-KB979906-X86.exeMS11-044 NDP20SP2-KB2518864-x86.exeMS12-035 NDP20SP2-KB2604092-x86.exeMS13-004 NDP20SP2-KB2742596-x86.exeMS13-015 NDP20SP2-KB2789643-x86.exeMS13-052 NDP20SP2-KB2844285-v2-x86.exeMS13-082 NDP20SP2-KB2863239-x86.exeMS14-009 NDP20SP2-KB2898856-x86.exeMS14-009 NDP20SP2-KB2901111-x86.exeMS12-035 NDP30SP2-KB2604110-x86.exeMS13-004 NDP30SP2-KB2756918-x86.exeMS13-052 NDP30SP2-KB2832411-x86.exeMS13-082 NDP30SP2-KB2861189-x86.exeSA973811 NDP30SP2-KB982168-x86.exeMS13-007 NDP35SP1-KB2736416-x86.exeMS13-052 NDP35SP1-KB2840629-x86.exeMS13-082 NDP35SP1-KB2861697-x86.exeMS11-066 NDP40-KB2487367-x86.exeMS12-035 NDP40-KB2604121-x86.exeMS13-007 NDP40-KB2736428-x86.exeMS13-004 NDP40-KB2742595-x86.exeMS13-015 NDP40-KB2789642-x86.exeMS13-052 NDP40-KB2840628-v2-x86.exeMS13-082 NDP40-KB2858302-v2-x86.exeMS13-082 NDP40-KB2861188-x86.exeMS14-009 NDP40-KB2898855-v2-x86.exeMS14-009 NDP40-KB2901110-v2-x86.exeThe following NDP patches were superceded as noted in the frogwalk. Several were superceded several times ... I guess MS just wants to be sure? NDP1.1sp1-KB2416447-X86.exe (MS10-070) superceded by MS11-078 KB2572067NDP1.1sp1-KB2572067-X86.exe (MS11-078) superceded by KB2572067 in MS11-078, by KB2656353 in MS11-100, by KB2656353 in MS12-035NDP1.1sp1-KB2656353-X86.exe (MS11-100) superceded by KB2656353 in MS11-100, by KB2698023 in MS12-074NDP1.1sp1-KB2656370-X86.exe (MS12-025) superceded by KB2656370 in MS12-025, by KB2742597 in MS13-004NDP1.1sp1-KB2698023-X86.exe (MS12-074) superceded by KB2698023 in MS12-074, by KB2742597 in MS13-004, by MS13-052NDP1.1sp1-KB2742597-X86.exe (MS13-004) superceded by KB2742597 in MS13-004, by MS13-052NDP1.1sp1-KB953297-X86.exe (MS09-061) superceded by MS10-041NDP20SP2-KB2418241-x86.exe (MS10-070) superceded by KB2418241 in MS10-070, by KB2656352 in MS11-100NDP20SP2-KB2446704-v2-x86.exe (MS11-028) superceded by MS11-044NDP20SP2-KB2478658-x86.exe (MS11-039) superceded by MS11-069NDP20SP2-KB2518864-x86.exe (MS11-044) superceded by KB2518864 in MS11-044, by KB2604092 in MS12-035NDP20SP2-KB2539631-x86.exe (MS11-069) superceded by KB2539631 in MS11-069, by KB2633880NDP20SP2-KB2572073-x86.exe (MS11-078) superceded by KB2572073 in MS11-078, by KB2604092 in MS12-035, by MS13-052NDP20SP2-KB2633880-x86.exe (MS12-016) superceded by KB2633880 in MS12-016, by KB2604092 in MS12-035, by KB2742596 in MS13-004NDP20SP2-KB2656352-x86.exe (MS11-100) superceded by KB2656352 in MS11-100, by MS14-009NDP20SP2-KB2656369-v2-x86.exe (MS12-025) superceded by KB2656369 in MS12-025, by KB2742596 in MS13-004NDP20SP2-KB2686828-x86.exe (MS12-038) superceded by KB2686828 in MS12-038, by KB2742596 in MS13-004, by KB2789643 in MS13-015NDP20SP2-KB2804577-x86.exe (MS13-040) superceded by KB2804577 in MS13-040, by MS13-082NDP20SP2-KB2833940-x86.exe (MS13-052) superceded by KB2833940 in MS13-052, by MS14-009NDP20SP2-KB974417-x86.exe (MS09-061) superceded by MS10-060NDP20SP2-KB979909-x86.exe (MS10-041) superceded by MS10-070, by KB979909 in MS10-041, by KB2742596 in MS13-004, by MS13-040NDP20SP2-KB982167-x86.exe (SA973811) superceded by KB982167 in Security Advisory 973811, by KB2656352 in MS11-100NDP20SP2-KB983583-x86.exe (MS10-060) superceded by MS11-028, by MS11-044, by KB983583 in MS10-060, by KB2572073 in MS11-078, by MS13-052NDP30SP2-KB2656407-x86.exe (MS12-034) superceded by KB2656407 in MS12-034, by MS13-052NDP35SP1-KB2416473-x86.exe (MS10-070) superceded by KB2416473 in MS10-070, by KB2657424 in MS11-100NDP35SP1-KB2604111-x86.exe (MS12-035) superceded by KB2604110 in MS12-035 by MS13-052NDP35SP1-KB2657424-x86.exe (MS11-100) superceded by KB2657424 in MS11-100, by MS13-082NDP40-KB2416472-x86.exe (MS10-070) superceded by KB2416472 in MS10-070, by KB2656351 in MS11-100NDP40-KB2446708-x86.exe (MS11-028) superceded by MS11-044NDP40-KB2478663-x86.exe (MS11-039) superceded by MS11-069NDP40-KB2518870-x86.exe (MS11-044) superceded by KB2518870 in MS11-044, by KB2604121 in MS12-035NDP40-KB2539636-x86.exe (MS11-069) superceded by KB2539636 in MS11-069, by KB2633870NDP40-KB2572078-x86.exe (MS11-078) superceded by KB2572078 in MS11-078, by KB2604121 in MS12-035, by MS13-052NDP40-KB2633870-x86.exe (MS12-016) superceded by KB2633870 in MS12-016, by KB2604121 in MS12-035, by KB2742595 in MS13-004NDP40-KB2656351-x86.exe (MS11-100) superceded by KB2656351 in MS11-100, by MS13-082, by MS14-009NDP40-KB2656368-v2-x86.exe (MS12-025) superceded by KB2656368 in MS12-025, by KB2742595 in MS13-004NDP40-KB2656405-x86.exe (MS12-034) superceded by KB2656405 in MS12-034, by MS13-052NDP40-KB2686827-x86.exe (MS12-038) superceded by KB2686827 in MS12-038, by KB2742595 in MS13-004, by KB2789642 in MS13-015NDP40-KB2804576-x86.exe (MS13-040) superceded by KB2804576 in MS13-040, by MS13-082NDP40-KB2832407-x86.exe (MS13-052) superceded by KB2832407 in MS13-052, by MS13-082NDP40-KB2835393-x86.exe (MS13-052) superceded by KB2835393 in MS13-052, by MS14-009edit==== forgot to mention -- the standalone installer for .NETv3.5sp1 includes a /norollback switch. The net result is probably close to sourcee integration. The patches for NPD updates use the similar /nobackup switch. I haven't tested but, if installed with these switches the uninstall option for the .NET installers and patches shouldn't appear under add/remove programs.==== Here are some links, one hard to find (for me anyway), to standalone installation packages for .NETs The standalone distribution package for .NET 1.1sp1 is available here http://www.microsoft.com/en-us/download/details.aspx?id=26and here http://download.microsoft.com/download/a/a/c/aac39226-8825-44ce-90e3-bf8203e74006/dotnetfx.exe The publish date was 8/17/12, so I assume MS included patches up to that vicinity of time (-- could be a bad assumption!). MS is very quiet about standalone installers. Just a personal preference, but I don't like internet installers. The standalone installer for .NET 2.0sp2 is available here. It's needed if you know you won't need the 3.5 family, which is 2.0sp2, 3.0sp2, and 3.5sp1. http://www.microsoft.com/downloads/details.aspx?FamilyID=5b2c0358-915b-4eb5-9b1d-10e506da9d0f quote "The .NET Framework 2.0 Service Pack 2 provides cumulative roll-up updates for customer reported issues found after the release of the .NET Framework 2.0. In addition, this release provides performance improvements, and prerequisite feature support for the .NET Framework 3.5 Service Pack 1." NetFx20SP2_x86.exe 23.8 MB released 01/16/09 http://download.microsoft.com/download/c/6/e/c6e88215-0178-4c6c-b5f3-158ff77b1f38/NetFx20SP2_x86.exe The standalone installer for the entire 3.5sp1 family (2.0sp2+3.0sp2+3.5sp1) is available from MS at http://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exe Google doesn't seem to like the above file very much. MS and Google flip all my searches over to the internet installer. It's a 242meg download, but when the x64 stuff is tossed out, the standalone .net 3.5sp1 family is down to 86meg. There's a pretty good article on depoying/installing the creature here. Microsoft .NET Framework 3.5 Deployment Guide for Application Developers The patches for the Service Pack updates for .NET 3.5 sp1 x86 are patches only. They are available here http://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en They total about 17meg. More importantly, the internal files have dates similar to the above standalone, so I assume the above full standalone was compiled about the same time as the patchs, which were published in Dec, 2008. I couldn't find any MS cover pages for the download, or what KBs were included, like MS used to do, back when. The standalone installer for .NET 4.0 is available here. http://www.microsoft.com/en-us/download/details.aspx?id=17718 MS did some kind of compression magic. For x86+x64 combined, it's 50.4meg (little m). When expanded, and then when 13.2meg of x64 stuff is removed, and when it's recompressed with 7zip at maximum compression, the resulting archive is larger (52.4m) than the original! With 13m of x64 removed from 249m expanded, even 7zip-maximum can't compress it back to what MS did with it's installer. I was surprised.

1 In the part where you build 7 cabs for the windows media patches 952069, 954155, 973540, etc. you cabarc the files in the patch folders for WMP9, i.e. move /y wm9\*.* .\ Can I use WMP11 instead of WMP9 with this build? If so, should I use the files for WM11\*.* instead of WM9\*.*? Within each patch, the filenames in the two folders are the same, but the files differ in size. Can I just feed wmp11-windowsxp-x86-enu.exe (25meg) into the nLite/RMVi patch/addon section, or does it need a good bit of tweaking by a special inf? 2. Can I just delete the stuff (the magic!! really) that you do in order to build an Windows Update Agent for XP? I don't use it. The use of split at 35328 bytes is too much! What a hoot! minor notes 1. when I first ran the batch, all of the mirrors timed out for the initial cabarc.exe download. In your zip package, the filesize for wget.exe is larger 401k -- when I tested with wget with the two dlls (1,220k total), the ftp into MS for win98 reskit worked ... Fut, a higher version of cabarc.exe is downloaded later (at ~~line 1030) when you build WUAgend, and extracted from a MS support.cab and that seems to work. So maybe that's better than the mirrors up at the top of the batch. When the batch timed out on the first download, I just plugged in a local copy, v5.1.2600, and the batch built all the cabs and dl'd all the files flawlessly. The cabarc exe that is downloaded from MS support, for building WUAgent, is v5.2.3790. The cabarc I got from the MS Win98 reskit doesn't even have a version number, and it doesn't say microsoft in the header. hmmm ... maybe I been hacked. 2. the link to the adobe installer for flash activex v16 is 404. A similar link to 18 exe works -- note addition of fp in from of the url around line 220 wget http://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_16_active_x.exe(404) :: http://fpdownload.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_18_active_x.exe (200) 3. IE8-Windows-x86.exe is in the download list (line 1840~) but it not included in the final check list at the end. 4. In the updates.txt file in the zip package, the file WindowsXP-KB974112-x86-ENU.exe is included twice. Totally minor stuff. The batch works beautifully. That was some VERY beautiful work you did! Very thoughtfully maintained, and appreciated. Any chance you know if I can feed this set of files into RyanVMI rather than nLite? I always end up "seduced" by nLite's powers -- meaning I always try to do more "tricks" than I really know how to work with. Meanwhie RVMI just keeps on chugging along and I "feel" (subtle ... arghh) like it gives me a stronger platform. Weird, admitted. Also, has anyone shared a batch script to convert a .NET hot patch into one that can be integrated? Thanks, and cheers!

When I build XP (sp3, OnePiece AIO + POSReady, x86 + .Net hassles), XP starts up with indexing service turned on, and during setup or prehaps first logon, XP builds an index for every hard disk it can find (or it sets an index=on tag for all files it can find, according to some set of rules somewhere, ...) When I turn indexing off for a hdd (Explorer > "drive" Properties > General tab > Indexing), it has to scroll through ?hundreds? of files, to reset some indexing attribute. Some files won't allow the "please index me" attribute to be removed. Is there a way to use WINNT.SIF to turn off indexing service before or during setup? I obviously don't need the Windows Desktop Search in my taskbar, but I think that can be turned off by adding a line in [Components] section.-- WDSearch = "off" perhaps? My preference is to use WINNT.SIF or other text file I can edit. nLite is too complex for me. There are several places to deal with indexing service and my machines don't have power to play virtual machines, to hack around with nLite to verify how it works. nLite is a great program, and I'm not insulting it, or anyone who has years of familiarity with it. I don't want to start a nLite discussion -- I just want to find another way to turn off indexing service during setup. == edit == An article suggests the following REG add command might turn indexing service off net stop cisvc REG add "HKLM\SYSTEM\CurrentControlSet\Services\CiSvc" /v Start /t REG_DWORD /d 4 /f (from http://www.computerstepbystep.com/windows-xp-indexing-service.html) maybe there's a way to add that to WINNT.SIF? == end edit == thanks ...

I seem to remember from a few (harhar) years ago that someone had done a driver extraction/driverpack build program, but I can't remember its name, and my search efforts on "driverpack" have failed ... ... it would dig into an existing existing system, pull out all the driver infs and files, and build a heirachy and copy them to a zip file that could be loaded into drivers section of nLite. ... in the meantime, I can use DriverGeniusPro v11, but I have to install and uinstall and yuk ... thanks if you have a better memory than mine! cio peace

Thanks guys -- I was hoping that /integrate or /nobackup would work. I should have mentioned XPsp3 x86 source with RyanVMI (OnePiece AIO + Addons) I didn't know about Ricktendo had worked on a .NET package as well. I like his runtimes product. I have a look at this one. OnePiece did nice work with AIO, but on .net 1.1sp1 it appears he may have left out KB2833941 (MS13-052, 2013-0709, i.e. pre-EOL) or at least it doesn't appear on his change log. Anyone know of a batch file floating out there where I can feed it an msi update for a .net and it will munge it into an Addon? XDOT.TK has a batch which converts a WMP patch into a CAB Addon for a standard inf install. Yes, maybe some touchy editing of an inf will be required. Is XDOT's blog still available on MSFN? Didn't he used to have that as a project on this forum? thanks

I tried integrating NDP20SP2 KB KB2894843 into XP source and the installer runs, but I get no change. setup is C:\XPsource C:\XPsource\I386 KB2894843 (09/09/14)is .NET20sp2 has type 2 installer I run with /integrate switch and path (edit--space betw filename and switch, no space betw switch : and path) C:> KB2894843.exe /integrate:C:\XPsourceInstaller opens dialog box, asks click to continue installer creates temp dir with 28 char hash installer offers EULA -- I click accept installer says please wait progress bar progresses while hard drive spins tirelessly about 60 sec later installer announced finished temp hash dir is deleted I check the source I386 folder and there is no change between before and after?? Anyone have an idea what is happening? It seems to install on a running system, but I'd like to integrate into source if I can ...

=== edit === SUCCESS!! the sfx packages by WinRar ran with no problems. (they deserve a plug ... I got WinRar in a MSFN promotion back when) thanks to all === edit 2 === NDP1.1sp1-KB2833941-X86.exe allows /passive but chokes on /nobackup for the .NET 1.1 patches modded for XP, I ran the modded setup.exe (the one that is in the \update folder) because it accepts switches! \passive \nobackup both work (I didn't if SFX archive would pass parameters to the right setup.exe (there are two, one in root - don't use, it's 2002, one in update folder, which is modded to XP) all of the other .NET setups for 2, 3 4 also accept the same switches \passive \nobackup (\no backup is not listed on the /? list but it seems to work) batch installs with /nobackup switch is MUCH faster (a lot of delayed diskwork, so I use start /wait NDPxxx /passive /nobackup) === edit 3 === pretty cool .NET version installed tool for free --- http://www.asoft.be/prod_netver.html(portable) (along with the MS Framework Setup Verification Utility) ==== WinRAR sfx (using WinRAR 351) VERY cool -- thanks for the intro -- 1st time I used it. I looked at a few 7zip SFX builders but they seemed clunky. There's one as MSFN project (http://www.msfn.org/board/topic/101552-7z-sfx-modified-module-and-tools/page-20) looks nice ... but where do I start??? you download a 7z with several sfx archives, but which advanced crypto name does what? which one goes first? where to start? I assumed it was plugin on 7z but probably not? WinRAR sfx was very cool! straight forward ...

@bphlph -- thanks! it's nice to see parts in a bigger picture! Or should I say, Slowly, I start to see a bigger picture ... haha @heinoganda -- even though we are using XP with SP3, we preserve the folder name SP2QFE (for Server 2003 sp2), and we preserve the file name update_SP2QFE as well? -- Just checking. I guess the SP2 names match the tables in branches.inf. == edit == wondering if there a way to recompile and make the /quiet and /norestart switches work for batch install? thanks also, whoops comment below doesn't apply -- I just rememberd that each KB has a different time stamp sorry it looks like the file "branches.inf" will be standard for all cases, so far, Which means maybe it could become part of a set called the "XP engine files" ... they always get copied into the new package (replacing same files for Server 2003), while the file "update_SP2QFE.inf" will always require the edits as shown. Thanks!

absolute awesome heinoganda!! some questions to finalize 1. in "update_SP2QFE.inf" there are two HKLM's which refer to two dll's which I don't have in my XP system. They are %systemroot%\system32\ws03res.dll and %systemroot%\system32\w03a2409.dll One call in [Product.Append.Reg.IA] and another in [Product.Append.Reg.ID] Do you have these 2 dll's in your XP system? Since the calls to these files appear in the original inf for Server 2003, I was wondering maybe they are dll's for Server 2003? 2. The find on KB 2833941 is HUGE to me. It's not in the changelog list for OnePiece's AIO Update Pack. HUGE find!! Big thanks. It runs in from command line. 3. so -x expands -- haha -- I've been using DXUPAC but it's just a hidden switch in the installer. Nice! Thanks. Saves lots of work. 4. How do I compile the service pack back into an installable (executable) exe. Or do I just start up one of the exes in each package to run the update. == edit == 5. three KBs (NDP11SP1-XP-x86-KB2972207, NDP11SP1-XP-x86-KB2978114, NDP11SP1-XP-x86-KB3037572) have two copies of update.exe. One is in root, the other is in \updates folder. After the hex edit of update\update.exe, so now do I copy it to both locations in above KBs -- Or, just overwrite thte one in the \update folder? -- thanks (The problem doesn't apply to NDP11SP1-XP-x86-KB3023211 because it doesn't have a copy of update.exe in the root folder. Only one in \update) Thanks! Biggest time ever!!

BIG thanks heinoganda!! I'm going to try it. I don't have VM, but I can do clunker just fine. I scanned thru several XP updates, but they are all SP3QFE. I'm guessing that's the name of the engine. Any chance you have a KB number for an XP update that is using SP2QFE. All of my dotNET 1.1sp1's are 2003sp2-SP2QFE and I'm guessing I should search for an XP-SP2QFE to build from. Using the same kb3037572, eng, I opened "\update\update.exe" in HxD.exe but search on hex string couldn't find your string to replace Find "E8 02 BA 02 00 85 C0 75 41" and replace by "E8 02 BA 02 00 31 C0 EB 41" There are two copies of update.exe in my kb3037572, one in root and one in \update. The are equal. If it helps, the MD5 is -- 50914702cb6c72275018643c557ef8c5 *update.exe I fed your version of update_SP2QFE_DE_mod.inf into the new Notepad++ v6.8 with my version update_SP2QFE_EN.inf and used plugin manager to install the compare.dll plugin -- it's very awesome. Probably the nicest compare that I've seen. If there's any chance you could have a look at mine, and post comments. I have a feeling it's mostly the first section on [Version], and then everywhere where "Windows Server 2003" is mentioned substitute "Windows XP" If I can locate a KB for an XP patch with an SP2QFE engine, and work out the tweaks for the two inf, we will have a template for everyone to benefit. BIG thanks if you can help!! kb3037572_update\update_SP2QFE.inf[Version] Signature = "$Windows NT$" LanguageType = %LangTypeValue% NtBuildToUpdate = 3790 ; change to 2600 NtMajorVersionToUpdate = 5 NtMinorVersionToUpdate = 2 ; change to 1 MaxNtBuildToUpdate = 3790 ; change to 2600 MaxNtMajorVersionToUpdate = 5 MaxNtMinorVersionToUpdate = 2 ; change to 1 MinNtServicePackVersion = 512 ; change to 768 MaxNtServicePackVersion = 512 ; change to 768 ThisServicePackVersion = 512 ; change to 768 CatalogFile = %SP_SHORT_TITLE%.cat[Prerequisite] condition=SingleOp,SP1QFE.SP1Check.Section[ProductCatalogsToInstall] %SP_SHORT_TITLE%.cat, update\%SP_SHORT_TITLE%.cat[ProductInstall.ReplaceFilesIfExist] CopyFiles=Microsoft.net.framework.v1.1.4322.Files[ProductInstall.CopyFilesAlways] CopyFiles=CopyAlways.Microsoft.net.framework.v1.1.4322.Files CopyFiles=CopyAlways.Cache.files[ProductInstall.DataCenterFiles] ; REMOVE AddReg=Product.Add.Reg.DataCenter[ProductInstall.BladeFiles] ; REMOVE AddReg=Product.Add.Reg.Blade[ProductInstall.BusinessFiles] ; REMOVE AddReg=Product.Add.Reg.Business[ProductInstall.AdvancedFiles] ; REMOVE AddReg=Product.Add.Reg.Advanced[ProductInstall.ServerFiles] ; REMOVE AddReg=Product.Add.Reg.Server[ProductInstall.ProfessionalFiles] ; REMOVE AddReg=Product.Add.Reg.Professional[ProductInstall.GlobalRegistryChanges.Install] AddReg=Product.Add.Reg[ProductInstall.GlobalRegistryChanges.ReInstall] AddReg=Product.Add.Reg[ProcessesToRun] ?"%systemroot%\%URTVERSIONDIR%\ToGac.exe %systemroot%\%URTVERSIONDIR%\System.Web.dll" ?"%systemroot%\%URTVERSIONDIR%\ToGac.exe %systemroot%\%URTVERSIONDIR%\System.Web.Mobile.dll" ?"%systemroot%\%URTVERSIONDIR%\SetRegNI.exe %URTVERSION%"[ProcessesToRunAfterUninstall] "%systemroot%\%URTVERSIONDIR%\ToGac.exe %systemroot%\%URTVERSIONDIR%\System.Web.dll" "%systemroot%\%URTVERSIONDIR%\ToGac.exe %systemroot%\%URTVERSIONDIR%\System.Web.Mobile.dll" "%systemroot%\%URTVERSIONDIR%\SetRegNI.exe %URTVERSION%"[ProductInstall.GlobalRegistryChanges.Append.IA] AddReg=Product.Append.Reg.IA[Product.Append.Reg.IA] HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\Clussvc","EventMessageFile",0x00020008,";%systemroot%\system32\ws03res.dll;%systemroot%\system32\w03a2409.dll"[ProductInstall.GlobalRegistryChanges.Append.ID] AddReg=Product.Append.Reg.ID[Product.Append.Reg.ID] HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\Clussvc","EventMessageFile",0x00020008,";%systemroot%\system32\ws03res.dll;%systemroot%\system32\w03a2409.dll"[Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE% HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup", "LogLevel" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%; HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%"HKLM,"SOFTWARE\Microsoft\Updates\Windows XP\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\Clussvc","EventMessageFile"[Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"Installed",0x10001,1 HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"InstalledBy",0,"" HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"InstalledDate",0,"" HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"Type",0,"QFE" HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"Description",0,%SP_TITLE% HKLM,SOFTWARE\Microsoft\Updates\.NETFramework\1.1\%SP_SHORT_TITLE%,"Merged",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Backup Dir",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed By",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed On",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Service Pack",0x10001,%SERVICE_PACK_NUMBER% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Valid",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"Flags",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"New File",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"New Link Date",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"Old Link Date",0,"" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ReleaseType",0,%SECURITY_UPDATE% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentKeyName",0,"OperatingSystem"[Del.Reg.Uninstall][Product.Add.Reg.Business] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_WS03%" HKLM,SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_WS03%[Product.Add.Reg.Advanced] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_WS03%" HKLM,SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_WS03%[Product.Add.Reg.Server] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_WS03%" HKLM,SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_WS03%[Product.Add.Reg.DataCenter] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_WS03%" HKLM,SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_WS03%[Product.Add.Reg.Blade] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_WS03% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_WS03%" HKLM,SOFTWARE\Microsoft\Updates\Windows Server 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_WS03%[Product.Add.Reg.Professional] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_XP% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_XP% HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME_XP%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_XP%" HKLM,SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_XP%[IE7.AdditionalSettings.Save.Reg.For.Uninstall][SourceDisksFiles] SP2QFE\togac.exe=1 SP2QFE\setregni.exe=1 SP2QFE\aspnet_isapi.dll=1 SP2QFE\system.web.mobile.dll=1 SP2QFE\system.web.dll=1 SP2QFE\netfxupdate.exe=1 SP2QFE\aspnet_filter.dll=1 SP2QFE\aspnet_wp.exe=1[DestinationDirs] CopyAlways.Cache.files=65619 ; %windir%\system32\DllCache (copy even if don't exist) Microsoft.net.framework.v1.1.4322.Files=10,"microsoft.net\framework\v1.1.4322" CopyAlways.Microsoft.net.framework.v1.1.4322.Files=10,"microsoft.net\framework\v1.1.4322"[CopyAlways.Cache.files] togac.exe,SP2QFE\togac.exe system.web.mobile.dll,SP2QFE\system.web.mobile.dll system.web.dll,SP2QFE\system.web.dll setregni.exe,SP2QFE\setregni.exe aspnet_wp.exe,SP2QFE\aspnet_wp.exe aspnet_isapi.dll,SP2QFE\aspnet_isapi.dll aspnet_filter.dll,SP2QFE\aspnet_filter.dll[ArchiveCatalogFilesOnly] %SP_SHORT_TITLE%.cat[SourceDisksNames] 1=%ServicePackSourceFiles%[Strings] URTVERSION="v1.1.4322" URTVERSIONDIR="Microsoft.NET\Framework\v1.1.4322" CMAKRegkey=SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Cmak.exe ProxyRegKey=SYSTEM\CurrentControlSet\Services\WSPSrv\Parameters IeRegKey=Software\Microsoft\Windows\CurrentVersion\App Paths\iexplore.exe HyperRegKey=SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\hypertrm.exe EudcRegKey=Software\Microsoft\Windows\CurrentVersion\App Paths\eudcedit.exe AdmtRegKey=SOFTWARE\Microsoft\ADMT TsclientRegKey=SOFTWARE\Classes\conman.exe\DefaultIcon PATH_ZONES="Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones" UDDIRegKey=Software\Microsoft\UDDI HELPLINK = http://support.microsoft.com/?kbid=3037572 URLInfoAbout = "http://support.microsoft.com" SERVICE_PACK_NUMBER = 3 BUILDTIMESTAMP = 1 EXPIRETIMESTAMP = 20150421.185757 UPDATE = "Update" HOTFIX = "Hotfix" SECURITY_UPDATE = "Security Update" PACKAGE_ARCHITECTURE = x86 LangTypeValue = 0x09 WSEDIR = "1033" TSCLIENTDIR = "Terminal Services Client" PORTUGAL = "Portugal" FALKLANDS = "Falkland Islands" LCID = "0409" W32ID = "0009" ACCESSDIR = "accessories" ACCESSDIRNAME = "accessories" ;; accessories folder name is different from the display name in case of PLK, FIN and ELL ServicePackSourceFiles = "Windows Server 2003 Hotfix Source Files" SP_SHORT_TITLE = "KB3037572" SP_TITLE = "Security Update for Windows Server 2003 (KB3037572)" SP_TITLE_XP = "Security Update for Windows XP (KB3037572)" SP_TITLE_WS03 = "Security Update for Windows Server 2003 (KB3037572)" LOC_UPDATE="Update" LOC_CRITICALUPDATE="Critical Update" LOC_HOTFIX="Hotfix" LOC_SECURITY_UPDATE="Security Update" PARENT_DISPLAY_NAME ="Windows Server 2003 - Software Updates" PARENT_DISPLAY_NAME_XP ="Windows XP - Software Updates" WUCUN_TS_JOBFILE = "windows critical update notification.job" BITS_DISPLAY_NAME = "Background Intelligent Transfer Service" BITS_DESCRIPTION = \"Transfers files in the background using idle network bandwidth. If the service is stopped, features such as Windows Update, and MSN Explorer will be unable to automatically download programs and other information. If this service is disabled, any services that explicitly depend on it may fail to transfer files if they do not have a fail safe mechanism to transfer files directly through IE in case BITS has been disabled." BITS_CLASS_NAME = "Background Intelligent Transfer Control Class 1.0" BITS_CLASS_1_5_NAME = "Background Intelligent Transfer Control Class 1.5" BITS_CLASS_2_0_NAME = "Background Intelligent Transfer Control Class 2.0" BITS_CLASS_2_5_NAME = "Background Intelligent Transfer Control Class 2.5" LEGACY_BITS_CLASS_NAME = "Legacy Background Intelligent Transfer Control Class" AU_DESCRIPTION = "Enables the download and installation of Windows updates. If this service is disabled, this computer will not be able to use the Automatic Updates feature or the Windows Update Web site." AU_DISPLAY_NAME = "Automatic Updates" MSI_DISPLAY_NAME = "Windows Installer" MSI_DESCRIPTION = "Adds, modifies, and removes applications provided as a Windows Installer (*.msi) package. If this service is disabled, any services that explicitly depend on it will fail to start." CancelEventType = "Cancel Report" MainCancelIntroString = "Thank you for reporting the Request. When you click ""Send Report"" button, data concerning why install failed will be sent to Microsoft" MainCancelDetailsLink = "See what the installer report contains." MainCancelReportBtn = "&Send Report" DetailsCancelHeader = "Report Information" DetailsCancelBody = \"Sending this report helps us improve the user experience. We will statistically process the collected data to understand what initiated the install failure. This information will help us reduce the number of install failures caused by applying updates." MsSHARED = "Microsoft Shared" OLEDB = "Ole DB" ADO = "ado" MSADC = "msadc" DAO = "DAO" MSSOAPBIN = "MSSoap\Binaries" MSSOAPBINRES = "MSSoap\Binaries\Resources\1033" SHAREDACCESS_SERVICE_NAME = "Windows Firewall/Internet Connection Sharing (ICS)" SHAREDACCESS_SERVICE_DESCRIPTION = "Provides network address translation, addressing, name resolution and/or intrusion prevention services for a home or small office network." Svc-Ip6Fw-DispName = "IPv6 Windows Firewall Driver" Svc-Ip6Fw-Description = "Provides intrusion prevention service for a home or small office network." WEBOC_SCRIPT="Allow scripting of Internet Explorer Webbrowser control" InvalidIEVersion="The version of Internet Explorer you have installed does not match the update you are trying to install." TSC_PACKAGE_EXPIRED="The pre-release version of Remote Desktop Connection has expired. To download the full version of Remote Desktop Connection, go to Windows Update or contact your system administrator." Argentina_Display="(GMT-03:00) Buenos Aires" Argentina_Dlt="Argentina Daylight Time" Argentina_Std="Argentina Standard Time" Armenian_Dlt="Armenian Daylight Time" Armenian_Std="Armenian Standard Time" Azerbaijan_Display="(GMT+04:00) Baku" Azerbaijan_Dlt="Azerbaijan Daylight Time" Azerbaijan_Std="Azerbaijan Standard Time" Bahia_Display="(GMT-03:00) Salvador" Bahia_Dlt="Bahia Daylight Time" Bahia_Std="Bahia Standard Time" Bangladesh_Display="(GMT+06:00) Dhaka" Bangladesh_Dlt="Bangladesh Daylight Time" Bangladesh_Std="Bangladesh Standard Time" Belarus_Display="(GMT+03:00) Minsk" Belarus_Dlt="Belarus Daylight Time" Belarus_Std="Belarus Standard Time" Cape_Verde_Display="(GMT-01:00) Cabo Verde Is." Cape_Verde_Dlt="Cabo Verde Daylight Time" Cape_Verde_Std="Cabo Verde Standard Time" Caucasus_Common_Display="(GMT+04:00) Caucasus Standard Time" Caucasus_Display="(GMT+04:00) Yerevan" Central_Brazilian_Display="(GMT-04:00) Cuiaba" Central_Brazilian_Dlt="Central Brazilian Daylight Time" Central_Brazilian_Std="Central Brazilian Standard Time" Central_M_Display="(GMT-06:00) Guadalajara, Mexico City, Monterrey - New" Central_M_Dlt="Central Daylight Time (Mexico)" Central_M_Std="Central Standard Time (Mexico)" Central_Pacific_Display="(GMT+11:00) Solomon Is., New Caledonia" CentralAsia_Display="(GMT+06:00) Astana" E_Europe_Display="(GMT+02:00) E. Europe" Eastern_M_Display="(GMT-05:00) Chetumal" Eastern_M_Dlt="Eastern Daylight Time (Mexico)" Eastern_M_Std="Eastern Standard Time (Mexico)" Ekaterinburg_Display="(GMT+05:00) Ekaterinburg (RTZ 4)" Ekaterinburg_Dlt="Russia TZ 4 Daylight Time" Ekaterinburg_Std="Russia TZ 4 Standard Time" Fiji_Display="(GMT+12:00) Fiji" Georgian_Display="(GMT+04:00) Tbilisi" Georgian_Dlt="Georgian Daylight Time" Georgian_Std="Georgian Standard Time" Greenwich_Display="(GMT) Monrovia, Reykjavik" GTB_Display="(GMT+02:00) Athens, Bucharest" Jordan_Display="(GMT+02:00) Amman" Jordan_Dlt="Jordan Daylight Time" Jordan_Std="Jordan Standard Time" Kaliningrad_Display="(GMT+02:00) Kaliningrad (RTZ 1)" Kaliningrad_Dlt="Russia TZ 1 Daylight Time" Kaliningrad_Std="Russia TZ 1 Standard Time" Kamchatka_Display="(GMT+12:00) Petropavlovsk-Kamchatsky - Old" Kamchatka_Dlt="Kamchatka Daylight Time" Kamchatka_Std="Kamchatka Standard Time" Libya_Display="(GMT+02:00) Tripoli" Libya_Dlt="Libya Daylight Time" Libya_Std="Libya Standard Time" Line_Islands_Display="(GMT+14:00) Kiritimati Island" Line_Islands_Dlt="Line Islands Daylight Time" Line_Islands_Std="Line Islands Standard Time" Magadan_Display="(GMT+10:00) Magadan" Magadan_Dlt="Magadan Daylight Time" Magadan_Std="Magadan Standard Time" Mauritius_Display="(GMT+04:00) Port Louis" Mauritius_Dlt="Mauritius Daylight Time" Mauritius_Std="Mauritius Standard Time" Mexico_2_Old_Display="(GMT-07:00) Chihuahua, La Paz, Mazatlan - Old" Mexico_Old_Display="(GMT-06:00) Guadalajara, Mexico City, Monterrey - Old" MidAtlantic_Display="(GMT-02:00) Mid-Atlantic - Old" Middle_East_Display="(GMT+02:00) Beirut" Middle_East_Dlt="Middle East Daylight Time" Middle_East_Std="Middle East Standard Time" Montevideo_Display="(GMT-03:00) Montevideo" Montevideo_Dlt="Montevideo Daylight Time" Montevideo_Std="Montevideo Standard Time" Morocco_Display="(GMT) Casablanca" Morocco_Dlt="Morocco Daylight Time" Morocco_Std="Morocco Standard Time" Mountain_M_Display="(GMT-07:00) Chihuahua, La Paz, Mazatlan - New" Mountain_M_Dlt="Mountain Daylight Time (Mexico)" Mountain_M_Std="Mountain Standard Time (Mexico)" Myanmar_Display="(GMT+06:30) Yangon (Rangoon)" Namibia_Display="(GMT+01:00) Windhoek" Namibia_Dlt="Namibia Daylight Time" Namibia_Std="Namibia Standard Time" NCentralAsia_Display="(GMT+06:00) Novosibirsk (RTZ 5)" NCentralAsia_Dlt="Russia TZ 5 Daylight Time" NCentralAsia_Std="Russia TZ 5 Standard Time" North_Asia_Display="(GMT+07:00) Krasnoyarsk (RTZ 6)" North_Asia_Dlt="Russia TZ 6 Daylight Time" North_Asia_Std="Russia TZ 6 Standard Time" NorthAsiaEast_Display="(GMT+08:00) Irkutsk (RTZ 7)" NorthAsiaEast_Dlt="Russia TZ 7 Daylight Time" NorthAsiaEast_Std="Russia TZ 7 Standard Time" NorthPacific_Display="(GMT-11:00) Midway Islands" NorthPacific_Dlt="North Pacific Daylight Time" NorthPacific_Std="North Pacific Standard Time" Pacific_Display="(GMT-08:00) Pacific Time (US & Canada)" Pacific_M_Display="(GMT-08:00) Baja California" Pacific_M_Dlt="Pacific Daylight Time (Mexico)" Pacific_M_Std="Pacific Standard Time (Mexico)" Pacific_SA_Display="(GMT-03:00) Santiago" Pakistan_Display="(GMT+05:00) Islamabad, Karachi" Pakistan_Dlt="Pakistan Daylight Time" Pakistan_Std="Pakistan Standard Time" Paraguay_Display="(GMT-04:00) Asuncion" Paraguay_Dlt="Paraguay Daylight Time" Paraguay_Std="Paraguay Standard Time" Russia_Time_Zone_10_Display="(GMT+11:00) Chokurdakh (RTZ 10)" Russia_Time_Zone_10_Dlt="Russia TZ 10 Daylight Time" Russia_Time_Zone_10_Std="Russia TZ 10 Standard Time" Russia_Time_Zone_11_Display="(GMT+12:00) Anadyr, Petropavlovsk-Kamchatsky (RTZ 11)" Russia_Time_Zone_11_Dlt="Russia TZ 11 Daylight Time" Russia_Time_Zone_11_Std="Russia TZ 11 Standard Time" Russia_Time_Zone_3_Display="(GMT+04:00) Izhevsk, Samara (RTZ 3)" Russia_Time_Zone_3_Dlt="Russia TZ 3 Daylight Time" Russia_Time_Zone_3_Std="Russia TZ 3 Standard Time" Russian_Display="(GMT+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2)" Russian_Dlt="Russia TZ 2 Daylight Time" Russian_Std="Russia TZ 2 Standard Time" SA_Eastern_Display="(GMT-03:00) Cayenne, Fortaleza" SA_Pacific_Display="(GMT-05:00) Bogota, Lima, Quito, Rio Branco" SA_Western_Display="(GMT-04:00) Georgetown, La Paz, Manaus, San Juan" Samoa_Display="(GMT+13:00) Samoa" Sri_Lanka_Display="(GMT+05:30) Sri Jayawardenepura" Syria_Display="(GMT+02:00) Damascus" Syria_Dlt="Syria Daylight Time" Syria_Std="Syria Standard Time" Turkey_Display="(GMT+02:00) Istanbul" Turkey_Dlt="Turkey Daylight Time" Turkey_Std="Turkey Standard Time" Ulaanbaatar_Display="(GMT+08:00) Ulaanbaatar" Ulaanbaatar_Dlt="Ulaanbaatar Daylight Time" Ulaanbaatar_Std="Ulaanbaatar Standard Time" UTC_Display="(GMT) Coordinated Universal Time" UTC_Dlt="Coordinated Universal Time" UTC_Std="Coordinated Universal Time" UTCm01_Display="(GMT-01:00) Coordinated Universal Time-01" UTCm01_Dlt="UTC-01" UTCm01_Std="UTC-01" UTCm02_Display="(GMT-02:00) Coordinated Universal Time-02" UTCm02_Dlt="UTC-02" UTCm02_Std="UTC-02" UTCm03_Display="(GMT-03:00) Coordinated Universal Time-03" UTCm03_Dlt="UTC-03" UTCm03_Std="UTC-03" UTCm04_Display="(GMT-04:00) Coordinated Universal Time-04" UTCm04_Dlt="UTC-04" UTCm04_Std="UTC-04" UTCm05_Display="(GMT-05:00) Coordinated Universal Time-05" UTCm05_Dlt="UTC-05" UTCm05_Std="UTC-05" UTCm06_Display="(GMT-06:00) Coordinated Universal Time-06" UTCm06_Dlt="UTC-06" UTCm06_Std="UTC-06" UTCm07_Display="(GMT-07:00) Coordinated Universal Time-07" UTCm07_Dlt="UTC-07" UTCm07_Std="UTC-07" UTCm08_Display="(GMT-08:00) Coordinated Universal Time-08" UTCm08_Dlt="UTC-08" UTCm08_Std="UTC-08" UTCm09_Display="(GMT-09:00) Coordinated Universal Time-09" UTCm09_Dlt="UTC-09" UTCm09_Std="UTC-09" UTCm10_Display="(GMT-10:00) Coordinated Universal Time-10" UTCm10_Dlt="UTC-10" UTCm10_Std="UTC-10" UTCm11_Display="(GMT-11:00) Coordinated Universal Time-11" UTCm11_Dlt="UTC-11" UTCm11_Std="UTC-11" UTCm12_Display="(GMT-12:00) Coordinated Universal Time-12" UTCm12_Dlt="UTC-12" UTCm12_Std="UTC-12" UTCp01_Display="(GMT+01:00) Coordinated Universal Time+01" UTCp01_Dlt="UTC+01" UTCp01_Std="UTC+01" UTCp02_Display="(GMT+02:00) Coordinated Universal Time+02" UTCp02_Dlt="UTC+02" UTCp02_Std="UTC+02" UTCp03_Display="(GMT+03:00) Coordinated Universal Time+03" UTCp03_Dlt="UTC+03" UTCp03_Std="UTC+03" UTCp04_Display="(GMT+04:00) Coordinated Universal Time+04" UTCp04_Dlt="UTC+04" UTCp04_Std="UTC+04" UTCp05_Display="(GMT+05:00) Coordinated Universal Time+05" UTCp05_Dlt="UTC+05" UTCp05_Std="UTC+05" UTCp06_Display="(GMT+06:00) Coordinated Universal Time+06" UTCp06_Dlt="UTC+06" UTCp06_Std="UTC+06" UTCp07_Display="(GMT+07:00) Coordinated Universal Time+07" UTCp07_Dlt="UTC+07" UTCp07_Std="UTC+07" UTCp08_Display="(GMT+08:00) Coordinated Universal Time+08" UTCp08_Dlt="UTC+08" UTCp08_Std="UTC+08" UTCp09_Display="(GMT+09:00) Coordinated Universal Time+09" UTCp09_Dlt="UTC+09" UTCp09_Std="UTC+09" UTCp10_Display="(GMT+10:00) Coordinated Universal Time+10" UTCp10_Dlt="UTC+10" UTCp10_Std="UTC+10" UTCp11_Display="(GMT+11:00) Coordinated Universal Time+11" UTCp11_Dlt="UTC+11" UTCp11_Std="UTC+11" UTCp12_Display="(GMT+12:00) Coordinated Universal Time+12" UTCp12_Dlt="UTC+12" UTCp12_Std="UTC+12" UTCp13_Display="(GMT+13:00) Coordinated Universal Time+13" UTCp13_Dlt="UTC+13" UTCp13_Std="UTC+13" Venezuela_Display="(GMT-04:30) Caracas" Venezuela_Dlt="Venezuela Daylight Time" Venezuela_Std="Venezuela Standard Time" Vladivostok_Display="(GMT+10:00) Vladivostok, Magadan (RTZ 9)" Vladivostok_Dlt="Russia TZ 9 Daylight Time" Vladivostok_Std="Russia TZ 9 Standard Time" West_Asia_Display="(GMT+05:00) Ashgabat, Tashkent" Yakutsk_Display="(GMT+09:00) Yakutsk (RTZ 8)" Yakutsk_Dlt="Russia TZ 8 Daylight Time" Yakutsk_Std="Russia TZ 8 Standard Time" PowerShell_CurrentlyInstalled=\"Cannot install this version of the product. You must first remove any earlier versions of Windows PowerShell(TM) 1.0 before you can install this version. Please click OK to close the Setup Wizard. Next open the Add/Remove Programs Control Panel, uninstall any versions of the Windows PowerShell(TM) 1.0, and run the Windows PowerShell(TM) 1.0 setup again." PowerShell_CLR_NOT_INSTALLED=\"Cannot install/uninstall Windows PowerShell(TM) 1.0 because it requires an updated version of the .NET Framework 2.0. Please install .NET Framework 2.0 RTM from http://go.microsoft.com/fwlink/?linkid=57014&lcid=0x409 and rerun Windows PowerShell(TM) 1.0 Setup" PowerShell_SCFN="Lucida Console" PowerShell_SCFS="12" PowerShell_SCDir="Windows PowerShell 1.0" PowerShell_SCName="Windows PowerShell" PowerShell_ShortCutRelNote="Release Notes" PowerShell_ShortCutGettingStarted="Getting Started" PowerShell_ShortCutUserGuide="User Guide" PowerShell_ShortCutQRef="Quick Reference" PowerShell_Comments="Windows PowerShell(TM) 1.0" PowerShell_Culture=en PowerShell_InstallLangPackId=1033 PowerShell_ReleaseNotesDir= WSMAN_ServiceDisplay="Windows Remote Management (WS-Management)" WSMANOOB_WSMAN_ServiceDescription="Allows access to management information from local and remote machines." WEC_ServiceDisplay="Windows Event Collector" WSMANOOB_WEC_ServiceDescription="Collects software and hardware events from local and remote machines." ADAMSP1NotInstalled="Setup cannot continue because Active Directory Application Mode Service Pack 1 is not installed. See KB929226 for details. (More info on KB 929226 at http://support.microsoft.com/?kbid=929226)" ADFSNotInstalled="Setup cannot continue because Active Directory Federation Services is not installed. See KB935449 for details. (More info on KB 935449 at http://support.microsoft.com/?kbid=935449)" WindowsIdentityFoundation_Culture="en" WIF_Prereq_Failure="Update cannot be installed as Windows Identity Foundation is not installed already."[LinkItems.Create.Uninstall][DeleteFilesInUninstallSections] "SystemRoot\%URTVERSIONDIR%.delete.files","ToGac.exe" "SystemRoot\%URTVERSIONDIR%.delete.files","SetRegNI.exe" "SystemRoot\%URTVERSIONDIR%.delete.files","netfxupdate.exe"[GlobalRegistryChanges.UnInstall][Add.Reg.Uninstall][Configuration] noPNPfiles=1 InstallationType = Hotfix InstallLogFileName = %SP_SHORT_TITLE%.log UnInstallLogFileName = %SP_SHORT_TITLE%Uninst.log UnInstallDirName = $NtUninstall%SP_SHORT_TITLE%$ EventLogKeyName = NtServicePack EventLogDllName = spmsg.dll[PreRequisite.Uninstall][SP1QFE.SP1Check.Section] EqualOp = CheckReg, HKLM, SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322, SP, 0x10001, "==", 1[Microsoft.net.framework.v1.1.4322.Files] system.web.mobile.dll,SP2QFE\system.web.mobile.dll system.web.dll,SP2QFE\system.web.dll aspnet_wp.exe,SP2QFE\aspnet_wp.exe aspnet_isapi.dll,SP2QFE\aspnet_isapi.dll aspnet_filter.dll,SP2QFE\aspnet_filter.dll[CopyAlways.Microsoft.net.framework.v1.1.4322.Files] togac.exe,SP2QFE\togac.exe setregni.exe,SP2QFE\setregni.exe netfxupdate.exe,SP2QFE\netfxupdate.exeand kb3037572_update\branches.inf[Version]Signature="$Windows NT$"FileVersion=5.2.1.7[FileBranchInfo]RTMGDR="%RTMGDR_NAME%",RTMQFERTMQFE="%RTMQFE_NAME%",SP1BTASP1BTA="%SP1BTA_NAME%",SP1RC1SP1RC1="%SP1RC1_NAME%",SP1RC2SP1RC2="%SP1RC2_NAME%",SP1RTMSP1RTM="%SP1RTM_NAME%",SP1GDRSP1GDR="%SP1GDR_NAME%",SP1QFESP1QFE="%SP1QFE_NAME%",SP2BTASP2BTA="%SP2BTA_NAME%",SP2IDXSP2IDX="%SP2BTA_NAME%",SP2RC1SP2RC1="%SP2RC1_NAME%",SP2RTMSP2RTM="%SP2RTM_NAME%",SP2GDRSP2GDR="%SP2GDR_NAME%",SP2QFESP2QFE="%SP2QFE_NAME%",SP2QFE[Strings]BUILDTIMESTAMP = "20150220.175757"RTMQFE_NAME = "RTMQFE"RTMGDR_NAME = "RTMGDR"SP1BTA_NAME = "SP1BETA"SP1RC1_NAME = "SP1RC1"SP1RC2_NAME = "SP1RC2"SP1RTM_NAME = "SP1RTM"SP1QFE_NAME = "SP1QFE"SP1GDR_NAME = "SP1GDR"SP2BTA_NAME = "SP2BTA"SP2IDX_NAME = "SP2IDX"SP2RC1_NAME = "SP2RC1"SP2RTM_NAME = "SP2RTM"SP2GDR_NAME = "SP2GDR"SP2QFE_NAME = "SP2QFE"

Is there a way to "test" a Server03 patch on an XP system? I'm trying to run three dotNET1.1sp1 patches for Server03sp2 on XPsp3 (with OnePiece-AIO + POSReadyAddon. The .NET1.1 patches are the old fashioned type-1 inf installers. The installer checks and announces that the target system OS is wrong. (That's funny because the type-2 msi installers for .NET 2, 3, 4 all install and verify on XP, even though some are Server03. As shown above, some are also POSReady.) Because they regular inf installers, DXUPAC will build an Addon to integrate. DXUPAC worked fine and I tried that as a work around, i.e. built a usb ios and ran setup. While installing I get two message box -- first is red(X) "aspnet_regiis.exe unable to locate component. This application has failed to start because MSVCR71.DLL was not found. Reinstalling the application may fix this problem." I included YumeYao's addon for VC runtimes, but it's not a running system yet, so I'm guessing VC runtimes are probably not included or registered during install. The system installation finished without any other hitch -- and ran just fine. I ran MS .NET Framework Setup Verification Utility at it reported .net1.1 was installed and functioning properly. So, maybe the workaround worked? I don't know. Also maybe the installer for the patch needed to run aspnet_regiis.exe which needed to access MSVCR71.dll. When I checked my running XP system, with OnePiece AIO which has .net 1.1sp1, and run > RegSvr32 MSVCR71.DLL, it reports that the file is loaded, but cannot be registered because no entry point was found. The MS .NET Framework Setup Verification Utility verfies that .Nets are all working, inspite of MSVCR71.dll not being registered. Does anyone have any suggestions on how to run an 03 patch for .net1.1 on an XP? Maybe tweak the inf on the system check? The three patches for .NET 1.1sp1 areKB2972207 http://download.microsoft.com/download/F/7/4/F74A5D79-02BD-428B-9B1E-7F5486B604F3/WindowsServer2003-KB2972207-x86-ENU.exeKB2978114 http://download.microsoft.com/download/F/7/8/F785E548-A947-4D47-BDE9-B91DEFCF0296/WindowsServer2003-KB2978114-x86-ENU.exeKB3037572 http://download.microsoft.com/download/C/5/4/C54DF342-AF8A-412D-93FD-36FAFC61FE84/WindowsServer2003-KB3037572-x86-ENU.exeThanks

I didn't save my log file since I saw my error, but my experience (and ignorance) may help in the design of your beautiful program. Being noob, I usually try default settings first. I'm installing XPsp3. Drives are SATA 3 but like most user I don't like AHCI (long story I don't want a discussion on that point). The Grub4Dos default position 1 is something like "Autodetect for SCSI/RAID/SATA drivers." (Technically they are AHCI drivers, my SATA hdds are faster for my applications using std emulation instead of AHCI.) So, anyway I went with the default. Obviously, I didn't add any F6 drivers to my source. There were messages like, Cannot find /JMInsDRV.DLL -- found JRAID_F.INF, copying JMIns.dll, error cannot find /JMInsDRV.DLL and then the installation hangs. Then I realized maybe by SATA you meant AHCI. Also, I'm older, so it would be nice if there was a way to toggle a pause/continue button or hotkey tp hold the screens so that I could read them. My notes say, Setup tries to continue but complains "Setup cannot install JMInsDrv.dll" ESC to skip file, but skipping ends up in a loop. It would be nice if there was a little edit window in the program, where user could resort and rename setup programs. So instead of having default position 1 being Autodetect SCSI/RAID/SATA drivers, and position 2 (too fast, I couldn't read it), and position 3 being Windows XP sp3 AIO v106 with post-EOL Addon or whatever Text mode, Gui mode etc., allow user to select which setup gets moved to default top position, and let him move SCSI/RAID/AHCI to the bottom if he doesn't have them. Anyway, I'm sure you get the idea. Not that it may not already be on the back burner, but low priority. I have both Intel and JMicron SATA on my mobo, so I was miffed when JM drivers started popping up. I was wondering how did they get into my source?? Then I realized that the program must have added them, and searched for them. Highest regards!! It's a wonderful program!! Thanks

Below (in code box) is my list of the .NET Framework patches for my XP post-EOL. I ran them in manually without any problems on a fresh XPsp3 source (English) integrated with OnePiece AIO v106 and an addon made from post-EOL patches for XP Embedded (regular patches POSReady used to build Addon -- KB2926765, KB2939576, KB2957509, KB2961072, KB2989935, KB2991963, KB2993254, KB2998579, KB3004361, KB3011780, KB3019215, KB3020338, KB3020393, KB3021674, KB3023562, KB3033395, KB3033889, KB3033890, KB3039066, KB3046482, KB3055973, KB3049874, KB3065822, KB3065979, KB3067903, KB3069392, KB3070102, KB3072630, KB3072633, KB3074886 (included in DL folder for KB3605822), KB3079904). The .NET patches below installed without any registry changes, like those given by Harkaz in post #1. (i.e. No need to spoof XP Embedded, as needed to use Windows Update.) I used Aaron Stebner's (or MS?) tool, .NET FRAMEWORK SETUP VERIFICATION TOOL to verify. (netfx_setupverifier.exe in netfx_setupverifier_new.zip linked from http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx) KB MS date filename XP Embedded Other OS -- replacesKB2932079*(MS14-026, 05/13/14) NDP20SP2-KB2932079-x86.exe XP Embedded, Server 2003 sp2 -- none -- *replaced by KB2978124KB2931365*(MS14-026, 05/13/14) NDP40-KB2931365-x86.exe XP Embedded, Server 2003 sp2 -- none -- *replaced by KB2978125*the above replaced -- thanks heinogandaKB2894843 ( -- , 09/09/14) NDP20SP2-KB2894843-x86.exe XP Embedded, Server 2003 sp2 -- KB2656352 (MS11-016)KB2972214 (MS14-053, 09/09/14) NDP20SP2-KB2972214-x86.exe -- Server 2003 sp2 -- KB2898856 (MS14-009), KB2833940 (MS13-052)KB2973115 (MS14-053, 09/09/14) NDP30SP2-KB2973115-x86.exe -- Server 2003 sp2 -- KB2756918 (MS13-004)KB2894842 ( -- , 09/09/14) NDP40-KB2894842-v2-x86.exe XP Embedded, Server 2003 sp2 -- KB2901110, KB2656351KB2972215 (MS14-053, 09/09/14) NDP40-KB2972215-x86.exe XP Embedded, Server 2003 sp2 -- KB2898855 (MS14-009), KB2835393 (MS13-052)KB2972105 (MS14-057, 10/14/14) NDP20SP2-KB2972105-x86.exe XP Embedded, Server 2003 sp2 -- KB2633880 (MS12-016)KB2979574 (MS14-057, 10/14/14) NDP20SP2-KB2979574-v2-x86.exe XP Embedded, Server 2003 sp2 -- noneKB2972106 (MS14-057, 10/14/14) NDP40-KB2972106-x86.exe -- Server 2003 sp2 -- KB2633870 (MS12-016)KB2979575 (MS14-057, 10/14/14) NDP40-KB2979575-v2-x86.exe -- Server 2003 sp2 -- noneKB2978124 (MS14-072, 11/11/14) NDP20SP2-KB2978124-x86.exe -- Server 2003 sp2 -- KB2932079 (MS14-026)KB2978125 (MS14-072, 11/11/14) NDP40-KB2978125-x86.exe -- Server 2003 sp2 -- KB2931365 (MS14-026)KB3037577 (MS15-041, 04/14/15) NDP20SP2-KB3037577-x86.exe -- Server 2003 sp2 -- KB2901111 (MS14-009)KB3037578 (MS15-041, 04/14/15) NDP40-KB3037578-x86.exe -- Server 2003 sp2 -- KB2901110 (MS14-009)I used KB2931365 above (not KB2938708). Both issued on same date. Both NPD40. But former is specified as XP Embedded latter as Windows7, Server08.KB2938780 ( -- , 05/13/14) NDP40-KB2938780-x86.exe Windows 7sp1, Server 2008 R2 sp1 -- replaces KB2633870 (MS12-016)The OnePiece AIO has .NET 1.1sp1 installed. Sadly, the following patches refused to install, claiming "Version of Windows does not match."KB2972207 (MS14-053, 09/09/14) WindowsServer2003-KB2972207-x86-ENU.exe Server 2003 sp2 -- KB2898860 (MS14-009)KB2978114 (MS14-072, 11/11/14) WindowsServer2003-KB2978114-x86-ENU.exe Server 2003 sp2 -- KB2931352 (MS14-026)KB3037572 (MS15-041, 04/14/15) WindowsServer2003-KB3037572-x86-ENU.exe Server 2003 sp2 -- KB2901115 (MS14-009)The XP Embedded list was made by going to https://catalog.update.microsoft.com/v7/site/Home.aspxand putting "XP Embedded" in the search box. Then go thru 6 pages and select ADD for any .NET update. MS creates a local folder for selected patchs and downloads files into them. Each XP Embedded patch for .NETxx comes with a second "cleanup" file. It has various names. AMD64_IA64_X86-all-msipatchregfix-x86_94a84b80b8b45a1ac53a0e5d085513da0f099655.exe but the size is 130,600 bytes and date is 10/23/2012. Does anyone know what it does, or if it should be run manually after each patch, or just be present in the folders from which each patch in run, or simpley run once after all patches are done, for a final cleanup, or just ignore it? Also, are there any unattended switches that can be used with these installers to accept EULA and etc. and run the patches from a batch file? Thanks to ALL!

thanks HarryTri and Ponch the repair suggested by Ponch for Win7 worked I just renamed the reg entries as suggested, removed 500M of internet and mail cache from documents and settings, administrator, local settings, application data, mozilla etc and rebooted, and as least that system is back well almost the Firefox browser got updated, and now when FF downloads nirsoft utilities, it sends them to some devnul somewhere -- claims it has virus program -- problem is, I don't have any antivirus installed, and windows security AV is turned off. so that's a Firefox topic big thanks! ==EDIT== in addition to installing a new FF browser, it also installed a program in the Quick Start area of the taskbar, which I had never seen or downloaded -- Lightscribe -- an old HP program. when I right clicked it it gave an explanation and a link, which looked very simple, www.lightscribe.com but which is longer valid -- so I'm clueless how that got in quickstart on the new admin profile. the shortcut to the quickstart lightscribe was not found in C:\Documents and Settings\[uSERNAME]\Application Data\Microsoft\Internet Explorer\Quick Launch, so I assume it was coming from somewhere else