mirror of
https://github.com/oerg866/win98-quickinstall.git
synced 2026-04-26 05:25:56 +03:00
[GH-ISSUE #92] Suggestion: HDA audio support #84
Labels
No labels
bug
documentation
enhancement
help wanted
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/win98-quickinstall#84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ell1e on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/oerg866/win98-quickinstall/issues/92
https://github.com/andrew-hoffman/WDMHDA This is a driver that might be nice to include! I've had trouble with Win98 inside VMs, since many VM managers nowadays remove the AC97 audio for some reason and expect Intel HDA. (My apologies if the driver is already included.)
Another thing I've wondered about is IPv6, apparently there was some sort of "Trumpet" winsock stack out there that could do it that might be compatible with Windows 98. Together with TLS the lack of IPv6 might be the biggest roadblock for easily accessing the modern internet, for those who might want to do that. However, I don't know if common VM managers employ IPv6 NAT as a protection and whether an IPv6 stack on Windows 98 would be wildly unsafe to enable out of the box otherwise.
@oerg866 commented on GitHub (Mar 2, 2026):
Hello, I'm well aware of the HDA developments but the problem for me is that its level of maturity is just not there yet. Once it is more stable, it will be added to the extra driver library :)
Regarding IPv6 - once it becomes a popular request I will consider it, but to be honest me and everyone else I know has at least a local IPv4 network and accessing the modern internet is just out of the question anyway because you need to half-brick your system with some hacky version of KernelEx to get any remotely modern browser to run at all... so, at the moment it's not a concern, but I will reconsider it if more people raise this issue
@ell1e commented on GitHub (Mar 2, 2026):
IPv6 can be relevant for e.g. package managers too, so it's not just for web browsing. The reason I brought it up is that I'm writing a software where I'm considering adding Windows 98 support, but my blockers are that I need to find some way to do up-to-date TLS 1.2 on Windows 98 (if you know a library for that let me know) and that some of my hosts will likely be IPv6 only soon. However, without a NAT I'm guessing IPv6 might be way too dangerous for poor unpatched Windows98, so I'm not sure yet how realistic any of this would be in practice.
@oerg866 commented on GitHub (Mar 2, 2026):
I'm actually not really up to date on that, so if you find out, please let me know so I can add it to the patch sets! :)
@oerg866 commented on GitHub (Mar 2, 2026):
https://github.com/OmegaAOL/curl-windows98
Well, it looks like it can be done after all. Is this helpful?
@ell1e commented on GitHub (Mar 3, 2026):
I was hoping for a TLS library that is actually still maintained, since if you use a firewall that's like probably the one major part that will be most likely attacked if you somehow have modern software on a Windows 98 machine connect to the outside. In theory it's possible, since a TLS library can be written without any socket access, by just handling all of the TLS math and providing an abstract interface for reads and writes and letting the client software handling the rest (which I will be writing).
Anyway, it was just a silly idea of mine. I am already planning to target Windows XP and I noticed if I use Windows 98's code page to unicode conversions, I don't really have any dependencies that aren't already present on Windows 98. Other than TLS...