Leaderboard

Hello, just a short update! The writing of documentation has been finished, hopefully (all the flies have suddenly disappeared, very strange! ). I did a lot of tests, performed a few adjustments. Fortunately, no new bugs have been occurred. At the moment I am creating the archive containing all necessary files. Furthermore, some final test have to be performed to finish private testing. And then, very soon, the beta testing can be started. So, stay tuned! Cheers, AstroSkipper

Microsoft Edge worked. However, I have to click several times to start it. The extended kernel is the latest.

Try this. Just replace original files. MUI XP 32-bit Russian.zip

https://docs.microsoft.com/en-us/dotnet/api/system.platformid?view=net-6.0 0 - Windows 3.x 1 - Windows 9x/ME 2 - Windows NT

You might have better luck with the newer versions. It could also be that there was an error installing the driver. VGA 16 colors is the default VGA driver that Windows reverts to, when there is a problem. Since VBEMP supports 32bit color, I would suspect the driver is not compatible or did not install correctly. But even the windows VGA16 driver may be enough to tell if the issues is your ATI driver. Wolf/Sod should still work, even if only 16 colors. Remember, VBEMP and VGA16 is not meant as a fix. Just a test to determine if the ATI driver is the issue. If you get the same blackscreen with VBEMP/VGA16, then you know the ATI driver is likely "NOT" the issue; since the black screen affects all video drivers. Not as far as I know. But I am glad you have sound.

I have pushed the new extended kernel to the usual sites. Now I am working on the next thing and making progress: It is almost done, there are just some issues with BCrypt now, PowerShell 6.0.1 works completely now but that is .NET Core 2.0:

Support for installing Chromium extensions, saving their settings, as well as keeping cookies and other settings has been implemented: The original objective was to fix the "CultureNotSupported"-related exceptions that prevented .NET Core 5 from working, but under the belief that the .NET and Chromium issues were connected, I worked on solving the issue using Chromium. It turns out that .NET's issues are unrelated.