Leaderboard

You haven't provided me the specs of your machine, nor the Foxbox version you are using. The purpose of the UOC Patch is to optimize Mozilla based browsers for old and obsolete systems. Not for modern computers. Your computer is multi-core with PCIe and such? You do not need the UOC Patch. As simple as that. Try it on an Athlon XP or a Pentium III machine with a supported graphics card, and you will notice the difference. As for why I use a Pentium III computer in 2019, I do not need to add anything other than "for fun", because I like to use it. You don't like that? Not my problem. You clearly have completely missed out the point of this patch, and I am not interested to continue replying to your posts. I have been taught that trolls must not be fed. Have a nice day.

You would be horribly mistaken. It’d still be wrong, but vastly less wrong to say you’re the only person who doesn’t use single core CPUs here these days. And complaining about the hardware people choose / choose not to use isn’t something we do here.

Yeah, instead of taking the old OS and giving it a modern look (lots of win8/10 visual styles for XP and even RP 9.7 floating around), the old OS should be updated with support for the newest hardware and win32 APIs. I want a UEFI bootloader and full GPT support in an x64 build of win2k, which I would wait in a ten-mile line to buy. But that really can't be shown off in a flashy video.

The patch works fine on all of my single core machines. Your inability to use the software correctly is not the authors fault Stop projecting.

That "ad-blocker" is actually there too, in the list just some lines above. Frankly that had me quite confused too! And archived here: http://web.archive.org/web/201910/https://legacycollector.org/firefox-addons/364867/index.html But thanks for letting us know that horrible news :-( It's an absolute desaster for users of older browsers or forks. Everything that good people created gets destroyed fully intentionally since many years, everywhere, without any need :-( How long until those addons will vanish from waybackmachine too? Or perhaps the waybackmachine will get destroyed? How long until justoff with his CAA-archive will have to give up too? Whoever created legacycollector as a service for humanity was FORCED to stop!! But that's how things are going in this downhill era. So currently only CAA addon is left, but I can't even read that on this computer, it only runs on more modern browsers :-( And the Seamonkey addons are nice, but only a tiny few of all Firefox addons. Have also read that Seamonkey is having growing problems too with Mozilla cutting all engine bridges that forks could use in the past. And hardly any developers remaining either, so assume it's only a matter of time until Mozilla will kill their addons too.

normal build is not suitable for SSE-only machines. and AF builds are for me to test their front-end changes and I don't have a plan to switch my codebase to it right now.

Arctic Fox is forked from PM 27, but I don't think @roytam1's build is SSE-only. Perhaps he can give us an SSE-only build of it; IDK

When is flat everything to die? Modern user interfaces have a serious lack of soul.

You should see at least two tasks; perhaps more (if you set dom.ipc.processCount to a value greater than 1. I use 2.) If you don't, click Help / Troubleshooting Information, and in the "Application Basics" section near the top, look for the "Multiprocess Windows" entry. If it reads 0/1, then it's disabled and there should be a reason in parentheses. I haven't tried it in a version earlier than FF 52. In FF 52 you have to create the browser.tabs.remote.force-enable Boolean pref, but that shouldn't be necessary in FF 45. (Mozilla disabled it by default for XP systems in FF 49.)

Glad you got it working! No biggie, but thanks! It did sort of grate on my nerves a bit, especially when jumper chimed in with the same misspelling!

Much more discussion about tweaking multiprocess mode there....

Just for the record, I tried out the new UOC Patch for FF 52 on my dual-core AMD A4 machine (integrated GPU) with Windows 7 and Serpent 55, and it did speed up scrolling noticeably. It wasn't a big difference, as performance was already fine with that hardware (even though it's near the low end for Windows 7 systems), but it was at least enough to notice. So it might be worth trying even if you have a multicore processor and/or have multiprocess mode enabled. BTW, you can benefit from multiprocess mode even with a single-core processor. Although the processor can only do one thing at a time, multiprocess mode will still let you split your RAM usage among several processes and let you open more tabs without running out of RAM.

It's been archived at the Wayback Machine: https://web.archive.org/web/20191013130454/http://legacycollector.org/firefox-addons/ Also, review this post from the old thread:

For pale moon 27-28 it is necessary to install: Greasemonkey for Pale Moon https://addons.palemoon.org/search/?terms=Greasemonkey+ (greasemonkey-3.31.4-pm_forkBranch.xpi) viewtube.user.js https://github.com/sebaro/ViewTube/raw/master/viewtube.user.js or view https://github.com/sebaro/ViewTube/blob/master/viewtube.user.js http://sebaro.pro/contact/

Windows 10...I never liked the OS. Released unstable like early Vista, constant bloat like 98 to XP, and a horrid start menu. The total installation size for Windows 10 is also absurd compared to all other versions; ISOs for windows 10 are a couple gigabytes while a perfectly updated XP is less than ~700mb and fits on a CD. I've seen modded Windows 10 isos to find that even the smallest isos are 1.8gb. That's VERY tiny for Windows 10 especially.

You're welcome. Google search for the exact filename in quotes. Ignore any "too easy"/questionable sites that come up early in the results. Go through the results looking for any full HTTP URL addresses to where the file once existed; try those live and in the Wayback Machine. If those don't work (i.e. the akamai.net link), the look for any FTP URL addresses. In this case the file name was inside a .TXT file that existed on an FTP server. I took a chance that that folder would contain the files listed in the .TXT, removed the .TXT file from the address, and checked the containing folder. As for Windows 10, that's out of my expertise. Theoretically drivers for earlier Windows 8/7/Vista might work, but it's a trial and error experiment.

Typo. I do know the real spelling, I just sorta had a brainlapse a couple of times, I'll fix the title

You win! I sure am ; I was planning to post a detailed new article in the Vista forum (when my spare time permitted), but since you couldn't wait, I didn't want to come off as giving you the cold shoulder... FTR, the setup file itself (mpas-fe.exe) used to be (until and including Sun Oct 20th) dual signed (both SHA1 & SHA2 digest algorithms); that file is comprised by four other files: MpSigStub.exe mpengine.dll mpasbase.vdm mpasdlta.vdm mpas-fe.exe v1.303.1946.0 released on Fri Oct 18th was the last one to be itself and all of its constituents dual signed - engine version in that file was 1.1.16400.2 (as said, dual signed); this was the last version of mpas-fe.exe (and, of course, mpam-fe.exe for MSE) installable on a Vista SP2 OS without SHA2 code-signing support present! Later that day (in my timezone), new version 1.305.17.0 was released (might've been another 1.305.x.x version I missed prior to that ); while file mpas-fe.exe was still at the time dual-signed (but I could only see the SHA1 sig then), to my great dismay I discovered that running the file would not update my WD defs ; to cut a long story short, and after at least an hour of troubleshooting (which included dependency walker, as I was misled by what M$ did to the XP users of MSE/WD), I realised that 1. The 1.305.x.x series introduced a new engine version, v1.1.16500.1 2. While I could see SHA1 sigs for files mpas-fe.exe, MpSigStub.exe, mpasbase.vdm, mpasdlta.vdm, I couldn't for the engine DLL file, mpengine.dll, so I assumed it was only SHA2 signed. In the past, I wasn't that worried about files only signed with SHA2, other than the fact I couldn't be 100% sure the file hadn't been tampered with... For executables, a prior update, KB2763674 , made it possible to run them (although, in retrospect, not a clever thing to do if one is unable to verify EXE's signature...). But in the case of WD (and MSE), the anti-malware application has to verify (via the OS) the updated engine and definitions files (contained in the downloaded mpas-fe.exe setup) for it to load them; not being able to verify mpengine.dll, WD remained stuck at defs v1.303.1946.0 (with engine v1.1.16400.2) Since I was not running Avast, I decided to install (latest) SHA2 code-signing support in my OS and retry with the 1.305.x.x mpas-fe.exe files; it WORKED! It wasn't until sometime during Sun, Oct 20th, that M$ posted some relevant details in their now "rebranded" Security intelligence page: Intelligence my... behind (!) ; make no mistake - you read right: they had already broken mpas-fe.exe on Vista SP2 since the evening (UTC+0300) of Fri 18th... FWIW, latest (1.305.941.0) mpas-fe.exe file is itself only SHA2 signed, files MpSigStub.exe + mpasbase.vdm are dual-signed and files mpengine.dll + mpasdlta.vdm only SHA2 signed (i.e. still a mess! ) It isn't I have blind faith in WD's efficacy these days, I have a paid-for full Internet Security Suite (Kaspersky) as my line of defence, WD is kept going for "legacy" reasons; KIS doesn't object to WD being enabled, nor did it manifest any adverse symptoms after the update to Vista 6003. Windows Update is busted in this machine since the first week of July 2019 (still at build .6002 then), when M$ reconfigured things; in any case, only WD (delta) definition updates were coming via WU until that time (I don't have M$ Office 2010); and, as expected, even after installing both KB4474419-v4 and KB4517134 (latest SSU for WS2008SP2), I still have to manually update WD... Regards

No surprise. The reason occurred to me a month ago. No surprise either. I am not aware of any advantage in installing KB4474419 on Vista. The update may be necessary for Server 2008 users who want to use Windows Update until January, but Windows Update clearly knows the difference between Server 2008 and Vista. Edit: VistaLover has recently found that KB4474419 v4 makes it possible to install Windows Defender definitions.

gosh damn it Microsoft. it seems that KB4517134 fails to install if the KB4493730 update is not installed first as I had tested this myself this past weekend (and KB4474419 is also not installed). so that MS article 4517134 is wrong but on the other hand the MS Update Catalog site about the KB4517134 update is correct that it does not replace KB4493730 [friggin inconsistent info by MS on patch supersedence] I also found that installing the KB4474419 update alone (without installing any other updates from April 2019 & later) changes the build number from 6002 to 6003 and prevents Windows Update from looking for any Vista updates

No warez is contained within the distributed ISOs. And there may be some value in providing such packages to newcomers to win2k, but there are some issues: -did you obtain permission from @blackwingcat or the creator of USP 5.1 to redistribute their files? -SP4 UR1 and USP 5.1 are roughly equivalent; each one has its own issues and only one needs to be installed. -the win2k extended kernel has no relation to the 9x kernelex and is not open-source. -the high encryption pack was rolled into the OS in SP2. -there is no indication that extended kernel development has stopped -all extended kernel releases are cumulative: no previous versions need to be installed before the current version

hello make little update... new hotkeys - Win + Numpad 1/2/3 (when Numlock is ON), will force almost any window to maximize for all desktop HEIGHT with setting 4:3 aspect ratio for CLIENT AREA of window. 1 - aling LEFT, 2 - CENTER, 3 - RIGHT. i found this usefull for VM's/Hardware Emulator's windows. now it look as if u have real 4:3 screen inside ur modern 49" ultrawide LCD... EVEN IN TEXT MODE! also here added very limited tray icon way as workaround for PCem and clones, which dont allow hotkeys work as normal... before: after: workkaround: keyx-19102701.zip

Didn't last, couldn't resist the nostalgia and thrill of getting such an old OS online. Running Windows 98 SE, official updates, no kernel extensions. Tiny Personal Firewall v2.0.14 and Dillo v3.0. Tweaked ethernet speed with TCPOptimizer v308. No JavaScript, fast and reasonably secure. Dillo was able to log in to this site to post this message. Last working versions Firefox v2.0.0.20 and SeaMonkey v1.1.19 now have even more issues with outdated certs and difficulties establishing secure connections, making them almost non-functional. Links v2.1 works pretty well, for a text browser pretty user friendly. To me Windows 98 would still be a viable OS today if it wasn't for the lack of a secure, up-to-date, full featured web browser. It has a rich history with lots of good old software, such a shame. Having fun hacking and tuning the system. Playing with some hardware and configurations resulted in a persistent blue screen 'vxd' boot error. No problem with DOS fallback. Running SCANREG /RESTORE fixed the issue without much drama or wasted time. Lots of respect for DOS based systems.

I can confirm the issues with iTunes Store when attempting to sign in; I get the same errors described in this post. However I can still view the contents of the Store, but that's pretty much useless since I can't purchase/download anything. I have updated the list to reflect this new information: As always, thanks so much to everyone for the additions to the list while I've been away, and sorry for taking so long to finally get around to updating it. With that said, here's the Summary of Changes this time: SUMMARY OF CHANGES TO THE LIST FOR OCTOBER 24, 2019: Added Viber 6.8.2.878 as last version for Vista to "Instant Messaging" section. Updated Autodesk 3dsmax 2012, Autodesk Maya 2012, & Autodesk Mudbox 2012 to their 2016 versions as last unofficially supported versions for Vista in "2D/3D Modeling software" section. Updated Blender to UNS status. Added VMware Tools 10.3.10 as last version for Vista to "Virtualization software" section. Added calibre 3.48 as last version for Vista to "File Management" section. Updated information about iTunes Store: While you still may access the store, signing in no longer works. Added OpenGL Extensions Viewer to "Hardware Identification & Temperature Management" section. Updated information about GTA V in "Games" -> "Active Development" section: Now requires a workaround for new versions as of Sept. 2019.

I for one am not a fan of the Edge browser, nor the telemetry that comes with it. It's hard keeping a Windows 7 install telemetry-free as it is, so why would I invite it to my front door?