Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Leaderboard


Popular Content

Showing content with the highest reputation since 12/17/2017 in Posts

  1. 10 points
    I finally managed to get also new versions of Basilisk work on windows NT 4.0 with my kernelex, now they work new versions of firefox too (up to 52.0 for now). The first release will be in the fist term of July.
  2. 7 points
    NEWS. the project is alive and I have managed to get some new browsers to work, even if I had to edited something to the pe file. Now it works (even if a little buggy): k-meleon by roytam (they work even video at 1080p on youtube but there is no audio), palemoon by roytam, seamonkey 2.33.1 and firefox 36.0... I decided to rewrite all and add the apis into the original dlls using code caves (no more api wrappers). I will release the first release in a month, for now I post some images:
  3. 6 points
    to fix recaptcha issue: for PM27 users: 1. goto about:config, add new Boolean value named "dom.messageChannel.enabled" and set it "true". 2. reload the page that has recaptcha next PM27 build will address it.
  4. 6 points
    New Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180121-4b2c1b329-xpmod.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180121-4b2c1b329-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win64-git-20180121-4b2c1b329-xpmod.7z Official repo changes since my last build: - Collapse notification bar in fullscreen (c1bcdecae) - Removed "on Windows" from comment (e335a9f6f) - Merge pull request #1576 from SpockMan02/master (f4444d4f2) - Remove WebRTC - Part 1: Configure (ccbc20a0f) - Added function for a showTabPreviews pref (10d74de4d) - Added checkbox for showTabPreviews (46f6b0ae5) - Added browser.ctrlTab.previews pref (951495c63) - Added label for showTabPreviews (295aee74e) - Removed unnecessary showTabPreviews function (2dd6ae6d4) - Remove WebRTC - Part 2: Remove all WebRTC files that are not depended upon by the rest of the build system (b16a33e19) - Merge pull request #1583 from binoc-central/webrtc-sec (08263752a) - Made showTabPreviews checkbox string less hand-holding (d208ead3c) - Merge pull request #1582 from SpockMan02/master (d9292ecaf) - Adjust the theme to account for natural border width rounding. (afa34c7a6) - Version bump (new cycle) (7f021126b) - Remove extraneous "tab". (fb9110941) - Implement ES6 22.1.3.31 Array.prototype[@@unscopables] (ee9d53abb) - Add Eyedropper to the app menu (9b2f63ec2) - Merge pull request #1589 from janekptacijarabaci/devtools_appmenu_eyedropper_1 (b5709d37b) - Add check for Windows 8.1 version (bdaa898f7) - Perform an `XCTO: nosniff` check only for 2xx responses (394350218) - Don't use transparency optimization for theme items in Windows 8 or later with a high contrast theme in use. (3dc0774f7) - Shut up rpmlint (73983c688) - Merge pull request #1593 from JustOff/PR_nosniff_2xx_only (538dfb780) - Don't style the menu bar items unless we don't have a compositor. (b8c009079) - Issue #1595 part 1: Remove Vista checks in XPCOM (f6c1a6b46) - Issue #1595 part 2: Remove Vista checks in /hal (723e8aed0) - Issue #1595 part 3: Remove Vista checks in DOM (8c4c48d34) - Issue #1595 part 4: Remove Vista checks in JS and XRE (d6e790af7) - Issue #1595 part 5: Remove Vista checks in Windows widget code (7c0acbff8) - Issue #1595 part 6: Remove Vista check in Windows DLL blocklist (e6294019c) - Issue #1595 part 7: Remove Vista checks in /gfx (4b2c1b329) My changes since my last build: - Reverted changes in Issue #1595
  5. 6 points
    Well Guys...I hope you enjoy Happy Holidays Modern Aero: Black Win10_Modern_Black.zip Modern Aero: Capri Win10_Modern_Capri.zip Modern Aero: Cyan Win10_Modern_Cyan.zip Modern Aero: Grass Win10_Modern_Grass.zip Modern Aero: Gray Win10_Modern_Gray.zip Modern Aero: Green Win10_Modern_Green.zip Modern Aero: Marine (Blue) Win10_Modern_Marine.zip Modern Aero: Orange Win10_Modern_Orange.zip Modern Aero: Pink Win10_Modern_Pink.zip Modern Aero: Purple Win10_Modern_Purple.zip Modern Aero: Red Win10_Modern_Red.zip Modern Aero: Yellow Win10_Modern_Yellow.zip Modern Aero: White Win10_Modern_White.zip
  6. 5 points
    So just replacing bitmap while keeping same layout is just boring. What about putting Beta boot screen into retail? cross post from betaarchive: I think I found the position that sets progress bar and scrolling bar: NTOSKRNL.EXE 5.0.2195.7376, CHT, 1,691,648 bytes File Date: Thursday, 18 February, 2010, 20:17:26 SHA256: 86356E3BB6DB3E873AE8C881358233F5CD142EC2CEDF34D7B007B427CE085394 .text:0041D14A loc_41D14A: ; CODE XREF: sub_41CFF6+14Aj .text:0041D14A push 1B5h .text:0041D14F push 112h .text:0041D154 call sub_41CDAC .text:0041D159 push offset loc_41D1F4 .text:0041D15E mov dword_476070, 1A0h .text:0041D168 mov dword_47606C, esi .text:0041D16E mov dword_476000, 280h .text:0041D178 mov dword_475F40, 0Ah .text:0041D182 call InbvInstallDisplayStringFilter Y = 0x1B5=437, X = 0x112=274 is progress bar starting location Y= dword_476070 = 0x1A0 = 416 X = dword_47606C = esi = 0 W = dword_476000 = 0x280 = 640 H = dword_475F40 = 0x0A = 10 is scrolling bar location. but there is difficulty on setting dword_47606C, since "mov dword_47606C, esi" is 4-bytes shorter than others. -- so hacking around it is working! (VA)0x41d14a: 68 b5 01 00 00 push 0x1b5 e9 6d 29 04 00 jmp 0x45fac1 be a0 00 00 00 mov esi, 0xa0 /* it is 0x41D154 here */ (VA)0x45fac1: 68 21 01 00 00 push 0x121 e8 e1 d2 fb ff call 0x41CDAC e9 84 d6 fb ff jmp 0x41D154 that splits call to sub_41CDAC into half, pushing X value goes to 15-bytes spaces at 0x45FAC1, call 0x41CDAC can jumps back to 0x41D154 for making a space to set ESI. Thanks http://shell-storm.org/online/Online-Assembler-and-Disassembler/ for a flexible-enough online assembler.
  7. 5 points
    Because he couldn't care less. Then again, we have @roytam1's PM mods already, which do work fine, and he's committed to keep 'em coming and to give 'em support... reason enough, IMO, for us all to ignore moonchild, instead of caring for what he thinks/wants/will actually do. My 2¢, of course.
  8. 5 points
    Here's the patch that can be applied on top of latest revision of Rufus source code to restore Windows Vista support and the executable (version 3.1.1321). I experienced strange bug where the code that is supposed to prevent DLL sideloading causes UI elements to lose Aero look and reverts to classic, so the patch removes that. The mitigation doesn't have much value IMO, if you're worried that the program will load malicious DLL from its folder, then you've already lost by getting such DLL in the first place. Still, the relation between UI look and the DLL search directory is odd. At first I thought older version of comctl32.dll was getting loaded, that's not the case though. Calling SetDefaultDllDirectories does it. It's one of those functions that were added with an update and the issue appears to be exclusive to Vista. Unless there's a separate update addressing that.
  9. 5 points
    Don't you do your own backups? I have completely shunned the cloud and yet - amazingly - I haven't lost any data since 1976 (though I admit that some of it is on punch cards and mag tape, which I never transferred into the PC environment). As far as files on my computer go, my oldest Word document in my Documents folder is from 1990 (which is when I started using Word). Never once have these documents been "on the cloud". You cannot espouse advantages of "cloud" computing - which differs from traditional computing with networking in one key point, you don't have control of the communications - because there simply are no advantages for users. The only advantages are for those who would seek to profit from handling your data. Surely you don't believe in a free lunch. The oldest program in my BIN folder is dated 1986, which is when I started accumulating useful applications. It no longer runs on my host system since it's a 16 bit application. However, to this day I still run the NT CLOCK32.EXE application, which is dated late 90s, on my desktop 24/7. Why? Because it accomplishes its purpose (showing me the time and date) with almost no resource consumption. The executable is a whole 42 kBytes in size. My point? There is no reason to believe that "newer is better" when it comes to software. People aren't any smarter than they were decades ago. If anything, they lack the wisdom and prowess people had to develop when computing was more expensive and difficult, and they weren't distracted by their damned phones all the time. -Noel
  10. 5 points
    Not at all. It's a sad day. Every time a technology that gives one a hardcopy of what one buys dies is a time some of our collective freedom is lost. You must understand one has a book or a CD/DVD with a .pdf, or with music, or whatever, one owns that... one has a text into kindle or a music in iTunes one got nothing, and it can be taken from one anytime with little or no explanation and no money back, because one had previously given them the right to do it, when buying that. Ever heard of the memory hole?
  11. 5 points
    Server crashed badly. They couldn't retrieve data from second (backup) HDD'a. We lost data for last 3 months. Luckily i had local backup from Februar. I apologize for the inconvenience caused.
  12. 5 points
    So Windows 10 really is a nightmare. It has wasted way too much of my time since installing it. Windows as a service, turns out to be Windows as 'your' servitude. The license agreement basically states that your hardware will be controlled by microsoft as long as you run their software. So if they are using my hardware as their surveillance system, and I have to maintain it for them when they keep forcing updates that break stuff, then shouldn't they be paying me? Personally, I think they are in some very gray territory legally. Really, I think they are way beyond grey. What they are doing is illegal in a dozen different ways at least. But the courts seem to be behind them, as the courts have been siding with corporations who have precluded class action lawsuits through their licensing agreements. The courts allowing licensing agreements to rule out class action lawsuits is basically a license for the corporations to get away with just about anything, no matter how shady. Because individual lawsuits will generally lack the financial and legal fortitude to go up against giants, and in those rare cases that they do, the cost of a settlement for the giants will be negligible and will not serve to curb their practices in any significant manner. Another thing that really makes me wonder too, is how shady are the enterprise licensing agreements. I have not gone through them in great detail. I mean currently in enterprise, it is possible to disable telemetry (which actually only sets it to a minimal level, so the setting of 0 is a bit misleading). It is also possible to redirect all telemetry data internally - though again, that does not really account for all telemetry, only some forms of telemetry. To really shut down all telemetry and gain complete control of updates is entirely possible, but it is also a lengthy and convoluted process which is liable to break some things, and seems intentionally designed to make it possible for admins who are not extremely thorough to miss something. The question though, is do the enterprise license agreements guarantee these 'features' of being able to control the software's penchant for phoning home? Just because the software allows these customizations at present, is there any guarantee that it will do so after the next update? Seems like some enterprises may be lulled into a false sense of security, by Microsoft including the ability to manage and control services, task schedules, logging, and set group policies according to their needs, rather than Microsoft's agenda. But is there any legally binding promise from Microsoft that such functionality will be supported in the future? Seems like a massive trap to me, and smart enterprises would probably do better to seriously look into other OSes at this point. I wish some of the big players would pour some resources into bringing ReactOS to maturity. That could be brilliant. It also seems to me that other companies who are supporting Microsoft's push for world domination, like Adobe, nVidia, Intel, Wacom, Lenovo, Dell, Etc.. Should really think twice at this point, because the moment MS doesn't need them anymore...
  13. 4 points
    Features: - Install Windows 2k/XP/2003/2008/2012/Vista/7/8.x x86/x64 - Practically runs even on the most minimalistic WinPE - Choose able drive letter for the new Windows installation - Install Windows also if nlite/vlite has remove winnt32.exe/setup.exe - Integrate Drivers: normal PNP and Textmode Drivers also - patch uxtheme to allow unsigned Themes - Some tweaks - Support "Windows to Go" for Windows 7 and later installs - Supports WimBoot option for Windows 8.1 Update 1 - supports all current WIM files: WIM/SWM (XPRESS / LZX / XPRESS HUFFMAN = Wimboot compression) - supports unencrypted ESD files (LZMS compressed WIM) Not Supported: - No Windows embedded version (this includes WinFLP) - No Installation onto USB disk *New* only Windows 7 and later - No upgrades of existing installations As some may know the last version 1.5 had only Support for Win 2000/XP/2003. Fujianabc present an very easy approach to install Windows 7 NT 6.x fast installer basically it's simply applying the windows image from install.wim and generating the boot files. He also discovered that the drive letter of a Windows 7 image can be (opposed to Vista) easily changed. So I have added that way of installing to WinNTSetup. For the driver installation: Every driver added in NT6.x windows will be added to the driver store. So it's not recommended to add countless driver, but rather more really required ones. NT5.x massstorage driver integration is possible thanks to Mr dUSHA powerful MSSTMake.exe tool To the Unattend option: It's possible to use an unattend.xml to run the Setup unattended. But as the actual WinPE Setup Phase isn't effective in that way of install, all Winpe related settings inside the unattend.xml won't be applied. Ini config file It's possible to save all GUI-settings to a ini file: push Ctrl + S to save all settings to an ini. push Ctrl + L to load all settings from an ini. A WinNTSetup.ini file in the same dir as the app itself will be loaded automatically at startup. It also can be selected via command line: WinNTSetup.exe /cfg:"C:\mysettings.ini" more command line options To install Windows in a VHD file: - requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source - create a partitioned VHD and assign a drive letter (push Ctrl + Shift + V to use build in diskpart wrapper for this) - select the VHD drive as installation drive (make sure you boot drive ist a active primary partition on a physical disk) If you get an Antivirus warning from your AV software, please report it to them as a false positive and let them check it. Current Version: 3.9.2 WinNTSetup3.rar
  14. 4 points
    The latest Zeranoe xp-compatible build was ffmpeg-20150525-git-8ce564e, released on May 2015. After that, people started complaining about the following error: "The procedure entry point _wfopen_s could not be located in the dynamic link library msvcrt.dll". On the official Zeranoe FFmpeg Builds site, it says that "All builds require at least Windows 7". So, I took a look at the code and I noticed that FFmpeg code itself has not stopped being XP compatible, but the inclusion by Zeranoe of some external libs that are either themselves by default not compatible or have become incompatible at some stage of their development is what broke Zeranoe builds. Anyway, many external libraries and codecs are still compatible with XP, they just need to be tweaked correctly, just like MSYS2 did, in fact I used their project to compile ffmpeg with GCC and, as result, the build is updated and XP compatible. FFMpeg 2017 x86 - Windows XP, WIndows Vista, Windows 7, Windows 8, Windows 8.1, WIndows 10 Compatible https://mega.nz/#!Od9DRD5R!ynjjY9uHzLM6UYLZl5xFMxQ1gnkPZxbmcCvGr9fuAvk Happy new year.
  15. 4 points
  16. 4 points
    Thank you for fixing it for older OSes (especially Vista)! Added to the list. You can link to its Sourceforge page now. The author accepted my modifications and the program is now at version 2.1.5.1.
  17. 4 points
    Hi. I would advise you to include the following software in the list: https://www.novirusthanks.org/products/osarmor/ Very good for your Security Setup. TH.
  18. 4 points
    It's a tough spot for sure. It's one guy working on the project, and we only have to pay once for a lifetime license. The last update came out superquick, but overall they've been slow to come out. It's too bad MS messes with the OS so much, that it takes BigMuscle month's to fix aeroglass to work with the new version. Hopefully 1.5.9 comes out soon, but I understand why the updates take so long.
  19. 4 points
    I had been otherwise occupied all day long, so only recently skimmed through the numerous MSFN e-mail notifications on this subject... My input: Moonchild wrote: Really? English is not my mother tongue, but doesn't "should continue" imply they are currently able to run on Vista? This is the furthest thing from the truth! Lots of places inside their forum; I did a quick search and I came up, amongst others, with: https://forum.palemoon.org/viewtopic.php?f=1&t=15806 This was when Moebius/UXP-T1 was forked from a Mozilla Platform 53.0a1 code snapshot; that snapshot was already devoid of any residual XP/Vista OS support, as the good () guys over at Mozilla had already excised all relevant code... MC team did absolutely nothing to restore at least partial Vista support... https://forum.palemoon.org/viewtopic.php?p=114825#p114825 https://forum.palemoon.org/viewtopic.php?f=61&t=18253 (Basilisk and Windows Vista; I urge you to read the entire thread , but I've selected the following part:) Officially released Basilisk 55.x.x.x was never compatible with Vista; by pure luck (or negligence on their part), the compiler flags were such that lowering the subsystem value of the executables (6.1 -> 6.0) would allow for them to run on the Vista kernel, but OS integration was suboptimal; non-existing code targeting Vista resulted in WMF (and possibly other parts, e.g. EME, aka Widevine DRM plugin) being broken! https://forum.palemoon.org/viewtopic.php?p=132054#p132054 And when in the start of spring this year they ditched Moebius in favour of UXP-T2 (now just UXP), they forked a Mozilla 52 ESR platform with full XP+Vista support and what was the first thing they did? Meticulously removed all that support (as it's always easier to delete existing code than write new one...). Are we to believe that MC has just now had a sudden change of heart and he's willing to devote precious coding time to undoing the Vista massacre? I'm not that gullible... What's worse, in official Basilisk 52 + Pale Moon 28, they have amended their compiler flags/optimisations to fully ignore NT 6.0 (Vista/Server 2008); this has been already documented previously in this thread by esteemed member @WinClient5270, but it was also the result of my own tests weeks ago, when the first official builds were publicly released... Unfortunately, it's more than those... Inspecting latest (official) PaleMoon_unstable-28.0.0b1.en-US.win32[buildID=20180625093249] package with dependency walker, I am disheartened; focusing on just xul.dll module, this has calls to 6 missing functions in kernel32.dll GetCurrentProcessorNumberEx K32EnumProcessModules K32GetModuleFileNameExW K32GetProcessImageFileNameW K32GetProcessMemoryInfo K32QueryWorkingSet and to 2 missing functions in shell32.dll SHGetPropertyStoreForWindow SetCurrentProcessExplicitAppUserModelID Main executable (palemoon.exe) has lesser issues, of course I wasn't bothered to check other DLLs... Similar results are obtained with official Bk52 releases... And I emphasise again, it isn't only compilation configuration that needs to be changed to target Vista, it's actual browser code that needs to be rewritten to accommodate a fully functional, Vista compatible, application... Will Moonchild deliver? I think not... (and until PM 28 "stable" gets released in the final quarter of 2018, Vista user-base will have dropped even lower to merit his support considerations...) @WinClient5270, if memory serves right, I recollect you having registered previously in the Pale Moon forums (about an issue with Visual Studio 2013 dlls affecting PM 64-bit, that I had identified for you...); perhaps the best way to clear the FUD once and for all would be to post in the linked thread (by Jody) and ask plain and simple what MC's definitive decisions are; not his thoughts/intentions, but if he's actually determined to support Vista in PM28 (at least in the same level he supported Vista in PM27); please don't hesitate to convey some of my reservations/points I raised here ; full WMF+MSE support on both 32-bit/64-bit Vista architectures would be a must; UXP (unlike Tycho) is suitable for that, if they're willing to undo the damage they did to it concerning Vista; these days, noone wants a browser that won't play back embedded audio-visual content... Here's hoping...
  20. 4 points
    Well, considering that: Windows Embedded Standard 2009, Extended Support will end on Jan. 8, 2019. Windows Embedded POSReady 2009, Extended support will end on Apr. 9, 2019. ...it does make sense. That's not to say we'll give up on XP so soon, of course!
  21. 4 points
    Links to various updates released from February 2018 until today (WES09/POSReady 2009 - English, IE8 - English, .NET Frameworks 2.0SP2 and 4 - international, Office 2003, Office 2007 Compatibility Pack and Office 2007 Suites - international) February 2018 http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/windowsxp-kb4034044-x86-embedded-enu_2eed2f8234cf7d6326ece957d4309979faf9d84a.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/01/windowsxp-kb4057893-x86-embedded-enu_678a583e6a1bd73beaccb0982f63bdd7dde328ff.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/01/windowsxp-kb4074603-x86-embedded-enu_4ee294a0f000172f98d1ccfa36bcf5d2070d248b.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/01/windowsxp-kb4074836-x86-embedded-enu_b53b106764ca5f49e44e5b2fff52f5bdf86ebe01.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/windowsxp-kb4074852-x86-embedded-enu_ecec2f8f0b489288f47908cca24f6cf8815c383c.exe http://download.windowsupdate.com/d/msdownload/update/software/uprl/2018/01/windowsxp-kb4074837-x86-embedded-enu_7d231ab54a6f0b4d967d3165ee89f8e08dedaa65.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/ie8-windowsxp-kb4074736-x86-embedded-enu_0033d1ad522fa02ff9ba5d605e0de15efbb72c66.exe http://download.microsoft.com/download/0/6/8/06815E71-9425-4ED8-BEDD-A63C4C3088B6/office2003-KB4011703-FullFile-ENU.exe http://download.microsoft.com/download/7/4/0/740D9C11-FD23-4245-BC96-01BBF7E160AE/mso2007-kb4011715-fullfile-x86-glb.exe http://download.microsoft.com/download/7/3/2/732DB082-67ED-4D69-820E-9521AE75AC88/outlookloc2007-kb4011200-fullfile-x86-glb.exe March 2018 http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/02/windowsxp-kb4056564-x86-embedded-enu_c425b71ca28f40befda2bf7435c4be394db32dfe.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/02/windowsxp-kb4087398-x86-embedded-enu_a20bce534494db1303efeff6f2abae8cb15f4861.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/windowsxp-kb4089082-x86-embedded-enu_56a4c587452f40f8e91f3192168f4cf1193e801c.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/windowsxp-kb4089175-x86-embedded-enu_1caf7f6ec0b27d38070eb0385f1548776bc65e6d.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/02/windowsxp-kb4089344-x86-embedded-enu_d38ccd66b4806b48fde45d75c7faa13df5d5c696.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/02/windowsxp-kb4089453-x86-embedded-enu_203d8aefdce6f5cdef4c0bc11a259395316b4714.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/02/windowsxp-kb4089694-x86-embedded-enu_f0698bdbb2c0dbaf56d7c4071061046865ec3526.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/03/ie8-windowsxp-kb4089187-x86-embedded-enu_792b4bd87dd3b8dbdd1767ffba210245a6638b04.exe http://download.microsoft.com/download/4/C/7/4C794678-568D-4947-942C-1B2102C1E9A9/wordconv2007-kb4011720-fullfile-x86-glb.exe http://download.microsoft.com/download/2/2/4/224AD805-7123-4949-9B18-D40DE64C6EED/excel2007-kb4011714-fullfile-x86-glb.exe http://download.microsoft.com/download/A/4/5/A45A8629-BB86-42DF-BEE0-9EBF8C269201/word2007-kb4011721-fullfile-x86-glb.exe April 2018 http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/03/windowsxp-kb4091756-x86-embedded-enu_4084e5a3bf76e0a22d8d33b0c5e8ff3b57e3faf3.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/03/windowsxp-kb4093223-x86-embedded-enu_3f5c77a133aaed66cb1dc3ffc1e60f2c61e12b52.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/03/windowsxp-kb4093224-x86-embedded-enu_832d011a2a213068c5438096b970c4ab7e830744.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/03/windowsxp-kb4093257-x86-embedded-enu_9c72fc51be7a7eb68e2c603b309a9c0163949cb8.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/04/windowsxp-kb4101864-x86-embedded-enu_26071c559b2766e6b0af5434429d2dcddd9d96db.exe http://download.windowsupdate.com/c/msdownload/update/software/uprl/2018/04/windowsxp-kb4093753-x86-embedded-enu_c554500ebc189c5467ebc83183ae7e6216133290.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/04/ie8-windowsxp-kb4092946-x86-embedded-enu_9d0680649223cca2f9f779026af3cb1d01a6cfcd.exe http://download.microsoft.com/download/7/7/B/77BB1461-9693-413C-9D32-982F15BFCEC7/wordconv2007-kb4018354-fullfile-x86-glb.exe http://download.microsoft.com/download/1/5/6/156FBC15-4A2F-47C3-8BA0-78C610A003D5/xlconv2007-kb4011717-fullfile-x86-glb.exe http://download.microsoft.com/download/3/C/4/3C4F04B1-24C6-4FEA-97AD-F84F1BF18EB8/excel2007-kb4018353-fullfile-x86-glb.exe http://download.microsoft.com/download/3/B/F/3BF141EA-A279-4056-B1BD-A004CE4EE600/word2007-kb4018355-fullfile-x86-glb.exe May 2018 http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/04/windowsxp-kb4056564-v2-x86-embedded-enu_964310efb26058c35b0233f008f8b5f6ffd102af.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/04/windowsxp-kb4089453-v2-x86-embedded-enu_23b1aec8d9e41242c20799e66045dc75c089df61.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/05/windowsxp-kb4101477-x86-embedded-enu_867ee71e20e05bcdcab83b86466ab20771f74ac5.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/05/windowsxp-kb4130957-x86-embedded-enu_dab532721ce76725b35909e6d95c9d430edc1e13.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/04/windowsxp-kb4131188-x86-embedded-enu_3b549e0eefed45285bd1f9fd87d168b09259ae34.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/04/windowsxp-kb4134651-x86-embedded-enu_ba2c6637491967e459b9f24b9939618dbcdc8978.exe http://download.windowsupdate.com/d/msdownload/update/software/uprl/2018/05/windowsxp-kb4130978-x86-embedded-enu_62fd7dad516fbe3c9c55e4f38db7f24f00b1666c.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/05/ie8-windowsxp-kb4103768-x86-embedded-enu_9faf1f4e5897354fcec0439149a928b2ac7b58cd.exe http://download.windowsupdate.com/d/msdownload/update/software/crup/2018/05/ie8-windowsxp-kb4316682-x86-embedded-enu_cc345109f94dd7b763cc415385974632a058fd07.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/05/NDP20SP2-KB4095516-x86_C5111BA0C2003141EE07C8CD75932E98F0D80948.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/05/NDP40-KB4095528-x86_169B199B7738982DF1DF89DC8951CF087695165A.exe http://download.microsoft.com/download/E/D/4/ED49C193-980B-4894-8814-40222F6B0EE9/mso2007-kb4018308-fullfile-x86-glb.exe http://download.microsoft.com/download/8/E/2/8E23AFC8-3FE3-4A61-9982-872E55BAFBBD/xlconv2007-kb4022150-fullfile-x86-glb.exe
  22. 4 points
    If someone installs the Aero Glass into Program Files, it is only his problem that it is not able to download and store the symbols. It has been said milliontimes that it mustn't be installed there and even the guide mentions "Important thing is that you must place all files in writable location (i.e. not in Program Files),, because DWM process does not run under user's credential. If you don't do this, Aero Glass will not be able to download symbols". Also the note about debug.log "if the verbose logging is enabled" was not probably too bold and underlined.
  23. 4 points
    Found XP running at the front desk at the local bowling alley. I tried several times to get a picture but my phone Reeeeeeeally does not like to focus on screens at a distance more than point-blank. (I will try again eventually) Heres the best I got: The little screens over by the lanes that show your score appear to be running MS-DOS. The first lane we tried to use was evidently having an issue:
  24. 4 points
    Updated the repository with 3 months of updates, including: All of the updates mentioned by @Ruan for November 2017, December 2017 and January 2018; Updated Extras folder with a better description of each update on a readme.txt file, a new timezone update and a dedicated folder for the .NET Framework 4.6.1 installer; Updated the readme.txt file at the root of the repository with updated info; Removed every superseeded update in the repository (from each month... It was a lot of manual labor). https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w Should be all. Vista lives on for another month
  25. 4 points
    only if you are running a Intel CPU that is based on integrated memory control you are vulnerable. That means anything that uses a FSB is safe. A lot of people don't understand that. 1st Gen Core means basically FSB cpus like Core 2 Duo. After that intel re branded their new architecture that used a integrated memory controller as 2nd generation core. I see a lot of people freaking out for zero reason. It irritates me so I am trying to educate. https://www.tweaktown.com/news/60411/heres-list-intel-cpus-affected-spectre-meltdown/index.html Intel® Core™ i3 processor (45nm and 32nm) Intel® Core™ i5 processor (45nm and 32nm) Intel® Core™ i7 processor (45nm and 32nm) Intel® Core™ M processor family (45nm and 32nm) 2nd generation Intel® Core™ processors 3rd generation Intel® Core™ processors 4th generation Intel® Core™ processors 5th generation Intel® Core™ processors 6th generation Intel® Core™ processors 7th generation Intel® Core™ processors 8th generation Intel® Core™ processors Intel® Core™ X-series Processor Family for Intel® X99 platforms Intel® Core™ X-series Processor Family for Intel® X299 platforms intel® Xeon® processor 3400 series Intel® Xeon® processor 3600 series Intel® Xeon® processor 5500 series Intel® Xeon® processor 5600 series Intel® Xeon® processor 6500 series Intel® Xeon® processor 7500 series Intel® Xeon® Processor E3 Family Intel® Xeon® Processor E3 v2 Family Intel® Xeon® Processor E3 v3 Family Intel® Xeon® Processor E3 v4 Family Intel® Xeon® Processor E3 v5 Family Intel® Xeon® Processor E3 v6 Family Intel® Xeon® Processor E5 Family Intel® Xeon® Processor E5 v2 Family Intel® Xeon® Processor E5 v3 Family Intel® Xeon® Processor E5 v4 Family Intel® Xeon® Processor E7 Family Intel® Xeon® Processor E7 v2 Family Intel® Xeon® Processor E7 v3 Family Intel® Xeon® Processor E7 v4 Family Intel® Xeon® Processor Scalable Family Intel® Xeon Phi™ Processor 3200, 5200, 7200 Series Intel® Atom™ Processor C Series Intel® Atom™ Processor E Series Intel® Atom™ Processor A Series Intel® Atom™ Processor x3 Series Intel® Atom™ Processor Z Series Intel® Celeron® Processor J Series Intel® Celeron® Processor N Series Intel® Pentium® Processor J Series Intel® Pentium® Processor N Series You are wasting your time even running tests. Cuz u dont get the bug. I plan on not even installing the patch on older systems,
×