Leaderboard

Sorry for the inactivity all- finally got around to updating the topic! Now to post the latest Summary of Changes... SUMMARY OF CHANGES TO THE LIST FOR JUNE 11, 2019: Updated Vivaldi 1.0 entry to 1.0.435.46. Added Vivaldi 1.1.443.3 Developer to "Web Browsers" -> "Chromium-based" section. Added Adguard to "AntiVirus/Security software" section. Updated information about Telegram Desktop: the software will stop supporting Windows XP/Vista on Sept. 1, 2019. Fixed broken download link for Adobe Reader X v10.1.16. Added FineReader 14 to "PDF Viewers/editors" section. Updated WPS Office 2016 entry to WPS Office 2019. Updated link for VLC Media Player 3.0.7 to point to the final version instead of the beta version. Added ArtWeaver Free and Pro 6.x to "Video/Photo Editing software" section. Updated information about Krita - no longer ONG; added 4.1.7 as the last version to work with Windows Vista (newer versions do not work due to missing Win7+ DLL functions). Updated information about Sony Sound Forge - later versions up to 13.x can be ran on Vista by using the Portable version of the software (thanks to @artomberus for finding this). Fixed broken download link for Microsoft Virtual PC 2007. Added new section - "Language Translation software" Added Promt 18 to "Language Translation software" section. Added Nero 2019 Platinum (unofficial repacked version) to "Optical Disc Media Management software" Added SuperTuxKart to "Games" -> "Active Development" section. Added Adobe AIR 29.0.0.112 to "Software/game development" section. Fixed broken download links for Java 9.x. Fixed broken download link for Notepad3 4.18.512.992. Added OpenVPN 2.4.6-I602 to "VPN Clients" section.

I am opposed to the idea that RT should have to 'worry' about some 'internalized' ADD ON working with his Browsers. It seems like that ADD ONS (LEGACY) can 'stand on their own' -- so LET them do that. (Evil Humor) And, @VistaLover enjoys solving SOME riddles related to 'Ghosts in the Old Machines' https://o.rths.cf/boc-uxp/ RT has some ADD ONS (*.xpi files) listed for download at his above URL for BNAV Browser. https://legacycollector.org/firefox-addons/ This above URL has Firefox LEGACY ADD ONS too. Just a straight forward download, no install involved. https://legacycollector.org/firefox-addons/722/index.html NoScript Security Suite

Where's @Bersaglio? I assume we can just change "192" to "207" in the links below. I'm about to give it a try anyway. Edit: Apparently works fine. (Avast did scan "plugin-container.exe" for me, but didn't find any malware!)

"DST changes in Windows for Morocco and the Palestinian Authority" How did they know I was waiting for this?

Time Zone Update released DST changes in Windows for Morocco and the Palestinian Authority KB4501226! Download via Update Catalog http://www.catalog.update.microsoft.com/Search.aspx?q=xp embedded KB4501226 http://download.windowsupdate.com/d/msdownload/update/software/uprl/2019/06/windowsxp-kb4501226-x86-embedded-enu_708fe12ecfbbb070821a87fd538af3b6b6fd3084.exe

Yes but what i meant was @looking4awayout had said to try the SSE version. All I was doing was clearing that up as IIRC that CPU doesnt support SSE Therefore needing to use the noSSE one

I agree. If this were to be done at all, it should be done by @i430VX's installer. I could see the installer offering to download and install a few popular add-ons after extracting the browser. In theory @siria's method below would be ideal, but I'm not sure it would work in practice: That would install add-ons in a new profile anytime one is created. It may work in KM - I haven't looked - but in NM and Serpent, the defaults\profile\ folder seems to live in browser\omni.ja, and I'm not sure it's feasible to modify that file. It seems to be a nonstandard .zip format. So that leaves you with storing the downloaded add-ons in the browser\extensions\ subfolder, which means they could be disabled but not removed easily (except of course by reinstalling). The installer would need to give the user a message to that effect.

One that only catches viruses... I doubt any exist anymore. However, traditional AVs are, nowadays, signature-based antimalwares, with some heuristics (not always very good) on top of it. Malwarebytes, OTOH, says it uses their own methods (not clearly disclosed) which appear to be very good heuristics and just a little pinch of signature-based as a seasoning. It just works, though.

Only updates will stop. At the current point, extremely old versions of telegram are still able to connect and work. So I'd say we have a while

So the UOC settings patch was pretty successful on a Celeron 400 Mhz from 1999. It speeds up New Moon under Windows XP. Don't see a difference between graphic cards like the "graphic decelerator" S3 Virge DX (1998) and the Radeon 7200 (2000). Using a good swap hard drive was more important on the performance. The processor tries its best, but fights with some 100% CPU loads. A Pentium 3 is probably a good recommendation.

Every Addon in a browser has to be removable. User cases are different like in terms of hardware, paranoia, skill... even NoScript can be too complicated for beginners. The ClassicAddonArchive is a very important link to improve the elderly browsers. It so unfortuneatly, that a lot of developers don't like their old software wandering around, causing troubles in the hands of greenhorns. So they try to remove every trace of legacy software. Edit: Some low-specification tests: New Moon (which is a cool name by the way) can run semi-fast on a Celeron 400Mhz with Windows XP. You learn to love the extra power of a Pentium 3, but New Moon is useable.

Wasn't aware that was possible. Presumably it would work in other browsers besides KM, and one wouldn't even need to modify the source repo: put the desired .xpi files in one of those subfolders after building, then just zip the whole thing up. And CAA would be a perfect candidate - if it didn't double the size of the final .7z! So I guess we won't do that one - too bad JustOff didn't put the CAA database in the cloud. But after looking over my own rather long list of add-ons, I don't see any (except CAA) that everyone should have - especially when you consider that it's common for different users to want different versions of an add-on. Should we include uBO? If so, New Moon presumably gets the latest legacy version, but which version does Serpent 52 get: the legacy version, 1.17.4, or a newer version patched to run on it? So maybe we're overthinking this. Instead of including any add-ons in the .7z files, remember that pref that started this whole discussion - startup.homepage_override_url - that opens whenever the browser version changes? Point that to a page of commonly requested addons, then the users will see it after every update and can decide for themselves which addons (if any) they want.

Thinking about it, just in theory, another way of including addons out-of-box is probably in the template folder for brandnew profiles: installdir/browser/defaults/profile/extensions/... Then it should show a Remove/Uninstall button on aboutaddons, but haven't tested.

Can only speak from very limited experience with older browsers, but K-Meleon has an addon included out-of-7z-box: NewsFox, an rss-reader. Technically it looks quite easy to me, just place an xpi (with it's final name) in folder /browser/extensions. The killer catch is, users will get NO Remove-button on aboutaddons, as if that folder is considered part of the engine. Reminds me of android phones, where owners are only allowed to remove their self-installed apps too, others can only be disabled. Of course such engine addons can still be removed too, provided you have full access to the app's install folder and can manually delete the xpi - unless that has changed in more modern browsers. Not sure. At any rate including addons this way is rather un-friendly on users who do not want a specific heavy or intrusive addon. So I would not want to see something as NoScript hardcoded in a browser, it's not everyone's cup of tea. But would like some other, basic ones included, like ExExceptions. And in the special case of KM find it important that the old, traditional NewsFox addon comes already included. It's a very tiny and harmless addon which adds basic functions, but most of all it's a demonstration of a working xpi addon in a browser that's so confusing to newbie users, regarding the extensions chaos (macros, complex multi-file KM-extensions, native FF addons etc.) For example out of box KM still doesn't even have any menu entry to open about:addons! And other important about-pages, users must already know those pages exist and can be opened by manually typing the about-addy in the urlbar, which I find completely incredible today. Or users who know about it, can install my tiny KM-macro aboutabout, which just adds a bunch of about-links in a menu. Still looking very rough, because I haven't investigated yet the matching menu positions and names in FF&Co, which is the final goal of course. That KM-GUI prob has historical reasons of course, xpi-addons were completely impossible prior to first KM74 versions, and at first very tricky to install (editing install.rdf and fiddling with prefs). Then slowly getting better with every new KM7x-version. And since KM76RC2 most Firefox-addons install quite fine, but still lack any xpi-created menus and toolbar buttons, rendering most of them useless again. The only chance is if the xpi comes with an own options page, as long as that's enough to handle it. Or if the user can get an additional KM-macro to create menu or buttons, but their interaction with addons is still quite limited too. How to call a native xpi-function by macro? All they can do so far is toggle some pref, or open a xul-url (Like ExExceptions). I've realized only lately they may be able to do a bit more too. Anway, it's a major pity that due to chronical lack of devs K-Meleon's GUI is meanwhile lagging some ten years behind the engine. But what I find very important in general, for all browsers which can only run 'legacy' XUL-addons, is to give clueless newbie users a hint about ClassicAddonsArchive! This addon I'd absolutely include out-of-box, except that it's impossible because this one is far too heavy, over 40MB. No go. Still, to help unexperienced users, I'm currently working at a K-Meleon macro that modifies the original aboutaddons page and injects a button opening CAA (and other buttons to KM macro ressources, and a little buttonmenu). Realized only lately that's even possible, just by macro with JS and for non-devs like me, still quite excited. When that macro is installed, it will inject those buttons at every page load, and clicking it will open "caa:list" or "caa:about", and if not yet installed the button will offer to download the addon from github. Of course, for other browsers too, with some dev-power and omni.ja-access, such modifications could be included in the source-code of aboutaddons page directly. If anyone is curious about how that might look, here's a little preview screenshot of my almost-finished macro: http://s000.tinyupload.com/?file_id=20610227332941181284

Most likely, gfx.font_rendering.cleartype.always_use_for_content was always set to false. That is the default value when FF is installed. Whatever Panda did to Firefox's font rendering, evidently setting that pref to true bypassed or overrode it somehow. So thankfully, you're back to normal now, but we may never know just exactly what happened.

Add-ons are installed in your profile folder, not in the browser's program folder (that's how they remain installed whenever you update), so they can't be included in the same .7z file as the browser itself. That said, old versions of NoScript are readily available for download from the Classic Add-Ons Archive (which is itself an add-on). Go to https://github.com/JustOff/ca-archive/releases and click on the latest .xpi file.

Might there be a possibility to include a legacy version of the NoScript addon by default in New Moon? It definetly makes the web much more useable, not only on the old Windows XP machines. The version 2 seems to be good, I use 2.6.9.32 (didn't find any better). The current NoScript version kills the Celeron from 1999.

I think I found the problem!! The first thing I did when the problem started was to go to about:config and look for anything related to "smoothing". Whatever was there did not fix anything, so I moved on to other areas. Today, I had the impulse to go back and scour about:config line by line to see if anything would look to be related. I searched on "font" and see a bunch of lines related to gfx.* , I played with a bunch of them, toggled, changed values, etc., and when I found the one called gfx.font_rendering.cleartype.always_use_for_content; it was set to default(false). I set it to true and Boom!! Now... I think I would have remembered if I had done this myself, even accidentally. There is almost zero chance it was changed by me. How weird would it be to assume that Panda changed this?

Holly molly! Microsoft you are finally loving XP Again! XP Forever!

Why don't you just redeploy your backup from just before installing Panda and try again from scratch? Read this (esp. the 1st Q of the included FAQ): https://blog.malwarebytes.com/malwarebytes-news/2016/12/announcing-malwarebytes-3-0-a-next-generation-antivirus-replacement/

2019-06 Actualización de POSReady 2009 para x86 sistemas basados en (KB4501226) Última modificación: 09/06/2019 Tamaño: 529 KB http://support.microsoft.com/help/4501226

This appears to be from some German speaking country.

We are all well aware of the mess WannaCry caused, yet it was mostly due to unpatched Win7 machines, not the ones running Windows XP, so here we are, years apart, with computers running Windows XP. We can see the programme opened in which the doctor was filling the forms and the obvious bar at the very bottom showing that it's Windows XP (no POSReady or whatever, plain XP). I wonder whether these machines are patched or not... (If you are wondering what that medicine is, it's something to encourage you to p*** and it's not for me. I was "lucky", though, 'cause another doctor asked the one I was talking to a consultation and as soon as she walked out of the room I took the chance to take a picture of the screen. When she came back, she suspected nothing).

Great news! @WinClient5270 will not have to edit the listings for AVG and Avast to add, "Works on build 6002 but causes BSODs on build 6003." (However there could be other build 6003 incompatibilities lurking out there.)

I had been meaning to respond to this topic for a week, but I'd been so preoccupied with work and other commitments that I hadn't had the chance to ... until now! I wanted to leave a huge thank-you, @XP-x64-Lover, for all you've done in finding these drivers and allowing those of us sticking with XP64 a chance to upgrade to hardware a bit more recent. Between your drivers and the trick explained by Matt's Repository for getting XP/XP64 drivers for the nVidia 9XX series, on Memorial Day Weekend I was able to finally give my desktop the badly needed overhaul I'd been wanting to do since my first posts at MSFN back in 2014! That's 64 GB of DDR4 RAM, SABERTOOTH X99 motherboard, Intel i7-6950X CPU, and a GeForce GTX TITAN X. I wasn't able to get the SSD thing sorted out, so I wound up using the IDE method, which has worked amazingly well with my existing install. Since @bluebolt figured out a way to get an install of XP64 working on a NVMe 2.0 drive, I may skip the SSD and attempt a fresh install off of that instead, since the X99 has a bay for NVMe drives. For now, though, I'm just excited to have not only put my hardware troubles behind me for now, but that I've now got the RAM upgrade I've wanted for years!