Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Today
  3. 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.
  4. @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.
  5. ... 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...).
  6. 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.
  7. 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.
  8. 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.
  9. Yup 24H2 is now in Release Preview.
  10. 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!
  11. You make it sound as if it was i who brought it up, apropos of nothing :\
  12. 26100.712 just installed (retail) SAB is running
  13. 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.
  14. 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.
  15. 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
  16. I assume that SSE4A was an update to SSE4, so you should be able to use the SSE4 version OK.
  17. Vesa video modes should be supported. Use a DOS app to set the screen to any standard Vesa mode.
  18. If you are interested to AI. Open a thread. Each person has his or her own priorities. You have yours. I have mine. Others have theirs.
  19. CPU-Z shows me the following: SSE, SSE2, SSE3, SSE4A Should I use SSE3 or SSE4? Are SSE4 and SSE4A the same? Prozessor: AMD Phenom II X4 945
  20. https://github.com/Alex313031/thorium-legacy/releases You will have to scroll down to the second section. There are versions for SSE2, SSE3, and SSE4 systems. Chose as appropriate, and do read what it says above the links. The zip files do contain installation batch files, but you don't have to use them. It should run fine as it is.
  21. As I said, deepl is not important because no sensitive data is transmitted. DeepL was only an example. When using 360Chrome together with ProxHTTPSProxy, then either the settings in IE8 have to be changed or the Manual Proxy option has to be used by Proxy Switcher. All this can be clearly seen in ProxHTTPSProxy's logging window. BTW, the web interface of DeepL is broken in 360Chrome. It looks like a CSS issue.
  22. On my system without Thorium running, the RAM usage is around 1150/2814 (40%). With Thorium running, with no tabs open, this changes to around 1600/2814 (57%). I do have quite a few extensions installed on Thorium though, without those I suspect that the RAM usage would be considerably less.
  1. Load more activity
×
×
  • Create New...