Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/12/2024 in all areas

  1. Let H0 be the null hypothesis "Thorium crashes due to lack of POSReady updates". H0 must be rejected due to @NotHereToPlayGames's and @Saxon's report that Thorium runs fine in their Windows XP installations without POSReady updates. Unfortunately, the probability of error for this decision cannot be determined due to the too small sample size.
    5 points
  2. https://catalog.s.download.windowsupdate.com/c/msdownload/update/driver/drvs/2018/04/443cca06-360f-45d7-9618-5fd66910a819_7f4d9720ab79ef21a6d6a8ded1091770100d2488.cab
    5 points
  3. On the other hand, if that update is honest, could probably help. I remember some sites that didn't work in earlier 36 versions, started to work in the patched 13.5
    4 points
  4. We already had this disscusion here: https://msfn.org/board/topic/184051-my-browser-builds-part-4/?do=findComment&comment=1251008 And there is nothing more to add to this statement.
    3 points
  5. The name is so generic, really hard to memorise.
    3 points
  6. Well, my cr@ppy doorstop (Thinkpad A31 with SSE2) is cr@ppier than your T42 and is able to run Thorium and Supermium. They have never crashed but are really sloooow and freezes now and then for a while. Thorium runs better than Supermium on this hardware but they are both annoyingly sloooow. 360Redux, MP68 and NM28 (in that order) are running much better on this old dinosaur with 1.2 GB RAM. BTW, I have never installed Thorium/Supermium or used the bat/cmd files provided with the download. Just unzipped and a shortcut starting with --disable-low-res-tiling --quick-intensive-throttling-after-loading --enable-low-end-device-mode --disable-background-networking --disable-encryption --disable-machine-id --user-data-dir=Portable BTW2, "clean" XP Pro SP3, installed 2003, probably not fully updated to 2014 and no POSReady things. BTW3, @AstroSkipper: Thorium and Supermium runs from both my C and D partitions, currently I have 4 different versions, two on C and two on D. BTW4, there are a few more settings to try and many of them are probably outdated... https://gist.github.com/cassioKenji/3d9bf02e09f4542b7bfad7c0b83adbd0
    2 points
  7. To avoid messing up my main partition, I actually wanted to test Thorium in my second partition. But there, as already reported, the browser does not work stable. It crashes all the time. But in one of its bright moments, I was at least able to open a link from a PDF file in Thorium by directly clicking onto it. The REG files from Thorium were not the solution. They contain syntax errors. I made Thorium the default browser with the help of the Default Browser 1.8 tool that @dmiranda had already recommended here. For me, this tool worked as it should.
    2 points
  8. You seem to be using the older release Thorium_122.0.6261.168_WINXP_x32. But I am usimg the most recent release Thorium_SSE2_122.0.6261.171_WINXP_x32. Did you try this one on your computer where is installed Windows XP 32-bit without POSReady updates?
    2 points
  9. There isn't, but it will be updated soon to 124. https://github.com/Alex313031/thorium-legacy/issues/105
    2 points
  10. My system is rather unstable with Watler's HDA2.DLL, really needs most stability measures mentioned in this thread. About SBEMUL/SBMIDI: as far as I know these need a WDM-driver, which HDA2.DLL is not. But VDMSound can be used, according to @sifonium even for midi with the Yamaha-driver. Jack-detection through software is not supported by HDA2.DLL, only if hardwired like on old-fashioned hifi.
    2 points
  11. @NotHereToPlayGames Which version of Thorium do you run on your Windows XP 32-bit without POSReady updates?
    2 points
  12. I have never worked in an IT Department. NEVER. I do use "IT deparment", IN QUOTES, as a REFERENCE to how STUPID our company's "IT department" is!
    2 points
  13. 2 points
  14. Yeah, I usually go on vacations in Autumn (The Fall, or whatever you call it), but it's just me. I know a lot of folks that do it during the summer. As for the browser, I agree, it's waaay too old. What about the China fork 115, then? Don't remember the exact name.
    2 points
  15. "I made some Benchmarking for myself, I decided to share them, frankly I doubt there are still many who uses 391.35 drivers, but i believe it's the best Drivers for Pascal cards" D.Draker never advises bad drivers. https://www.reddit.com/r/nvidia/comments/cbfls3/benchmarking_39135_vs_43136_drivers/
    2 points
  16. He wouldn't be able to install them at all, if he had no required updates on the machine,
    2 points
  17. Open nv_ref_pubwu.inf and replace all occurrences of 1B80 with 1BE0, click save, when a prompt shows about the unsigned driver, click yes.
    2 points
  18. I have recently been re-testing modern versions of Java under Windows XP, having figured out many fixes and workarounds to issues that were present on these newer versions when being ran on that operating system. To be more precise, i have managed to solve a crash with keyboard input, the java control panel refusing to launch, java applets being broken, as well as JavaFX applications and its WebKit component not running. Ultimately, this has allowed me to get the latest and newest revision of Java 8, which currently is 8u421, running on XP without any major bugs or glitches. This version needs XomPie in order to run, however, instructions for slightly older versions of Java are also available, having been revised to include all of the mentioned workarounds, including JavaFX compatibility, so people can run more modern and stable versions on their original installs. These are available on my website: http://neonfloppy.sytes.net/software/winxp/java/ Moreover, Windows Vista can also run 8u421, provided Extended Kernel or XomPie are installed on the system. Previous versions have also been revised, for those still running vanilla Vista. More details here: http://neonfloppy.sytes.net/software/winvista/java/
    1 point
  19. Sorry, no such hardware here. The lowest I could find is Pentium E6600. SSE3 is supported,
    1 point
  20. We need an MSFN Member to step forward that also runs an SSE2 CPU. My ThinkPad T42 is SSE2 but I have no interest in loading Thorium onto it. At least not at the moment.
    1 point
  21. Upgraded to Thorium_SSE2_122.0.6261.171_WINXP_x32 and have been running non-stop for over 15 minutes without any issues. No "gain" in going from .168 to .171. But no "loss" either. Right out of the box. No extensions, no settings changes, all defaults. Browsing works just fine. YouTube will stutter, but YouTube always stutters for me until I add my extensions then YouTube is generally flawless for me also.
    1 point
  22. Supermium can work by enabling IPC access, but I'm not sure if it's safe
    1 point
  23. I agree. We used to have several XP x86 SP2 forum members. They were "ran off" when they tried to "rep farm".
    1 point
  24. FWIW, it's always worked fine for me. I get a lot of pops and clicks, but that's expected. Volume I can adjust using WaveOut.exe. I have no sound in DOS games, but that's not a problem for me. There is no recording functionality, but I would have been really amazed if there had been! I've never had any system hangs which were knowingly due to the audio driver.
    1 point
  25. The screenshots below show the major issue of virus-checking with Kaspersky installed into a sandbox: 1) You canNOT select in the normal Windows Explorer the specific subfolders or files to be virus-checked. Kaspersky can only check whole partitions etc. For selecting files and folders for virus-checking you have to select the items in the Windows Explorer context menu. When Kaspersky is not normally installed, but installed into a sandbox, then Windows Explorer will NOT display a content menu entry "K scan for viruses". I have created a .reg file with 5 registry patches to display in the normally run Windows Explorer a content menu entry "K scan for viruses". pointing to shellex.dll in the Kaspersky folder in the sandbox, even if Kaspersky was not normally installed. The Windows Explorer context menu did then display a content menu entry "K scan for viruses". but it stayed greyed out. I fiddled around with OpenPipePath and OpenFilePath entries in Template.ini, but I couldn't establish a communication between the context menu entry in the normal Windows Explorer and the sellex.dll in the Kaspersky sandbox. Maybe the 5 registry entries were wrong, or the parameters in the OpenPipePath entry in Template.ini were, or you just cannot do it. This demonstrates that if an application does not install and run immediately in a Sandboxie sandbox, it may require very profound knowledge to get it going. This explains also the huge size of Template.ini, with the many customized holes and settings for many applications. 2) When you right-click on a partition in My Computer and select in the context menu -> Run Sandboxed -> select the sandbox with Kaspersky, you can browse to the folders/files to be virus-checked. The context menu will then display OK "K scan for viruses". The virus-checking, however, has big issues: - it it inconvenient to have to open an extra sandboxed Windows Explorer window for virus-checking - the stuff to be virus-checked will be copied into the sandbox and remain there, even after having exited Kaspersky. You now have a copy of potentially infected stuff. - the virus-checking with Kaspersky installed into a sandbox is very slow, maybe an issue for the Pentium 3, maybe less so with a more recentcomputer. - the many bugs of Sandboxie are added to the few bugs of Kaspersky For several special uses, however, installing Kaspersky into a sandbox may be quite useful (e.g. obtaining quickly additional signature updates for one-time-update trial versions, for comparing downloaded signature updates, for comparing updates of the same Database Release Date with vs. without updating application modules [=updating the installed software build]. Running two instances of Kaspersky simultaneously side-by-side I tried to run on the Pentium 3 laptop two instances of Kaspersky side-by-side (one in sandbox Kaspersky with the signatures of 9Aug2024, the other in sandbox Kaspersky_2 with signatures of 10Aug2024). Only the instance which was loaded first would run. When I selected the 2nd instance in the System Tray, the same Kaspersky came up, even if 2 Kaspersky icons were displayed in the System Tray. When I clicked on -> Exit of one of the two Kaspersky icons in the System Tray, both Kaspersky icons disappeared but the red dots in the Sandboxie icon remained, i.e. one instance of Kaspersky was still running but you couldn't access it via the System Tray anymore. Again, running 2 versions of Kaspersky consecutively works Ok, but 2 versions of Kaspersky canNOT be run simultaneously side-by-side.
    1 point
  26. Thanks, I had forgotten about the size 2MB limitation. I am also reducing the size of the screenshots to be uploaded. Sandboxie v5.22 and my ancient version of Kaspersky Update on 22Feb2025: screenshots were removed from this posting, because of limited upload space. The page showing the screenshots was archived at https://web.archive.org/web/20250222143024/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/page/2/#comments I have installed, updated and run my ancient version of Kaspersky in 2 separate sandboxes of Sandboxie v5.22 on a 24-year-old Inspiron 7500 laptop (650MHz Pentium 3 SSE-only, 512MB RAM) under WinXP SP3. The findings below apply only to Sandboxie v5.22, not necessarily to v5.40 (SSE2) by David Xanatos, and only to the virus-checking features of my ancient version of Kaspersky, not to the protection components, which I have not installed. I first created 2 additional sandboxes, "Sandbox Kaspersky" and "Sandbox Kaspersky_2". as shown in the screenshot below of "Sandboxie Control", Another screenshot shows the content of the folder "M:\Sandbox\", which contains the 3 sandbox folders of Sandboxie and renamed backup copies of the sandbox folders. "Copy of Kaspersky_after_customization" is the a renamed copy of "Kaspersky" with the installed and customized trial version which has not yet been updated, the Update button is still ungreyed [=functional, 1 update is possible], size: 166MB. "Copy of Kaspersky_updated_9Aug2024" is a backup copy of "Copy of Kaspersky_after_customization" after updating the signatures. It was created by making a copy of "Kaspersky" after the successful update, size: 927 MB. After the update the Update button turned greyed out [= no more updates possible]. "Kaspersky_2" was initially created as a copy of "Copy of Kaspersky_after_customization", i.e. the Update button is still ungreyed [=functional, 1 update is possible]. On the next day "Kaspersky_2" [with the functional, ungreyed Update button] was updated. After the update the Update button turned again greyed out [= no more updates possible], size 1.24GB (much larger). A binary compare with Beyond Compare of "Sandbox Kaspersky" vs "Sandbox Kaspersky_2" indicates that temporaryFolder was 391MB larger, maybe I should have used a different Update folder location for the update of 10Aug2024 (see screenshot below). The old Pentium 3 laptop now contained two functional Kasperskys under the same WinXP. "Sandbox Kaspersky" contained Kaspersky with the signature updates of 9Aug2024, "Sandbox Kaspersky_2" contains Kaspersky with the signature updates of 10Aug2024, i.e. with updates of the following day.
    1 point
  27. I could do what your followers do - ask for proof of being a mathematician.
    1 point
  28. Just for clarification. I am not a self-proclaimed "mathematician" but just a mathematician. I have not announced anything here, but only mentioned it in passing. No more, no less. As part of my search for the cause of the spontaneous Thorium crashes, I formed a lot of hypotheses and had to unfortunately reject them. And I have investigated many things as part of my hypotheses. But so far without success.
    1 point
  29. Yep! A clean, genuine Windows XP Professional. Only the service pack SP3 and all post SP3 updates until 2014. POSReady stuff has never been applied to this partition.
    1 point
  30. cab files work a little like installers https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options?view=windows-11
    1 point
  31. Those were the good times when didn't have to give our phone numbers to every bystander. Now I go on vacation, I can't even login to Instagram 'cause their "security" triggers and blocks my account due to "suspicious location". Nothing suspicious in it! I tried log in from the Dutch overseas territories, from a public hotel WiFi spot, so what? I wonder what other people do? How do they live? No one goes on vacations anymore? Everyone is chained to only one location?
    1 point
  32. And you had doubts it wouldn't? Why? PS Have I ever given a bad driver to anyone?
    1 point
  33. What exactly you don't like in that guy? He looks like the facebook type, posts cats, stays short, straight to the point, no politics, only talks about Vista, basically a dream guy for any modern website.
    1 point
  34. You're welcome, glad to be of help, the driver I gave, it's one of the best for the Pascal gen., Let's not forget, GTX1080 is 8 years old. So don't chase newer drivers.
    1 point
  35. I would caution you to not rely on uBO (or any extension!) to reveal what "connections" are being made by the browser (any browser!). It's very easy for "built-in" browser functions to do whatever they want without landing on a uBO log! It's also very easy to "bundle" an extension but it be rewritten in a way that the user isn't aware that it "does stuff" that it would not do if installed from the browser-of-choices "store". Heck, I've even witnessed over the years where "built-in" 'communications' DO NOT USE the browser's proxy settings, they SNEAK THROUGH as a "direct connection" (I still catch them and block them anyway, lol).
    1 point
  36. Something tells me that device is locked to the OEM manufacturers drivers only. I had a similar case in the past, only the supplied drivers worked, all drivers from Nvidia site simply crashed during high load.
    1 point
  37. Yes it is. It's a comparison of "how Firefox does it" to "how Chrome does it". You cannot compare apples to oranges. Firefox can do things that Chrome cannot do. Chrome can do things that Firefox cannot do. We all decide for ourselves which does what we need it to do, and which does not do what we need it to do. If they didn't do things differently, than one of the two would cease to exist.
    1 point
  38. I hope that was sarcasm.
    1 point
  39. Stop writing this nonsense under every post mentioning Thorium. If you are so disgusted by him, just ignore those posts.
    1 point
  40. Besides, sites may simply crash or not work at all when they discover the function they requested is absent in chromium 86. I once used an android mobile UA with this browser, many sites tolerate the old mobile Chrome agent much better. Something like: Mozilla/5.0 (Linux; Android 10; insert phone model) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/xx.x Chrome/xx.x.xxx.xx Mobile Safari/537.36 xxx replace with the Chrome/browser version you want.
    1 point
  41. On some websites, to some extent - yes, but you always leave a unique fingerprint behind.
    1 point
  42. Yes, replacing files should work for updating from older builds. basilisk(moebius/UXP) and PM28 builds doesn't need LAV dlls.
    1 point
  43. New Palemoon 27 Build! This build is on par with 27.9.3 release. 32bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180616-4197dba32-xpmod.7z 32bit SSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180616-4197dba32-xpmod-sse.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180616-4197dba32-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win64-git-20180616-4197dba32-xpmod.7z source patch against official palemoon: https://o.rthost.cf/palemoon/sources_patches_20180602.7z Official repo changes since my last build: - Add a nullcheck in DOMProxyHandler::EnsureExpandoObject (dea50cbf6) - Satisfy AMO's discrimination by UA. (4197dba32) My changes since my last build: - Applied ICU CVE fixes for CVE-2017-7867, CVE-2017-7868, CVE-2017-14952, CVE-2017-15422
    1 point
  44. New Palemoon 27 Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180609-4463c7031-xpmod.7z 32bit SSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180609-4463c7031-xpmod-sse.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180609-4463c7031-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win64-git-20180609-4463c7031-xpmod.7z source patch against official palemoon: https://o.rthost.cf/palemoon/sources_patches_20180602.7z Official repo changes since my last build: - Clarify status or repo in README. (cbf1d4591) - Update HSTS preload list (d77bbb826) - Merge pull request #1682 from trav90/HSTS-preload-update (500b1e67e) - Fix count of compacting update tasks started. (4463c7031) My changes since my last build: - Updated NSS to 3.36.4, with patches of bug1464618, bug1465241, Restore-DBM-storage, bug1465186, bug1464616, bug1464971, bug1451936 - Updated libpng to 1.6.34+apng
    1 point
  45. you know that KM release post is just a mirror in case KM forum is not working (yeah sf hosting sucks) and IIRC there is not much KM discussions in this thread (before forum HD crashing)
    1 point
  46. Just got a request of SSE(not SSE2) build, and I updated latest PM27 build post adding SSE build. since 52ESR can't compile as IA32 or SSE, I created 45ESR fork and picking changes from tenfourfox repo. test binary: https://o.rthost.cf/gpc/files1.rt/firefox-45.9.8-20180530-1ff8f7bef-win32-sse.7z repo: https://github.com/roytam1/mozilla45esr (reposted after forum data lost, original date: 30 May 2018)
    1 point
  47. PM28 will include av codecs, PM27 needs LAV DLLs.
    1 point
×
×
  • Create New...