UCyborg

The problem is that apparently nobody understands how this all works internally to be able to come up with good solution. I recently asked about it here.

That's because it doesn't do anything impressive, it just makes Firefox unaware of the fact that it's running on Windows 10. And since dark mode is Windows 10 thing, it won't work if it's run in the context of the older OS.

Support for UWP apps has been buggy since forever. The only thing you can do to avoid such glitches is to turn off that component of Aero Glass by running regsvr32 /U C:\AeroGlass\DWMGlass.dll from administrative Command Prompt.

I'm not an expert when it comes to IRQs, I can only tell what I've seen. No issues on Windows 7 guest. No driver I tried worked on Windows XP though, got the error that the device cannot start (code 10) in Device Manager. Doesn't help with anything, including volume control.

Sorry for the messed up post, spoiler tag seems to be buggy. Even though I only enclosed HDACFG content in the spoiler tag, the forum software trapped all the following text in there as well. The editor is royal PITA.

6.0.4

I see, 7-Zip 15.05 does show the decompiled script in this case. That remark about language files applies generally when dealing with anything where those languages are used. I merely wanted to point out that the way your screenshot looked isn't how it's supposed to look. We were discussing beta version of PotPlayer, which drops XP support, the current stable version still supports it officially.

Or you could just do what was said here: Your method is worse. Edit: Since Chrome 74, one must modify Chrome's shortcut to disable custom drawn title bar, see this post. BTW, compatibility settings for Chrome are automatically cleared on launch, at least if they are set for the current user, rather than globally for all users.

There's no easy straight-forward way to de-compile NSIS installers AFAIK, so I just extracted the files from it with 7-Zip. You can make ZIP package by extracting everything except the following: $0 $PLUGINSDIR Alarm.wav D_Exec.exe LogManager.exe PotNotify.exe PotPlayer.exe PotPlayerMini.exe uninstall.exe.nxis Then you can rename PotPlayerXP.exe to PotPlayer.exe and PotPlayerMiniXP.exe to PotPlayerMini.exe in the folder where you've extracted the files and ZIP it up. Usually, only Mini EXE files are installed. I remember that with the older releases, you got both normal and mini versions. The normal version can connect to Kakao's streaming services, so it's possible that it gets installed only if you choose Korean language during installation or if regional settings in Windows are set to South Korea, but I haven't experimented with that, so that's just my guessing. Also, when you upload it to the FTP, make it clear that it's only for use on Windows XP. The XP executables throw an error if you try to run them on Vista+. I don't have Server 2003, but the latest version does work on XP x64 Edition, which is similar under the hood. Yep, that's mandatory. Files for East Asian languages have to be installed for that text to render properly (Control Panel->Regional and Language Options->Languages).

To those that might be interested, whenever PCem v15 is done, it'll come with some speed improvements. https://pcem-emulator.co.uk/phpBB3/viewtopic.php?t=3162

Nope, no IRQ conflicts. BTW, QEMU can also emulate Intel HDA, but I haven't tried it yet. Both VirtualBox and QEMU are open-source.

Can also confirm PotPlayer 1.7.18193 actually runs on XP, just the installer was modified to output an error when ran on XP (simple version check). Regarding PotPlayer*XP.exe, they've been using separate executable for XP systems for several years now. PotPlayer.dll, where the guts of the player are, cannot be normally loaded on XP, so they use separate executable with some kind of workaround to get it to load. On Vista+, the normal workaround-free .exe is installed while .exe with a workaround is installed on XP. Loading PotPlayer.dll the usual way produces access violation exception in its initialization code due to some differences in Thread Information Block, value at FS:[0x2C] is NULL on XP.

That's true, I just assumed the possibility of using a different sound card when I said that. No, there's also AC97 and SoundBlaster 16 in VirtualBox, the point is just to see the HDA in action. Oops, I wrote "HDA Audio" in my previous post when I really meant "HDA Sound". Advanced tab was renamed to Devices on Windows 98. There, the audio driver appears like on Dave-H's screenshot. Not that I know of. It appears under System devices. I wonder if choppy audio under VirtualBox with HDA is just a simple configuration issue. AC97 works OK. I only know about the volume application that comes with the driver. Its Readme only says it may not work on some computers. And it really doesn't on that virtual computer. I see there's the volume setting in HDAcfg.ini at the end. How to interpret the value?

Steve Ballmer

Nothing appears on my end under Sound, video and game controllers, but High Definition Audio Controller is added under System devices. Testing with Windows 95 on VirtualBox with Intel HD Audio. It does give choppy audio after putting HDAICOUT.HDA in place and also "HDA Audio" appears in Multimedia properties, but volume can't be controlled there. 16-bit Windows 3.1 driver on Windows 9x strikes me more as an emergency solution rather than anything else.

The history teaches us it takes few months if all goes well. From the changelogs, there was/is some preliminary support for the older insider builds of 1903 in recent releases of Aero Glass, but it doesn't work anymore due to significant changes to the compositor.

Surround sound comes for free with HD audio specification. The latter is universally supported across modern operating systems, so it just works out-of-the-box without having to install a special driver.

MIME type for 7z archives is still wrong, application/x-troff-man instead of application/x-7z-compressed.

If they waited this long, they might as well wait a little longer.

The final version will also exist in x86 flavor at least...right? Edit: I guess it will as long as they still ship x86 Windows 10 images.

Looks like it was just a temporary issue with the official website.

It's anything but trivial, that's for sure. I suspect what @mikedigitize meant when he said nope was that he wasn't interested in the new Windows build. I don't think Aero Glass compatibility alone is the biggest concern, Microsoft keeps breaking things left and right, stuff that should just work. When was the last time you've seen the empty known issues section in the cumulative updates changelogs? It's a rare sight. Plus the bugs that exist but aren't on those lists.

When you login, the dialog with the machine ID pops up, which also offers to copy it to the clipboard. The ID is also logged in C:\AeroGlass\debug.log file.

Well, apart from DirectX 11, it also wants several other API functions that don't exist on XP.