Leaderboard

I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...

Well, you're much welcome to vent up. So am I to rant, right? Yeah, it goes like this: 1.) All the issues you mentioned have solutions described in detail in this very forum. 2.) Athough it's easy to filx the Word 2010 issue, one can remain using Word 2000 (or even Word 97) for most if not all tasks commonly performed with it. Same goes for XL and Powerpoint. 3.) Al that is required is to arm oneself with patience and read the threads where the solutions are described. XP went EoS, then POSReady 2009 went EoS. MS did it because it was in their power to do so and they've decided it was in their interest to do so. Regardless of what any of us thinks about it. So it's up to us, the die-hard users, to support ourselves 'n one another... it's less confortable than leaving all responsibility fall on MS. Then again, for one who loves XP or just isn't confortable (or able) to cave in, it sure is worth it. One may whine. Then again, one may stand up and fight. Long live XP!

Today marks the 20th anniversary of the release of Windows 98 SE, which was on May 5th, 1999! The OS that changed my life forever! Share your birthday wishes and OS experiences here! Many great things awaits...

First try a SSUAO to spoof FF 52: something like general.useragent.override.earthcam.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9 It could be the same problem as Instagram. NM 28 and Serpent 52 spoof FF 60.9, but don't support some of FF 60.9's Javascript, so a few sites see the "60.9," feed NM/Serpent incompatible Javascript, and break. Moebius works because it spoofs FF 55, which predates Quantum. If that doesn't work, try the previous version of NM 28; it's not uncommon for one of the weekly updates to break some sites. If that's the problem, it'll probably be fixed by next week.

You can force "multiprocess mode" (aka "e10s") in Firefox 52 or @roytam1's Serpent 52 and 55, by creating the Boolean preference browser.tabs.remote.force-enable and setting it to true. This splits Firefox or Serpent into two processes. To allow more than two, set dom.ipc.processCount to a value greater than one (i.e., setting it to 2 allows 3 processes, etc.) Don't try this in New Moon, though; it will crash! It doesn't work in BNavigator or IceApe either; setting the above preference makes it appear to work in about:support, but Windows Task Manager nevertheless shows only one task no matter how many tabs are open. Edit: Summarizing what was discovered below, this preference is required to enable e10s (multiprocess mode) in FF 52 on Windows XP. But with later Windows versions, or some other FF forks on XP (confirmed with Serpent 55), you can instead use the preferences @VistaLover recommends in the next post: toggle browser.tabs.remote.autostart from false to true, and if necessary (due to add-ons flagged as incompatible with e10s), toggle extensions.e10sBlocksEnabling from true to false. In Chrome, each tab is a separate process; but in FF the maximum number of processes is limited by that preference. If you open more tabs than that value, tabs will begin to share processes vs. creating new processes.

Thank you, this was exactly what I was looking for! I'll test what you described in the thread you linked as soon as I have enough extra time for experimentation. Fair enough, making a fully updated installation medium by slipstreaming all the necessary updates would be the ideal way to do things, but I have no experience on that sort of project, and I'm not sure if there's enough time anymore for all the testing and trial&error that's likely to go in creating the slipstreamed disc and verifying that the installations made with it work flawlessly. Nor do I know if I can trust the various unofficial update packs that are floating around the 'net, at least if there's no reliable way to verify that they only contain executable code from official sources. Moreover, since activation for Windows XP (even the phone activation) is not likely to be working forever, there's no guarantee that new installations can be made far into the future, thus the usefulness of a fully updated installation medium may be more limited than what might first seem. That's why I'm actually planning to create an image of a system partition with fully updated WinXP on it, along with all the XP-specific programs I want to preserve for future. So if my hard drive breaks for example, I don't need to re-install anything as I can recover an already activated & fully updated system from backup. I've also purchased a couple of identical motherboards to serve as replacement parts for the same purpose (i.e. to avoid the need to re-install + activate), and I'm planning to get a few identical XP-compatible graphics cards as well. Anyway, thanks to everyone for your contributions. I'll report the results when I've tried the solutions suggested in this thread.

Works in IE 11 too. I haven't tested a Quantum FF version but I bet it works there too. MDN may have the explanation: That would explain why it fails specifically on our UXP-based browsers. I agree someone needs to confirm this with official PM/Basilisk on Win 7+ and report it to MCP. (And this should go without saying, but do not mention New Moon, Serpent, XP, or even Vista, as MCP will simply blame @roytam1's "inferior" code, then Matt will come here and hassle him about "misrepresenting" his builds. We don't want to go through that yet again.) This particular issue is minor, but it's the sort of thing that will continue to bedevil the UXP platform as Javascript continues to evolve.

I would love to think that MS are addressing the Office 2010 compatibility problem, but I'm not holding my breath!

Do not panic! For everything there are solutions: Office 2010: Antivirus: In Firefox, due to a crash in all versions, all add-ons stopped working, this problem has affected all operating systems. Fix: TeamViewer 14 version works in XP. Skype 7 version no longer works in any OS.

@Mathwiz Yes, an SSUAO was all that was needed. In about:config there was about 40 existing overrides with a variety of spoofs. I copied and pasted an existing 52.9 spoof into a new string. It was very easy, due to the great advice given here. Thanks again

@BTTB, Chromium-family browsers use multiple processes, whereas older Firefox-family browsers use a single process and typically in x86 Windows, a single process can only use up to 2 GB of memory (unless /3GB is set to assign 3 GB to programs and 1 GB for the kernel). Firefox 54 is the first multithreaded version, and 53 was successfully run on Windows 2000 extended kernel by @blackwingcat. I wonder if later 5x versions are possible with the kernel wrappers available for XP?

To be very honest, I've been using it for the last 1 week or so and it seems like it is in fact a lot faster and I am very impressed considering the fact that it is actually a chinese browser.

I ran into a situation while travelling, that may have been exascerbated by my OS update preferences. I was unable to use the hotel guest wireless networks. Although I was away for two weeks, each week I had different computers with me but they both generally had the same problem. They could connect to the guest network, but wouldn't allow me to go anywhere via a browser. Either the guest portal wouldn't open (because it uses XSS and I have XSS blocked) or I received certificate errors. So one casualty of trying to keep a computer under your control or secure, is that it can't be easily used in the real world.

A word of caution about HTML5test.com: Many of the points awarded by that site are for features that have privacy and/or security concerns: e.g., 15 points if your browser supports geolocation; 10 points for "service workers," a point for the "ping" attribute, etc. A very high score may not be the best news about your browser.

I really like the new edge based on chromium. People should try it out.