NotHereToPlayGames Posted March 11, 2023 Author Posted March 11, 2023 (edited) 1 hour ago, Humming Owl said: AF, which tool did you use to rebase the chrome.dll file and how? I think I am going to follow that method with my releases as well by default. Also, why at address 0x3e1c0000? Cheers. You will need delcert.exe mentioned by @mixit here -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1233000 Then you will need rebase.exe and cab1.cab mentioned by @mixit here -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1233344 chrome.dll was originally based at 0x10000000 i have been rebasing my chrome.dll at 0x10010000 (my last upload was "rebuild_7" and it was rebased at 0x3e1c0000 but I have since been using 0x10010000) I used Process Hacker 2.38.343 (I don't recall offhand, I think it was the last version to show System Information CPU, Memory, and I/O all on ONE PAGE). You can right-click 360chrome.exe and select Properties then go to a Memory tab to see where everything resides in memory by address. I was using two desktop computers (one on XP x86 and one on XP x64) and two laptop computers (both on XP x86). I ended up at 0x10010000 basically for no other reason then it worked on all four of my XP computers without conflicting with a "hooked .dll" (from a mouse-gesture program I run) that does or does not run on all four of those XP computers. If I recall, 0x10010000 was the smallest address I could rebase to that was higher than the original 0x10000000. It was my assumption at the time that selecting the smallest address possible increased chances of working on all four of those XP computers (because other members here were not having success with 0x3e1c0000). Edited March 11, 2023 by NotHereToPlayGames 1
NotHereToPlayGames Posted March 11, 2023 Author Posted March 11, 2023 (edited) I suppose it's quite possible (though I have not confirmed) that the original chrome.dll only needs to be rebased "away" from its original address and then rebased BACK TO its original address. Edited March 11, 2023 by NotHereToPlayGames
rereser Posted March 11, 2023 Posted March 11, 2023 360ChromePortable_13.5.1030_rebuild_7_regular and ungoogled , webgl files and folder are missing : in the 13.5.1030.0 root folder ... 1 / the swiftshader folder with the two dll files ( libEGL.dll - 352 KB , libGLESv2.dll - 2,35 MB ) 2 / libegl.dll ( 332 KB ) and libglesv2.dll ( 5,13 MB )
NotHereToPlayGames Posted March 11, 2023 Author Posted March 11, 2023 4 hours ago, rereser said: 360ChromePortable_13.5.1030_rebuild_7_regular and ungoogled , webgl files and folder are missing : in the 13.5.1030.0 root folder ... 1 / the swiftshader folder with the two dll files ( libEGL.dll - 352 KB , libGLESv2.dll - 2,35 MB ) 2 / libegl.dll ( 332 KB ) and libglesv2.dll ( 5,13 MB ) Ah yes! Good catch! The swiftshader files were removed originally due to FALSE INFO from the MSFN Community. I have always kept them in MY local copy due to multi-monitor setup crashes when they are removed (even with WebGL disabled via loader.ini). In my local setup, I keep the swiftshader SUB-FOLDER but I delete the two files in the ROOT FOLDER -- so I am unsure if "both" sets are required or not. My apologies, yes, MY local setup has always kept the swiftshader sub-folder -- and I had no desire to "debate" with the MSFN Community at the time those were being discussed as "not needed". 1
NotHereToPlayGames Posted March 11, 2023 Author Posted March 11, 2023 I'll be uploading a "rebuild_8" later this weekend or so (despite intentions to never upload again because I get tired of folks calling v86 "ancient"! WE KNOW, the thread is entitled OLDER NT-FAMILY OSes! It will NEVER be "cutting edge"!). This one will have WebGL enabled by default since most "this site doesn't work" reports seem to always be WebGL-related.
msfntor Posted March 11, 2023 Posted March 11, 2023 I see clearly that I'm NOT interested in WebGL, WebGL sites...it's not for me.
Ascii2 Posted March 12, 2023 Posted March 12, 2023 On 12/30/2022 at 4:34 PM, NotHereToPlayGames said: This build is targeted to be more RAM-friendly than earlier builds. The chrome.dll file now has a default base address of 0x3e1c0000 and this seems to work well for both x86 XP and for x64 XP. Limited to no tests whatsoever were performed outside of XP. ... 360ChromePortable_13.5.1030_rebuild_7_regular.zip... 360ChromePortable_13.5.1030_rebuild_7_ungoogled.zip Thank you @NotHereToPlayGames for these builds. I tried the ungoogled build on my computer running Windows XP Professional with Service Pack 3 and note that it works way, way better than previous builds. Also, there is a long existing bug that manifests with your 360Chrome builds (any major version series) that I request attention to and, hopefully, have the bug corrected. Please let me know if the bug can be corrected. The Bug: While an instance of the 360Chrome browser is opened, and the main toolbar's "Show bookmark menu" icon (has a star shape) is clicked three times (does not need to be all at once), the 360Chrome browser software crashes.
Milkinis Posted March 12, 2023 Posted March 12, 2023 (edited) On 3/11/2023 at 2:23 AM, NotHereToPlayGames said: I used Process Hacker 2.38.343 (I don't recall offhand, I think it was the last version to show System Information CPU, Memory, and I/O all on ONE PAGE). the version 2.9 supports with XP even though the website says it doesn't Edited March 12, 2023 by Milkinis
UCyborg Posted March 12, 2023 Posted March 12, 2023 On 3/11/2023 at 2:23 AM, NotHereToPlayGames said: i have been rebasing my chrome.dll at 0x10010000 (my last upload was "rebuild_7" and it was rebased at 0x3e1c0000 but I have since been using 0x10010000) When Chrome was still developed for XP, chrome.dll's base address was 0x1c30000. 2
NotHereToPlayGames Posted March 12, 2023 Author Posted March 12, 2023 54 minutes ago, UCyborg said: When Chrome was still developed for XP, chrome.dll's base address was 0x1c30000. Are you sure? There's only 7 bits there instead of 8. 1
UCyborg Posted March 12, 2023 Posted March 12, 2023 Yes, I could've written 0x01c30000, but what difference would it make? Old Chromes can still be downloaded from some places to check. 2
NotHereToPlayGames Posted March 12, 2023 Author Posted March 12, 2023 25 minutes ago, UCyborg said: Yes, I could've written 0x01c30000, but what difference would it make? Doh! Didn't even dawn on me, thanks for the clarification. 2
Cixert Posted March 13, 2023 Posted March 13, 2023 On 12/30/2022 at 11:34 PM, NotHereToPlayGames said: This build is targeted to be more RAM-friendly than earlier builds. The chrome.dll file now has a default base address of 0x3e1c0000 and this seems to work well for both x86 XP and for x64 XP. Limited to no tests whatsoever were performed outside of XP. Download links: https://www.dropbox.com/s/90of6ljan32ivm6/360ChromePortable_13.5.1030_rebuild_7_regular.zip?dl=1 https://www.dropbox.com/s/k1h2v0s68lt2g7h/360ChromePortable_13.5.1030_rebuild_7_ungoogled.zip?dl=1 Links are down...
NotHereToPlayGames Posted March 13, 2023 Author Posted March 13, 2023 4 hours ago, Cixert said: Links are down... Correct, links are down for rebuild 7 due to space needed for rebuild 8 -- https://msfn.org/board/topic/184515-arcticfoxienotheretoplaygames-360chrome-v1351030-rebuild-8/ I will upload ALL versions one of these days to Internet Archive (including past v11, v12, and v13 builds). Unsure when I will be able to do that. 4
Milkinis Posted March 13, 2023 Posted March 13, 2023 On 2/28/2023 at 1:36 AM, D.Draker said: I has some certain similarities with the chinese Opera GX (gaming edition). I'm not sure though. http://www.yinsiliulanqi.com/XuanWu/VersionList.html
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now