-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome 101 Windows XP 32 Bit #57
Comments
Chrome 100 doesn't work for me. If I run it without setting executable to Vista SP2 compatibility mode and no --no-sandbox parameter set on the shortcut, it gives this error. |
I know of a way to install latest Chrome on XP. If there's demand, I can tell instructions on how to install newer Chrome versions on XP. |
please tell |
Ok, so people are asking me for my instructions. Here it is. |
Not Working |
You really can skip all of this by just getting A: portable chrome also up to Chromium 75 works on XP x64 (NT 5.2) EDIT: I should note some sites just dont work like youtube. This isn't a stable way to use modern chromium |
Ungoogled Chromium (what i use): https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/windows/32bit/ Standard Chromium (make sure to go for "stable" builds of chromium btw): https://chromium.cypress.io/win/ |
Well, I don't prefer Chrome in portable, but in an installation, so I discovered that way instead. Of course I am aware of the fact that --no-sandbox is required. |
you can always just move the chromium portable/files you downloaded to a folder in your C: drive (or really anywhere) and make a shortcut on the desktop |
Yes, I know, but I prefer an installation over a portable/zip file. |
Hey, i see on my Windows XP installation and oleacc.dll has this function. The version of file is 7.0.2600.6153. Maybe on your installation has a previous before these version. I will add oleacc.dll from my installation to prevent this error. |
Hot to fix it? |
In my testing on latest updates i could only get Chromium 85 working on NT 5.1 and it was unstable. |
It was just fixed on next release, will be launch today. Be Patient. |
Please, check the version of your oleacc.dll |
My installation is a clean one with no updates. |
@Skulltrail192 Ok, so I tried it with OCAPI version 2.4.0, and the issue of oleacc.dll is still happening. I even tried to replace it manually, but it still stays with version 4.2.5406.0. This was tested with Chrome 102. oleacc.dll file version before OCAPI installation: oleacc.dll file version after OCAPI installation: Is the latest Chrome version working for anyone? |
@mina354 |
How sad. |
@mina354 But new Advanced Chrome only 94.0.4590.0 |
For version 51~69, you must set compatibility to Windows Vista SP2, add parameter to shortcut "--no-sandbox". And all version above, you only need add the paremeter "--no-sandbox". The problem with oleacc is solved on version 2.5.0 |
@Skulltrail192 But there's a problem, downloading files using newest Chrome version, gives a "Failed - Download error" error. I can't also install extensions. |
@Skulltrail192 In my browser there is no sound at all. On chrome, chromium and brave there is no sound at all, I tried with --wave-audio and then without it and no difference. How to fix it? |
Well, need a little fix: the correct parameter is: "--force-wave-audio" |
Chrome still has instability and crash randomless, it need some investigation. On Server 2003 and XP x64 now has some compatbility, run chrome at last version (tested 105 version) |
@Skulltrail192 Also not working audio in chrome |
What about these? My network connection is working fine, so the download error appears even if my network connection is fine. |
@Skulltrail192 Just updated to Chrome 103 (released today), and Chrome immediately closes upon launching it. |
How i said on release notes, Chrome has instability both XP/Server 2003, need investigaton. |
What version used? |
Got it.
102, the last version that lets me download files is 74. Extensions don't install on any newer Chrome version though. |
Thanks man, i will analyze differences between these 74 and 75 versions. |
Hello, i made a mistake. The correct parameter to get audio working on Chrome is: --enable-exclusive-audio |
Oops. |
Chrome 94 can't Download |
For now, no. |
Alright. |
This seems to be an issue where Chromium cannot get write access to the temp folders, according to Chromium source. If you want Chromium to work perfectly on Windows XP (i.e. install extensions, be able to access its own cookies, etc), one of the things you will have to do is enhance FindFirstFileExW so it accepts the new flags and enums that Windows 7 added for it. You can find an example in my API repository. |
Hey friend, i will test. We can talk by email, skype or other way? |
Yes, try e-mailing me at [email protected] (it is a terrible provider anyway, that inbox is clogged up with lots of local spam anyway so I don't care if harvesters get at that one). |
First of all, congratulations and a big thank to Skulltrail192 for the progress in making newer Chrome versions work in XP! I use XP SP2 and I tried to start Chrome v102 and v90 without installing One-Core-Api. Here's what i did... To my pleasant surprise, with proper command line options and the proper compatibility setting, I started Chrome successfully. But there's just one "little" problem - Chrome cannot load any web page! I get the following error message: "This site can’t be reached ... ERR_NAME_NOT_RESOLVED" I tried everything that came to my mind but nothing helped. Does anybody have any idea...? |
Are you updated Root Certifcates? To navigate with Chrome, you must use the tool on this repository to update Root Certificates. |
Thanks, certificates were updated, anyway I finally solved the problem. (Although I have some issue with security it can be avoided by using option "--ignore-certificate-errors".) I was inspecting Chrome's Internet and networking API calls with API Monitor (rohitab.com) and found out that function getaddrinfo from Ws2_32.dll returns error code WSANOTINITIALISED, and that WSASocketW returns INVALID_SOCKET while trying to load a website, most likely because Ws2_32.dll is not properly initiated by Chrome. With Ollydbg I found a call to WSAStartup in Chrome.dll which looks related to this and I managed to read out the function's return value, it was 10107 what means WSASYSCALLFAILURE, an untypical error which didn't mean much to me. Fortunately, the solution was very simple. Instead of a redirection to another Ws2_32.dll this DLL should be loaded with the system. I had to remove lines for redirection to Ws2_32.dll and Ws2_base.dll in Chrome's folder from my Chrome.exe.manifest, and to move these DLLs to Windows\System32. Just to mention for those ones who are interested, to make wrapper Ws2_32.dll work you should also put unmodified Kernelbase.dll, Ntext.dll and Normaliz.dll from O-C-A in Windows\System32. Interestingly, with App Compat files from the newest O-C-A v2.9.0 I have to set compatibility mode for Chrome.exe to XP SP2 instead of Vista SP2. Chrome 102 is still not usable for me, webpages crash constantly, they cannot be saved, no download is possible, but it looks like the things move in the right direction :) |
Well, maybe ws2_32 is related with steam and discord problem? |
On 32 bit XP, latest version of Chromium fails to even launch...let alone install. |
|
Fixed main issue and chrome 103-109 is working on XP. See chrome main thread: #178 |
Hey. I installed the latest One Core Api on Windows XP Professional SP3 x86 - Integral Edition 2021.12.19 (Vanilla).iso and trying to fire up Chroma but I have this problem.
The text was updated successfully, but these errors were encountered: