I installed W98SE using setup /p i with 1GB of memory, all was going well 'till the 2nd reboot at which stage it got stuck in start-up, BOOTLOGPRV attached as BOOTLOG was from a safe boot.

The only irksome downside is that it destroyed the W10 boot, once I have sorted this I change the system name and will look some more into why W98SE gets stuck.

The good news is that it booted in Safe mode and SIV worked with only one issue which I was expecting, the On Semi ASP0800 power controller was not reported. I have just added W9x support for this, it's never been tested and will be easy to fix once I get the MSVC 6 remote debugger working as it does show up on [PMB Bus].

red-ray wrote on 2026-01-30, 14:58:

I installed W98SE using setup /p i with 1GB of memory

I tried again and this time, by mistake, I just ran SETUP with no qualifiers and it's looking much better, but I still need to get networking to play. I also changed the CPU.

It's now working with 1GB, does anyone know what the limit is if I don't patch the system. Could I just add MaxPhysPage=40000 to system.ini to limit it to 1GB?, what about MaxPhysPage=80000 for 2GB?

I got the system on my network using a Digital DE500-BA, I then used the MSVC 6 remote debugger and it didn't take long to get PWM reporting going.

Next I have to decide if I wish to latch the system so I can run W98SE with all the DIMMs installed.

Sounds like Supermicro issues. I ran Windows 10 IoT Enterprise LTSC 21H2 on a few desktop X58 boards just fine.

The Serpent Rider wrote on 2026-01-31, 21:40:

Sounds like Supermicro issues. I ran Windows 10 IoT Enterprise LTSC 21H2 on a few desktop X58 boards just fine.

How can it be a Supermicro issue when the motherboard is an ASUS P6T SE?

Oh, I misread it then. P6T is bog-standard board, so that's a bit strange. Perhaps try out installing on another X58 board and then load the system from P6T?

Does the Windows 10 issue only occur with VT-D enabled in the BIOS ?

The Serpent Rider wrote on 2026-01-31, 22:21:

Oh, I misread it then. P6T is bog-standard board, so that's a bit strange. Perhaps try out installing on another X58 board and then load the system from P6T?

Years ago I used to run W10 insider builds on my ASUS P6X58D Premium Intel Core i7 Extreme 980X (Gulftown) system, then there was a build when it stopped working, but I don't remember the build # when the issue started. At the time I suspected it was the CSMI RAID disks. I got the P6T SE as I don't wish my mess up the P6X58D which is my main W7 test system.

This is mainly for XP-x64 + W98SE and I only use W10 to trim the SSD once in a while and TH1 does that OK, I would like to try RS1/RS2, but can't find install media for the licences I have.

darry wrote on 2026-01-31, 22:28:

Does the Windows 10 issue only occur with VT-D enabled in the BIOS ?

No, thank you very much for your post, once I disabled it then I was able boot the 22H2 install flash so I then copied the kit from my main system, crossed my fingers and did the update from TH1. Windows 10 22H2 is now installed, seems to be OK and I even managed to get the system enrolled ESU. How did you figure this out please?

What facility does enabling VT-D provide? Even with it disabled it offers "enable core isolation", but when I tried to enable it this was rejected because of the very old GeForce 6600 GT drivers (I need an old GPU for W98SE).

Windows update seems confused, it tells me I need updates then when I press Check for updates fails to find them, I guess it may sort itself out in time.

red-ray wrote on 2026-02-01, 22:22:

No, thank you very much for your post, once I disabled it then I was able boot the 22H2 install flash so I then copped the kit f […]
Show full quote

darry wrote on 2026-01-31, 22:28:

Does the Windows 10 issue only occur with VT-D enabled in the BIOS ?

No, thank you very much for your post, once I disabled it then I was able boot the 22H2 install flash so I then copped the kit from my main system, crossed my fingers and did the update from TH1. Windows 10 22H2 is now installed, seems to be OK and I even managed to get the system enrolled ESU. How did you figure this out please?

What facility does enabling VT-D provide? Even with it disabled it offers "enable core isolation", but when I tried to enable it this was rejected because of the very old GeForce 6600 GT drivers (I need an old GPU for W98SE).

Windows update seems confused, it tells me I need updates then when I press Check for updates fails to find them, I guess it may sort itself out in time.

VT-D is mostly useful for running a VM with PCI passthrough. This is not supported when client versions of Windows (Home and Workstation) are used as hosts, AFAICR, except possibly for GPU partitioning, which I have never tried. Apparently, VT-D's functionality is used to implement some security features. That set aside, unless you are dual booting to an OS that can support VMs with PCI passthrough and you actual intend to do so, VT-D does not do anything useful, on Windows 10 more so than on 11.

EDIT: My experience with that scenario and the associated technet article Re: What retro activity did you get up to today?

darry wrote on 2026-02-01, 23:27:

This is not supported when client versions of Windows (Home and Workstation) are used as hosts, AFAICR, except possibly for GPU partitioning, which I have never tried. Apparently, VT-D's functionality is used to implement some security features. That set aside, unless you are dual booting to an OS that can support VMs with PCI passthrough and you actual intend to do so, VT-D does not do anything useful, on Windows 10 more so than on 11.

Thank you for the information and links, I will look some more later. What about Pro Workstation and Enterprise?, I used to run Enterprise and changed to Pro Workstation so I could get ESU.

I just checked and VT-D is enabled on my other X58 system, I may now be tempted to disable it and update to 22H2, W10 used to run OK on it, but then stopped and I had assumed it was down to it using CSMI RAID.

I just checked and my X79 + C602 + X299 all have it enabled and W10 22H2 works well on them all, so why not X58, maybe there are bugs in the X58 implementation.

All in all today has been a good day, I got both W98SE (with all 12GB of RAM) and W10 22H2 running on the ASUS P6T SE .

I now have W10 + WXP-x64 + NT4-ES all working as I would like, but on W98SE SMART does not work, SIV reports SMART on my other W9x systems so I don't think it's a SIV issue, what needs doing to make it work please?

Boot log attached, is anything else needed? It's a new W98SE install I did in the last week, it's never worked, not even then I only had 1GB of DDR3 installed before I patched it.

I looked some more as to why SMART does not work and suspect it's down to there being a resource conflict, but one tab says resource conflict and another says No conflicts !, how can this be?

I just noticed 03F6 + 0376, where do these come from? BAR 5 is I/O Port FFA0 which is not even in the Windows Properties.

The device only has I/O Ports + IRQs 14 + 15 and no other PCI device uses either of those, so I made [I/O Ports] to work on W9x and there are no I/O Port conflicts either.

How can I find the conflict? I can boot the exact same system into Windows XP-x64 + fully patched Windows 10 x64 Build 19045 22H2 and there are no issues with any of the devices on either.

red-ray wrote on 2026-02-08, 23:46:

I just noticed 03F6 + 0376, where do these come from?

I should have RTFM so I did, after doing this I updated SIV and am still none the wiser as to what the resource conflict is.