Leaderboard

Since 0x3e1c0000 seems to work for everything I've thrown at it (one x86 XP laptop, one x86 XP desktop, one x64 XP desktop, two Win10 x64 laptops), I'm getting ready to repackage everything, upload, and start a new thread dedicated to 13.5 build 1030. There still could be a "better" base address, not really sure. I literally just tacked via trial-and-error until I hit one that worked.

Just an off-topic thank you. That worked perfectly! I've also removed the Standby button, as that doesn't work as it should either, it goes into standby, but then you can't get it back out of it! Finally, no more having to force it off with the power button because I've forgotten that it doesn't standby or restart properly! Cheers, Dave.

10 years ago or more, I used to have both Firefox 3.5.x and 4 installed, in their own "Program Files" directories of course , each assigned its own separate profile via the method you detailed above ... The move by Mozilla from Fx-3.5.x/3.6.x to Fx-4.0 (and higher) introduced major profile incompatibilities in a way that whenever a Fx-3.x.x profile was (even once) touched by Fx-4.0+, it became corrupted beyond repair and could no more be used by Fx-3.x.x ... Launching the browser(s) via the dedicated shortcut(s) (pointing to the right profile) worked as expected, but... when I clicked a link inside a document (Word, PDF, etc.) or e-mail, often times catastrophe would strike ... Depending on which Fx version was configured as the system default browser (associated with these links), Fx-4.0 would open the link in the Fx-3.x.x profile (thus corrupting it), because the plain document/e-mail links don't contain the "-no-remote -p" options... So, I had to always keep a back-up of the Fx-3.x.x profile in case s**t happened (pardon the language ) ... Fortunately, in a later stage, I migrated to using the two different Firefox versions inside their dedicated "PortableApps.com" format (PAF) installations and had made IE9 the system browser - no "accidents" happened since, that is until Fx-3.x.x was ditched altogether and the "newer" Firefox was adopted permanently ... (Happy New Year to the frequenters of these threads )

The October 2020 version works if it is set to "big picture" mode. You will see store information and everything. But sometime after that, the login window switched to being rendered by CEF (Chromium) so it is not possible to sign in as there is no text, graphics or buttons on the login screen now. As for the Intel drivers, I have a couple of systems that can use them but they are in very poor shape. Various differences in rendering quality are known to exist between Vista and 7 and I don't want Vista to be compromised by any changes I do. So I'll try to do something that doesn't "change" Vista to its detriment. Also, the Vista extended kernel will be able to run Chromium 110 and 111, at least with --no-sandbox. I will try to get the sandbox working in time for the main release of Chromium 110 in February. I am adding the appropriate functions to kernel32 and userenv. I just checked the Chromium source code and discovered that the version nags are persistent now because they are not calling GetVersionEx* or similar to check the version, but they are checking the version number of kernel32 instead.

Hardware firewall has been my best performing option. Also makes it so I don't have to tool around in the OS changing a bunch of things.

It supposed to ! This topic tells not working on Windows 7.

Build 1030 will be discussed in a separate thread -- https://msfn.org/board/topic/184266-arcticfoxienotheretoplaygames-360chrome-v135-build-1030/ Download links will be provided shortly.

@legacyfan, could you post the links to articles you post, please? Always post the links, don't forget these, of course... Thank you!

I have: RAM used after Windows boot (without browsers): 272/3071 MB (8%) RAM with 360Chrome 13.5 regular: 455/3071 MB (14%) (and with my 3 extensions for now....) 455-272=183 MB for 360Chrome... RAM with DCBrowser (ancient v.): 512/3071 MB (16%) (and with my all 11 extensions...) 512-272=240 MB for DCBrowser... I've NOT rebased...

You could use the normal chrome.dll standard and also a chrome.dll_rebase in the same folder. Then everyone can test it themselves which runs better. That would be the best.

I use different profiles for all my browsers. No sharing of profiles anymore for years. In the past, I made bad experiences with shared profiles which became suddenly corrupted. And I always keep backups of important profiles to be on the safe side. Happy New Year, too

Sorry, I made a mistake. I posted this here, cause I thought it could be helpful for developers who make extended kernels and such things. If someone would backport something to Windows Vista/7/8.1 (something that requires Win10) it should be easier to start from 1507 (2015) instead of 22h2/21h2 (2022/2021). Both versions of Windows 10 are really diferent despite of the name.

I suppose I could run with a default that work on x86 even though it will not work on x64. I have a strong hunch that MOST folks here on XP are all on x86. I think me and @UCyborg are the only two on x64.

Me too! With the original file, my RAM usage went from 48% to 75% when 360Chrome was run, with no tabs open. With the rebased file, it goes from 48% to 52%!

Sorry if i wasn't clear enough, i didn't mean to I want to prevent this. What i would like is for both browsers to not interfere with each other, to behave like really separate browsers. The issue until now was that they share the profile index file profiles.ini - whichever profile is set as default in there loads regardless if you started NM27 or NM28. I mostly use NM27, and start NM28 only to test something, if i have an issue with some site, or if i want to quickly check a page and close the browser (here both NM27 and Serpent52 have over 150 tabs and start pretty slowly). The way i start NM28 is by using the -P parameter, which brings up the profile manager. This also means that i have to do the same the next time i start NM27. If the wrong browser gets launched accidentally, it will (most likely) mess up the current default profile. Last builds fixed this by making each browser have its own profiles.ini file. Now @roytam1 says this will be reverted in the next builds (if i didn't misunderstand something). Ugh... As i said previously, one way to have your cake and eat it would be to allow a copy of profiles.ini in the same folder as palemoon.exe to take priority over the file buried in "C:\Documents and Settings\". Hopefully, Roy gets the time (and desire) to implement this. The only issue is if Palemoon is in "C:\Program Files\", on newer Windows you would need to start it as admin to let it modify that file. But, since this is optional (and not needed for a single NM2x browser), you can just let the browser use the regular file in "C:\Users\".

It appears as though the best I can really do as far as "default" settings for a "public release" is to NOT rebase chrome.dll. But add a post or two with every rebuild on how the end-user can rebase their own chrome.dll. The problem that I am finding is that rebasing is not "universal". I cannot use a rebased chrome.dll that "works" on my x86 and use that same rebased chrome.dll on my x64 (RAM goes from 207 MB without rebase to 388 MB with rebase, I'm better off without rebase on my x64 [or rebase to a different base address]). I rebase to an incorrect address and it doesn't "work". 0x1d10000 seems to work for both my x86 laptop and my x86 desktop - but I do knot know if this address will work for "everybody". I don't think there is going to be a "one size fits all" approach.

There's a tutorial that allegedly lets you run 16-bit apps on 64- bit. I don't know if it works but there are some comments below that say it does.

That Dr. Who character is the best portrayal of "vanity of vanities". Her name is Lady Cassandra. She claims to be the last "pure" human. But she's had so many surgeries performed over the years that she is nothing but the skin of a face stretched in a frame. The world revolves around Cassandra. Every other human still in existence is at her becking call to spritz her with a spray bottle of water so that she doesn't dry out. She reminds me of people on this forum. We are all just here minding our own business and yet some here are so into themselves that any and every move any of us makes is somehow turned and twisted into revolving around their own little universe. I'd say it's fun to watch. But it isn't. Dr. Who, on the other hand, that is fun to watch!

Now I have the timerhack for hal.dll XP bit64, Lan with Basilisk Browser, but still works only with /ONECPU in boot.ini Dietmar

I know it's Windows 8.1, but it looks like Visual Studio 2022 works on Windows 8.1 unofficially. Gives me a warning that the OS isn't officially supported, but works anyway ^o^ Now, I won't be forced to use that malware Windows 10 just to get school classes done.

You don't have to pick up the right profile with each start - just create two shortcuts with the right targets and put them to your desktop / start menu / quick launch bar, f.e.: target: C:\program files\NewMoon27\palemoon.exe -no-remote -p default target: C:\program files\NewMoon28\palemoon.exe -no-remote -p default2 So you still have a choice, but I don't see a way to circumvent different profile folders and still use the same profile in NM27 and NM28. kind regards soggi

It has been changed since Windows 7 build 6936. I tried replacing the d3d9.dll file with build 6910's and it still behaves like Vista's d3d9.dll (BEX64 crash code c0000005), but build 6936's works perfectly just like normal. I tested it myself on Windows 7 build 7000. Driver version: 10.18.10.4885 (December 2017 build), using George King's NTOSKRNL Emu_Extender

Based on my experience with Vulkan on Vista-compatible NVIDIA drivers, I would not be so quick to pin the issues on user-mode components. I'm not sure if there were any major changes to D3D9 since Vista brought in D3D9Ex. I would have to do a binary diff of the Vista SP2 and 7 SP1 D3D9 binaries...

It is random.org not .com Anyways, sites with Cloudflare DDOS protection have has a pre-loader message for a few years now. It is only recently that 1) random.org has had it (it appeared shortly after that large cookie notice that takes up the top 1/4 of the page) and 2) the Cloudflare message changed the text to checking if secure. It is also possible that websites that are using the Cloudflare service are not aware that some browsers can't pass this message. But I also wonder if these same browsers were able to pass the old pre-loader message that Cloudflare used to use.

Since I still use 1030, I actually used it to develop this patch before applying it to 2022. So, for 1030: Drop Share URL QR Code from Chrome mode page context menu: 89 F9 68 6D 1A 00 00 68 4F 81 00 00 EB 0F 68 6D 1A 00 00 68 4F 81 00 00 Drop Share URL QR Code from Chrome mode link context menu: 89 F1 68 6D 1A 00 00 68 50 81 00 00 EB 0F 68 6D 1A 00 00 68 50 81 00 00 Drop Share URL QR Code from IE mode page context menu: 6A 00 68 D5 08 00 00 FF 75 08 FF 15 E4 B1 EA 16 EB 5E 68 D5 08 00 00 FF 75 08 FF 15 E4 B1 EA 16 68 E4 25 00 00 FF 75 08 FF 15 E4 B1 EA 16 68 D5 08 00 00 FF 75 08 FF 15 E4 B1 EA 16 68 E4 25 00 00 FF 75 08 FF 15 64 B2 EA 16 68 D5 08 00 00 FF 75 08 FF 15 64 B2 EA 16 Drop Share URL QR Code from IE mode link context menu: 8D 7D E8 68 6D 1A 00 00 57 E8 41 58 17 FB EB 3A 90 68 6D 1A 00 00 57 E8 41 58 17 FB Drop Share URL QR Code from IE mode image link context menu: 8D 45 D8 68 6D 1A 00 00 EB 43 90 68 6D 1A 00 00 Drop Share image location from Chrome mode image context menu: 89 F9 68 6E 1A 00 00 68 51 81 00 00 EB 0F 68 6E 1A 00 00 68 51 81 00 00 Drop Share image location from IE mode image context menu: 6A 00 6A 0F 53 FF 15 E4 B1 EA 16 83 F8 FF 74 3C EB 4A 6A 0F 53 FF 15 E4 B1 EA 16 83 F8 FF 74 3C Drop Translate to English from Chrome mode page context menu: 8D 86 F0 02 00 00 50 E8 2F 9E 72 FE E9 E6 00 00 00 90 50 E8 2F 9E 72 FE As for your questions, I used the obvious suspect for such things. But its free version or Ghidra or OllyDbg should work just as well. Finding the locations isn't too hard with the source code for Chromium available, don't really need to decompile or use the debugger. It takes quite some time to disassemble/analyze a huge DLL like this one, though.

Standard 32 bit Chromium works as well, including extensions. But Steam and Discord do not work properly yet. Steam can connect to the Internet again, but the Chromium parts of it don't display anything and logs are not very helpful at this time. They are continuing to add functions to Chromium 111, and I was able to run that with --no-sandbox, but not with sandbox yet.

@UsefulAGKHelper Original razzle is ideal to compile anything from leaked sources, just cd to directory and build any .sys/.exe/.dll To show BSOD info on UEFI screen i think a lot of things need to rewrite or create from scratch, technicaly BSOD screen is text screen rendered by bios fonts, so in win8/win10 no more text mode, only hires screen with bsod code

I mostly remember 1977/78/79, no earlier years. I was at a concert with my grandmother in 1979, yes I think it was 1979 or 78, maybe . The band called Rockets, they were French, but sang in English, nice band, the accent is heavy though. But they aren't Disco, more like space rock style. I mean the original French Rockets, not the later para-Rockets with a very weak Italian singer. And Disco came here mostly in the eighties, and I didn't like it, sorry.

Thank you @roytam1

... As I added later, it's because of: with Goanna versions being different between Pale Moon (5.2.1, but recently changed to 6.0.0 in official UXP master) and the UXP forks (4.8.6) discussed in this thread...

Same in official Pale Moon, works in SeaMonkey.

It is NOT an intentional change, upstream pushed some changes that removing some PM changes which effectively/finally changed vendor name in resulting binary. a fix that reverts such changes is pushed to tree and will be available with old vendor name in next build.

Sorry, a bit late due to Christmas... The mirror of latest ArcticFox 40, BNavigator 0.9, Firefox 45ESR, IceApe 52, IceDove 52, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28, RetroZilla, RZ browser and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20221224 build - added latest IceApe 52 20221224 build - added latest IceDove 52 20221224 build - added latest K-Meleon 76 20221224 build - added latest MailNews 52 20221224 build - added latest New Moon 27 20221224 builds - added latest New Moon 28 20221224 builds - added latest Serpent 52 20221224 builds - added latest Serpent 55 20221224 builds To don't lose track of things I want to update too someday... todo: - add various flash player versions - add FlashFix for WinXP - add VLC 2.2.8 (WinXP non-SSE2) - add polyfill addons ------------------------------------------- OMG - even inside the most casual correspondence this is unacceptable! The first impression counts - so the check of the first word is extremely important! LOL I had no problems using the same profiles with NM27 and NM28 (beside some expected due to different code base). Hm... have to check if this doesn't work anymore now!? I always just replace the program folders. Edit: OK, I just tested NM27 right now and it couldn't access the profile which it's shortcut was linked to before because it now links to ..\Moonchild\Pale Moon\.. instead of ..\Moonchild Productions\Pale Moon\.. - see screenshot below. kind regards soggi

Damned they be! They plainly reject the UA sent by Serpent 52/55 (the Goanna and/or Basilisk slices) ... Edit: It's the "Goanna/*" UA slice they really object to ... The site loads fine via spoofing a "pure" Firefox UA, e.g. : "Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101 Firefox/52.0"

Greetings all MSFN members! This post is to serve as a reminder that the report system is not for communicating with moderators. If you need help with your own post, please PM an active moderator or post in the Site & Forum Issues forum. The report system is only to be used for reporting problematic posts or threads made by other users that break the rules. Also, please be sure to include a short description when you do submit a report so it can help us discern the issue with the post quicker and we don't have to spend a lot of time going through other posts to figure out the underlying issue. Thank you!