All Activity

The irony is, the original idea behind Pale Moon, waaay back before XP even, at least as I understood it, was that it was supposed to just be Firefox optimized for Windows, so it was supposed to be (and seemed to be, on my ancient Win 98 PC) faster than vanilla Firefox. No new or different features, just better performance. This was like PM 3.6 or so, but it sure seems like they went astray somewhere along the line. And enabling AVX or whatever in 64-bit builds isn't going to make up for it. I tried disabling multiprocess mode on St 55 on Win 7 and had a similar experience. Couldn't even type a post on MSFN at 10-20 seconds per letter, with one CPU core maxed out! So, even with a single core, you might have had better luck with e10s forced on. It's my opinion that the OS version makes little difference in performance, assuming the application (browser or whatever) will run on both OSes. The app might be faster if optimized for a newer version, but in that case it's unlikely to run on the older version at all. It's mostly the hardware, rather than the OS, that provides good performance.

Our 26100.1 ISO came from a trusted U.S. source. It is a digital license, but we don't like to cheat (too much anyway).

If you're using mas hwid you have a digital license, you really don't need the key at that point. Where did you get the iso? I've only seen a leaked one from a chinese site that people say not to use on production systems since there is no MD5 to compare to.

Back when we upgraded from Win 7 to 10, we installed Win 10 Pro and ran it for testing. Pro was loaded with games and I looked at switching us to a Linux distro. I found an ISO of LTSB 2015 and tried that. It was great. LTSC has no games, uninstallable Edge and either 5 (LTSC) or 10 (IOT LTSC) years of support and most importantly for us, feature updates when we want them, not when MS wants them. For us, it's perfect. Yes, we activate 26100 with mas hwid. Towards the end of the year, they'll be online key sellers with $5 MS keys for Win 11 IOT LTSC and we'll get those. Jim

Sorry, but I don't understand what you mean

I have 5! Only 3 machines but 5 licenses. Out of curiosity what do you like about Iot Enterprise LTSC? How are you activating it? massgrave.dev hwid?

Downloaded and installed the 24H2 Cumulative Update for 26100.712 (KB5037850) on our Iot Ent LTSC installs. No problems with SAB. Purchased license 3-pack on the 20th. I would urge everyone to buy at least one license and support Tihiy. Jim

Just a reminder that today (22-May-2024) is supposed to be the official EOL for all legacy Norton Security v22.15.x products for Win XP and Vista. I checked the Norton Security | Norton Internet Security | Norton AntiVirus board today and didn't see any new topics about this EOL, but if Norton follows through and stops pushing out malware definition updates it could be a week or so before v22.15.x users start seeing pop-up warnings in their system tray about out-of-date protection files.

@Anbima If you try Thorium as a solution to your secure connections problems with 360Chrome, and you have issues, please address those problems in the Thorium thread. Thorium should not need the use of any proxies, as it is based on a very recent Chromium version.

Thank you, shows how much I know about it!

... As I understood this, the suggestion was to use Thorium standalone (presumably because Thorium comes also with its own CA store/is less prone than 360EEv13.5 under WIndows XP to fail on secure connections... But yes, thanks to Anbima, last pages on this thread went like this: 360EEv13.5 standalone -> 360EEv13.5 + ProxyMII -> 360EEv13.5 + ProxyMII + Local PAC script -> 360EEv13.5 + ProxyMII + Local PAC script + Chromium extension(s) -> 360EEv13.5 + ProxyMII + Local PAC script (without extension) -> 360EEv13.5 + ProxyMII (standalone, without PAC script) -> 360EEv13.5 + ProxyMII + extension -> Thorium standalone (for his "problematic" HTTPS connections) -> exclusively Thorium-related queries -> ... IMHO, ProxyMII / ProxHTTPSProxy was the constituent with the lesser percentage in these recent discussions ; the "issue" (with still non-reproducible for everyone sample URLs shared) could well have been posted in one of the 360EE threads ... FWIW, if the issue encountered is the infamous "red-X" instead of a padlock on some HTTPS connections on 360EEv13.5 under XP, this is an already known "issue" and can well be a "red herring" (or not, but no-one posted something definitive on the matter...); IIRC, you can restore the padlock on these connections by running the 360chrome.exe executable in win2k compatibility (or something in this vein - have never faced this issue under Windows Vista SP2 x86 myself...).

Good to know. I will also change that in my next release.

Well I had a problem years ago where I tried using aswclear. It did remove it. However after I remove it many programs failed to start because of missing files or dlls. I don't know how that happened. Another thing about Avast is that it doesn't have any cleaning function at all for the infected files it finds. Unless you had the vrdb ready then you were screwed. One time I was servicing a computer and I let it scan at boot. And I it deleted Internet Explorer completely because it couldn't clean it.

In general, absolutely unnecessary. If Avast can't be removed from Windows inside, no matter whether in normal or safe mode, you can do this from outside. I did that in the past to remove locked registry entries which couldn't be deleted from Windows inside, not even by using Avast Clear in safe mode.

Incorrect, SSE4A is AMD-only instruction set containing 4 instructions which are not available in SSE4.1 and subsequent SSE4.2, collectively known as full SSE4 set. SSE4.1 is being targeted by SSE4 build of Thorium, so @Anbima should stick with SSE3 version on his old AMD.

Yup 24H2 is now in Release Preview.

Just a little reminder. This thread is about proxies. I believe there is no need to use Thorium together with ProxHTTPSProxy. @Dave-H Can you please move your conversation with @Anbima to the Thorium thread? A bit offtopic is normal and ok but I think this is the wrong place here. The Thorium thread is more suitable. Thanks!

Glad it worked for you!

You make it sound as if it was i who brought it up, apropos of nothing :\

26100.712 just installed (retail) SAB is running

As mentioned before. Avast can be really difficult to remove. And it can sometimes even leave a system crippled after removal. I prefer to just reinstall Windows at that point.

Thank you both. I do have another XP machine laying around, but the other fix seemed a bit cleaner. Following the discussion linked by AstroSkipper, I 1) Headed to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WmiApRpl\Performance 2) Deleted the First Counter, First Help, Last Counter and Last Help entries 3) Headed to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib 4) Set Last Counter to decimal 1846 5) Set Last Help to decimal 1847 6) Rebooted It worked like a charm.

When first booting to DOS, the display surface is usually in a 720x400 text mode. That's 80x25 characters, 9x16 pixels each. To reset the text mode to 80 or 40 columns, color or black&white, use: mode { co80 | co40 | bw80 | bw40 } e.g.: mode co80

I assume that SSE4A was an update to SSE4, so you should be able to use the SSE4 version OK.

Vesa video modes should be supported. Use a DOS app to set the screen to any standard Vesa mode.