Jump to content

xrayer

Member
  • Posts

    247
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Czech Republic

About xrayer

Contact Methods

  • Website URL
    http://rayer.g6.cz

Profile Information

  • OS
    98SE

Recent Profile Visitors

4,002 profile views

xrayer's Achievements

7

Reputation

  1. >NotHereToPlayGames I had normally some other running apps and bkgnd process e.g. of vmware ~ 45 processes and the rest was chrome.exe of Supermium. E.g. now I have only 6 tabs and there are 12 chrome.exe >hidao I don't like to, I also use some older SW linked with HW that don't run on new Windows. If everything would be ideal compatible I could run Win 10/11 and don't messing on MSFN with some alternate browsers and other XP hacks...
  2. Probably not the fastest for older machines but on my i7 it's OK. I run it heavy memory load with multiple tabs and after it exhausted entire free memory it silently crashed, leaving 4 zombie chrome.exe processes. But it's better than getting win32k.sys BSOD :)
  3. I'm now running Supermium 121.0.6167.81 for a few weeks and it seems work well, even some pages that failed in 360EE 86.x and MyPal68 so still can live with XP
  4. Aha, so it's some minor patches around old chromium core (chrome.dll)? So there are multiple forks based on different chrome.dll developed simultaneously? Or did author decided to revert to older chrome.dll? Why not keep them for download? It seems that MiniBrowser_1.0.0.127 uses the newest chrome.dll available on XP - 87.0.4280.66 but it's something different fork. It's still confusing how many forks there are and which ones are alive and which are abandond...
  5. Another confusion - 360Chrome v13.5 Build 1030 Redux has chrome.dll dated 9.11.2023 but timestamp is much older Time Date Stamp: 0x60CC878C (18.06.2021 12:46:20) and the file size is the same as version 13.5.1030.0 with chrome.dll dated 21.10.2021 that I previously used, Time Date Stamp: 0x60CC878C (18.06.2021 12:46:20) -the same... So anyone has working link to https://www.dropbox.com/s/pi43092cazygjz6/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1 or some other package version listed here?
  6. Sorry I didn't meant official chinese one (I see the installer latest ver. is 13.5.2044) but modified by ArcticFoxie or who else is developing it now, simply by member of MSFN whom I can trust not a random googled fileshare storage.... EDIT: is it this one, the latest? Well chrome.dll pretty recently dated 9.11.2023
  7. Aha, it's your build. Please can you tell me where can I get the latest version of your build? There are multiple threads about 360EE on MSFN, every over 100 pages and with dead links so I'm a bit confused why it's not pinned somewhere on 1st post or I didn't find. I also found some version 13.5.2042 in RAR file that seems to be an installer instead of portable but I didn't trust the source. >NOT RECOMMENDED! One has to be realistic with their expectations when running "Older NT-Family OSes". I think that any application running at CPL3 (not kernel ring 0) should not shoot the OS down by a BSOD. even I don't need open many tabs, sometimes it happens after a while during panning and zooming at mapy.cz If I remember well when I tried overload MyPal68 it just silently crashed after opening too much tabs but didn't BSOD. I got BSOD from Mypal only before I disabled layers.omtp.enabled that came very easily but for about half an year I never got BSOD using MyPal anymore... HW acceleration in 360EE is disabled by default so does it means also similar option to layers.omtp.enabled is not used?
  8. Where can I get this version? I only found 360EE_13.0.2310.0_Modified.7z and MiniBrowser_1.0.0.127_Modified.7z , both have chrome.dll dated 19.3.2023, one is chromium 86.0.4240.198 and other 87.0.4280.66. UPDATE: Link http://360chromeportable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-xp-skin.zip/ is dead UPDATE: I found at least version 360ChromePortable_13.5.2036_r1_regular_MSFN_beta-3xxx by some polish guy dated 31.3.2023. HW acceleration is disabled by default. I tortured it by opening a lot of tabs. When system exhausted over cca 7GB it triggered win32.sys BSOD again..
  9. Yes, this is the version that I actually use (13.5.1030 , exe file dated 360chrome.exe - 15.10.2021 - it's the latest I think?)
  10. Hi, after a bit more extensive usage of ExtremeExplorer360 under WinXP (after some 20+ tabs opened or longer maps panning and zooming) I got this win32k.sys BSOD. I think it maybe the same problem as with MyPal68 where many users complained about the BSOD that came very easily. For MyPal there's an option: layers.omtp.enabled = false that eliminates the BSOD. Is there similar option for EE360/chromium that would solve this issue?
  11. I tested the patch on GTX 970 and Dell 4k LCD and the HDMI pixel clock limit patch works but there's another artifical limitation to max 1600p! It needs to ba patched too... I played with custom modes and timings. The max I can reach is 3840x1600 @89Hz - near 600MHz pixel clock. But Anything over 1600p is immediatelly refused - test mode failed. I need to remove this limit to utilize the native 4k resolution 3840x2160, pixel clock is enough to get 60Hz, maybe a bit more.
  12. Hi, thanks for info about the patch, I've been waiting for this a long time and I believed it could be patched such way, that it's just some stupid constant nvidiot's limitation... Well, from what I read, it seems this patch unlock HDMI output only, not the DisplayPort, well? Did/can someone try this if it will work also for 4k resolution @60Hz? I would like to try this but I have access to 4k monitor only at work and my GTX970 is in home PC and both things are not small enought to take it in a pocket or bag to meet them 😀
  13. Hi, any update about this problem? Can we assume it's rather bios related that new cpu/chipset itself? maybe some incompatability introduced in new uefi csm module? did someone tried biosmod to downgrade specific csm module to isolate the problem?
  14. I think that microcode or AGESA firmware module could change CPU behavior to introduce such bug. Sou you can try extract microcode and AGESA from your older working BIOS and try to insert it in your new BIOS one by one to see if/when it breaks to narrow down the problem. If it will be solved by downgrading one of this module you cannot fix it but at least you could utilize other new features compared to reverting completly to old bios...
  15. Thx for explanation with IDs change. I give not much chance that someone will make a working plugin. With One Core API would be a way. How is it possible to install One Core API beside instead replacing system files? I didn't test last version yet but older one had setup that just installed and replaced system files. I would prefer some opt-in like possible in kernelex to enable API extension only for explicitly configured apps instead for all.
×
×
  • Create New...