pangoomis

I'm getting reports, and also tested myself that Internet Games in Windows XP (and Windows ME) no longer can connect to the game server. I've tested Windows 7 Internet Games and they seem to work fine. Can any of you fine XP diehards here test if they are not working for you either?

They do say though that the iGPUs are NOT supported, so did ASRock a while back as you can see here (select Windows 7), nothing new for me: https://www.asrock.com/mb/Intel/H310CM-HDVP/index.asp#Download

NVIDIA driver for Windows 98 does support DVI-D. Try DVI then.

Ethernet is much, much easier to deal with than HD Audio/AC'97 so not a fair comparison. As for HD Audio, even if the Win3.1 driver works, it would require special settings per every PC, and that's not really convenient. So far, haven't seen it working other than for walter (the author) and deomsh. @deomsh Does the HD Audio works in games (specifically Direct3D games with some kind of audio acceleration) , and programs? (Audacity and alike)

Have you tried that GPU under other OS like Windows XP? Maybe the card is faulty. What are your PC specs? If you have more than 512MB of RAM, try limiting it by using the MaxPhysPage=20000 parameter in SYSTEM.INI under [386enh] section.

What does USB2 drivers have to do with restarting?

What about restarting? That is actually more useful for me than shutdown. You could add a Shutdown/Restart dialog in the WinOff16.

@LoneCrusader What drivers you've used to test the HDAUDIO device, the generic HDAUDIO.SYS or the Realtek one? As for the Win3x driver, check here: https://web.archive.org/web/20180329132229/http://win3x.conforums.com/index.cgi?board=Pascal&num=1502071336&action=display&start=165 Haven't tested it myself, last time I've checked it caused startup delay and did nothin.

Sorry, couldn't find drivers for XP, Only Windows 7+. It's an Intel NIC commonly found on the higher end 100-series motherboards, unlike cheap Realtek chip like on my ASRock H110M-DVS R3.0 motherboard which works with Windows 98 SE+. Dietmar, if you can share the XP drivers for the Intel(R) Ethernet Connection (2) I219-V chip, it would be helpful. It is a simple INF mod, or is the driver modded itself?

For sound, a dirty workaround is using a cheap USB Sound Card, but you can't use laptop's speakers and microphone by doing that. Try these drivers for audio: http://download.windowsupdate.com/msdownload/update/driver/drvs/2009/01/3606_2a8375c3d140e7fe404fdfe59c4441ade24aea48.cab

What is the Hardware ID of that Ethernet Controller? (VEN & DEV)

Have you tried the latest LAN drivers from Intel for XP? They might work...or not. https://downloadcenter.intel.com/download/18717/Network-Adapter-Drivers-for-Windows-XP-Final-Release?product=36773

I can't really think of any other software that is reasonably up to date in terms of modern hardware detection that works on Windows 98 SE, other than AIDA64 and HWINFO32. You should really give AIDA64 a try, either it will work fine, or you will have a BSOD. I had AIDA64 working fine with 82.69 drivers, but then it suddenly stopped working and I do not know why is that. That was with the same program version, so that wasn't the problem! I've been discussing this issue with the authors of AIDA64, as you can see here: https://forums.aida64.com/topic/4017-windows-98se-blue-screen-of-death-with-the-kerneldw9x-llkd/ They can't seem to reproduce the issue I'm experiencing, so it's all a matter of being lucky AIDA64 has some HW monitoring overlays, but I do not know if they work with Windows 98 SE. There's no FPS monitor, I can't think of anything else than Fraps 1.9d. I haven't used HWINFO32 much but I know it works, but the functionality is limited there, unlike AIDA64.

Ooh! That explains why A405 and A406 never worked for me when I had the ASRock K8Upgrade-NF3 motherboard with Windows 98 SE! PS: Some drivers include WDMSTUB.SYS in their packages!

This site may be useful for you: http://www.activewin.com/faq/faq_7.shtml http://www.activewin.com/directx/directx8.shtml Since I'm not interested in Windows 95 at all, I don't have any background about DirectX 8.0a/b limitations/features.

Here's how it looks on my Windows 10 1809 17763.316 system (I'm long overdue for an Arch Linux install, I'm sorry ) <tt>GetVersion: 0x23F00206 GetVersionExA (OSVERSIONINFOA*): dwOSVersionInfoSize 0x00000094 dwMajorVersion 0x00000006 dwMinorVersion 0x00000002 dwBuildNumber 0x000023F0 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] return TRUE GetVersionExA (OSVERSIONINFOEXA*): dwOSVersionInfoSize 0x0000009C dwMajorVersion 0x00000006 dwMinorVersion 0x00000002 dwBuildNumber 0x000023F0 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] wServicePackMajor 0x0000 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE GetVersionExW (OSVERSIONINFOW*): dwOSVersionInfoSize 0x00000114 dwMajorVersion 0x00000006 dwMinorVersion 0x00000002 dwBuildNumber 0x000023F0 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] return TRUE GetVersionExW (OSVERSIONINFOEXW*): dwOSVersionInfoSize 0x0000011C dwMajorVersion 0x00000006 dwMinorVersion 0x00000002 dwBuildNumber 0x000023F0 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] wServicePackMajor 0x0000 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE gv=0x23F00206 gvex=6,2,23F0,2,,0,0,100,1,0</tt>

Are you using these drivers? https://www.asix.com.tw/download.php?sub=driverdetail&amp;PItemID=97 You can try replacing the sys file with the Windows XP version, have low hopes for this but don't have any other ideas right now.

What is the device hardware ID of that adapter?

@ruthanYou can try AIDA64, it has some disk benchmarks: https://www.aida64.com/downloads/NTEzMWY5ZTE= Latest beta version still works natively on Windows 98 SE. Although you might have a BSOD if you have an NVIDIA card, in that case, you can use VBEMP to avoid that problem.

This all seems logical, I had some problems with 3DMark 2001SE with 1GB of RAM, even if the rest of the system worked fine, that disappeared when limiting the amount to 512MB. I myself stand that having the amount of RAM between 512MB and 1024MB may still cause unexpected problems, like me or OP had, even if the system boots up correctly. I never had ANY problems with using 512MB of RAM or below. Put: MaxPhysPage=20000 in the [386enh] section in the system.ini file inside the Windows directory. This will limit the amount of RAM to 512MB. If you still encounter issues, try MaxPhysPage=10000 This will limit the amount of RAM to 256MB, although I don't think that would be necessary.

Have you tried different PCI slots on your motherboard? What are the rest of the system specs? (CPU, GPU, RAM)

Thanks @rloew! With the USBD.SYS file copied, the USB controllers are enumerated correctly, and USB Flash Drive and USB Sound Card is working fine! I had to also copy USBHUB.SYS. Also, if anyone wants to run 98SE on X230 and alike, make sure to disable USB UEFI BIOS Support in the BIOS once you've installed the system, because it causes major startup delay for whatever reason.

I have it setup like that already, I have the latest 2.74 BIOS/UEFI. There's no problem with using USB flash drivers in the BIOS/UEFI, and in other operating systems. It's the way the motherboard/PCH was designed that is the problem. And how Windows 98/USB drivers can't handle that.

On my ThinkPad X230, there's no OHCI controller present in the system, all the USB ports are handled by the EHCI and XHCI controllers, I can disable the XHCI controller in the BIOS/UEFI, but that's about it. Now, since there's no OHCI controllers, Windows 98 SE does not pick up any USB devices when installed. When I've tried to install the unofficial USB 2.0 drivers, I get Code 2 on the USB Hub, which means USB does not work at all. Does USB 2.0 on Windows 98 SE require OHCI/UHCI (USB 1.1) controllers to be present before hand?

From what I know, Windows ME welcome works very differently, I haven't tested it. All files you need are on the setup CABs in the CD of the system, I can't share them here. I don't know if the registry is needed in the first place, but all the instructions are on the screenshot itself. You also need win.wbm in the WELCOME folder, it got cut off in the screenshot, sorry Even if you managed to get it working, the buttons don't do anything, it's just a useless show piece. Off-topic - Welcome.exe also works on Wine on my Arch Linux laptop