UCyborg

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.

AFAIK, it's a separate thing containing documentation for Windows API functions. You could say Visual Studio 6.0 comes with older version of Platform SDK (these days, it's called Windows SDK). https://stackoverflow.com/questions/18844383/windows-sdk-vs-visual-studio I only did simple modifications to some existing games, nothing directly related to rendering with Direct3D, so can't be much of help in that department. I'd go with Plug and Play Monitor in most cases. It's the best to let the user choose any resolution supported by the system. Some games display dialog with graphics settings the first time they're launched.

Windows XP compatible version of WineD3D is very old (2015) and its Direct3D 11 implementation was still pretty bad in late in 2017, when DXVK emerged, which was soon capable of running some serious D3D11 games (eg. Grand Theft Auto V or The Witcher 3) with decent performance unlike WineD3D, which choked on them. DXVK's trick is translating D3D11 calls to Vulkan rather than OpenGL, which is practically significantly less expensive performance-wise. Obviously, it's of no use on XP because no Windows XP compatible graphics driver implements Vulkan.

Did I miss something there? There was one guy who failed to register DLL due to not running Command Prompt as administrator. Other than that, I only know about the game Survival Crisis Z with that dependency. The samples included with SDK also work, at least those that don't require comdlg32.ocx or mscomctl.ocx; I have yet to try to register those. I guess the chance of breaking something due to DirectX VB DLLs is minimal since they're just wrappers exposing Direct3D functions to Visual Basic. Its installer doesn't do much on newer Windows versions. The one for DirectX 9.0c released in 2004 actually installs dx8vb.dll and also dx7vb.dll, after working around obstacles preventing it from running in the first place. Interestingly, when I ran it, it registered dx8vb.dll, but not dx7vb.dll.

No. In this case, it doesn't really matter as the SDK doesn't integrate tightly with Visual Studio. You could even install it before Visual Studio and everything would still work as expected. Yes, that would be OK. We're talking about d3dx8_0b.exe, correct? Everything'll be fine if you follow instruction in its ReadMe. I found your other thread on this forum where you were concerned about this update and the OS stability. This update affects the utility library called D3DX8, which functionality is baked directly in your application in the end in the case you choose to use it, so your application specifically benefits. System stability would be compromised in the case your application managed to trigger some critical bug in your graphics card's driver. Yes. Visual Studio 6.0 actually refers to the package of separate IDE (Integrated Development Environment) programs used to write programs, so you have one program for C/C++ and another for Visual Basic. In later versions, there's a single program for everything. Free Express editions are an exception. So, my instructions were for Microsoft Visual Basic 6.0, that may have been obtained as part of Microsoft Visual Studio 6.0 (it was also sold separately in the old days). The one ISO I found under that name has Windows 98 Resource Kit and Microsoft Plus! 98 on it. There are apparently multiple discs. If you decide to write something in Visual Basic, you'll have dependency on dx8vb.dll. This library is not part the OS since Windows Vista, but it's possible to take it from an older OS (version from Windows XP SP3 is the latest and probably most popular), place it in C:\Windows\System32 (32-bit OS) or C:\Windows\SysWOW64 (64-bit OS) and register it with regsvr32 to make programs dependent on it functional.

You don't need to bother with Platform SDK if you don't intend to use Windows API functions that only exist in Windows 98 and later. Visual Studio 6.0 and DirectX 8.0a SDK would be a good start. So, install things in the following order: Microsoft Visual Studio 6.0 (picking both Microsoft Visual C++ 6.0 and Microsoft Visual Basic 6.0 will let you study all example projects that come with DirectX 8 SDK) Microsoft Visual Studio Service Pack 6 (vs6sp6.exe) Microsoft DirectX 8.0a SDK (DX8a_SDK.exe) You're not done yet: Go to Start->Programs->Microsoft Visual Studio 6.0->Microsoft Visual C++ 6.0 From there, go to Tools->Options... and open Directories tab. In the right drop-down menu, pick Include files and then the New button under it (it's the very first one). In the empty line that appears, browse to the include folder of DirectX header files, it'll be C:\mssdk\include if you've installed DirectX SDK in the default folder. Move the new entry to the top with the up arrow button. Now repeat the previous steps for library files, choose Library files in the drop-down menu, browse to C:\mssdk\lib and move it to the top. That's it for Microsoft Visual C++, you should be able to open and build example projects under C:\mssdk\samples\Multimedia. In Microsoft Visual Basic, you have to go to Project->References... and tick DirectX 8 for Visual Basic Type Library after you create a new project to be able to use DirectX 8 functionality. The example stuff is in C:\mssdk\samples\Multimedia\VBSamples.

I was unable to find "DX8a_DevRT.exe", but its content is probably part of the "DX8a_SDK.exe", so the latter should be everything that's needed. The setup program gives the option to install either retail or debug runtime, I guess "DevRT" refers to the latter. Debug runtime is meant to ease finding and fixing bugs in your code, it consists of DLLs your game loads to utilize DirectX functionality.

Fast startup feature is known to have some odd behaviors, which can cause what you're experiencing under certain circumstances. There's no definite fix AFAIK. You can try and see if switching to newer or older graphics card drivers helps.

Didn't know what was status on those crashing bugs since nothing was said about them until now, so that's cool. Well, those two still exist: Interpreting HIWORD of TextGlowMode setting bug (acknowledged, but never fixed, it also didn't exist in older versions) Bug with window caption centering with certain settings when window is re-sized There's also a second issue with caption centering, for which I remember the author claiming it's not a bug (so must be a feature ); if you set TextGlowMode to 1 and CenterCaption to 1, the glow is stretched over the entire title bar. Either way, addressing these would bring us closer to perfection.

Probably just like the latest experimental version without debug stuff. The old bugs I reported years ago related to caption rendering are still there.

GetThreadId exists in NT 5.2 (Server 2003 and XP x64 edition).

Another difference between IE and Edge, some newish extensions like uBlock Origin and Enhancer for YouTube can be found only for Edge. What's boggling from my POV, there's no port of extension that would integrate with KeePass. There were plans to port Kee from Firefox (the XUL version is called KeeFox), but hasn't been done due to some limitations in Edge. One thing Edge has really done right is scrolling. It feels the smoothest, particularly with the touchpad. Firefox Quantum comes close second in that department. Again, that's my subjective experience on low-end laptop. Finally, it seems Edge is the most famous when it comes to energy efficiency. Now one has to wonder if things done right under the hood are inherent in the Chromium version of Edge. I suspect it's possible with some effort. Navigating YouTube for instance oughtta be smoother with Chromium under the hood. Google knows this and intentionally serves the new version of the page, which EdgeHTML variant of Edge handles exceptionally poor, particularly evident on weaker devices. Yes, I said videos play OK (once they load), but everything else on the page is pretty bad on slower devices unless you spoof IE11's user agent.

Sorry, just assumed it would work. Either way, the .xpi files in the profile folder in the extensions sub-folder should be transferable. The .xpi file can be drag-and-dropped on the Firefox's window to trigger installation process.

Would those be preserved if you were upgrading from Windows 7 to 10? Those upgrades were always shaky when it came to preserving global, non-user specific data. And so called feature updates act like OS upgrades. Did anyone try installing Group Policy Editor on the Home edition and try to turn off updates from there? There's also PolicyPlus.

The update that was supposed to bring version 1809 closer to the state in which it should've been released in the first place. Didn't seem to accomplish the goal. Am I too optimistic by assuming that was the goal? The frequency of new feature updates should really be reduced. What's the point of releasing a bugged OS every 6 months, only for it to take another 6 months at least to fix it when another bugged build is released into the wild?