Jump to content

Leaderboard

Popular Content

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

  1. Sorry, no such hardware here. The lowest I could find is Pentium E6600. SSE3 is supported,
    3 points
  2. Thanks for your idea! That's why I originally assumed POSReady updates were mandatory for running Thorium. Maybe, there is really an POSReady update which is urgently needed to run Thorium on my hardware. But I should mention that there are 365 updates in my archive applied after the POSReady hack. And without this hack, you can't install those updates, either. So, it does not make sense to investigate them. And I already have a perfectly working Windows XP Professional installation with all POSReady updates. All my very deep investigations lead me to modify my null hypothesis: Here is my modified null hypothesis H0: "Thorium crashes due to the lack of one or more POSReady updates under certain hardware conditions". Personally, I tend to accept H0 due to my experiences and deep investigations. Unfortunately, the probability of type II error for this decision cannot be determined again due to the too small sample size, either.
    3 points
  3. @NotHereToPlayGames Which version of Thorium do you run on your Windows XP 32-bit without POSReady updates?
    2 points
  4. Genuine Windows XP Professional is what I have on my notebook, I'm sorry, I have no plans to install any updates at all. Thorium and Supermium both launch fine.
    2 points
  5. It would only be needed if @AstroSkipper relied on that do fortify his position on the site, which he never did, as he told, he only barely mentioned it, unlike you who frequently mentioned you worked in the "IT department".
    2 points
  6. Any ideas what can cause these sudden closings of Thorium? My hardware can't be the causer, though. Has anyone had similar problems?
    2 points
  7. I added bold and underline to be sure that everyone is asked here. This has nothing at all to do with your answer, for which I have already thanked you. You should calibrate your sensor a little. It is set too sensitively.
    2 points
  8. Agree. In Holland, most online shops demand Chrome 110-115, at the very least. Not that surprising since Chrome 110 is 1 year and 8 months old.
    2 points
  9. some extensions has seamonkey/iceape support, like ublock origin.
    1 point
  10. https://woshub.com/manually-install-cab-msu-updates-windows/
    1 point
  11. 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
    1 point
  12. Hi @blueclouds8666, thank you very much for this. I can confirm that (installing XomPie) the last version of Java, with the modifications you clearly outlined, works in XP. I will try it in apps I use that require java (OpenOffice, Qgis, etc). I don't have XomPie installed in my bare-metal system (afraid of instability) but will try it soon to see what happens. In the meanwhile, I followed your indications to improve the java version (Java 8u251 I use on my bare-metal I would recommend you to modify this thread to introduce all the software and your inputs at neonfloppy, using the original post to do so, and copying the current article into a sub-post. It's not just good for advertising your page, but to more widely distribute your fine job. Cheers and congrats.
    1 point
  13. @VistaLover, why won't you ask win32 to reimplement the flag from the ready made Ungoogled patch?
    1 point
  14. We are doomed: "Unfortunately there are issues passing the site-specific UACH override to the renderer (specifically, the URL information that is available at HTTP header creation is not available at renderer creation), which means that it is only reliable for UACH information transferred by the HTTP header and not by JavaScript. With this in mind, I can only implement one default override." https://github.com/win32ss/supermium/issues/779#issuecomment-2282871131
    1 point
  15. @Tihiy Keep up the good work and development of a great app. Here is something to possibly improve\review. I am not sure if this is possible for you to implement but asking for insight anyway; it would improve the UI experience. Would it be possible to enable dark mode on Toolbar flyouts? In the image I show below I have a toolbar pointing at a folder with internet shortcuts. Currently the background on the toolbar is light while in settings the OS is set to dark and File Explorer windows are dark following the OS.
    1 point
  16. No offense, but these reports are extremely difficult to follow when the screencap is NOT IN ENGLISH.
    1 point
  17. Probably, it's more suitable for someone who lives in Russia.
    1 point
  18. 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.
    1 point
  19. 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?
    1 point
  20. Saxon is being objective. My purely personal opinion regarding updates, especially XP updates, they slow down your PC. I'm not taking sides, and there's no need to do that. I'm not participating in any "formations", or whatever someone earlier tried to insinuate. Does my opinion match yours? Good! It also matches @Gansangriff's, too! My respect to @AstroSkipper is huge, nevertheless.
    1 point
  21. 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.
    1 point
  22. A native English speaker would tell: "you said you were a mathematician".
    1 point
  23. Hello our dear @Astroskipper, the pillar of wisdom! How do you do? @D.Draker taught me to delete Vulkan, Swiftshader and D3D 47, perhaps try it? Have a nice evening!
    1 point
  24. Constantly having the same password problem when they reset it whenever they want. It's the same with facebook, btw, my grandma told me.
    1 point
  25. That's good to know. In both systems, all runtimes have been installed.
    1 point
  26. 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
    1 point
  27. The name is so generic, really hard to memorise.
    1 point
  28. 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.
    1 point
  29. You still didn't show your "IT professor" profile, come on. Or what? You'll report your insults and crappy off-topic spam?
    1 point
  30. New issue with Thorium, got a BSOD today without minidupms, The browser was open without any sites for quite some time, Several hours, maybe. Then I heard two short beeps, saw a short splash with BSOD, the PC went into reboot, Yes, on that PC, I do have the reboot option checked.
    1 point
  31. Oh, actually they are right. WoW64 is a subsystem on a 64 bit OS, so my true 64bit is properly detected. I just confused with Dave's screenshot. So, they now don't see which OS exactly, only that it's a 64 bit OS.
    1 point
  32. BTW, I don't know why it says Wow 64 - false, I'm on a 64 bit OS.
    1 point
  33. What works or doesn't work in Ungoogled isn't relevant, and has no relation to Supermium of Thorium. Supermium of Thorium aren't Ungoogled, therefore they function differently. Does your site work in Thorium? Edit. It (*the site) may try to invoke google services.
    1 point
  34. YumeYao WMP11 Addon Updated to 29/04/2015 File: YumeYao_WMP11_Addon_ENU_29042015.7z (Google Drive) File: YumeYao_WMP11_Addon_ENU_29042015.7z (4Shared) MD5: 0920E443CC27F30EE8D0786FA8DA7135 SHA-1: 0A158F8E6FE219A7FA046F591FE27D8CE36357FF SHA-256: 710868A92390AACA976AAF951830FC923AFEDB85808B7F994D04370A4EC21675 File Size: 20.2 MB Release Date: 08/06/2022 The version number of this build is the build date for wmp.dll supplied in the POSReady 2009 update KB3033890. I have disabled the entries for the WMP9 files deleted by the addon in sfcfiles.dll to remove them from Windows File Protection monitoring. SFC should not flag missing protected system files. List of Updates and hotfixes KB954155 - wmspdmod.dll/11.0.5721.5263 KB974905 - wmnetmgr.dll/11.0.5721.5269 KB975558 - mpg4ds32.ax/8.0.0.4504, mp4sdecd.dll/11.0.5721.5274 KB978695 - wmvcore.dll/11.0.5721.5275 KB973540 - wmpdxm.dll/11.0.5721.5268 KB943604 - Npdsplay.dll/3.0.2.629 Dxmasf.dll/6.4.9.1133 Npdrmv2.dll Npwmsdrm.dll/9.0.0.4504 KB970159 - Windows User-Mode Driver Framework 1.9 KB2834904-v2 - wmvdecod.dll/11.0.5721.5289 KB3033890 - wmp.dll/11.0.5721.5293) KB3067903 - cewmdm.dll/11.0.5721.5295) Description by YumeYao This addon will replace your Windows Media Player Component in your windows installation CD with its contents. Why your first release is V3? Check this post. Why do you release another WMP11 Addon as boooggy and onepiece both do good job? I have workd on an addon including Windows Media Player 10 and Windows Media 11 Runtimes, therefore i only need to modify a few to create this addon. Features by YumeYao Compatibility with XP/MCE/2k3 in one Addon. for 2k3, M$ does not install skins but this addon does Obsolete files are removed. They are either utility to migrate DRM stuffs or a file with several KiloBytes which is used to overwrite the old file. Addon structure: File Copy and Registry handling are system-like A working MTP on Windows 2003, both their WMP Integration solution can't offer this. Original Wincert thread here Original RyanVm thread here Note that 4Shared is blocked in the UK. Residents in the UK should use a VPN server in the US or the Netherlands.
    1 point
  35. 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
  36. On some websites, to some extent - yes, but you always leave a unique fingerprint behind.
    1 point
  37. SSE means SSE-only build, for Intel Pentium 3/AMD Athlon XP and later. IA32 build is for anything from Original Pentium and later. for Pentium 4 and later, use normal build. you may check your system drivers(antivirus filesystem filters, etc.) if anyone is malfunction.
    1 point
  38. It is hard to say, running on old SP is totally untested. Trying to run palemoon26-win2000 on XP RTM will just cause c000021a BSoD for example. but it works quite well when SP1 is installed. I can even hack XUL.dll to NOT loading uxtheme.dll(of course that means no watercolor theme in PM, since uxtheme format is incompatible) and removing manifest in palemoon.exe and hacked MSVCR80.dll NOT to parse manifest, making PM26 working in XP build 2296!
    1 point
  39. build 0623 is in the time just before they bump from alpha to beta 1.
    1 point
  40. nope, it is same as official builds i.e. it is beta now!
    1 point
  41. New Palemoon 27 Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180630-53606d9e9-xpmod.7z 32bit SSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180630-53606d9e9-xpmod-sse.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180630-53606d9e9-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win64-git-20180630-53606d9e9-xpmod.7z source patch against official palemoon: https://o.rthost.cf/palemoon/sources_patches_20180602.7z Official repo changes since my last build: - Restrict web access to moz-icon:// scheme (1ffd7ba7a) - Prevent various location-based hazards. (53606d9e9) My changes since my last build: - Port TenFourFox changes: + Ported changes: bug1380292, bug1386905, bug1395598, bug1396570, bug1368269, bug1400399, bug1368852, bug1393098
    1 point
  42. try enabling layout.css.moz-document.content.enabled and restart. because it is not intended to use SQLite-format cert9.db and key4.db, which have bad experience when starting a profile over network drive, and it is caused by updating NSS. And finally it is reverted back to old DBM-format cert8.db and key3.db. for MSE and JSON-based update manifest, I hope I can have time having a look on it. for Auto Update issue, tag #409@UXP: https://github.com/MoonchildProductions/UXP/issues/409
    1 point
  43. I'll just remove the disclaimer, but they will still share same post in future.
    1 point
  44. I think it is no worth to do so since they're going to nuke legacy XUL externsions in AMO in near future.
    1 point
  45. because of versioning, AMO server refused to provide updates to (they think) "old" firefox alpha versions.
    1 point
  46. then you may try my palemoon26, which is Firefox24 based with TLS 1.2.
    1 point
×
×
  • Create New...