Leaderboard

... I don't want to derail this thread, but I recently became aware of the following extended article: Mozilla - Devil Incarnate It's certainly an eye opener for those that have little to do with Mozilla internals, most certainly a recommended read... Having been a Firefox Nightly tester (from versions 27.0a1 all the way to 46.0a1, then briefly from versions 51.0a1 to 53.0a1=EoS for Vista SP2 ), having been a subscriber on both Bugzilla and the Nightly Testers mailing list, I can assure you the attitude exhibited by most Mozilla devs towards anyone in the user base not condoning their "devine" decisions is pretty accurately detailed in the linked article... E.g., I, with several other Vista users, tried - in vain - to persuade them not to put Vista in the same boat as XP and, hopefully, extend Vista support further, past Fx 52 (up-to-version 54.0 could've been easy), but was met with a brick wall - their pretenses were that Vista was too much of a burden to support resource-wise and they insisted I switch to Linux; and that was at a time (circa end of 2016) when Firefox users on Linux were 1/20th of the Vista users... I recall I persevered and tested the whole 53.0a1 development cycle on my Vista machine many days after they made everything in their power to block 53.0a1 on Vista; when the installers blocked the OS, I switched to the "zip" packages and continued telling them that their - then - current code remains Vista compatible and that they were wrong to drop Vista support so soon - they were really mad and unsure as to how I was able to pull this through, until another user pointed to them (!) that the standalone executables (firefox.exe) would launch on NT6.0; then they quickly patched that by raising subsystem version to 6.1 in the EXE's PE header; but I used PE_patch (or similar tools) to undo their artificial block and set it back to 6.0; they went livid when I posted with a Nightly 54.0a1 version running on Vista SP2: ... But eventually they started using their new shiny toy, Rust programming language, which, when compiled, only targets Win7+, thus my 54.0a1 testing experiments ended abruptly... In fairness, very few code authors like it when their coding decisions are being challenged by the user base; I've witnessed this in many instances and this is certainly true with Moonchild Productions team, too; simply browse their official forum and GitHub tracker, where any "questioning" voice (outside their narrow circle of devs) is quickly muffled (more politely by Moonchild himself, brutally by you know whom...) But in the end, if I had to choose between a Google product and a Mozilla one, the lesser of two evils is the obvious choice...

Sadly, this came too late, but please try it. It's based on the same AMDXHC driver for Windows XP, but this required just a device check patch. Included are both 32-bit (x86) and 64-bit (x64) drivers, plus the "switch" driver. - The AMDXHC driver is safe to use and easily installed. - Supports all Intel USB 3.1 XHCI controllers (7, 8, 9, 100, 200 and 300 series, maybe even HEDT chipsets). - "Switch" driver may be needed if you don't get USB3 speeds on Sandy Bridge, Ivy Bridge and Haswell (*) systems (7, 8 and 9 series chipsets). To use this, I'd recommend a backup. Open Device Manager -> System Devices -> PCI Bus Update driver -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer Have Disk -> open the folder containing the HCSwitch driver files PCI Bus will be displayed, continue the installation. When finished, just restart Vista. (*) Haswell should work with Vista 32-bit (x86) only. http://www.mediafire.com/file/1kjhhl0fq1ofc2m The original Intel XHCI driver can be modded to work on Vista, but as this one works so fine, I don't have any plans to do it.

not really. lack of CMOV instruction set is the problem. In PCem, only Cyrix 6x86MX series emulates CMOV instructions, and it runs sp52-ia32. and I can make a list of processors that can run sp52-ia32 (which support CMOV instruction): Intel: Pentium Pro or later AMD: K7 (original Athlon/Duron) or later VIA: C7 or later Transmeta: all CPUs are capable to run sp52-ia32. Cyrix/IBM: 6x86MX or later, MediaGXm(MediaGX-S) or later National Semiconductor/AMD: Geode GX or later DM&P/Vortex86: Vortex86DX3 or later

Today I managed to install .NET Framework 4.8 on my VM with Windows Vista Home Basic x64, how did I do it? First to install it use the method previously used with the .NET Framework 4.6.2 and 4.7.x; nothing more than this time the procedure is longer since when starting any application designed for .NET Framework 4.x in Vista an error dialog appears for lack of instructions in kernel32.dll and ole32.dll respectively. In HxD edit the clr.dll file that was the library that calls those instructions, replace clr.dll with the edited version and, surprise! NET Framework 4.8 is compatible with Windows Vista! Even create a small application with Visual Studio in Windows 7 to see if it worked at all and NET Framework 4.8 works correctly in Vista. Instructions for installing NET Framework 4.8 on Vista (you need to have a minimum .NET Framework 4.6.1 installed) 1. With the method of previous versions on this page: https://msfn.org/board/topic/178673-tutorial-how-to-install-net-framework-472-on-windows-vista/ 2. After finishing the installation, replace clr.dll in "C:\Windows\Microsoft.NET\Framework\v4.0.30319" and "C:\Windows\Microsoft.NET\Framework64\v4.0.30319" with the versions in the zip file 3. Do regsvr32 if necessary 4. Restart your Windows Vista 5. NET Framework 4.8 in Windows Vista! Link to download the parch: Download

In my case, even Basilisk doesn't stomach everything I throw at it anymore.

@dencorso Done! Was about to post this on Win-Raid, but I believe this forum has more Vista diehards!

Changelog is inside the rar comment: WinNTSetup 4.0 RC2 - added capture mode NONE - added apply mode Wimboot:WIMCOPY - update offreg.dll - allow creation of expandable VHD with any size - non fitting expandable VHDs will stop from auto expanding on boot

not quite possible as mozilla has millions of commits between them, many APIs are changed. Simply reverting random commit(s) might make the situation worse.

You may be right - you usually are - but ... ... so I think it's at least worth a try.

You need to install the Adobe Primetime CDM. As posted in the past, since my old Intel Core 2 Duo processor (Merom) does support the SSE2 instructions set, I've not had the curiosity to try Firefox (Nightly) 45.9.x on this laptop, happily using the UXP forks, rarely Serpent 55.0.0. But, from memory, I think your quoted suggestion regarding RoyTam1's Firefox 45.9.18 under Windows XP is flawed... 1. EME support in the Mozilla Firefox browser in the form of the Adobe Primetime CDM first materialised in Firefox 38.0; the CDM targeted Windows only OSes and was only visible from Vista SP2 onwards ; in a later Firefox version (unsure exactly which ), it was made available to Windows XP, too; but the makers, Adobe, didn't want to support APCDM for DRM purposes under XP, especially since the initial implementation of it, v15, had issues on that OS; the Mozilla team couldn't make their minds up whether to keep the CDM on XP or not: they kept un-hiding and then hiding it again for a certain period (), especially when the next iteration of it (v17 - v16 was only 64-bit) was offered by Adobe (with lesser issues on XP): Unhide Adobe GMP on Windows XP https://bugzilla.mozilla.org/show_bug.cgi?id=1234099 Make Adobe GMP available to Windows XP users in Firefox 45 and later https://bugzilla.mozilla.org/show_bug.cgi?id=1234100 GMP crash or garbled HE-AAC audio when playing MP4 decoded using Adobe's GMP https://bugzilla.mozilla.org/show_bug.cgi?id=1236756 Hide Adobe GMP on Windows XP in Firefox 46 and 47. https://bugzilla.mozilla.org/show_bug.cgi?id=1265928 On supported OSes, the CDM was automatically downloaded and installed in Fx <=46.0; in v47.0-51.0, in new profiles, it was only downloaded and installed on demand, when visiting a media site that asked for it (although previous installations of the CDM in existing "dirty" profiles, put there under Fx < 47.0, remained unaffected). Support was officially disabled by Mozilla in Firefox v52.0 for all WinOSes, because, by then, the Audio-Video media industry had completely moved over to (Google acquired) Widevine CDM for enforcing DRM on copyrighted content (the WVCDM first appeared in Firefox v47.0 and is visible on Vista SP2+) ; in Fx 52.0/ESR 52.x.x, the APCDM would no longer be downloaded on demand in a new profile, previous installations of it get disabled; but the underlying support code was still left intact; that code was finally completely removed in Fx v53.0 (compatible with Win7+). At least on Vista (SP2), FxESR 45.9.1 downloads and installs APCDM v15 automatically: 2. From a previous exchange with Roy in these forums, it was made known to me that to get proper h264/aac decoding support on that fork under XP, needed for HTML5 embedded MP4 video, you'll have to download and place inside the browser's main installation folder (not its profile) the LAV filters DLLs that were made available previously to get the same feature for the New Moon 27.x.x/Tycho fork: @roytam1 : Post #1 in the original thread is now locked, so probably you can't edit that yourself now (nor can I properly quote the above excerpt ); perhaps a mod can, or you could add that FxESR 45.9.x specific bit on post #1 of this second (continuation) thread ? Thanks! Sadly, even with the above decoders installed, it's not definite Twitter clips will play OK; they use MPEG-DASH and/or HLS streams, which require MSE support in the browser; I'm not sure how mature is Fx45's MSE implementation for those vids to work...

... which is why I added You need to install the Adobe Primetime CDM.

Yep, whenever the error is "this is not a valid Win32 applicarion" it is worth to try this, though sometimes it is needed to change also the "Minor" OperatingSystem and Sybsystem fields though 5 0 5 0 is OK, jaclaz

@Sampei.Nihira Regarding SumatraPDF-prerelease-11495.exe (portable) Seems to work once you edit the version check in the PE header: Two bytes changed soon after marker "PE" 06 .. 06 to 05 .. 05.

@WinFX, I confirm - it works. Thank you! To check it the useful program is AniView 1.5.3 - it requires .NET 4.8. https://github.com/CodeDead/AniView/releases But I used the MSI installation method - on top of the already installed .NET 4.7.2. Now Vista has a fully functioning .NET stack Advanced PortChecker 1.5 - https://github.com/CodeDead/Advanced-PortChecker/releases DeadPix 1.2 - https://github.com/CodeDead/DeadPix/releases Now they can be launched on Vista.

Now Install .NET Framework 4.8 is possible to install without ordinals problem

360ee v11.0.2251 was released. I recommend not to install official version but Repack & Portable version. https://lrepacks.ru/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html

Change is inevitable. Necessary. We have increasing needs for tech. Embracing change is not what this is about. Creating incompatibility to suit business goals is not right. Our parents were appalled at planned obsolescence. Now we're told to accept it. Embrace it. Our tech becomes obsolete even before it can wear out the batteries! Using Fear, Uncertainty, and Doubt in the name of "security" as a way to herd people into doing what they would not do is deplorable! Yet for the most part we find ourselves powerless, because people who predicted this and warned against ceding control were marginalized. Ridiculed. Pushed aside. -Noel P.S., the latest incompatibility I've noticed: RDP from an older system into a Windows 10 v1903 system and your mouse jumps around when the cursor graphic is changed. It didn't do that remoting into v1809. The protocol has been good enough - indeed excellent - for decades. It doesn't have to change. Aero Glass just gets shut off and requires regular reinstalls, even though it works fine. Presumedly because some jerk inside Microsoft wants us NOT customizing our Windows look, because that goes against their current Marketing direction. Who the &%$& do they think they are? We could talk about the atrocities Apple is pushing on people... No more 32 bit programs. No more putting things where you want them on your disk. Can't reach your Documents area even though you've shared it? Oh, right, that's security. P.P.S., I'm typing this on a perfectly good Digital LK250 keyboard circa 1985. And there isn't a better one built today. Stuff doesn't HAVE to go bad just because it's tech.