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. 


Popular Content

Showing content with the highest reputation since 03/22/2017 in Posts

  1. 11 points
  2. 8 points
    So new build and new thread. Latest build is here: Binaries are moved to here: (I'm lazy to edit all previous posts) https://o.rthost.cf/palemoon/?sort=date&order=desc FAQ: Q: Can't play H264 clips? A: Download following packages for your browser edition(32bit/64bit) and extract DLLs to same place as palemoon.exe lives. 32bit LAV dlls are in separated package (extracted from K-Lite codec pack 13.5.5) https://o.rthost.cf/palemoon/lav.7z Just in case if you have an older processor which has no SSE instruction set support: 32bit NoSSE (ffmpeg 3.1.1 lite build) https://o.rthost.cf/palemoon/lav-dll-lite-mmx.7z 32bit No ASM (ffmpeg 3.1.1 lite build, if build above doesn't work on your processor) https://o.rthost.cf/palemoon/lav-dll-lite-noasm.7z 64bit LAV dlls are in separated package (LAV Filters 64bit 0.70.2) https://o.rthost.cf/palemoon/lav64.7z Q: VP9 Support? A: VP9 works if async MSE option is unchecked and "Enable MSE for WebM Video" checked in options. Q: Extensions/Themes not working after updating binaries. A: If you encounter extensions not show icon, clicking options button of extension causing browser unresponsive, etc. please try following actions: 1.a Killing palemoon.exe process 1.b Copy whole extensions folder out of profile folder (to somewhere else for example, desktop) 1.c Restart browser without restoring previous sessions 1.d Goto about:addons page 1.e Drop XPI files from the copied-out extensions folder to about:addonss page One-by-One. 1.f After all XPI files are dropped and installed/updated, restart browser Q: Virus detected? A: Tell your anti-virus program to exclude palemoon.exe and/or plugin-container.exe. Some anti-virus heuristic engines (for example symantec's sonar engine) is too sensitive to palemoon.exe/plugin-container.exe network activities. Q: Where's your patches for compiling my own? A: Please visit the link above "FAQ:". Latest source patch files are named "sources_patches_YYYYMMDD.7z" in that page. Q: How to change User Interface language? A: Please see this post: Q: Portable Loader? A: You can always use official portable launcher with my binaries, or you can use my simple portable loader written in NSIS: ------------------------------------- basilisk/UXP browser (MCP reforked 52.6ESR as new base): ------------------------------------- basilisk/moebius browser (deprecated by MCP, forked by me), and also 26.5 as playground : ------------------------------------- K-Meleon browser with Goanna/Tycho engine: It has its own sub-forum in K-Meleon official forum! http://kmeleonbrowser.org/forum/list.php?19 Latest build: Original cross-post is here: ----original post message belows---- Today's build with portable LAV libraries. Place LAV dlls (av*.dll) in same place as palemoon.exe lives. Official repo changes since my last build: -Clobber for Brotli/WOFF2 update -Fix some comments (no code change) -Enable Brotli content-encoding by default (https only). -Pull woff2 upstream update. -Update Brotli decompressor. My changes since my last build: - Upgrade Mozilla NSPR and NSS to 4.16 and 3.22 for (hopefully) faster AES operations 32bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win32-git-20171002_2-e68ab5b3d-xpmod.7z 64bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win64-git-20171002_2-e68ab5b3d-xpmod.7z
  3. 8 points
    Don't afraid. It was just an ironic note, because of users asking the same things over and over again and they still expect some answer although it has been covered milliontimes.
  4. 7 points
    But... but... then, why reply to this thread if all you have to say is "never used 1.0 to 9x/ME"? This is, hands down, the most off-topic reply I've ever seen!
  5. 7 points
    TL;DR, there's now an easy way to enable MP4 (H.264 + AAC) HTML5 video support in Firefox on Windows XP using the Primetime Content Decryption Module plugin by Adobe (distributed by Mozilla). Meaning, you could get rid of Flash (with some caveats). The irony of course being that you'd have to use another thing by Adobe , but at least it's something not as prone to security problems. NOTE: If you're suddenly unable to watch videos on Facebook (or any other site) even though you haven't changed anything re: Primetime, you may have to start spoofing your browser UA (user agent) string to work around this problem. See the posts starting here for the specifics. (EDIT October 30, 2017) IMPORTANT: The Primetime CDM plugin can no longer be downloaded from Adobe servers, which means that attempts to automatically download the plugin through Firefox GUI will fail even if you edit the download configuration URL per the old instructions below. From now on, you will have to manually install the plugin for all new Firefox installations and any new profiles you create; see the new instructions below. If you already have the plugin installed, you don't need to do anything. (EDIT July 18, 2017) If you're here because MP4 video has stopped working after you upgraded to Firefox 52.0, see this post. If you still have problems, make sure you have all of the required preferences listed below and their values are set correctly. If you're here because MP4 video has stopped working after you upgraded to Firefox 49.0 or higher, that happens because 49.0 introduces a new pair of preferences. You now need to set media.gmp-eme-adobe.visible and media.gmp-eme-adobe.forceSupported to true; media.gmp-eme-adobe.forcevisible is no longer used. Toggle the Primetime plugin to Never Activate and back or restart Firefox for the pref change to take effect. NEWS July 26, 2016: Unfortunately, but maybe not all that surprisingly: Primetime CDM will not be getting official support on Windows XP after all. Says a Mozilla developer: Not to worry though, this does not appear to have any near-term (<=FF52 ESR) effect on forcing the plugin to work with the same workarounds we've been using all this time. However, just in case Adobe compiles some XP-incompatible Windows APIs into future plugin updates, you may want to save a copy of the gmp-eme-adobe folder from your FF profile or download the v.17 distribution package. (Adobe has removed the package from download but @sdfox7has kindly archived a copy (backup link).) Technically, this plugin has been added to FF for DRMed HTML5 video, but it can be used to play non-DRM as well. It's not officially supported on XP, but hey, neither is XP itself, right? I've been trying it out with FF 46 (later also confirmed with 45, 52 ESR and 47-52) on XP Pro SP3 x86 (with POSReady updates, though I doubt that matters any) for about a week now, and the experience has been pretty encouraging. The vast majority of HTML5 videos have worked without a hitch; ~5% have had 1-2 temporary freezes (the video stops, the audio continues with some crackle), which can be easily worked around by moving the video position slider back a bit and then forward again to where the freeze happened. I've seen only one (1) case of a show-stopper error message about "corruption or unsupported features in video" (quote not verbatim) that couldn't be worked around by jiggling the slider (not a crash, just an error message and the video stopped). You may not necessarily be as lucky, though, as the reason the plugin is not included by default by Mozilla is its reported crashing on some high profile sites. (If you're interested in getting this to work on Windows 2000, be sure to read @blackwingcat's post below in addition to this one, and why not his blog posts (1, 2, 3) as well (in Japanese, but with screen shot images).) To be able to install and operate the Primetime CDM, add and/or set the following FF preferences in about:config (be careful, all of these are cAsE sEnSiTiVe!): media.gmp-eme-adobe.enabled (boolean; true) media.gmp-eme-adobe.forceSupported (boolean; true; FF 49.0+) media.gmp-eme-adobe.forcevisible (boolean; true; FF 45-48, no longer used in 49.0+) media.gmp-eme-adobe.visible (boolean; true; FF 49.0+) media.gmp-eme-adobe.version (string, not integer; 17; required for manual install now that automatic install is no longer an option) media.gmp-eme-adobe.abi (string; x86-msvc-x86 (EDIT: x86-msvc-x64 for 64-bit XP users); not required, you can set it if you want to more closely mimic automatic install) media.gmp-eme-adobe.lastUpdate (integer; 1500000000; not required, you can set it if you want to more closely mimic automatic install) media.gmp.decoder.enabled (boolean; true) media.eme.enabled (boolean; true; defaults to false if you downloaded a DRM-free version of FF; thanks @heinoganda for pointing this out) To manually install the actual Primetime plugin software, first download the ZIP package (backup link) from @sdfox7's site (he has plenty of other useful XP stuff there as well, definitely worth checking out!). You can use the following checksums to verify package integrity: To install the plugin: Open your FF profile folder. An easy way to navigate to it is by opening about:support in FF and clicking the Open Folder button next to Profile Folder. Inside the profile folder, create subfolder gmp-eme-adobe and open it. Inside gmp-eme-adobe, create subfolder 17 and open it. Unpack the Primetime ZIP archive into folder 17. Folder [your FF profile path]\gmp-eme-adobe\17 should now contain three files: eme-adobe.dll, eme-adobe.info, eme-adobe.voucher. After this, check the Plugins in your Add-ons list and you should see the Primetime plugin listed and ready for use. If you don't see the plugin there, make sure you've set all of the required preferences as described above and put the files into the correct subfolder. Restarting Firefox to complete the manual install isn't usually required, but try it if the plugin doesn't appear, (Also, remember that if you have more than one Firefox profile, you'll need to repeat these steps for each of them individually.) Set the Primetime plugin to Always Activate, Flash to Never Activate (not strictly necessary, but better for testing), and go to Youtube HTML5 video player check page. Both H.264 and MSE & H.264 should have blue checkmarks. You may want to try this test page (kindly suggested by @dencorso) or some Twitter videos to quickly make sure H.264 really is working (with Youtube you can get fooled by WebM getting played instead). In theory, you could uninstall Flash at this point, but realistically it's probably wiser for now to leave it installed and disabled in the browser. Personally, I installed the FlashDisable extension to quickly toggle Flash on some of the sites I frequent that don't support HTML5 video. Some of those insistently serve Flash video to desktop FF without even checking if it can do HTML5 video or not. That can be worked around by faking a different user agent string, but for now I've found it more convenient to just temporarily toggle Flash back on for them. FlashDisable supports the Ask to Activate setting, so you don't have to worry about other sites if you forget to turn Flash off again. Based on what Mozilla devs have been saying on Bugzilla (Unhide Adobe GMP on Windows XP, Hide Adobe GMP on Windows XP in Firefox 46 and 47, Make Adobe GMP available to Windows XP users in Firefox 45 and later) it seems quite possible that this plugin could soon (FF 48+) be made available without having to use any tricks (or pre-release versions), but I suppose it's also possible that the current situation will continue indefinitely (or even that the plugin will eventually be made more difficult to access under XP). (EDIT July 18, 2017) As you've likely heard, FF 52 ESR is the last version of the browser that's going to work on XP (unless some intrepid person forks a special version for us). In a way, this is a blessing in disguise, as Primetime support has been completely excised from FF 53 and Google's Widevine CDM doesn't have our helpful side-effect (and doesn't work on XP), but ESR 52 will be supported well into 2018. So, why not make use of it while we can, right? Note that HLS streaming is not natively supported with this plugin. It does work on sites coded to use some JS library or player to work with HLS, but not for directly playing .m3u8 video sources. You may want to keep an eye on developments with hls.js in general and firefox-hls in particular if a favorite site of yours falls into the latter category.
  6. 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:
  7. 6 points
    We will be online for one more month for now. If we get enough donations we will continue to be online. Advertising no longer works. Ad blockers hurting us. You can donate here: sponsors at msfn.org or http://www.msfn.org/board/donate/make-donation/. Thank you. Best regards MSFN
  8. 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 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
  9. 6 points
    Project Name : ExtendedXP(Extended Kernel for XP) Current Version : 2017/05/22 Production Stage :: Public beta KernelEx or ExtendedKernel was invented long ago by loyal MSFN Member Xeno86 to run XP/2000 application on 9x .Further reflected by rloew in his unicow wrapper project for windows 98 second edition .The idea was carried after long time by BlackWingCat of Windows 2000 community and WildBill of windows 2000 community . This my attempt for coming up with similar kernel extension for windows xp in time so that when in future most programs will stop working on XP that time we can use it . Updated System Components :- Functions added to advapi32.dll:- Function added to kernel32.dll:- Added function to ntdll.dll:- Added function to shell32.dll Note: Most of the functions are stub so i have future plans to remove them Added functions to User32.dll :- KnownIssues :- *VLC media-player always crash (Though Skinned mode work) *Resource hacker setup crashes always .(inno setup ) ( Bug found with CryptoLibrary )(thanks to heinoganda) *Avast free 2017 & esed does not work (Something wrong with Shell32 )(thanks to heinoganda) LINKS ARE REMOVED DUE TO NEW RELEASE OF HOT FIXES WITH KERNEL32.DLL & NTDLL.DLL This Post is my request to knowledgeable persons to help me to fix the known issues . Thanks in advance THIS VERSION IS ONLY FOR TESTING PLEASE KINDLY USE ANY VIRTUAL MACHINE OR ANY PC THAT NOT IMPORTANT . THANKS FOR UNDERSTANDING. !!Windows XP Forever!!
  10. 6 points
    With the latest patches out this Tuesday, Microsoft has completely removed Equation Editor from all still supported Office versions, so it's a very good idea to also remove it from older Office versions ASAP. I'm guessing this drastic measure by Microsoft has to do with the fact that they don't seem to have the source code for this bundled third-party application, and since it's been under ongoing attack even after the previous binary patch was issued for it, they decided that continuing to patch the binary just wasn't feasible. In any case, keep in mind that even if you've never used Equation Editor in any of your own documents, as long as you have it installed, boobytrapped documents you download or receive can still invoke it. If your version of Office is still supported, simply apply the latest patches from Microsoft Update (see the CVE link below for manual downloads). For older versions like Office 2000/XP/2003, you can either remove this feature with the Office installer and mark it unavailable (as described below in the If you don't use Equation Editor section), or simply replace the existing EQNEDT32.EXE with a 0-size empty file still called EQNEDT32.EXE (this appears to be what the patches for newer Office versions do). See the following links for more details and Microsoft's suggestions for replacements of Equation Editor functionality. https://support.microsoft.com/en-us/help/4057882/error-when-editing-an-equation-in-office https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0802 This post used to be titled HOWTO: Install Office 2007 Equation Editor security update (KB4011604. aka KB4011276) on Office 2000/XP/2003 and had the following contents: A remote code execution vulnerability was patched this month in Equation Editor, an Office component (CVE-2017-11882 | Microsoft Office Memory Corruption Vulnerability, Description of the security update for 2007 Microsoft Office Suite: November 28, 2017). Official patches are available only for Office 2007 and higher, but since it's a standalone component that hasn't changed since the year 2000, and Microsoft has simply applied a binary patch to the executable and resigned it, you can also use this patch with Office 2000, XP and 2003. NOTE: KB4011604 was initially released as KB4011276 for English and Chinese only. If you've already installed KB4011276, you don't need to install KB4011604, the Equation Editor payloads are byte-for-byte identical. If you prefer a statement from Microsoft (from the CVE link above): "Customers who have already installed the previously-released updates (4011276 or 2553204) do not need to take any further action." If you don't use Equation Editor, instead of updating it, you might want to remove it from your computer altogether. (Even if you don't have it installed right now, since it defaults to Installed on First Use, it's a good idea to explicitly deselect it in the Office installer.) Go to Control Panel > Add or Remove Programs, locate your Office 2000/XP/2003 installer and choose the Change option, then pick Add or Remove Features when the installer launces. Find Equation Editor in the component tree. The exact location may differ depending on your Office version, in my case (Office XP) it was under Office Tools. To disable its installation, or remove it from your computer if already installed, mark it as Not Available and complete the update. You should no longer have an Equation folder under (typically) C:\Program Files\Common Files\Microsoft Shared. If you do use Equation Editor, you'll have to update it manually. (Trying to run the installer, it'll just tell you that you don't have an applicable product installed.) To do this, you'll be needing 7-zip (or a similarly versatile unpacker). Get the patch either as an EXE installer from the Download Center (English; other languages direct links by @Bersaglio) or a CAB file from WU/Catalog (English) . Right-click on the downloaded file and choose to open it with 7-zip. (EXE only) Select [0], right-click, Open Inside. Select eqnedt32-[your-language].msp (e.g. eqnedt32-en-us.msp), right-click, Open Inside. Select PATCH_CAB, right-click, Open Inside. Extract EQNEDT32.EXE_[numeric language code] (e.g. EQNEDT32.EXE_1033) to a location of your choice and remove the numeric part from the file name, leaving you with EQNEDT32.EXE. Copy this file to your Equation Editor folder, (typically) at C:\Program Files\Common Files\Microsoft Shared\Equation, replacing the old EQNEDT32.EXE in there. (If you like, you can make a copy of the old version, but you can always restore it later by re-running the Office installer.) To make sure everything is kosher now, check EQNEDT32.EXE properties. The version should show 2017.8.14.0. (Note that if you use the Office installer in the future to change installed components or repair your installation, it may put back the old EQNEDT32.EXE and you'll have to manually replace it again.)
  11. 6 points
    I am sorry I have been gone for so long everybody, but I'm back now, hopefully for good. I had a death in the family, and it tolled on me extremely, along with some complicated projects outside of computing, as well as being locked out of my main building machine. I now have some more free time on my hands, and I recently picked up an old laptop that I could dedicate to building and testing on. I can't promise when I could get a build out, but work will be done slowly but surely. I have to get re-oriented with the code and build process, and where I left off. I haven't read the thread since I left, but I will tonight and answer any of your questions and concerns. Again, I am sorry that it took so long for me to work on this project, I really wish that I didn't fall off the radar like I did, but I'm back.
  12. 6 points
    A Start Menu and other amazing apps like OldNewExplorer etc can fully fix Windows 7 or 8.1, but they cannot fix the atrocities of Windows 10. Windows 10 is an OS fundamentally designed to mess up your setup. Candy Crush and other crap auto installing without asking, ads in File Manager and other places, shilling MS apps to the user even after the user has set his defaults, using bandwidth without permission to download or share updates, taking an abnormally long time to do updates, wasting the user's time at logon and logoff with configuring huge updates, randomly breaking and uninstalling things people are using with updates that nobody asked for, overriding hardware configurations with forced driver changes, and countless other things. It is evil. P.S. And I didn't even mention the SIZE of typical updates which is so completely out of control that they hid it from the UI so the user would never know how much data he is downloading to his PC and what a bandwidth waste this OS is. Edit: Cleaned up language. Thank you! -Tommy
  13. 6 points
    Your guess is as good as mine. It's been over six weeks since the Creators Update has been available and at least 3 weeks since Bigmuscle said 'very soon' in another thread to the availability of a version compatible with rs2. I know from Noel who has received an experimental version that BM has worked on this and more or less had a version that worked well. Why he has not distributed anything to his donors or the public is, again, anybody's guess. I hope all is well with him and that he's not in any predicament that prevents him from doing his work. I suppose we have no choice but to wait for a version or for some news regarding BM.
  14. 6 points
    Yes. I have successfully installed the following (post-Vista EOL) Server 2008 updates in Windows Vista (SP2, x64): KB4020535 KB4019206 KB4019204 KB4019149 KB4018927 KB4018556 KB4018885 KB4018821 KB4018466 KB4018271 Screenshot: http://prntscr.com/f602cl From my testing, the following updates did NOT work on Windows Vista: KB4018196 (Displays "Not applicable to your system" message) Windows Malicious Software Removal Tool for May 2017 (Not compatible with your OS error message) So it looks like Vista will be good to go until 2020, with the exception of a few updates here and there. I also must note that I didn't try any updates related to .NET Framework, as I couldn't figure out how to obtain them. Alright @greenhillmaniac, it's time to make that Server 2008-Vista repository
  15. 5 points
    As all of you Vista users surely know, IE9 is the last version of the MS supplied browser that can be installed on that OS. It has several prerequisites, notably KB948465 (SP2 for Vista SP1), KB971512 (Windows Graphics, Imaging, and XPS Library) and KB2117917 (Platform update supplement for Windows Vista); you can read more here. MS had continued patching security vulnerabilities in IE9 on Vista SP2 via "Cumulative Security Updates for Internet Explorer 9 on Windows Vista SP2" up until Vista's EOL on April 11th of this year (update KB4014661). MS will continue patching IE9 on Windows Server 2008 SP2 (as, again, it's the last version installable there, too) until that product reaches its (Extended Support) EOL in 2020. If you have been following our Server 2008 Updates on Windows Vista thread, then you should have already installed follow-ups KB4018271 (May 2017), KB4021558 (June 2017) and KB4025252 (July 2017). For the rest of this post I'll assume your Vista SP2 OS (ergo IE9 copy) is fully updated even with post EOL updates intended for WS2008SP2; e.g. on my setup (Vista SP2 Home Premium 32bit), "About Internet Explorer" looks like: For those of you out there with an intention to using IE9 as your main browser on Vista, sadly, you'd have come to the conclusion it's only half-usable currently, at best; this is a result of: 1. Most modern sites have removed support for IE9 completely, via UA string sniffing: Somes sites (like Youtube) offer a workaround, for others it may be necessary to spoof the actual UA string as one from a later OS+IE version (e.g. via the "Set UA String" IE addon). 2. Many sites have moved to recent web design, so they don't render correctly (if at all) in IE9, even in "Compatibility View" (well, actually, this is to be expected; CV means the site was optimised for IE8-); FWIW, even MS pages don't display correctly now in IE9 . 3. A third scenario I find quite irritating is that many sites fail to load at all in IE9 if they use the HTTPS protocol; with the recent move of many major sites to the more secure, encrypted, HTTPS, "allegedly" to increase user privacy and security, I found the list of "secure" sites not opening in IE9 growing at a high rate; of course there's always Firefox, but it's IE9 we're discussing here... Upon investigation, I discovered this is due to IE9 on Vista only supporting TLS protocol v1.0; this is considered by today's standards no longer secure enough, so many sites using HTTPS have moved to the more secure versions 1.1, 1.2, even to 1.3! Fortunately, a recent MS update (intended for the WS2008SP2 OS) can be applied on Vista SP2 that will implement TLS 1.1/1.2 support on Vista's IE9, too! ; I have spoken about this important update here. 1. Install then KB4019276 2. Reboot the Vista machine 3. After restart, launch the Registry Editor (regedit), preferably as Administrator. 4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 5. Delete the "OSVersion"="" subkey; BTW, I don't know which WinOS that string refers to (Win6.1=Win7) 6. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2 7. Again, delete the "OSVersion"="" subkey. Exit Registry Editor. 8. Launch IE9; Tools -> Internet Options -> Advanced tab -> Scroll all the way down to "Security": Prior to KB4019276 and registry manipulations, only "Use TLS 1.0" had been available on Vista; you should have already unchecked the older "Use SSL 2.0/3.0" options, to avoid being targeted by "POODLE" attacks; uncheck "Use TLS 1.0" (optionally also "Use TLS 1.1") and check "Use TLS 1.2". 9. Click Apply, OK, then exit IE9. 10. Upon restarting IE9, you'll find you can now visit all those sites that previously would not load due to unsupported TLS protocols: 10. You can verify further that indeed 1.2 is being used during server-client negotiations via specialised sites or via IE9's native GUI: I honestly hope you'll find my post to be of value; enjoy your more secure (than ever before?) Vista OS!
  16. 5 points
    I just found out something very interesting for both Vista and 7: https://support.microsoft.com/en-us/help/4012371 I also found this pdf file from Microsoft detailing this service: https://download.microsoft.com/download/C/5/1/C51D8E55-5538-4F21-8C9D-A66DB31C4B46/SQL_Server_and_Windows_Server_Premium_Assurance_Datasheet.pdf Microsoft probably knows how s*** Windows 10 (and its related Server offerings) are for enterprises, and is milking the NT 6.0/6.1 cashcow for all it's got. In fact, if you go to the lifecycle page, you can see it mentions the 6 years extended support: https://support.microsoft.com/en-us/lifecycle/search?alpha=windows server 2008 Seems like this agreement could extend to Server 2012/R2, but I haven't found concrete dates on that, aside from the same support page: https://support.microsoft.com/en-us/lifecycle/search?alpha=windows server 2012 Anyway, if we could get a hold of someone (anyone) who had access to this licensing agreement and could provide the updates, we could be seeing Windows Vista and 7 support up until 2026!!!
  17. 5 points
    basilisk/moebius new build for XP! Test binary: Win32 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win32-git-20180203-a296623c2-xpmod.7z Win64 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win64-git-20180203-a296623c2-xpmod.7z diff: http://o.rthost.cf/gpc/files1.rt/moebius_restoreXP_20180128.7z source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z Official repo changes since my last build: - Put nsSearchService.js into preprocessing (51259aa16) - Take FirefoxAccounts.jsm out of preprocessing (a0b6970c6) - Added option to remove all session cookies for a specific domain (a1f1f1205) - WebRTC: GetUserMedia should reject when document not fully active. (7fd56b754) - Check for integer overflow in AesTask::DoCrypto() (DiD) (65b6c2b49) - Avoid a race condition in AutoClose. (9f2c3e611) - Use nsITimerCallback for DTMF timers. (0d5cc6e75) - Don't allow queue-jumping for gathering state change events. (020315c8d) - Move to LIFECYCLE_WAITING_FOR_MAIN_THREAD_CLEANUP at end of iteration. (8c46342c1) - Don't insert source content into the document for XSLT transforms. (958da71bc) - Switch to WeakPtr. (4e97e1c7a) - Mirror changes done to Encoder InitDone to decoder. (179d5d2ce) - Improve the use of XHR.mProxy in workers after the dispatching of sync OpenRunnable. (cffb0d60f) - Skia: port upstream path cleanup patch. (777a9638e) - Fix the remove-while-iterating for RemoveCookiesWithOriginAttributes. (5bbfaf473) - Revert "WebRTC: GetUserMedia should reject when document not fully active." (e504410aa) - Merge pull request #337 from janekptacijarabaci/devtools_storage_removeAllSessionCookies_1 (b5882cdd5) - Merge pull request #334 from binoc-central/ppfix-work (3bcf295ee) - Use CheckedInt to compute guess for the location of -> in FTP parser. (173f6034c) - Merge branch 'master' of https://github.com/MoonchildProductions/moebius (e354dd6bc) - Avoid potential race condition in nsJAR. (624dc91f6) - Handle large string lengths in nsAString's ParamTraits. (DiD) (8cbbfdc3d) - Mac: Ensure that the proper mouse cursor is shown on macOS when switching between custom and default system cursors. (60cf1d91a) - Use a consistent window for CSP, etc. for FontFace loads. (e094ab30f) - Change resolution of .now() to 1ms (following Safari's lead) (444a37c23) - Make it possible to add cookies, local and session storage entries (4b616da23) - Fix button style (ddd12eefb) - Merge pull request #339 from janekptacijarabaci/devtools_storage_addItem_1 (9412b75a6) - Columns are not sorted correctly (3a7a189a1) - Merge pull request #342 from janekptacijarabaci/devtools_storage_columns_sort_1 (a296623c2)
  18. 5 points
    New Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180203-d3e1e49a9-xpmod.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180203-d3e1e49a9-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win64-git-20180203-d3e1e49a9-xpmod.7z Official repo changes since my last build: - Check for integer overflow in AesTask::DoCrypto() (DiD) (ac44e1fee) - Avoid a race condition in AutoClose. (961d03967) - Add a null check before NotifyMediaStreamTracksAvailable (3518fbf02) - Improve the use of XHR.mProxy in workers after the dispatching of sync OpenRunnable. (6b6ec3876) - Use CheckedInt to compute guess for the location of -> in FTP parser. (0de6888e0) - Avoid potential race condition in nsJAR. (d3e1e49a9)
  19. 5 points
    Hello everyone, in the last past few months I have been working on a windows nt 4.0 api wrapper which can run softwares designed for new windows's version. I'm writing the functions in inline assembly (I'm using ida) and C. (There is also some code from reactos and wine). There are some issues with certain softwares, some don't load at all and some crash, so I can't release nothing for now. What are some software you use and you want to run on it? List me and I will try to get them work. Unfortunately firefox (the 3.5 version and newer), opera 12.18 and utorrent don't load even if I added the missing functions... They don't throw me any error, they simply don't load at all... Maybe I have to do something. I will investigate. Here, there are some software that load. Filezilla 3.8.1 (last version crashes, but I think I will be able to get it work) vlc 2.2.0 last version of 7-zip last version of Sumatra (it's a little buggy but it reads pdf).
  20. 5 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
  21. 5 points
    New Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.7.0a2.win32-git-20171121-e15e1197a-xpmod.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.7.0a2.win64-git-20171121-e15e1197a-xpmod.7z Official repo changes since my last build: - [minor fix] Build - warnings (a49558e42) - DevTools - gcli - screenshot - the vertical mode (2b66fccbe) - Merge pull request #1465 from janekptacijarabaci/build_warnings_1 (917c86ca6) - Merge pull request #1467 from janekptacijarabaci/devtools_gcli_screenshot_1 (1ce42d280) - DevTools - network - Copy as cURL (POST) (cbc57c6c5) - Potential fix for missing locate_t on Mac OSX. (468257cac) - Fix Linux loading throbber to be properly encoded. (2b5597ff5) - Make sure the PNG set-option function is available. (abd5fc481) - Force a larger zlib inflate window. (623d24cdb) - Merge pull request #1473 from MoonchildProductions/osx-fix-1 (56b2a7318) - Change nsIDocumentLoaderFactory and nsIURIContentListener to take MIME types as an XPCOM string, not a char* (5952adeef) - Refactor nsContentDLF (83098db20) - Add text/json and text/vtt as text MIME types (2b145a4ed) - Merge pull request #1478 from JustOff/PR_char_nsACString (10f08b259) - Profiles - the refresh - migrate (7a6b077e4) - Merge pull request #1479 from JustOff/PR_add_text_json_vtt (d875128c0) - Merge pull request #1472 from janekptacijarabaci/devtools_network_curl_2 (aa9d16c92) - Profiles - the refresh - migrate (passwords) (c40ee8c60) - Remove the "ask every time" policy for acceptance of cookies. (b243a16d7) - Profiles - the refresh - migrate - improvements (a6f83d31d) - Merge pull request #1481 from janekptacijarabaci/profile_refresh_migrate_1 (db9f8a174) - Implement X-Content-Type-Options: nosniff. (2f965ebf1) - Handle custom URLs and add "My home page" for the New Tab URL. (aff0e2bf9) - Merge pull request #1484 from MoonchildProductions/newtaburl-enh1 (ea66708b4) - Merge pull request #1483 from JustOff/PR_XCTO_nosniff (fae3ec362) - Define Ci before using it. (ccbd72d00) - Implement "cookie-averse document objects". (1ccbaeb2c) - Expose cookieBehavior and cookieLifetimePolicy preference variants from nsICookieService. (e15e1197a)
  22. 5 points
    Introduction: As the title implies, this post serves as a guide for anyone potentially seeking to install and use Vista on the Intel Ivy Bridge platform. I felt there was a need to create this guide, because although getting full driver support for Vista under Ivy Bridge IS possible, it requires you to use certain motherboard(s) from the Sandy Bridge era to get USB 3.0 driver support for Vista. Intel HD 4000 Graphics drivers are also not so easy to obtain for Vista, so a link to them has been provided below. Choosing the right motherboard: With Ivy Bridge, Intel dropped Windows Vista (and XP) support from its USB 3.0 drivers, rendering XP/Vista support for the Ivy chipset incomplete. To work around this, you will need to find a motherboard from the Sandy Bridge era that supports Sandy AND Ivy Bridge CPUs. Almost all Sandy Bridge motherboards, except those with the Q65, Q67 or B65 chipsets, will support Ivy Bridge CPUs through a BIOS upgrade. A notable example of such a motherboard is the Asus P8Z68-V LX. This motherboard in particular has Asmedia USB 3.0 controllers, and Asmedia has excellent driver support for Windows Vista. Gigabyte also offers a number of boards that include third-party USB 3.0 chipsets, which support Vista. Be aware that you might have to purchase (or borrow from a friend/relative) a Sandy Bridge CPU to boot up your system for the first time if you are building from scratch, as the original BIOS version for these boards does not support the use of Ivy Bridge CPUs and will not allow you to boot the machine with an Ivy Bridge CPU without first updating your BIOS. For Ivy Bridge-E processors, the X79 chipset is fully supported on Windows Vista and you may choose any motherboard you like (the BIOS update situation still applies). If you do not care about or need USB 3.0, then you may choose any Ivy Bridge motherboard you like. Chipset drivers for Ivy Bridge do support Vista and can be downloaded here. I personally use the ASUS P8B75-M motherboard with Windows Vista Ultimate, and I find it to work well (Vista simply uses its generic USB 2.0 drivers for the USB 3.0 ports). Finding Intel HD 4000 Graphics drivers: You can download Intel HD 4000 Graphics drivers for Vista here. For some reason, Intel decided initially to not support Windows Vista with its HD 4000 graphics chipsets. However, it appears that they later decided to add in Windows Vista support, evidently via backporting Windows 7 drivers, since this installer claims that the drivers are for Windows 7 but doesn't mention Vista specifically. Despite this, the drivers work just fine in Windows Vista. I have studied the driver setup information (.inf) files and found that both desktop and mobile HD 4000 graphics chipsets are supported, so this driver should be able to be used with any Ivy Bridge graphics chipset under Windows Vista. That's it! No additional special steps are required, and you may install and use Vista normally with full driver support on the Ivy Bridge platform (arguably the best platform for XP/Vista). I hope this guide helped you!
  23. 5 points
    StartIsBack++ 2.5 BETA - JumpListIsBack! BEGONE, XAML BEAST! http://www.startisback.com/StartIsBackPlusPlus_setupBETA.exe
  24. 5 points
    There are most likely many fans of AeroGlass and supporters of @bigmuscle that contribute financially with minimal interaction in this forum. Some may not even be aware of this forum. That being said, you can never have too many financial supporters for any project like this and the man deserves probably far more than he has received in donations. People with special skills like his are usually very generous and almost never get as much as they deserve to receive for their efforts. While I seldom engage in the forum here, I have contributed 35.50 € to support the work and really hope we get support for 1703 (Creators Abortion as I prefer to call it) because every version of Windows from 8.X to date sucks without Aero transparency. I am doing the best I can to tolerate it, but it's a sucky OS in many ways besides the absence of an attractive UI.
  25. 5 points
    NEWS: I was able to load windows media player 10.... It's a little buggy because there are some missing functions I have not added yet, but now it loads
  26. 5 points
    I have no problems with the Windows 10 computer when it's powered off.
  27. 5 points
    The only thing Windows - and Microsoft - can possibly respond to from this point forward is complete contempt. Not just no, but HELL NO, I will not allow them to control MY system. Period. FYI, I think Mr. Burnett hasn't worked quite hard enough. He's not going to be able to get there with just settings. Microsoft doesn't care to honor those settings. They're not smart enough to think through how to make their cloud-integrated toy apps even begin to work without a full-time mothership tether. I've let my Win 10 v1703 system just sit quietly for days. It doesn't make any unsolicited contacts except to an NIST time server on a schedule I've set. Not sure if this image will show here, I posted it on another forum: This is WireShark showing no outside-the-LAN communications for half a day. And the only error my system logs all day is right after bootup. Apparently it thinks it’s an error that I’ve disallowed it from starting UAC, because UAC was, is, and always will be an abomination... The trick is to completely shun the toy Apps, cloud integration (OneDrive/Settings), and half-baked personal digital assistant. Then of course that leaves Windows 10 no better than any prior version. -Noel
  28. 5 points
    A new name for the "Windows Store Only" strategy (that already failed) : and : a pure marketing attempt, seemingly, I don't believe that there is anything particularly "lite" (unless you want to be forced to the limited amount of - BTW largely crappy - Apps in the Store). jaclaz
  29. 5 points
    StartIsBack++ 2.0.2 http://www.startisback.com/StartIsBackPlusPlus_setup.exe (Not marked as beta since apparantly nobody installs beta versions) This version addresses all feedback received since 2.0 release.
  30. 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: WinNTSetup3.rar Current Beta: 3.8.9 B2 WinNTSetup3_Beta
  31. 4 points
    I made a video describing all creations of roytam1
  32. 4 points
    New Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180224-e2794cd9a-xpmod.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180224-e2794cd9a-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win64-git-20180224-e2794cd9a-xpmod.7z Official repo changes since my last build: - Properly handle new tab selection dialog when instantApply is enabled (a933414a3) - Merge pull request #1617 from JustOff/PR_newtabUrl_instantApply (11cc18496) - Issue #1610 part 1: Add valgrind suppression for uninitialized memory access and leak in old fontconfig. (7f85e40d0) - Issue #1610 Part2: Supply a bundled emoji font on Windows. (410afd43a) - Issue #1610 Part 3: Bypass GDI table loading for embedded fonts. (1d10949de) - Update Emoji font to 0.2.2 (latest release) (4eb2191aa) - Update NSPR to 4.18 (9ce3bb3bd) - Update NSS to 3.35 (819938451) - Update build system for changed NSS (version/symbols) (e2794cd9a)
  33. 4 points
    First build of basilisk/UXP for XP! Test binary: Win32 http://o.rthost.cf/gpc/files1.rt/basilisk52-55.0.0a1.win32-git-20180220-d77729916-xpmod.7z Win64 http://o.rthost.cf/gpc/files1.rt/basilisk52-55.0.0a1.win64-git-20180220-d77729916-xpmod.7z diff: http://o.rthost.cf/gpc/files1.rt/UXP_RestoreXP_20180221.7z source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z My changes: * Added H264/HEVC/AAC/MP3 support in ffvpx * The following changesets are reverted: - Update exe manifest (drop Vista support) (756b27f58) - Adjust requirements (45f2fcd80) - Part 2 (d38f86569) - Stop shipping d3dcompiler_43.dll (b6c330e1c) - Prevent installing stand-alone installers on unsupported environments. (47b8c58d4) - Update executable manifests. (b55f0e7f0) - Remove unnecessary code in /widget. (a24398e42) - Remove no longer relevant ClearType prefs. (bc9ad467f) - Make the proper Windows APIs natively available to our tree. (85edb1c71) - Remove the use of GetProcAddress() for shell32 (c76689719) - Remove dead code in the Windows battery module. (e52c019ec) - Remove redundant Vista checks in toolkit/xre (2b01522cf) - Remove redundant Vista checks in dom/ipc (039f3e49c) - Remove useless version check from PDMFactory. (3d37f6181) - Remove always-false block from WMF. (ee70e3a36) - Remove always-false #if WINVER < 0x0600 (Windows Vista) checks in widget/windows. (66248cfbc) - Remove always-false #if WINVER < 0x0600 (Windows Vista) check in toolkit/win. (8f1c9fe4f) - Remove always-false #if WINVER < 0x0601 (Windows 7) checks in nsLookAndFeel.h. (2e0f80af4) - Remove always-false #if WINVER < 0x0601 (Windows 7) checks in nsWinGesture.h. (39578317e) - Use GetTickCount64 without a GetProcAddress check in Timestamp_windows.cpp. (a14048f0a) - Remove SEH try blocks from a11y code. (616475a0c) - Use thread_local calls on Win and Mac. (ce1bd4f24) - Remove StartupSpecialSystemDirectory() workaround. (01b1e411b) - Remove Windows shell integration checks for Windows Vista. (4f82d71df) - Remove XPCOM checks for Windows Vista and clean up unused header files. (13a9ea648) - Remove some gfx/thebes checks for Windows Vista+. (f297ef798) - Remove gfx/thebes checks for Windows 7+. (38ec1c796) - Remove some obsolete front-end code in Basilisk. (da8f20a3b) - Remove Windows XP specific code in netwerk. (40d8e355c) - Remove obsolete WinXPWifiScanner class. (a1bc6f33e) - Remove DLL blocklist checks for Windows XP. (20e533f6b) - Remove more Vista checks in dom/media (f1e863a49) - Remove more Vista checks in ipc code (a930db1c9) - Remove more obsolete checks in dom/media and ipc. (5d1eb0d3a) - Clean up Firefox specific considerations from WindowsVersion.h (9ecbf3331) - Fix build bustage: keep MF_WIN7_VERSION name (8826313be) - Remove Windows XP and Windows Vista theme components and resources. (fd9d8c20d) - Remove windows-xp and windows-vista from @media(-moz-os-version) (4c697043d) Tugging war begins, and my reverted changeset will become longer and longer in foreseeable future.
  34. 4 points
    I do, too, and your effort in maintaining the updates repo is highly appreciated; however, the last round of manual updates I installed here was last November's; I will - sometime soon - catch up, no doubt there, but I keep postponing it... Thing is, I don't feel especially vulnerable from a security standpoint (and the only one time something malicious found its way on my system was last August when I installed that hacked CCleaner x86 version - MS security updates, WinDefender, Kaspersky, all three did not prevent the infection at the time ). What I miss is new feature updates (that won't come via MS), because, as @burd rightly pointed out, server owners and app authors are moving away from things Vista supported in the past, thus obsoleting the OS little by little... I had a discussion with a server owner yesterday night (over e-mails) to try and convince him to enable server-side cipher suites compatible with Vista's SChannel/IE9; because having TLS 1.2 implemented is one thing (and how many Vista users out there in the wild are aware that's even possible?) but having support for the required stricter cipher suites dictated by the secure servers is another (as demonstrated in a more pronounced way in the XP subforum...). Server admins only look at access statistics - that's all; that specific host was configured to TLS 1.2 only, so by this setting alone all XP/Vista IE users were excluded by default; Vista OS accounted only for 0.7% on that host, this is not a real motive to continue supporting Vista there... Speaking of sites, I've found several in the recent past that would simply refuse to load if they detect NT 6.0 in the sent UA string; so I have to spoof my browser's UA to include NT 6.1 (Win7) for sites like that . While UA-sniffing is a deplorable behaviour for sites, many just do it and block Vista on the assumption NT 6.0 is vulnerable, because EOL'd by vendor... And as for software, we have a dedicated thread in the forum, the rate with which app authors are abandoning Vista support (by turning to Win7+ APIs) is quite alarming, to say the least... Yes, we need a KernelEx for Vista that would backport some (or all) of the missing APIs found in the Win7+ kernel; the ones missing are not that many in number, my experience (dependency-walker test) with recent software broken on Vista is only because of 1 to 3 missing functions, not more... I guess with some compromises we, Vista users, could well continue to use the OS for the duration of this year, but come 2019, even with MS security updates available, it'll be a crippled OS app-wise... Apologies for the slightly OT nature of my post
  35. 4 points
    Let me know the next time you read this thread so I can wait outside to catch it.
  36. 4 points
    This was also driving me crazy until I figured out (by looking at the debug file from the latest experimental version 1290) that AeroGlass was unable to download: http://msdl.microsoft.com/download/symbols/dwmcore.pdb/4DFDA14B2ACD35B23AC37976303DB51A1/dwmcore.pdb Finally, by simply manually pasting the above link into my browser, I was able to download the above required symbol file. I then had to manually create a subfolder with the name "4DFDA14B2ACD35B23AC37976303DB51A1" in the '..symbols\dwmcore.pdb' folder, and then copied the 'dwmcore.pdb' file into this new subfolder. Everything worked great from that moment forward! Hope this helps anyone! -JT
  37. 4 points
    basilisk/moebius new build for XP! Test binary: Win32 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win32-git-20171121-2c7948df3-xpmod.7z Win64 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win64-git-20171121-2c7948df3-xpmod.7z diff: http://o.rthost.cf/gpc/files1.rt/moebius_restoreXP_20171113.7z source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z Official repo changes since my last build: - DevTools - gcli - screenshot - the vertical mode (822529aa6) - Merge pull request #166 from janekptacijarabaci/devtools_gcli_screenshot_1 (5810a403b) - DevTools - network - Copy as cURL (POST) (9036828c0) - CSP 3 - support for "worker-src" (973cea24f) - Don't enforce the arbitrary cipher suite profile. (a7b697388) - Fix freetype glyph metrics. (d092a1fe8) - Merge pull request #167 from janekptacijarabaci/devtools_network_curl_2 (12f836eaa) - The profile - resetting (doesn't work) (44386a127) - The profile - resetting - follow up (6b1e15959) - Ensure we process FIN flags on all-padding final frames. (42a21e0d4) - DOM - nsIContentPolicy - context (document) (3aae057a9) - Merge pull request #187 from janekptacijarabaci/dom_nsContentPolicy_context_1 (b642577f6) - Merge pull request #184 from janekptacijarabaci/profile_refresh_migrate_1 (37c004cb9) - Merge pull request #186 from JustOff/PR_Http2Session_FIN (8e4a08278) - Merge pull request #169 from janekptacijarabaci/csp_worker-src_1 (f4dc53287) - HTML - table - editor (contenteditable) (30ebac5c2) - Add more NS_BUILD_REFCNT_LOGGING in AtomicRefCountedWithFinalize. (a80fdd244) - DOM - PointerEvent - improvements (1755f4f75) - DOM - PointerEvent - improvements (tests / marionette) (2e70a3c51) - Implement "cookie-averse document objects". (da172983f) - Merge pull request #195 from janekptacijarabaci/dom_PointerEvent_improvements_1 (30b1721f3) - Merge branch 'master' of https://github.com/MoonchildProductions/moebius (1ea04c544) - Merge pull request #191 from janekptacijarabaci/html_table_editor_contenteditable_1 (599676a6a) - Hard-code the version number for Mozilla's version checker for add-ons. (bd9692aeb) - Hard-code the version number for Mozilla's GMP service. (2d4d09315) - Merge branch 'master' of https://github.com/MoonchildProductions/moebius (2c7948df3)
  38. 4 points
    Anyway I built my own palemoon-27.4.2 with patches in #1 and replaced GetTickCount64() with dynamic loading NtQueryPerformanceCounter() like One-Core-Api does (with --disable-skia and bundled New Moon branding, nothing else changed) http://o.rthost.cf/gpc/files1.rt/palemoon-27.4.2-unofficial-xp.7z
  39. 4 points
    Not only, When everyone agrees there are risks : http://gutenberg.net.au/ebooks05/0500421h.html#c03 Now to get back on topic (of the need to disagree), we must agree to disagree. One thing is someone expressing his/her own disappointment (or disgust) at something (or on the contrary show one's enthusiasm or appreciation for something). Another thing is telling other people what they should do. So, I can say that the way Metro Apps work suck (and suck big) and you can say (hypothesis) that they are much better than traditional programs. Both these are opinions, and each of us will bring some arguments, examples, anecdotes, etc. in favour of his thesis, and possibly the discussion will also heat up a little bit, but all the time the reciprocal respect remains unchanged. The moment I start (still hypothesis) saying that people using Metro Apps should be fired, that professionals should not allow the use of Metro Apps, I am clearly stepping over a (maybe subtle and almost invisible, still right there) border line, starting to touch other people freedoms. reputation and what not. Much more if there is not a fully demonstrated, 100% proved, objective, undeniable reason behind such a thesis. Besides, comments like your original one (as dencorso stated off-topic here since the thread is - or was - intended only as a "documentary" of the remaining "public" use of XP) will inevitably provoke a rebuttal, and then a (senseless) war is likely to start, with reciprocal accuses of incompetence, fanboyism, condescence, etc. In other words, I believe that you can well start a new thread titled "Why Windows XP sucks" (or "is totally outdated" or "is insecure", etc.) and there we can well discuss (hopefully in a plain manner) the matter, but not here. As a matter of fact if we can (for once and exceptionally ) agree on something, if you are OK with it I would ask dencorso to move the off topic posts, starting from your original comment to a separate thread. jaclaz
  40. 4 points
    I want to advise you all that the Pale Moon website has deleted the download for the last Atom/ XP compatible Pale Moon browser. The below link no longer works: http://rm-us.palemoon.org/release/palemoon-26.5.0.Atom.WinXP.installer.exe You must now use the archived link (March 19, 2017), or get it from my FTP: https://web.archive.org/web/20170319043844/http://rm-us.palemoon.org/release/palemoon-26.5.0.Atom.WinXP.installer.exe http://sdfox7.com/xp/sp3/EOL/palemoon-26.5.0.Atom.WinXP.installer.exe
  41. 4 points
    I hate to be frank.... STAY THE HECK AWAY FROM THAT FORUM! I've met friendly, helpful people there before. There have been useful tutorials as well. But the administration left me with a very sour taste. I created a thread about 4 years ago regarding the-then upcoming EOL. I asked if anyone had the knowledge to create a 7/8 compatibility layer. I was greeted with friendly responses, some expressing similar concern and ideas. But about 1 hour in, my account was terminated on the grounds of "Advocating illegal activity". I created a new account and contacted the board expressing my apologies for the misunderstanding. I was terminated a second time. I sent an email and never heard back. I caution using that forum, especially post EOL. Simply put, many of the projects you see here on MSFN simply wouldn't exist had this forum been a similar environment. I've considered migrating over to BleepingComputer, but I'm not sure. I'm not convinced any forum can replace the mammoth of information and professionalism found here. The loss of MSFN is truly a tragedy.
  42. 4 points
    A year or so has passed, and I decided to give the OS another (quick) shot. Doesn't seem like anything changed. What I can get to with 2-3 clicks in Windows 7 I most often can't even FIND in Windows 10. The new settings is a pure mess. Like even after two hours (I really was determined to figure it all out this time and didn't wipe it from the drive within 10 minutes) I haven't figured out how to get to pagefile settings. OR how the hell do I put "This Computer" to the desktop. That shortcut is not even in the Start menu anywhere. Those are two of the more painful things so far. Basically, I am unable to use the stupid system, because some of the most basic things I take for granted are simply not there, and/or are buried/obscured under tons of garbage I cannot get through. Despite my strong disgust with the OS, every time I install it again I try to approach it with open mind, thinking "It's not THAT difficult. It's just Windows. I've been using it for 22 years. It must make sense somehow." - but NO. It just doesn't. last edit: I eventually got borderline physically sick from the ***** flat design, and after 1) seeing the Calculator app and 2) starting the new Internet Explorer, where I had no idea what was part of the page and what was part of the toolbar, I shut the VM off in pure disgust. No thank you. Keep this crap, Microsoft. I'll keep using Windows 7 for as long as humanely possible. I really tried this time. Didn't work. And I lost three hours of my life.
  43. 4 points
    Maybe in the US. Not necessarily elsewhere. 7 McRib sandwiches won't last very long. My Patch still works ten years later.
  44. 4 points
    Tsk tsk tsk .... that's not an educated opinion. Out of the box, perhaps. But Windows 8 can be molded in to a VERY VERY productive environment. Better than Windows 7 - hands down! )
  45. 4 points
    I can understand your frustration, but come back to the ground. Please, if you have a problem with a user, then send him a PM and clarify it. With some far-sightedness it was clear that the Extended XP is not a simple project, at times at the present time the danger exists that updates of MS some files of your package replaced by newer file versions. KB4018556 has been withdrawn by MS, but there will be an update, this concerns Extended XP. An ongoing care of this package is essential. Then let Extended XP once in the alpha phase, so you have won time and no longer this pressure. Communicate it to the users, rather than maneuvering themselves into a hopeless situation and reacting against other users with anger. With the screen print, in a previous post, I wanted to knock you on shoulder and say so continue so great. Yes, my beloved Google Chrome still does not work, so I will not consider you as incapable, it takes time, experience and a learning phase (You hold it in the eye and somewhere there is perhaps a way, with the head through the wall does not go). At your age you tend to overestimate yourself, it is all too human. Many users are grateful for your commitment, only now and then you have to get back to the bottom of reality so you do not harm yourself.
  46. 4 points
    And here it is! The most awaited Vista repository with Server 2008 updates (atleast for the few people who care about the OS). Included in here are updates for both x86 and x64 architectures, and all versions of .NET available for Vista, from 2.0 to 4.6.1. If there's anything missing, do let me know. https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w I would like to direct a huge thank you to @VistaLover and @2008WindowsVista, for testing out the updates, and listing them in an easy to copy way
  47. 4 points
    Hi all, I just got a reply over at Adobe, and we are back in business with the Google Chrome PepperFlash PPAPI on Windows XP. The latest stable is version, and the latest beta is Both work on XP. Sometimes you just have to ask nicely, and people will be willing to help you out. https://forums.adobe.com/message/9507336#9507336
  48. 4 points
    You won't even have to do that apparently. I've been doing some searching, and all you have to do is edit wuaueng.dll so that IsCPUSupported always returns true. Here's some information I found on it: https://github.com/zeffy/kb4012218-19 Edit: I just tried this myself, I have a newer update that changed the patch, so I made a patch myself. I can see Windows Update again and get any update I need again. Can confirm this works.
  49. 4 points
    Big Muscle, I was just thinking people would like hearing any thoughts you have about the new version. I know I would. I was just dropping a hint that folks, myself included, really like your software and hope you'll continue to develop it (though I wouldn't blame you if Microsoft has made you tired of having to re-develop it). You've done such good work in the past people are hoping you'll continue, that's all. I had build 1607 build 14393 running (and looking) very nice, in no small part because of your fine work. I've been using - trying to use - the Windows 10 out-of-box UI while testing version 1703 build 15063 and frankly it sucks pretty hard. And of course I'm indebted to you for making my Windows 8.1 set up the system I can count on continuing to use on my real hardware. Thank you! -Noel
  50. 4 points
    If you'd like I can also create a Server 2008 updates for Vista repository on my Mega account... I think it will be more useful for Vista users, since 8.0 users have the Monthly Rollups, whereas Server 2008 still delivers updates the old fashioned way (that is, seperate KB for each update).