Leaderboard

It was @UCyborg's idea, actually. Here's the initial comment.

@chermany4ever said he doesn't have enough RAM for multiprocess mode, so he should definitely make the settings changes to disable it, whichever FF-based browser he ultimately chooses. But my experience with using multiprocess mode in Serpent 55 has been generally positive. Besides higher RAM usage, it does have downsides I mentioned earlier, but instability hasn't been one of them. I haven't noticed an increase in crashes, and if a tab does crash, it rarely takes the whole browser down. Instead, you just refresh the crashed tab. I haven't tried MyPal 68, but I would've expected multiprocess mode to be even more stable by the time Mozilla got to version 68. Perhaps multiprocess mode has grown less stable on XP since Mozilla obviously doesn't test on XP, but I'd expect it to be OK on Win 7 if you have enough RAM. Make sure you get Waterfox Classic. AIUI, at some point "Waterfox" got sold to some corporation that wasn't committed to the original spirit of the project, so fans of the "original" Waterfox resurrected the original project as Waterfox Classic. Where it "comes from" is kind of complicated. AIUI, originally it came here from China - via Russia - but our own @NotHereToPlayGames made extensive improvements, removing telemetry, creating an "unGoogled" version, rebasing to reduce RAM use on XP, etc. It has a pretty good reputation on MSFN.

Thank you. I'm going to give Waterfox a try. XP wise I'm very happy with Roytam's Serpent Basilisk. It works really really well. I'm actually using an addon called New Tab Suspender in the FF installed in W7 and it does exactly that. Thanks again for all the info. Much appreciated. Couldn't agree with you more. Like I said in previous posts I use XP SP2 so I'm testing MyPal 68 in W7 but it's filled with bugs. I just can't get it to work. Thanks for your comments. In my experience official releases are crappy and full of cheese and that's why I always go for any unofficial modification. I have been using Windows UE 6 (my XP machine) for many years now and everything has been satisfying. Even now with this Windows Minios 7 the performance is amazing. As a south american myself, you don't know how much I wish these unofficial versions were French or Italian... it sounds so much cooler! I'm a legacy FF user, never liked chrome or any google stuff... but I'm gonna try this chrome you recommend and I hope it doesn't come from some caribbean island.

I recently had some free time on my hands, and started working on putting Real Mode DOS support back into Windows Millennium. Not only the common patches available around the internet, but all of it - Restart to MS-DOS mode enabled, AUTOEXEC and CONFIG processed on boot, advanced PIF options in DOS application properties panels, and applications can be instructed to reboot into DOS and back into Windows when they’ve completed. It accomplishes this by redirecting the rewrites of AUTOEXEC and CONFIG in REGENV32.EXE, using a specialised IO.SYS and COMMAND.COM from the Windows Millennium CD NETTOOLS (CBS.DTA and LTOOLS.DTA), and using the MS-DOS application layer (WINOA386.MOD and PIFMGR.DLL) and command line utilities (SYS.COM) from Millennium Developer Release 1. The current testing version also includes WIN.COM from Windows 98 Second Edition as this allows the user to type "exit" from DOS and restart back into Windows, however the aim would be to eventually re-integrate this functionality back into Windows Me's WIN.COM instead. "Restart in MS-DOS mode" is restored by removing the "NoRealMode" value from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WinOldApp in the Windows registry. So, what currently works? "Restart in MS-DOS mode" from the shutdown dialog restarts to a command prompt - with a caveat. (See Issue 1 below.) Typing EXIT or WIN from MS-DOS mode restarts the computer back into Windows. DOS applications can be configured to restart in MS-DOS mode from the Properties window, and custom AUTOEXEC.BAT and CONFIG.SYS entries can be specified per application. The IO.SYS included with NETTOOLS automatically loads IFSHLP.SYS, and automatically calls WIN on startup, so these lines are not required in AUTOEXEC and CONFIG. The Windows Me boot logo is preserved. Windows XMS driver, integrated into IO.SYS, loads and mostly replaces the functionality of HIMEM.SYS. EMM386 loads and works, both in DOS mode and within Windows, although it currently requires the IO8EMMOK driver (https://github.com/pufengdu/IO8EMMOK) to be loaded first in CONFIG.SYS to make the built-in XMS driver behave more like a standard HIMEM. AUTOEXEC.BAT and CONFIG.SYS are processed and loaded at startup. Holding CTRL on startup brings up the Windows Millennium Startup menu, and it now includes "Command Prompt Only" in addition to the normal startup options. Creating a MS-DOS boot disk by using the SYS command line utility has been re-enabled. When editing PIF properties, "DEVICE=C:\Windows\Himem.Sys" is no longer autofilled in CONFIG.SYS as this is not required on MS-DOS 8 / Windows Millennium. The modifications can be installed via a Setup INF, without the need to disable System Restore or System File Protection. There are still some issues to work on however - Selecting "Use current MS-DOS configuration" in an application's MS-DOS mode properties / PIF and using it to restart into MS-DOS mode just shuts down the computer. Selecting "Specify a new MS-DOS configuration" and entering a custom AUTOEXEC and CONFIG works fine. This includes the "Exit to DOS" PIF used when selecting "Restart in MS-DOS mode" from the Start > Shut Down menu, which just shuts down the system if the Exit to DOS PIF doesn't have a custom AUTOEXEC and CONFIG specified. Because resuming from Hibernation is handled partly in IO.SYS, the alterations to this file mean that Hibernation still needs to be tested. Likewise, System Restore needs to be tested to ensure it can still create and restore system snapshots correctly. Update KB311561 contains an updated IO.SYS with some bug fixes. The IO.SYS used to currently boot into DOS mode does not contain these fixes. The first issue above has been the sticking point for this project. When "Use current MS-DOS configuration" is selected, or "Restart in MS-DOS mode" is selected from the shutdown dialog without an "Exit to DOS.pif" specifying a new MS-DOS configuration present in the WINDOWS folder, the computer just shuts down instead of restarting into DOS mode. After experimenting side-by-side with Windows 98, I think I know what the problem is. When restarting into MS-DOS mode in Windows 98 using "Use current MS-DOS configuration", Windows shuts down and returns the computer to an MS-DOS command prompt without restarting the computer, using the already-loaded AUTOEXEC.BAT and CONFIG.SYS. However when "Specify a new MS-DOS configuration" is selected, because the AUTOEXEC and CONFIG files need to be replaced temporarily and DOS loaded from the ground up, Windows does restart the computer. Therein lies the problem - the functionality that allowed Windows 98 to end its session, unload and drop back to a DOS prompt without restarting the computer isn't present in Windows Millennium, so instead, the computer just shuts down when "Use current MS-DOS configuration" is selected. When a custom MS-DOS configuration is specified, it forces a warm restart instead, bypassing whatever function of the OS is broken, and it works - but because we had to specify a custom configuration in the PIF, the existing AUTOEXEC.BAT and CONFIG.SYS in the root of the C drive is ignored. Dencorso over in this thread may have an explanation as to why this occurs - So the problem is likely deep within the Windows Kernel itself. This is about as far as I can go, with my current knowledge, at least without some assistance to either point me in the right direction or to come up with a suitable workaround for this issue. As it stands, it means that *any* DOS application needs to have its own AUTOEXEC and CONFIG entries specified in the properties dialog - it can't inherit the existing entries from the AUTOEXEC.BAT and CONFIG.SYS already in the root of the C drive. Now this isn't inherently a bad thing - if an application does require DOS mode, then set it up in properties, include EMM386, MSCDEX, MOUSE, whatever it needs, and double click to restart the computer and run it. That part works fine. Likewise if you want to run something before Windows Me boots in AUTOEXEC and CONFIG, that's fine too. Or if you want to reboot to a command prompt by holding down CTRL and selecting Command Prompt Only, that also works. But you can't double-click a DOS application icon in Windows and have it use the existing AUTOEXEC and CONFIG. And at the moment, to make "Restart in MS-DOS mode" work, I'm bundling "Exit to DOS.pif" with the package and anyone that wants to have a custom AUTOEXEC or CONFIG in that MS-DOS mode session just needs to specify their contents in that PIF file instead. It works, but it's a "95% of the way there" solution when ideally, we want that last 5 percent.

To be fair, MyPal 68 is still in beta, and its author lives in a country at war, so I'm not surprised that 68 still isn't very stable. It's stunning that it works on XP at all, given that Rust was supposedly fundamentally incompatible with XP. My comments were merely to express surprise that it's more stable in single-process mode, and to wonder whether that applies to Windows 7 or only to XP.

In practice, I myself ran an MSI Twin Frozer GTS250 1GB on a board with the 1.0 PCI-e version. The board was Fujitsu Siemens D2317-A1, made in 2005-2006 or so. It had the 1.0 PCI-e version only.

Then you definitely won't get away with a modern low-power PSU, you need to look for that appropriate one I told you. But from what I know, you could borrow that card and try, becuase GTS250 has a decent backwards compatibility, so (in theory) it should limit itself to the 1.0 PCI-e version,

AFAIK, according to @feodor2's GitHub page, you need at least Windows XP SP3 completely updated until 2014, and even better would be all POSReady updates until 2019. Mypal 68 is not intended to use under Windows 7, but you can try to run it in single-process mode which is the most stable mode.

Good suggestion. Lots of CSP errors helped me figure it out. Github now requires service workers merely to load its CSS! I use CSP to block service workers except when needed for a site to function. Had to add github.com and githubassets.com to the list of exceptions. In some ways I think M$ is worse than Google. Google just provides the rope; M$ actively uses it to try to hang you! Service workers just to load CSS. Sheesh. Could they possibly come up with a more complicated way to perform a simpler task? They must pay their Web developers by the number of lines of code they write!

I use Mypal 68 in single-process mode from the first beta 68.12.0b in April of 2022 until the current third pre-release 68.13.0b. I never had a browser crash nor a BSOD. This browser is totally stable in this mode although it is still in development. @feodor2 is doing a great job. Providing a JavaSript engine version 78 in the form of a Firefox derivative for Windows XP is just great and incredible. About the stability of Mypal 68 in multiprocess mode, I can't say anything. I did and do not use it in this mode. According to some reports in the issues on GitHub, there seemed to have been stability problems in multiprocess mode.

Mypal 68 is a buggy amateur project so you can't compare it to the original Firefox 68 Mypal 68 is far more unstable than the old Firefox releases prior to 52 version

I utilize Windows Server 2019 at work, it runs our Point of Sale and the SQL Database that goes with it. I actually had to add functions too it for it to work properly with my setup. Domain>AD>Multiple Users via PCs and thin-clients. 1 SSD for the OS. 1 SSD for the POS data and SQL. Backups are- 1 Internal SSD >8TB HDD>External SSD>Offsite NAS in RAID at my home. I would never recommend a Server product for a home/gaming PC, it's not designed for it.

Your objection is justified. I thought I had already written that, but it was just a slightly longer post. I already corrected my post above. Thanks for the hint! No one has to buy a licence for whatever. In this thread, I list all possible editions of antimalware and other security programmes. Nothing more and nothing less. And guessing wishes is not my job. Here is a comparison of free and pro features: https://www.superantispyware.com/free-edition.html The Free Edition is of course considerably limited. Above all, no real time protection. But what is the saying: PS: Personally, I couldn't care less which version of which programme a user prefers. I provide information, the mature reader can decide for himself what to do with it.

From now on, the most recent version is SUPERAntiSpyware Professional X Edition 10.0.1254. I checked the System Tools - System Investigator Options and didn't observe any problems. Here is a screenshot: No blocked Explorer, no issues. I guess there must be another cause for your problems. Greetings, AstroSkipper

Update notification! Contrary to the system requirements published by RealDefense in their FAQ (actually Windows 7 and higher), SUPERAntiSpyware Professional has been updated to the version 10.0.1254 via automatic update and is still compatible to Windows XP. It works as it should without any problems. Here is a screenshot showing the main interface of SUPERAntiSpyware Professional X 10.0.1254 in my Windows XP partition: Cheers, AstroSkipper

If you mean the ordinary chrome, no, and I don't see much interest in it. But win32 made his own version of 115, it works on Vista, and it should work on 8.1 too.

You won't have the memory leaks once you strip it down. Not for the faint of heart, it is a tedious process and you won't get it right the first time. But none of my Linux versions have ever worked right the first time either - so it boils down to whether your heart is in it to get it working or not, if your heart isn't in it, you'll give up way too easily. Proxomitron is another one, a great deal of power but a steep learning curve where far too many give up way too easily.

I failed to mention, you would need some pretty decent hardware, otherwise it will be slooooooow. Windows 7 era PC might be too old for that task.

I'm not sure about the lumping those tools with extended kernels. I used nLite years ago on XP to add drivers and apply TCP half-open connection patch. I don't bother with that anymore, modern Windows do basic AHCI out-of-the-box and having the rest of the drivers right after installation vs. installed a bit later, well, I don't find the latter problematic. Not sure about stripping either. I don't really know how to approach it, stuff breaks easily and my interest list is short, almost non-existent as it is, so messing with Windows isn't on it, troubleshooting problems that occurred because something is missing even less. I turned off some scheduled tasks and put some services from auto-start to manual, although the latter seems pointless as something else turns them on soon anyway. I'd like to upgrade to the Windows version that doesn't memory leak over pro-longed period, I haven't found it so far, though I haven't tried Win11 yet. Seems more of a hassle than it's worth at this point, even if it miraculously solves memory leaks, which I still think is doubtful. Stuff never works right anyway.

Topaz AI (only older versions) will work on 7, or even Vista, surely won't run on XP and 2000. The only problem, it's a paid software. https://www.topazlabs.com/ https://www.google.co.uk/search?q=Topaz+AI I don't remember which old version exactly, need to do a research. Somewhere from 2019.

Well. Setting browser.tabs.remote.autostart to false is the "traditional" (FF vers. 54-67) means of disabling multiprocess mode. In FF 68+ this no longer works (at least not by itself), hence the article I linked to. I can think of a couple of reasons why it may still work in MyPal 68: @feodor2 intentionally re-enabled the setting in MyPal The other settings you listed in your post allow the "disabled" setting to work anyhow. If it's #2, the combination of four settings you listed may work in Firefox itself as well as MyPal 68. Should be worth a try, at least! Of course, if you're lucky enough to have the RAM (physical, or virtual via, say, a fast SSD) you should probably leave e10s enabled for better security and crash resistance. That advice doesn't necessarily apply to Serpent, though, where you have to forcibly enable e10s. (There's a pinned thread explaining how.) Many legacy extensions won't work correctly with e10s enabled, so you need to balance what you gain against what you lose.

In Mypal 68, the settings for enabling single-process mode are a bit different. Have a look here: Greetings, AstroSkipper

... and/or (as others here have suggested) just switch off multiprocess mode: https://techdows.com/2019/08/multi-process-e10s-can-still-be-disabled-in-firefox-68-or-later-versions-here-is-how.html Mozilla made it harder in FF (and consequently MyPal) 68 and above; you now have to set a Windows environment variable vs. just changing a pref in about:config, but it's still doable. N16s is quite likely correct that forcing single-process mode increases vulnerability to Spectre/Meltdown attacks (and that probably applies to Serpent as much as FF or MyPal); hence the increased difficulty shutting it off. But if the browser hogs too much virtual RAM, it'll start thrashing and end up having to be shut down and restarted, so if you have little physical RAM (regardless of OS) it may be worth the security trade-off. But remember, a major reason for the OP preferring FF-based browsers was to keep as many of his legacy extensions as possible, which I why I suggested Waterfox Classic. If one uses a lot of extensions, switching browser platforms becomes a major hassle.

I forgot to mention in regards to the previous issues with Far Cry series games. I never got Reshade to work to a point where a game would actually launch but now the point is moot. Ubisoft has moved to a new version of Ubisoft Connect that no longer generates any sort of error. The process just exits (cleanly it appears, as there is no crash log) after a few seconds. I can't do any more troubleshooting or testing with it because I just decided to uninstall all of those games.

No disagreement. Although users should be reminded that it was "Meltdown" and "Spectre" vulnerabilities that largely brought about the need for multi-process versus single-process more so than the increased number of multi-core CPUs. MSFN Members were quick to point out that Chrome and its forks can have site isolation disabled and reduce RAM 20% or so but that Chrome itself would prefer you use a different browser then use theirs with site isolation disabled. Has the same level of scrutiny been applied to disabling Mozilla's site isolation topology? Low-on-resource users must weigh the pros and cons - but they should also be aware of those pros and cons. If "Meltdown" and "Spectre" scared you into losing sleep when their tentacles were sprawling the internet, then you should think twice before disablling site isolation (which in the case of Firefox and forks, single-process = site isolation disabled). edit - I used to shout from the roof top that single-process was "superior". I can only speak from my own paradigm, but to me, RAM consumptions had me "blind-sided" and viewing browser performance through a tunnel-vision lens. It took me a LONG TIME to break myself from that perspective. EVERY COMPUTER is different, so this is not a "blanket statement", but what I started doing is looking at SPEED instead of RAM. If a computer running at 80% of RAM being used isn't slowing anything down, then why run the risk of "Meltdown" or "Spectre"? If the SPEED of everything is the same at 20% as it is at 80%, then why is the sky falling when we coast around at 80%? Again, that was just MY paradigm-break. We all know our own computers better than others, so everyone must "decide for themselves" what works for them and what doesn't.

I don't use that unnoficial W7 lite crap made in south America. I have heard many times the original chrome is a notorious memory hog but I'm unable replicate this behavior here. I can have 50 tabs open at a time with just about 3.5GB of RAM and for XP use I would highly recomment you the rebuild from @NotHereToPlayGames

All more recent browsers show these behaviour. If you have a lot of RAM, it should be not a problem at all although I don't like such consumption. My Windows XP Professional computer is very low on resources. Only 1.5 GB RAM. One of the reasons I appreciate @roytam1's browser so much. On my machine, they are running in single-process mode, consuming RAM as they actually should do. Additionally, I installed Mypal 68 from the very first and also configured it working in single-process mode. It works great, and its RAM usage is low.

For legacy extension support, you could try Waterfox Classic. (I've heard good things, but I haven't tried it myself.) For the memory consumption I'd suggest JustOff's "Lull the Tabs" extension, although I suspect it's a legacy extension that'll only run on Waterfox Classic.

Because I never read this thread until today. What I wonder is why you had to throw my name out there? It's okay if your world revolves around me, I get it. My world revolves around me also. (Technically speaking, EVERYBODY'S world revolves around THEMSELF - their eyes, their ears, their perceptions.) waka waka waka

"What Is Happening to Chrome's Built-In Google Translate Feature? In a community post on the Chrome Support page, Google announced its plan to disable Chrome's built-in translation service on version Chrome 95 or older. If you try to use Google Translate on an outdated version of the browser, you'll receive an error message stating that the page cannot be translated." https://www.makeuseof.com/older-chrome-losing-google-translate/

For every desired feature, there is a solution in the form of an extension. But my tabs will stay horizontally. I am a creature of habit.

You mean these ? https://www.google.co.uk/search?q=horizontal+tabs+on+firefox The instructions should be here. https://www.pcworld.com/article/823939/vertical-tabs-in-firefox-yes-its-really-possible.html

Yep, I thought we also need here software coming from Europe. So that no one gets the idea that I would only favour countries here that still use Windows XP more often, such as China. And in terms of your question, there is an old song in Germany called "Wunder gibt es immer wieder", translated "Miracles happen all the time".

Do we really need to see on MSFN this survivalist/conspirationist/apocalyptic crap? <- this is a rhetoric question, the answer is NO. msfntor, it is already tiring to see all the meaningless, non techinical crap you post on this (supposedly technical) board every single §@ç#ing day, often many times each day, but this is too much. Mind you, you are perfectly free to insist on this as much as you want, but at least you now know how at least one MSFN user is fed up with this senseless garbage. jaclaz