Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/08/2019 in all areas

  1. I extracted the core folder from the firefox 53 installer and patched all .exe files with XomPie. You just have to install it and it adds xpatcher.cmd to the send to thingy when you right click and it only needs the kernel32 patch so you hit 1 and enter and then it just works. This won't patch any system files. XomPie: https://github.com/tumagonx/XomPie/releases Working Software: Firefox: https://ftp.mozilla.org/pub/firefox/releases/53.0.3/win32/ Extract, then patch all .exe files Sugar Sync: https://filehippo.com/download_sugarsync/3.9.5/ Install, then patch SugarSync.exe
    2 points
  2. Reading about such killer probs on "full" facebook and even here on MSFN is rather scary. Am stuck on a yet older system and browser version, used to such pains on 'modern' sites and wasting much time finding workarounds, but didn't imagine that younger browsers are already so very badly broken too. But if you say K-Meleon (76.2?) works better there, that means NewMoon27 must be able to work the same way, since both use the same engine. Unless there are yet more probs involved? But probably just a matter of fiddling with different useragent-strings or css-tricks. Some special useragent strings for stubborn sites come already predefined in the browsers, and need newer strings occasionally. You could check those on about:config page, filtering just for 'override' or 'facebook'. Although those prefs only work if no "Addon" is installed, since those I've looked at closer all overrule that native useragent system with their own one. You can also open those problematic sites and check the really sent UA on scratchpad or whatever those non-KM browsers have, by a little scriptlet: alert(navigator.userAgent);
    2 points
  3. You need to click on the icon in the form of the letter "e" in the address bar, a lightning icon will appear in its place, which means that the engine has switched to chrome.
    2 points
  4. I installed 12.0.1202, which is a pre-release of 360 Extreme Explorer 12, based on Chromium 78. It can be obtained here: http://www.qiuquan.cc/browser/360chrome.html (behind some other stuff and semi-broken classic captchas) I installed it on Windows 2000 and XP. However it is quite broken as the first few attempts to use ended in freezes; now it is more stable. However it tries to use IE6 to render everything on Windows 2000; as IE6 is blocked in my firewall that went nowhere quick. XP is being a pill on my T60 so haven't tested as much there, but it was able to load the post-install page without apparently relying on IE. There is no indication that XP has been dropped so hopefully they will continue refining the product in time for its final release! Two other notes: -I had to rename the installer because my English NT5.x installations had a hard time with the Chinese characters and kept telling me "file not found". XP went into a classic GDI+ resource shortage fit and required a logoff when I tried renaming it there. -I had to copy the EN-US locale file from my v11 install to get v12 to start. However everything is still displayed in Chinese.
    2 points
  5. I have yet to go through stuff on what I think are his testing machines. I have plans for doing that mid next week though. I can use this info (knowing that there might be an RFDISK 3.1) to help me figure out if I'm looking at something more recent than what I am working off of.
    1 point
  6. You mean upload? Then for users' convenience, here it is: https://mega.nz/#!Z0dE0CAA!oJhI3ZaBDOfkPKgR18lTkPEt3wllL5LxuqiGgl20x2U I tried again under XP and it tries to use IE for rendering as well. Then I ran it under Windows 7, where it actually used Chromium. When Windows 2000 is set to identify as Windows 7, the browser just crashes with a "new tab" dialog. I do hope that they don't force it to use IE on NT 5.x.
    1 point
  7. Thanks for trying a new profile and confirming that it doesn't help. I don't think it's a matter of you and @kitaro1 being ignored, so much as the fact that no one here has a solution to the problem. I haven't tested it, but I strongly suspect "official" Pale Moon and Basilisk (on Win 7+) will have the same issue. I seriously doubt this is a bug that both @roytam1 and @feodor2 have both independently managed to introduce into their respective PM forks. So unless @looking4awayout's UOC patch helps, we're at the mercy of MCP to come up with a fix. Unfortunately the browsers (that @kitaro1 mentioned) that don't have this issue with GMail simply don't run on XP (or Vista), and can't be made XP-compatible. If that's the case, you know the drill: confirm the issue with official PM on a supported OS (Win 7 or later) and report it to MCP directly via PM's Help / Submit Feedback link. I agree; this has bitten me too when trying multiple versions of, say, Firefox, on the same PC. @VistaLover has the right answer - install at most one non-portable version of each browser - but it's easy to forget and not always practical. Luckily some combinations do work: Basilisk/Serpent 52, Serpent 55, PM/NM, BNavigator, Seamonkey, and FF all use different profile folders, so one of each of those can coexist peacefully without using "portable" versions. That's a bit much to ask of, say, 7-Zip; how's it supposed to know that what you're unzipping is a browser with this particular potential issue? But I'll look at adding a message of that sort to my "Download Latest Browser" batch file. AFAIK e10s/multiprocess only works on FF and Serpent, not NM; trying to enable it on NM just crashes it. But @roytam1 is customizing NM by locking some e10s-related preferences, so inadvertently installing the "wrong" UOC patch from @looking4awayout won't crash the browser.
    1 point
  8. yes but not only that, my build also provides some functions they removed(e10s/webide/webextensions/etc.), and maybe additional fixes.
    1 point
×
×
  • Create New...