Well, that was quick and easy to test. It doesn't seem to fix the problem though.

Here is a screenshot of what I got on screen when I ran it in a batch file. I just put the whole thing in a batch file with PAUSE in between some of the commands so I could see the results.

It basically had this message or one similar to it for every command:

The "Multi-function" part, and the Device 0000:0000 not found seemed to be the same for each stage of the process.

It seems like if I tell the system not to do the bootup floppy seek it will start normally (from hard disk), and I can generally just keep retrying commands on the floppy drive over and over to eventually get it to work... but it's quite tedious to use it this way, obviously. I didn't notice any difference before or after running the fix.

EDIT: By the way, this is the pciedit I downloaded. I assume this is what I'm supposed to be using? I didn't see any links or mention of this anywhere in the discussion... I just googled and figured this was right.
https://github.com/oerg866/pciedit/releases/tag/v0.5

Ozzuneoj wrote on 2026-02-11, 19:13:

Well, that was quick and easy to test. It doesn't seem to fix the problem though. […]
Show full quote

Well, that was quick and easy to test. It doesn't seem to fix the problem though.

Here is a screenshot of what I got on screen when I ran it in a batch file. I just put the whole thing in a batch file with PAUSE in between some of the commands so I could see the results.

It basically had this message or one similar to it for every command:

The attachment 20260211_140736.jpg is no longer available

The "Multi-function" part, and the Device 0000:0000 not found seemed to be the same for each stage of the process.

It seems like if I tell the system not to do the bootup floppy seek it will start normally (from hard disk), and I can generally just keep retrying commands on the floppy drive over and over to eventually get it to work... but it's quite tedious to use it this way, obviously. I didn't notice any difference before or after running the fix.

EDIT: By the way, this is the pciedit I downloaded. I assume this is what I'm supposed to be using? I didn't see any links or mention of this anywhere in the discussion... I just googled and figured this was right.
https://github.com/oerg866/pciedit/releases/tag/v0.5

Always dangerous to post something without being able to test it. 🙁 The syntax provided was for WPCSET. For PCIEDIT it should be like this:

To Disable ISA Post Write (Reg 52h):
PCIEDIT.EXE 1106 0686 52:fe
To Adjust ALE/BALE Timing (Reg 54h):
PCIEDIT.EXE 1106 0686 54:02
To Boost ISA/DMA Priority (Reg 48h):
PCIEDIT.EXE 1106 0686 48:01
To Enable Delayed Transaction (Reg 70h):
PCIEDIT.EXE 1106 0686 70:02

Yoghoo wrote on 2026-02-11, 20:06:

Always dangerous to post something without being able to test it. :( The syntax provided was for WPCSET. For PCIEDIT it should b […]
Show full quote

Ozzuneoj wrote on 2026-02-11, 19:13:

Well, that was quick and easy to test. It doesn't seem to fix the problem though. […]
Show full quote

Well, that was quick and easy to test. It doesn't seem to fix the problem though.

Here is a screenshot of what I got on screen when I ran it in a batch file. I just put the whole thing in a batch file with PAUSE in between some of the commands so I could see the results.

It basically had this message or one similar to it for every command:

The attachment 20260211_140736.jpg is no longer available

The "Multi-function" part, and the Device 0000:0000 not found seemed to be the same for each stage of the process.

It seems like if I tell the system not to do the bootup floppy seek it will start normally (from hard disk), and I can generally just keep retrying commands on the floppy drive over and over to eventually get it to work... but it's quite tedious to use it this way, obviously. I didn't notice any difference before or after running the fix.

EDIT: By the way, this is the pciedit I downloaded. I assume this is what I'm supposed to be using? I didn't see any links or mention of this anywhere in the discussion... I just googled and figured this was right.
https://github.com/oerg866/pciedit/releases/tag/v0.5

Always dangerous to post something without being able to test it. 🙁 The syntax provided was for WPCSET. For PCIEDIT it should be like this:

To Disable ISA Post Write (Reg 52h):
PCIEDIT.EXE 1106 0686 52:fe
To Adjust ALE/BALE Timing (Reg 54h):
PCIEDIT.EXE 1106 0686 54:02
To Boost ISA/DMA Priority (Reg 48h):
PCIEDIT.EXE 1106 0686 48:01
To Enable Delayed Transaction (Reg 70h):
PCIEDIT.EXE 1106 0686 70:02

Thanks! Step 1 shows a grid of hex numbers with a couple highlighted in green. After that, step 2 just kind of gets stuck. The system isn't hard locked (cursor is still blinking and ctrl-alt-del reboots instantly), but Step 2 never proceeds.

EDIT: Oh, I see now that it will eventually say "Not ready reading drive C" abort, retry, fail... Retry just causes it to happen again. So yeah, step 2 is causing an issue with the system's ability to read the C: drive. No sign of data loss at this point so, no harm done. 😅

Ozzuneoj wrote on 2026-02-11, 21:51:

Thanks! Step 1 shows a grid of hex numbers with a couple highlighted in green. After that, step 2 just kind of gets stuck. The system isn't hard locked (cursor is still blinking and ctrl-alt-del reboots instantly), but Step 2 never proceeds.

EDIT: Oh, I see now that it will eventually say "Not ready reading drive C" abort, retry, fail... Retry just causes it to happen again. So yeah, step 2 is causing an issue with the system's ability to read the C: drive. No sign of data loss at this point so, no harm done. 😅

Make sure to check the floppy problem after each successful statement. Could be that 1 of those steps could mitigate the problem. As a last resort you could try all the successful statements of course. Not forget to do a cold boot after each change as the registers will not reset/change back with a warm boot.

And yes, I gave the warning as playing with registers could potentially causes crashes or (worst case) data corruption. That never happened to me but btw. 😀