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. 


  • Content count

  • Donations

  • Joined

  • Last visited

  • Days Won


VistaLover last won the day on July 27

VistaLover had the most liked content!

Community Reputation

45 Excellent

1 Follower

About VistaLover

Profile Information

  • OS
    Vista Home Premium x86
  • Country
  1. Hi - Facebook has phased out the use of the Adobe Flash NPAPI plugin months ago; to view FB vids you need a HTML5/MSE capable browser; please refer to post #1 of this thread and review the section "Q: Can't play H264 clips?" Please also make sure that you have enabled "MSE" and "MSE for MP4 video" inside New Moon's Options/Content/Video... Default language for New Moon 27.6.0a1 is en-US; head over to localization releases, you should pick your corresponding language pack (it?) from the latest release 27.6.0_RC2; just click "it.xpi" and allow the installation to take place; then open about:config?filter=useragent.locale in a tab and modify the value from "en-US" to "it"; finally, restart NM and once it loads the GUI should be in Italian!
  2. I am sorry to report that yet another application moves out of Vista support mpv is a CLI media player, a recent fork of MPlayer (itself a fork of mplayer2); while it is mostly known/used on non-Windows OSes, it does support Windows too codewise and win32/win64 executables (mpv.exe) can be compiled via, e.g., MSYS2 native Windows compiler (but, sadly, MSYS2 now requires Win7+ and preferably the x64 architecture ). Power Windows users may be already familiar with mpv when using it with other CLI applications like the stream-downloaders livestreamer (now defunct), its maintained fork streamlink and youtube-dl; but perhaps others may know mpv as the media engine driving the front-end SMPlayer (this can also use the original MPlayer under the hood, but from experience has worse performance compared to using mpv). The mpv devs have made it clear from the start of the fork (ca. 2012) that they'll be dropping support for very old systems... Windows XP was accidentally dropped in November 2015, but then the devs decided to do nothing to restore its support. Most unfortunately, we're now seeing a repeat of that with regards to Windows Vista; you can read about it in this GitHub issue . Though the breakage was indeed unintentional, there'll be no effort spent by the devs towards restoring Vista support As you'd expect in such cases, the same ol' "Microsoft’s extended support has ended" mantra was recited but, in all fairness, the dev did acknowledge that as The justification of "Vista not registering in my download statistics: https://mpv.srsfckn.biz/stats.html" I found quite lame, TBH; what it all comes down to is While he obviously could, the main dev providing the Windows executables said The only options offered by the devs to Vista users (cross compile in a Linux VM or install Linux in the Vista machine and dual-boot) are far from realistic for most Vista users on old-ish hardware, not to mention the huge learning curve required to master Linux at first and the cross-compiler itself after that... So, on the Windows builds page the very last Vista compatible binary is the one marked as 2017-04-23, which is in fact mpv-v0.25.0: https://mpv.srsfckn.biz/mpv-i686-20170423.7z https://mpv.srsfckn.biz/mpv-x86_64-20170423.7z versions 0.26+ will simply not run on Vista; to be exact, this is only valid for the pre-compiled binaries offered by the main dev in his repo; in theory, code newer than v0.25 could be compiled with modifications to the crypto lib used so as to restore Vista support; I, for one, don't possess neither the hardware nor the know-how to even attempt such a task...
  3. FYI, latest language pack (27.6.0_RC1) released by JustOff also targets unstable builds 27.6.0a1 natively, so no longer the need to manually hack the install.rdf file of the pack
  4. ... Just go to Pale Moon localization and save to disk latest language pack v27.5.0_RC8 that suits you (this is an .xpi file, i.e. a .zip file); modify the install.rdf file inside it (e.g. with 7-zip) and change maxVersion from 27.5.* to 27.6.* ; save your changes and then install modified language pack in PM 27.6.0a1 (install from file in the add-ons manager or simply by drag-n-drop in a tab). This is how I got the Greek locale myself on PM unstable in the screenshot posted previously So, you can easily enjoy PM 27.6.0a1 in German, if you so wish! PS: After installing the LP, you'd have to go in about:config, filter general.useragent.locale and modify the default en-US to the language of choice, e.g. de; restart PM for the change to take effect; tada!
  5. Congratulations @roytam1 That was it! Your xpmod now loads successfully on this old Vista laptop: And with your "portable" LAV Filters DLLs, MSE+H.264 works too (without the need to install system-wide)! I think my old (2007) Intel CPU (Core2 Duo T5250 @ 1.50GHz) can only go as far as SSSE3... Will better check tomorrow how your build compares to the "official" one on Vista SP2 x86 - and of course you're a true gem for people still on XP... Cheers!
  6. Hello @roytam1 I was reading your posts in the Pale Moon forums (not a member there, just a frequent lurker) and decided to come and follow you here, too I am currently using the official unstable (x86) Pale Moon builds (latest is 27.6.0a1 buildID 20171001090158) on my Vista SP2 32bit laptop and out of pure academic curiosity I wanted to check whether your latest xpmod would actually run on Vista, too... However, as others have stated, it will refuse to load a GUI (though there's a palemoon.exe process running in Task Manager at ~ 29MB of memory) and Windows informs of a crash: Problem signature: Problem Event Name: APPCRASH Application Name: palemoon.exe Application Version: Application Timestamp: 59d1184b Fault Module Name: mozglue.dll Fault Module Version: Fault Module Timestamp: 59d1183f Exception Code: c000001d Exception Offset: 000034c5 OS Version: 6.0.6002. Locale ID: 1032 Additional Information 1: 98b2 Additional Information 2: e55896255cd32d51a93c767d394c7c40 Additional Information 3: 4946 Additional Information 4: 85d6476da8052e18313817c31a393122 I can confirm (though I suppose it's irrelevant in this XP-targeted thread) that Feodor2's 27.5.0 x86 compile will load and run fine on Vista (but MSE+h.264 doesn't work - I haven't installed LAV Filters system wide to check, either...). Keep trying and thanks for your efforts
  7. Server 2008 Updates on Windows Vista

    Source: Description of Software Update Services and Windows Server Update Services changes in content for 2017 Thursday, August 17, 2017 New non-security content: Update for .NET Framework 4.6, 4.6.1 on Windows Server 2008 SP2 (KB4038923) Support link: KB4038923 , catalog link: KB4038923 Prerequisites: 1. .NET Framework 4.6/4.6.1 2. D3D Compiler Update for WS2008 SP2 (KB4019478) (Should be already installed since July 2017) Note: Installed without issues on this fully patched (Vista EOL + WS2008 updates) Vista Home Premium 32bit laptop. Next regular Patch Tuesday is following Tuesday, September 12th, 2017.
  8. Server 2008 Updates on Windows Vista

    Nice find . It was file Windows6.0-KB4034786-x86.msu, Microsoft Knowledge Base Article for that was on this link, which now returns a 404 type error (Try searching for what you need - This page doesn’t exist.). And it's nowhere to be found on catalog either ... Who knows what... (Un)fortunately, I never jump to install MS updates the first day they become available (for fear they have screwed up things... ), I patched my system on the 11th, i.e. after KB4034786 pulled a disappearing act...
  9. Server 2008 Updates on Windows Vista

    There has been some discussion recently over at the BleepingComputer.com Forum's similar thread about the prerequisite update KB4019478. My personal findings are: 1. When KB4024848 was first released in July, it was included in the .NET FW update bundle labelled as KB4032116 ; when one accesses the catalog link, its prerequisite KB4019478 (x86 flavour) is offered as file "windows6.0-kb4019478-x86_246d86dae3b75ce3ee0180a18db1f04992a14c1b.msu". That file has a size of 1.434.955 bytes and a digital signature of "Thu Apr 13 2017 19:47:38 UTC". This is the file I installed myself... 2. When KB4033990 was released this August (that replaces KB4024848), it was part of the .NET FW update bundle labelled as KB4035039 ; when you go to that catalog link, the prerequisite is again (?) included and labelled as KB4019478, but the x86 flavour is now downloaded as file "windows6.0-kb4019478-x86-custom_83098465b9ee0b4b39e02fa8f6853fe196966a26.msu". That August file has a size of 1.435.558 bytes (slightly bigger) and a digital signature of "Thu Apr 13 2017 10:53:14 UTC", which means the August file (updated one?) has a dig sig almost 9 hours prior to (i.e. it's older than) the previous July file for KB4019478 I don't know what to make of the above . Obviously, these are different files for the same "D3D Compiler Update for WS2008 SP2", which is, no doubt, related to this KB article and KB4019990. In the BC thread, the thread maintainer (Sardoc) has successfully installed this second (but according to my examination) older file on top of the previous, July, one... I am still undecided, leaning to hesitant... Take your peak... (I really have no idea how "amicable" is MSFN towards BC; I do know that some MSFN members ( @JodyT and recent @Ruan ) are also members there; participants in that similar BC thread are perplexed wrt to the newly introduced TLS 1.1/1.2 support in Vista/WS2008; see here onwards... Perhaps a kind soul here can refer them to my previous MSFN post . Thanks in advance )
  10. I have! But in all honesty, it's not a browser I can use as my main Vista browser: 1. It's focused on Privacy and Security, thus it doesn't store any browsing/download history (gets wiped out upon exit - no way to override that... ); plus, it won't allow you to resume a previous tabbing session 2. Has a nasty bug when trying to open a bookmarks folder placed on the bookmarks toolbar (won't let you inspect the content of the folder, is only able to open all bookmarks within the folder in equal number of tabs. 3. Its WMF/MSE support on Vista SP2 is broken (much like Firefox 53); so it can't use system codecs for h.264/aac playback, either as standalone MP4/m4a files or AV streams encoded in h.264/aac; you can also perform the youtube HTML5 test where you'll discover both "H.264" + "H.264 & MSE" are disabled (red). 4. The real deal breaker is that Epic Browser doesn't accept ANY EXTENSIONS from Google store, including themes, thus its overall functionality (as a Chrome 58 based browser) is severely limited to basic web browsing... Its own webstore (only viewable with Epic Browser) currently only lists 7 (security related) extensions! Quite frankly, the only feature I found semi-useful was its built-in Epic (encrypted) Proxy, which, among making you more invisible on the net - plugins disabled for that, it does allow for accessing geo-filtered content...
  11. Yes, I have tried that; has some minor issues, though... But it's based on Chrome 50.0.2661.102 code, so quite old already from a performance and security standpoint... Even if the (Chinese?) devs are actively patching security holes, 50.0.2661.102 is/was the last version of Chrome that would run on Vista SP2, this fact alone makes me pessimistic about future Vista compatibility/support... The Slimjet devs dropped Vista support when they had to move to Chromium > 53 codebase, the Russian devs of Yandex Browser managed to keep Vista support even when their code was based on Chromium 57 (last version of Yandex Browser that supported Vista SP2 was, code based on Chrome 57.0.2987.137); Yandex no longer supports XP/Vista
  12. Server 2008 Updates on Windows Vista

    Source: Description of Software Update Services and Windows Server Update Services changes in content for 2017 Tuesday, August 15, 2017 New non-security content: 1. Update for WS2008 (KB4019276) This is a re-issue of the exact same MS update first published on Tuesday, July 18, 2017 and documented here; what's indeed curious is that MS catalog link for this update now has two separate entries, one with a "last updated" attribute on 18/7/2017 and another one "last updated" on 14/8/2017 ; FWIW, both .msu files appear identical, with a digital signature of 20170610. I had this installed last month, trying to re-install the re-issued version fails, with a "This update does not apply to your system" message (which is highly expected and justifiable...). So, if you did not install this last month, have a go now... EDIT: The reason for re-issuing KB4019276 again is explained in this MS blog entry; first issue in July was catalog-only, this second re-issue adds it to WU/WSUS as an Optional update, there's a third re-issue next month on all three WU/WSUS/Catalog, when the update will be uplifted to Recommended (thanks to BleepingComputer.com forum member "lmacri" for the find ). 2. Update for Windows Vista (KB4036162) "The desktop app WordPad crashes in Windows Server 2008 SP2" In case you're wondering whether I made a mistake, then no, this is another post-EOL update for Vista and is listed as such in MS catalog site; Windows Update on Vista doesn't work for this one though, you'll have to download and install manually... 3. Update for WS2008 (KB4037616) "The spoolsv.exe process crashes in Windows Server 2008 SP2"; link . Wednesday, August 16, 2017 1. August, 2017 Preview of Quality Rollup for .NET Framework 2.0 SP2, 4.5.2 and 4.6[.1] on WS2008 SP2 (KB4035039) Support link: KB4035039 , catalog link: KB4035039 This is a .NET Framework bundle update, that breaks down to the following individual ones: 1a. Quality Rollup for the .NET Framework 2.0 Service Pack 2 for WS2008 SP2 (KB4033994) Supersedes KB4014592 (May 16, 2017) 1b. Quality Rollup for the .NET Framework 4.5.2 for WS2008 SP2 (KB4033993) Supersedes KB4024845 (July 18, 2017); install this update if, by choice, you're still on .NET FW 4.5.2 1c. Quality Rollup for the .NET Framework 4.6[.1] for WS2008 SP2 (KB4033990) Supersedes KB4024848 (July 18, 2017), but still has the same prerequisite of "D3D Compiler Update for WS2008 SP2 (KB4019478)"; install this update if on .NET FW 4.6/4.6.1 Happy manual updates Vista folks!
  13. Server 2012 Updates on Windows 8

    Bookmark the following MS URL: https://support.microsoft.com/en-us/help/894199/software-update-services-and-windows-server-update-services-changes-in as have I (to keep track of WS2008 updates to apply on Vista) ... According to that URL: Tuesday, August 8, 2017 Changes to existing nonsecurity content: Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7 on Windows Embedded 8 Standard and Windows Server 2012 (KB4035508) Metadata has changed. Binaries have changed. This update will need to be reinstalled. MS catalog link Prerequisites: To apply this update, you must have the .NET Framework 4.6, 4.6.1, 4.6.2, or 4.7 installed. (So not applicable if you're still on 4.5.x). I wouldn't... Any particular reason not to upgrade .NET Framework on your Win8 setup?
  14. Server 2008 Updates on Windows Vista

    Since we've got a month's worth lease of life (fingers crossed it'll be for much longer ), am just going to post August 2017 WS2008 updates, applicable to WinVista SP2: Source: Description of Software Update Services and Windows Server Update Services changes in content for 2017 and Security update deployment information: August 8, 2017 Tuesday, August 8, 2017 Security Updates 1. Cumulative Security Update for IE9 (KB4034733) Supersedes: KB4025252 2. Security Update for WS2008 (KB4022750) Security update for the Windows NetBIOS denial of service vulnerability in Windows Server 2008: August 8, 2017 Supersedes: KB4021923 3. Security Update for WS2008 (KB4034034) Security update for the Windows Search remote code execution vulnerability: August 8, 2017 Supersedes: KB4032955 4. Security Update for WS2008 (KB4034741) Security update for the Windows Kernel information disclosure vulnerability in Windows Server 2008: August 8, 2017 Supersedes: KB4022013 5. Security Update for WS2008 (KB4034744) Security update for the Volume Manager Extension driver information disclosure vulnerability in Windows Server 2012: August 8, 2017 6. Security Update for WS2008 (KB4034745) Security update for the Windows CLFS elevation of privilege vulnerability in Windows Server 2008: August 8, 2017 Supersedes: KB3203838 7. Security Update for WS2008 (KB4034775) Security update for the Microsoft JET Database Engine remote code execution vulnerability in Windows Server 2008: August 8, 2017 8. Security Update for WS2008 (KB4035055) Security update for the Win32k information disclosure vulnerability in Windows Server 2008: August 8, 2017 Supersedes: KB4022887 9. Security Update for WS2008 (KB4035056) Security update for the Express Compressed Fonts remote code execution vulnerability in Windows Server 2008: August 8, 2017 10. Security Update for WS2008 (KB4035679) Security update for the Windows Error Reporting elevation of privilege vulnerability for and Windows Server 2008: August 8, 2017 Supersedes: KB2929733 11. Windows Malicious Software Removal Tool - August 2017 (KB890830) August's edition is file Windows-KB890830-V5.51.exe ; M$ have blocked this file from running on Vista, but it does so on WS2008; still curious as to how they do that, considering they're both NT6.0; any thoughts some clever people here have? Never mind though, for an equal (even better) workaround head over to Microsoft Safety Scanner old site and download latest version of file msert.exe (mine was on v1.249.918.0 yesterday...); both 32 and 64bit binaries are available. The tool can be run on Vista SP2 fine; choose the default quick scan, which should last ca. 12-15min (YMMV): M$ have a new site for the tool here ; as you can see, no mention of Vista in the supported OSes, but I can assure you the version I fetched yesterday ran fine on my setup; perhaps they'll change things in the future, then again perhaps not... All WS2008 updates mentioned thus far installed successfully on this Home Premium SP2 32bit laptop (not a VM): I explained this in a previous post ; KB4024848, a NET Framework 4.6[.1] update, has the D3D Compiler update (KB4019478) as a prerequisite...
  15. Server 2008 Updates on Windows Vista

    Well, if you indeed look at it from M$'s perspective, you shouldn't even be considering patching your OS after it has become EOL'ed - apart from Win10, which is sold as a service, previous Windows OSes can be likened to perishable goods with an expiration date - past that date, it should be thrown in the bin, not injected with preservatives ... It would appear the Vista64 mods were somewhat more closely affiliated with M$, or simply thought in a similar vein, hence the blocking of your account... Fortunately, threads like this and the one we're on attest to the fact MSFN mods think in a more liberal fashion...