Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Molecule

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

3,060 profile views

Molecule's Achievements



  1. 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!
  2. 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?
  3. 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!!
  4. 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
  5. @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
  6. @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
  7. @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 ...)
  8. 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 ...
  9. 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.
  10. 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
  11. 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 ...
  12. 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.
  13. 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!
  14. 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 ...
  15. 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

  • Create New...