Jump to content

NotHereToPlayGames

Member
  • Posts

    5,011
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. Reminder that Chrome Web Store is intentionally broken in the "ungoogled" version. The best route I have found to return a degree of functionality to Chrome Web Store but to do it without the telemetry/tracker/persistent-cookie is to manually install this extension -- https://www.crx4chrome.com/crx/265228/ Scroll down to the Download Now section and click the Crx4Chrome download link (the other links should work as well, I have only ever used the Crx4Chrome link). Note that the download will download without any "where to save" dialog, it will download to your default directory as set in chrome://settings/downloadSetting. To manually install, drag-and-drop this .crx file onto "empty whtie space" on your chrome://extensions/ page. You should get a dialog asking to confirm installation - click the Add button (then close the self-advert nuisance tab). Now whenever you visit a Chrome Web Store addon page, you can download the .crx directly and manually install as opposed to installing via the Chrome Web Store.
  2. 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
  3. "Regular" build 1030 will maintain "Translate to English" feature. "Ungoogled" build 1030 will have "Translate to English" totally removed/disabled.
  4. That's an oldie-but-goodie little trick. I used to remove Hibernate and Standby on XP x64 systems with more than 4GB RAM because they were "greyed out".
  5. 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.
  6. I was originally aiming for "contiguous". ie, force a "defragged" RAM. Looks like this is not really the best approach. Looks like what is working better (and more universal) is to base to an address BELOW all of the SysWOW64 and WinSxS stuff. But to keep it ABOVE a mouse-gesture app I run on all of my machines (ironically, this mouse-gesture app resides at 0x10000000 - ie, the original default for chrome.dll). Admittedly, it's all been trial-and-error and just keep trying new base addresses. 0x3e1c0000 seems to be working out just great. For x86 and for x64.
  7. 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.
  8. Color me naive, but I was hoping to find the "magic number". I was hoping to find a rebase address that works on all three of my test-case computers.
  9. 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.
  10. Has anyone had any luck with the -e rebase switch? What I would like to do is to UPX chrome.dll (it UPX's from 114 MB to 44.5 MB). But I haven't been able to rebase a UPX'd chrome.dll - it is my assumption that it is this -e switch.
  11. @AstroSkipper - I think you kind of missed one of @UCyborg's main points. There is literally nothing to gain in this community by jumping through your normal hoops to always prove yourself correct and everybody else incorrect. We can all be "equals" even if we all have very different IQ's. Masters learn from their students. Here is my suggestion. Can we post this "issue" on a WiseVector StopX forum and gain some insights from its own user-base? Even without ASLR, a computer can run twenty different programs that all "default" to the same exact base address and all twenty of those programs will run without any BSOD's despite NONE OF THEM being able to land on their "default" base address. There is something else amiss with your computer if you are getting BSOD's. Posting on a WiseVector StopX forum should in the very least IMPROVE the product for future versions.
  12. 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!
  13. What do you have for these options? The "unsafe" URL message tells me you have a third-party being contacted for each and every download!
  14. From the underlying code, the proxy and "mediamanagement" were reindexed somewhere between 1030 and 2022. So were the translation .pak file indexes. That doesn't really answer "why", but it is the differences I see between the two after telemetry was stripped out. I'd probably have to restrip the two in order to spot more differences.
  15. Same here. I plan to upload on a different forum. IF I provide it here at MSFN, it will be under its own build 1030 thread.
  16. That's the direction I am leaning also. One version that should work well for x86 users and for x64 users. I'm pretty sure that ASLR overrides anyway for Vista+.
  17. Same here. But a thousand times more important is that I can access all of my bank account and bill pay web sites with it on XP. NOTHING else exists (yet?) for me to continue to do that on XP.
  18. @mixit - how where you able to isolate the QR Code and Translate to English context menu entries? Was there a specific software debugger you used? I've been able to edit your build 2022 patches to work with build 1030 but I'd like to verify them with the method that you used as a compare/contrast.
  19. I've also been comparing/contrasting libase with ReBase. ReBase has a nice "coffbase" feature that I'm still experimenting with.
  20. I agree. I've actually been using 13.5 build 1030 for the last three days. Still experimenting with rebasing it for my x86 machines. I am undecided as to whether I will upload download links for my newest 13.5 build 1030 here at MSFN.
×
×
  • Create New...