Jump to content

NotHereToPlayGames

Member
  • Posts

    6,724
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. Here are some .dll's to try (they of course need renamed to chrome.dll but I know you know that). These are "no-translate" versions of chrome.dll. #6 may be the most revealing - it rebases "away" from the ORIGINAL address only to rebase "back to" the ORIGINAL address. #4 is rebased to the same address as that used in rebuild 7. Please let me know how these do for you and many thanks in advance, this will prove VERY helpful. .7z (236 MB, six different .dll's to try) -- https://www.dropbox.com/s/7augkeqjb00wwkr/chrome-dll.7z?dl=1
  2. Okay, one minute, I'll upload a few chrome.dll test cases. Your situation is perfect as a means to improve the overall product.
  3. Interesting. I see that you are running three instances of 360Chrome and Dr. Watson only triggered on the multiple instances. I do not have Dr. Watson has part of any of my XP installs so about all I can suspect is that this is due to rebuild 8 being rebased at a different address then rebuild 7. Which version are you using (webgl, translation, skin)? I can upload a chrome.dll that is rebased at a different address and see if that solves your Dr. Watson trigger.
  4. I was afraid that might happen. Until I can change all the names, you should be able to right-click and select Save-As and then change the name. Also, save to a directory as close to the root directory as possible, avoid adding too many characters to the path name. I've never liked the default "C:\Documents and Settings\<username>\My Documents\Downloads", already at 60-some characters.
  5. Your chrome.dll file needs "rebased". If you upload your chrome.dll and provide a link to that upload, I will "rebase" it for you and send it back to you.
  6. No. There is an intermittent "flash" where the default LIGHT background is presented and then "quickly changed" to dark. It doesn't change "fast enough" and I will never associate my name with that "flash" - it induces migraines and seizures to some folks.
  7. You are bumping it constantly. So be warned, you can be banned from MSFN for doing this kind of IMPATIENT bumping of your topics.
  8. I direct you to Forum Rule 2.a. 2.a Use some common sense. Do not create identical topics or make identical posts in more than one forum. Think before posting and choose the right topic for your question or answer. Do not "bump" newly created topics until at least 24 hours have passed. If a topic has been "bumped" three times without any new replies, please consider reviewing and editing your original post and adding any information which you think may help other members in answering your question(s) or concern(s). When posting, have something to say, not just "My First post!" or "Cool site!!!" We sort of have the idea by now. :-)
  9. I direct you to Forum Rule 2.a. 2.a Use some common sense. Do not create identical topics or make identical posts in more than one forum. Think before posting and choose the right topic for your question or answer. Do not "bump" newly created topics until at least 24 hours have passed. If a topic has been "bumped" three times without any new replies, please consider reviewing and editing your original post and adding any information which you think may help other members in answering your question(s) or concern(s). When posting, have something to say, not just "My First post!" or "Cool site!!!" We sort of have the idea by now. :-)
  10. Note - there is a known issue if you run this browser with a very long sub-folder file name. Please rename the downloaded file upon download, the names here are only to distinguish their differences. This thread is devoted primarily to WinXP and a Chromium fork based on Chromium v86. Any discussions regarding v86 and its "age" will be reported to the mods as "disrespect" and in direct violation of Forum Rule 7.b. 7.b This community is built upon mutual respect. You are not allowed to flame other members. People who do not respect personal opinions and/or personal work will be warned in first instance. If you ignore the warning and keep on flaming, you will be banned without notice. This project is my personal work that I share with MSFN because there is a need for a "relatively modern" web browser for use in WinXP and v86 has performed "reasonably well" in that regard. The user-base is perfectly aware that XP will not serve 100% of our needs, that v86 will not serve 100% of our needs, we know this and accept this, we are not here to be told to "move on" from XP and what works for us in XP. We The Community can respect this endeavor in the same manner that we respect content shared at MSFN threads devoted to Win98 and Win2000 without trolling such threads and citing "age". Many thanks to all that continue to support this personal work. There is a combination of several versions to choose from. Regular versus Ungoogled -- ungoogled intentionally breaks telemetry sent to the Chrome Web Store, this in turn breaks the "Add to Chrome" feature at the Chrome Web Store so extensions need added via other means. WebGL enabled/disabled -- WebGL may or may not work on older hardware, so mileage may vary. Translation enabled/disabled -- Chromium-based browsers have an embedded Google Translate context menu feature, I offer versions with and without this embedded feature. WinXP / Win10 skin -- I only use this browser in WinXP and therefore I prefer it to look-and-feel like everything else I run in WinXP. Others prefer the more "modern" Chrome GUI and the Win10 skin attempts to please that crowd. https://www.dropbox.com/s/wsch5owpc8yv184/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/fl9ureunhg2k2x7/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/whki7vldp655nx1/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/59561mewhx0ufzb/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/l3e5m48tzzb30bj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/npnxobadg89m7uj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/ithrm1ttt2nypb1/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/f2935ei6q5d0w3u/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/i9t2rul2t5g99ml/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/wqm2tzaum2088ph/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/wqzujgi97cyuf7u/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/tbt5g1pv9nazfo4/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/g4g0jdgogoexa3p/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/bcsexi8cm5tw2np/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/yz8usl2hgsbxtk0/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/pi43092cazygjz6/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1
  11. You will not win any friends here at MSFN by posting similar topics in multiple threads. You've only joined MSFN approx 7hrs ago and all three of your posts are this one issue. It's a general rule-of-thumb to WAIT at least 24hrs (if not THREE DAYS minimum!) before BUMPING your own threads because nobody has answered yet.
  12. You will not win any friends here at MSFN by posting similar topics in multiple threads. You've only joined MSFN approx 7hrs ago and all three of your posts are this one issue. It's a general rule-of-thumb to WAIT at least 24hrs (if not THREE DAYS minimum!) before BUMPING your own threads because nobody has answered yet.
  13. 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.
  14. I will upload a "rebuild_8" of my version that has WebGL ENABLED out-of-the-box. But you will have to PICK ONE OR THE OTHER, it is not advisable to run MY version and Humming Owl's versions side-by-side! Humming Owl's versions SAVE data to the Windows Registry permanently. Mine only uses the Windows Registry for temporary data storage - but it will "see" the PERMANENT data stored by Humming Owl's versions. Again, PICK ONE OR THE OTHER, it is not advisable to run both side-by-side - not even if one has been "exited" before the other is launched - Humming Owl's registry writes are PERMANENT. I will have a "rebuild_8" new thread later this weekend or so.
  15. 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".
  16. 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.
  17. Will depend on your graphics card. I do not need to change any flags to enable WebGL on any of my computers, I only need to not disable via the loader.ini.
  18. 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).
  19. Then your Windows Registry has been polluted with 360Chrome entries that should not be there. Step 1 - CLOSE 360Chrome Step 2 - verify in Task Manager that 360Chrome is NOT RUNNING Step 3 - launch regedit - 360Chrome must NOT BE RUNNING Step 4 - go to this section of your Windows Registry Step 5 - if you have any 360 or 360chrome keys between Software and where I have 7-Zip, DELETE THEM and REBOOT THE COMPUTER Step 6 - delete the entire 360Chrome folder, PROFILE AND ALL, and extract a brand new folder
  20. Neither one of those screencaps is my browser. If you are going to mix-and-match skin files, then you have to face the consequences of not using my browser "as-is". I suggest deleting EVERYTHING and starting all over again with a fresh download then run it "as-is".
×
×
  • Create New...