yoltboy01
Content Type
Profiles
Forums
Events
Posts posted by yoltboy01
-
-
14 hours ago, ceo54 said:
Many thanks for the support @Dixel but this library caused another issue. When I launch Opera, it won't come up and crashpad debug log says not a valid win32 app. I downloaded api-ms-win-core-localization-obsolete-l1-2-0.dll and renamed it to api-ms-win-core-localization-l1-2-2.dll and now it seems to be working. Haven't tested youtube/download/upload or MB pages yet but will test and report back.
Many thanks to @yoltboy01 @Dixel @mjd79 & @UCyborg for the kind help. You guys rock.
Edit: Everything seems to be working normally, except for the scrollbars. When I move the scrollbars to move page up/down, browser gets resized instead.
Your welcome. I hope that the compatibility for Firefox and Opera will be up for a good amount of time on 8(.1) without the need of an Extended Kernel.
Firefox 121 is the sixth post-EOL version and Opera 106 (Chromium 119) the eleventh to work on Windows 8.1 with the methods stated above.
0 -
10 hours ago, UCyborg said:
Just replacing "DiscardVirtualMemory" with "VirtualAlloc" in opera_browser.dll (or equivalent in other browser ) doesn't make much sense, they're different functions and have different number of parameters, leaving VirtualAlloc to be called in place of DiscardVirtualMemory corrupts the stack after function returns, plus it'll receive some other values in the stack in place of its 3rd and 4th parameter, so it can't know what it should do exactly. When I got 32-bit Opera 104.0.4944.33 running with just that string replaced, it didn't take long for the tab that opened on first launch to crash.
Chromium uses DiscardVirtualMemory in its memory manager, it's a faster way to do one specific operation that could be done with VirtualAlloc with MEM_RESET flag pre-Win10. There is still fallback to VirtualAlloc in place, so easiest way to get it going correctly is to simply skip the code that would call DiscardVirtualMemory. I think they used to check if function exists before dropping pre-Win10 OS, might have to check older revisions to be sure. Obviously, we still have to replace the string "DiscardVirtualMemory" in the import table so the loader is happy when it loads the DLL.
Here's the full patch that can be applied with x32dbg (included with x64dbg), this is only for opera_browser.dll of 32-bit Opera 104.0.4944.33, started with this one as I'm more at home with x86 code. The text file usually has *.1337 extension. I was working with a very recent version of x32dbg, it's compatible with Windows 8.1.
>opera_browser.dll 000000D0:89->EA 000000D1:E9->78 000000D2:E4->E5 032BD3CB:57->EB 032BD3CC:56->11 032BD3CD:E8->CC 032BD3CE:24->CC 032BD3CF:79->CC 032BD3D0:2D->CC 032BD3D1:06->CC 032BD3D2:85->CC 032BD3D3:C0->CC 032BD3D4:75->CC 032BD3D5:08->CC 0448C04F:53->8B 0448C050:8B->7C 0448C051:7C->24 0448C052:24->04 0448C053:08->E9 0448C054:57->80 0448C055:E8->00 0448C056:9C->00 0448C057:8C->00 0448C058:10->CC 0448C059:05->CC 0448C05A:85->CC 0448C05B:C0->CC 0448C05C:75->CC 0448C05D:7A->CC 0448C05E:8B->CC 0448C05F:54->CC 0448C060:24->CC 0448C061:08->CC 0448C062:8B->CC 0448C063:5C->CC 0448C064:24->CC 0448C065:0C->CC 0448C066:8B->CC 0448C067:7C->CC 0448C068:24->CC 0448C069:10->CC 0448C06A:E9->CC 0448C06B:E5->CC 0448C06C:FE->CC 0448C06D:FF->CC 0448C06E:FF->CC 0448C0C2:56->8B 0448C0C3:8B->7C 0448C0C4:7C->24 0448C0C5:24->0C 0448C0C6:10->EB 0448C0C7:57->38 0448C0C8:E8->CC 0448C0C9:29->CC 0448C0CA:8C->CC 0448C0CB:10->CC 0448C0CC:05->CC 0448C0CD:85->CC 0448C0CE:C0->CC 0448C0CF:75->CC 0448C0D0:2F->CC 0798707E:53->EB 0798707F:57->09 07987080:E8->CC 07987081:71->CC 07987082:DC->CC 07987083:C0->CC 07987084:01->CC 07987085:85->CC 07987086:C0->CC 07987087:74->CC 07987088:2F->CC 0A7FCF04:44->56 0A7FCF06:73->72 0A7FCF07:63->74 0A7FCF08:61->75 0A7FCF09:72->61 0A7FCF0A:64->6C 0A7FCF0B:56->41 0A7FCF0C:69->6C 0A7FCF0D:72->6C 0A7FCF0E:74->6F 0A7FCF0F:75->63 0A7FCF10:61->00 0A7FCF11:6C->00 0A7FCF12:4D->00 0A7FCF13:65->00 0A7FCF14:6D->00 0A7FCF15:6F->00 0A7FCF16:72->00 0A7FCF17:79->00
When importing it into x32dbg, say yes to both prompts that appear. You have to at least open opera_browser.dll before and "launch" it before you can right-click->Patches (or CTRL+P)->Import, then Patch File to save the patched copy on the disk. I like things to look clean so it's not the most minimalistic...back in the day I went out of my way to leave no empty gaps, now that makes it super annoying for someone who would want to compare changes afterwards!
About "api-ms-win-core-localization-l1-2-2.dll" error, you don't get it if you actually use DWrite.dll from Windows 10 Build 9926, but with many newer versions, they're linked to "api-ms-win-core-localization-l1-2-2.dll" rather than "api-ms-win-core-localization-obsolete-l1-2-0.dll". The latter is supplied with Windows 8.1. Still, I used DWrite.dll from my daily driver Win10 installation, so I just created a hard link of system "api-ms-win-core-localization-obsolete-l1-2-0.dll" named as "api-ms-win-core-localization-l1-2-2.dll" to satisfy DWrite.dll's dependencies without having to modify DWrite.dll, as some have apparently done in the past. Dixel's suggestion about "api-ms-win-core-localization-l1-2-0.dll" is redundant, the one supplied with Windows 8.1 already satisfies the other dependencies of newer DWrite.dll, related to localization APIs and most importantly, doesn't contain any API that "obsolete" version does.
To put it simple, there's just one lone function that was exported through "api-ms-win-core-localization-obsolete-l1-2-0.dll" at one point on Windows 8.1 and early Windows 10 builds, but got moved to "api-ms-win-core-localization-l1-2-2.dll", so that's what newer DWrite.dll references. Today's Windows 10 and 11 no longer use stub DLLs, it's all handled internally by the loader, so even when there's no actual DLL referenced (despite being called DLL), the special name with the help of the logic in the loader makes a link to real DLL where particular function implemented. Just read the bloody docs...those who actually want to learn something.
It still has to be run without sandbox, which I hear is pretty much Win10 exclusive in its current form.
Do you know a way in how to make Chrome 115+ working on Windows 8.1?
0 -
16 hours ago, ceo54 said:
Thanks. Yeah, my system is updated till September 2023 (only October updates are not installed)
Okay I tried the steps as shown in the video for Opera but unfortunately the result is the same. When I copy DWrite.dll and launch Opera, it complains about missing api-ms-win-core-localization-l1-2-2.dll
I think this is some kinda runtime library so I installed all C++ runtimes, 2005-2022 to no avail. I already have .Net 3.5 and 4.8 so I'm out of ideas.
Also, it's kinda weird to be not able to find a Windows .dll online. I looked everywhere but couldn't find this api-ms-win-core-localization-l1-2-2.dll
Nonetheless, thank you for the help, Your support is highly appreciated.
Nonethe
2 hours ago, Saxon said:Putting doubts in the fact @yoltboy01runs Opera on 8.1?
That's very strange.
I am running Windows 8.1 x64 (!) in a VM but that ISO is fully updated till January 2023 (!). No mods, no tweaks what so ever. Sometimes, I even delete that VM and create a new one once a month. I install CFF Explorer, 7 Zip and use DWrite.dll (from Windows 10 Build 9926) (!).
The tutorial shown in the linked video above is my video. Please don't forget to make a shortcut of opera.exe on the desktop and NOT launch it in it's folder because of --no-sandbox
I am currently writing this in my VM, running Opera dev 105 (based on Chromium 119)
0 -
Happy to see that Firefox 121 (Nightly) works on Windows 8.1 (with obvious mods)
imgur.com/a/0C8xyG5
1 -
2 hours ago, ceo54 said:
Thank you from the core of my heart for helping me out here. I'm sorry but I did as instructed and when I launched Opera from the shortcut with --no-sandbox flag enabled, it complained about missing api-ms-win-core-localization-l1-2-2.dll I looked around on the dll sites but couldn't find this library.
Any other ideas ?
No matter what becomes of it, I'm truly grateful to you.
Watch this.Furthermore, is your Win8.1 PC fully updated?
1 -
2 hours ago, ceo54 said:
Yeah, I understand it needs to be modded and accompanied with some libraries from Windows 10 but I'm no techy and I can't do it on my own, I need help.
I can explain it briefly:
- Download a portable version of Opera/Opera GX (or an offline installer)
- Download CFF Explorer, DWrite.dll (from Windows 10+) and 7zip
- Extract Opera and put that DWrite.dll in the folder where the browser is located
- Right click opera.dll (it‘s around 200 MB) and open it in CFF Explorer
- Go to Import Directory -> Kernel32 -> Scroll down to DiscardVirtualMemory
- Change DiscardVirtualMemory to VirtualAlloc and save it
- Go back to the folder where Opera is located -> Right click opera.exe -> Create a shortcut on the Desktop
- Go to the Desktop
- Right click the newly created shortcut -> Properties
- On the General Tab write —no-sandbox next to the location and save it
Opera should now work and open
2 -
2 hours ago, Dixel said:
@yoltboy01 is a talented modder, what works for him, doesn't necessarily means will work for others.
From what I read, the last rather simply modded and fully working Opera for ordinary people - was Opera 97 (Chrome 111).
Dixel got me smiling
13 hours ago, ceo54 said:Latest Opera working for everyone except me :crying:
As he also stated, I modded it to work on 8.1 (which is the only option you have if you want to use the latest version on that OS). Firefox also needs to be modded but doesn't need any extension from Windows 10+ to work on Windows 8.1. The Browser is technically still compatible with Win8, you just need to lower the system requirements manually to say it simply.
1 -
I just noticed two changes in Windows 10 since the October Update (Release Preview Chanel)
- Apps are now classified as System Apps if they cannot be uninstalled like Settings or Tips in the Start Menu (Ported from Windows 11?)
- The Game Icon has changed in Settings (previously the XBox Logo - now a Joystick)
imgur.com/a/SNpw0um
0 -
On 10/16/2023 at 11:41 PM, yoltboy01 said:
Well, speaking of Modded Software for Windows 8.1, Opera 104 beta (based on Chromium 118) does no longer work.
It shows an error linked to the VirtualAlloc Function. It requires the CreateEnclave function introduced in Windows 10
I have to apologize for that statement. Actually, 104 works too. I had a RTM Build of 8.1, which needed to be updated fully first
1 -
Well, speaking of Modded Software for Windows 8.1, Opera 104 beta (based on Chromium 118) does no longer work.
It shows an error linked to the VirtualAlloc Function. It requires the CreateEnclave function introduced in Windows 10
0 -
On 10/5/2023 at 6:13 PM, Cocodile said:
I guess it's not, but it would be wise not to mix all in one, to avoid creating confusions, agree?
On 10/5/2023 at 8:49 PM, Dixel said:From a purely technical persperctive (so no offence), the app doesn't work as intended,
you simply switched off the most important security feature.
The last Opera-Chrome for Win7,8,8.1 are still based on Chrome 109, it will change if you fix the sandbox and make it fully working. like someone did in CatsXP.
I didn‘t mean to offend anyone/anything . My bad I guess? Sorry.
2 -
2 hours ago, Cocodile said:
It's still a mod, for which you would need to edit Opera's/chrome's files.
Respectfully, the topic is about the last versions without mods, no?
Yes, it is a mod indeed. However, Win8(.1) is capable of running that software unlike Windows 7, for which you would need an extended kernel.
Call it simple modding if you like, but all I did was to edit opera.dll and put that —no-sandbox behind it. When it comes to Firefox you also need to mod the firefox.exe and Office also needs a patch.
Since when is this post limited to official EOL‘s?
0 -
Quick October Update
- Opera 103, now released and based on Chromium 117, unsurprisingly works on Windows 8.1 with --no-sandbox and VirtualAlloc
- Latest Firefox Nightly (04-10) works
- Microsoft Office 365 v2311 (beta) works
0 -
When it comes down to speed Windows 8(.0) was very underrated. I also installed it on an old Netbook (Mini 1012) and it was the only OS that ran fluently. Windows 7 and 10 couldn't compare (11 obviously not)
4 -
So, not even released for 10 minutes and I already tested Firefox 120 on Windows 8.1. Works good so far. This is the fifth post-EOL version of Firefox to work on Win8.1
imgur.com/a/IFCyHIA
0 -
14 hours ago, broken120x120 said:
Edit: How far can Windows 8.1 go?
Currently, Windows 8.1 can run the latest version (119). Since 120 Nightly will be released tomorrow, I think it will run as well. It‘s going to be the fifth post-EOL version to run on 8.1
1 -
Opera 103 - based on Chromium 117 - works on Windows 8.1. I just tested the beta.
0 -
Google Drive v81 works on Windows 8.1
Support ended two months ago with v79. They haven't upgraded their embedded Chromium framework since v105. Support will probably be up till they move to 115+
0 -
1 hour ago, Cocodile said:
I tried Supermium, finally, well it's quite good, but not portable and writes BrowserMetrics info collecting. Open it with Hex, you will see.
You know what, you're right! I'll stick to the ported Opera 97 and Ungoogled 111, apply the anti webp-crap patch to decrapify them, certainly.
If you use Opera, don't forget to apply the patch against collecting info-spying, made by @D.Draker.
Are you using Windows 7? If you use Windows 8.1 go for Opera 102 (Chromium 117). Works great
0 -
So, Supermium v118 just got launched. Works great on Windows 8.1
0 -
13 hours ago, Cocodile said:
And what about Supremium? Did you try it? It's on latest Chrome build, did you like it? It claims to work on 8.1.
I used it for a brief time. Didn‘t they drop two releases? One based on Chromium 115 and the other on 117?
I don‘t know if it differs a lot from Chromium, except for the name.
Supermium is build from scratch, by independent developers. It‘s downside is that you never know if they plan to update the browser or not. They don‘t offer daily/weekly/monthly builds. If they continue with their pattern like they did before then Chromium 119 should be the next backported build. I wouldn’t bet my money tho.
If I want to use a Chromium based browser, I stick to Chrome 109 (till the end of the year) or use Opera, based on the latest Chromium, with some modifications
0 -
23 hours ago, Cocodile said:
I rather afraid of this. And I trust @Mr.Scienceman2000 and @Dixel. Not saying I don't trust you, perhaps you just missed the facts.
Yeah I won't lie, I missed that post. Regardless of Firefox itself, other Gecko based browsers like Waterfox, which claims to be more privacy focused with no telemetry, might work on 8.1 for a longer time as well. You can obviously choose to use the browser you want. All I ment is that Firefox (-based browers) will be safer than Chrome after October, as Mozilla has extended 7/8 support till late 2024. Currently, it is harder to find/build a Chromium browser, based on the latest version, than to modify Firefox to work on 8.1
1 -
4 hours ago, BW134 said:
That's surprising, in fact the site for Catsxp still claims it's supported for Win7+.
Is Opera Developer and Opera GX working on Windows 8.x with the same method as main Opera?
To clarify a few things: I haven't tested anything on Windows 7, only on 8.1, and from what I know the latest Opera (tested yesterday) works fine on Windows 8.1. As I had already discussed with @D.Draker Opera is probably just lagging behind in adjusting changes to the browser. In this particular case it's good for us, as we can use a browser, which is based on the latest Chrome right now.
Chrome and Chromium themselves do not work on Windows 8.1 anymore since the release of v115. The last version of Google Chrome to work on Windows 8.1 was 114. Chromium based alternatives are: Supermium, CatsXP, Vivaldi and Opera (there might be others too but I tested these). Supermium isn't updated as frequently as the others are but is the closest to resemble the Chromium browser optically.
I would recommend any active 8.1 user to switch to Firefox instead, as long as they don't break compatibility with 8.1. Even Windows Vista ran Firefox 115 ESR, although it ended with 52. I am optimistic to say the least but I wouldn't bet my money on Mozilla not adding any dll or function from Windows 10+ that will eventually break 8.1 support anytime soon. Best scenario would be if 8.1 made it till the release of the next ESR. That would at least guarentee another year of promised security updates. However, the next ESR will be v128 and that version is set to release in May-July 2024. Support could crack wayy earlier. If that happens, use 115 ESR instead.
2 -
On 9/7/2023 at 12:04 PM, Cockatiel said:
7. Copy this dll file to Firefox folder
That dll is needed for what? Never used it and Firefox 119 works on 8.1
1
Official - Windows 10 Worst Crap Ever!
in Windows 10
Posted
So, Windows Copilot is coming to Windows 10 as well? Just read some news about the development (just type Windows 10 News in any search machine). Furthermore, MS could and I also believe extend the support of W10