Jump to content

yoltboy01

Member
  • Posts

    283
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by yoltboy01

  1. 8 minutes ago, Dixel said:

    I already predicted it would have happened (link), I'm not surprised, even though folks wrote their chrome still worked on the old Win 10 at that time.

    So looks like now 1809 is the new bare minimum, link. And like I said before. the whole memory function would have to be replaced to be able to run on such old versions, link.

    This would explain the delays with the Chinese forks of Chrome for Win 7. Each new release will be harder and harder to port, so build from scratch is the only method left.

    As you all see, I could be the new clairvoyant, in addition to @D.Draker, I think I don't even have to mention, @jaclaz's half-functional (maintenance mode?) crystal ball is already mine.

    Yeah, I agree with you. There are plenty of Windows 10 releases and even driver manufactors like Intel always increase their minimum system requirement to the latest 2 or 3 versions of Windows 10. My i5 8250U was released in 2017 and couldn't run anything below 1703 as far as I remember (with modified drivers only). I am also curious if the upcming Intel 14th Gen processors will even offer Windows 10 support anymore, since 13th Gen was already 21H2 and up only. We also have company based apps that get revised annualy and always increase their system requirements between Windows 10 versions. 

    Edit: I tested Chromium 118 on 1607 and it works well. They implemented a function that was introduced with Server 2016/14393

  2. I also tested Opera 102 (based on Chromium 116) and it also works on Windows 8.1 (will share a screenshot later).

    What I don't quite understand is how Opera, a Chromium based browser, can still work on W8, when the source Chromium browser doesn't even start up anymore. Same goes for Chrome and Edge btw. I'm not complaining tho, I am just curious.

  3. 12 hours ago, Dixel said:

    Basically, yes. 116 beta requires Windows 10

    116 works on Windows 7

    117 alpha builds works up to 2023-07-18

    118 does not work

     

    I'm testing new nightly builds on 8.1 every day and it still seems to work. Let's see for how long. Would be nice to get another ESR working on 8.1. This would indicate that support would extend for another year.

  4. Google has just released Drive v79 and it seems to be the last supported version available for Windows 8.1. They have stated this in their release notes (support.google.com/a/answer/7577057?hl=en). It's chromium underlayer is still based on Chromium 105. I think they will update the Chromium framework to v115 with the next update. 

    Nonetheless, it will be worth trying to backport newer versions to 8.1, since newer Chromium versions technically work on W8.

  5. 1 hour ago, Tripredacus said:

    Did you ever think that maybe people at Microsoft know all about how people have been exploiting update compatibility in order to continue to use OS versions that Microsoft doesn't want you to use anymore? That would be my guess.

    Nah they ain't that smart I guess. They're known for doing senseless decisions from time to time.

  6. Browser News:

    Despite the fact that Chrome/Chromium 115 as well as Edge are not working on Windows 8.1 anymore, I tried out other Chromium based browsers and landed at Opera. Opera ended their support for Windows 7 and 8.1 in January 2023 (March actually) with v95 based on Chromium 109. I tried out the latest version (101 based on Chromium 115) and it works without any issues. You need to apply some changes with CFF Explorer, however it does not crash like Chrome 115. Newer versions might work as well, but no guarantee obviously. 

     

    Opera 101 (Chromium 115) on Windows 8.1: imgur.com/a/hFe2ooy

  7. Maybe it's a little off-topic now but I just realized something strange.

    Server 2008 is based on Vista (both 6.0.6000)

    Server 2012 is based on Win8 (6.2.9200)

    Server 2016 is based on Win10 Anniversary (10.0.14393)

    Windows Server 2022, which was released in August 2021, right before Windows 11, looks like Windows 10 but it's build number is 10.0.20348. It's actually a higher build number than Windows 10's (19045) and it has Windows 11's icons (e.g. Settings, Security). What was Microsoft thinking when they were building that version? It's updates are NOT compatible with Windows 10, meaning that one can not just install Server 2022's Updates on Windows 10, once 10's support runs out. I remember there were new Windows 10 builds in 2021 and it is probably based on one of them.

  8. 23 hours ago, Dixel said:

    Why, really?

    DiscardVirtualMemory  is supported Windows 8.1 [desktop apps | UWP apps]

    https://learn.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-discardvirtualmemory

    It is indeed, however it does not work on 8.1, showing the error DiscardVirtualMemory could not be located (since v112). There might be some things missing or Windows 10`s one is extended. Supermium und other Chromium forks also changed DiscardVirtualMemory to VirtualAlloc. Thats's not even all. You need a newer version of DWrite from Windows 10+ and obviously add --no-sandbox. That combo worked from 112-114, but 115 will not open up anymore. It just crashes, without any error shown

  9. 7 hours ago, Dixel said:

    I'm afraid not, because it would require backporting the whole shared memory API from Windows 10 build 1809 to windows 8.1. Better/easier/legally safer to build chromium from scratch (source), which is open, so anyone can try.

    Thanks for your reply.

    Do you/or anyone know what changed between Chromium 114 and 115 that the browser does not work anymore on Windows 8.1? Starting with 115 it instantly crashes, whereas 114 would work perfectly fine without any glitches. I changed DiscardVirtualMemory to VirtualAlloc but still. No luck.

  10. On 7/15/2023 at 9:48 PM, adi2137px said:

    supermium is already based on 117, works very good on 7 so ofc it will work on 8.1

    Could the original Chromium Browser also made compatible with 7/8.1 again by applying the same changes the Supermium Team did? Like those changes in Chromium.dll for example

  11. So, new news:

    - Microsoft 365 (formerly Office 365) v2308 works on Windows 8.1. Support had ended with v2301, roughly half a year ago (link below)

    - Firefox 117 (latest Alpha) works flawlessly on Windows 8.1 (7 as well)

    - Chrome 114 works, but 115 crashes for me (there are forks like Supermium or CatsXP that are based on 115 but I haven't tested them, so I cannot recommend them)

     

    I am kind of surprised that Microsoft didn't implement functions that would break compatibility with Windows 8.1 yet. They probably don't care. Windows 7's

    compatibility was broken after v2002 as far as I remember. 

     

    imgur.com/a/FvieLQC

  12. 8 hours ago, WalksInSilence said:

    I've taken the precaution of downloading various older portable versions of FF.

    I'm not minded to update beyond my current installed version TBH, even the ESR option. I know and have been dealing with or just accepting my preferred FF version having problems on some web sites particularly those which actively prevent you using "unsupported" browser versions and try to persuade you to 'upgrade'.

    What is the situation in regard to Win7 and the Mozilla Thunderbird email client which shares features with FF? I've not read anything about that. 

    I also liked the aesthetic of Firefox in v57-88 very much. Sadly, 78 ESR isn't supported anymore, so I always try to keep up with latest version. Right now all versions, including the betas and nightlies work fine on 7/8.1

  13. 3 hours ago, Old Technology said:

    Have you tried changing the user agent or using a bypass?

    No, I haven't tried that out yet. 

    I also wanted to point out that the latest Nightly Installer no longer works on Windows 7/8.1. You get the same message like when you tried installing newer Firefox versions on XP/Vista. If you copy the latest Nightly from a Windows 10+ machine, it will still work. There are no implemented software restrictions (yet)

  14. New News regarding Firefox:

    - If you are on Win7/8.1 you can't download the Beta/Nightly installer anymore. If you visit the installers website there will be a notice, something similar to "Firefox is only supported on Win versions above 8.1". If you still press at download v115 Stable Offline installer will be downloaded instead

    - The Beta/Nightly installers aren't blocked, they still download the latest version (117a1)

    - 115 Beta release notes weren't mentioning the EOL of 7/8.1 - the stable version now does 

×
×
  • Create New...