VOGONS


Reply 20 of 32, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie

That could be anythimg. DOS uses BIOS for floppy driver. ROM and very little RAM.

Winblows even W95 has much more complex drivers loaded in RAM.

It could be a signal error causing a condition those drivers can't handle'

It could be a memory error - try running MemTest.

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filetransfer(w/o netSW)via Lan/Lpt/Com

Reply 21 of 32, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie
Nicolas 2000 wrote on 2026-11-04, 17:27:

ESDI is related to IDE so hard disk and/or CD ROM. Not floppy.

Good point, and what leads me to suspect it's not a simple floppy problem but either a RAM error or some weird interaction between system drivers.

As aways I suggest doing extensive tests with ImageDisk as it uses non-BIOS drivers and can give much mere information on errors.

After confirming system with MemTest of course!

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filetransfer(w/o netSW)via Lan/Lpt/Com

Reply 22 of 32, by kingcake

User metadata
Rank Oldbie
Rank
Oldbie
DOSdm wrote on 2026-11-04, 17:09:
I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win […]
Show full quote

I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win95 I eventually got a blue screen that says

"A fatal exception 0E has occurred at 0028:C0FF2897 in VXD
ESDI_506(01) + 00001633. The current application will be terminated."

Is this because of some sort of hardware mismatch? It's a Mitsumi floppy drive from a late 90s Gateway.

I would take a step back and run memtest overnight before going any further. Just to rule it out. I think V4 should work on your machine.

Reply 23 of 32, by Nicolas 2000

User metadata
Rank Member
Rank
Member

If you are unsure of/suspecting RAM, a decent MEMTest can rule out a lot indeed. Related example, Atari ST also have quite a reputation for being unstable and crashing. Yeah, until you have one that has healthy hardware and ZERO memory errors. Rock solid. That said, not sure your issue is due to RAM. Your BIOS is at default settings so likely the wait states etc are set conservatively, but it could still be a myriad of other causes.

Reply 24 of 32, by kingcake

User metadata
Rank Oldbie
Rank
Oldbie
Nicolas 2000 wrote on 2026-11-04, 19:02:

If you are unsure of/suspecting RAM, a decent MEMTest can rule out a lot indeed. Related example, Atari ST also have quite a reputation for being unstable and crashing. Yeah, until you have one that has healthy hardware and ZERO memory errors. Rock solid. That said, not sure your issue is due to RAM. Your BIOS is at default settings so likely the wait states etc are set conservatively, but it could still be a myriad of other causes.

I'm not saying it's THE problem, but A problem.

BSOD = always rule out ram

Reply 25 of 32, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie
kingcake wrote on 2026-11-04, 19:09:

... BSOD = always rule out ram

Agreed - absolutely!

Most (but not all) system s/w can detect othet errors and exit "somewhat" gracefully. But RAM problems cause fundamental problems that can prevent the S/W from "doing its thing".

Always the first thing I check when "weirdness" happens!

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filetransfer(w/o netSW)via Lan/Lpt/Com

Reply 26 of 32, by DOSdm

User metadata
Rank Newbie
Rank
Newbie
kingcake wrote on 2026-11-04, 18:21:
DOSdm wrote on 2026-11-04, 17:09:
I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win […]
Show full quote

I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win95 I eventually got a blue screen that says

"A fatal exception 0E has occurred at 0028:C0FF2897 in VXD
ESDI_506(01) + 00001633. The current application will be terminated."

Is this because of some sort of hardware mismatch? It's a Mitsumi floppy drive from a late 90s Gateway.

I would take a step back and run memtest overnight before going any further. Just to rule it out. I think V4 should work on your machine.

I downloaded the img and wrote it to a disk, booted up the 486 with the disk in but once it gets to the test screen my computer reboots, every time.

Reply 27 of 32, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie

Assuming you are talking about MemTest ... odd that it can't run enough to report bad memory yet DOS can run.

Can you try booting on another system to confirm the boot disk is good?

And if you have multiple memory "sticks" - try to see how few you need for the system to POST and try booting, then swap them around to try and identify the bad ons(s)

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filetransfer(w/o netSW)via Lan/Lpt/Com

Reply 28 of 32, by DOSdm

User metadata
Rank Newbie
Rank
Newbie
DaveDDS wrote on 2026-11-04, 20:12:

Assuming you are talking about MemTest ... odd that it can't run enough to report bad memory yet DOS can run.

Can you try booting on another system to confirm the boot disk is good?

And if you have multiple memory "sticks" - try to see how few you need for the system to POST and try booting, then swap them around to try and identify the bad ons(s)

I will try that and update in a little while. I do want to add that the floppy drive I just put in was working initially, however now it's behaving oddly. In DOS I was able to install most of a game, but on disk 5 there was some sort of problem and it couldn't continue. Sometimes when I boot up it works, other times it won't do anything at all. I tried running memtest from floppy so could the problem I'm having with running memtest have to do with my floppy drive not working reliably? Just now I was trying to copy a directory from the floppy to my hard drive and then it said "general failure reading drive a".

Reply 29 of 32, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie

Clean the connectors & heads .. could just be simple "dirty" faults.

BSOD when booting something "special" on a driver with errors isn't that uncommon too.

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filetransfer(w/o netSW)via Lan/Lpt/Com

Reply 30 of 32, by kingcake

User metadata
Rank Oldbie
Rank
Oldbie
DOSdm wrote on 2026-11-04, 19:50:
kingcake wrote on 2026-11-04, 18:21:
DOSdm wrote on 2026-11-04, 17:09:
I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win […]
Show full quote

I tested one of my other floppy drives in the 486 today and so far it's working normally in DOS. However, when I booted into Win95 I eventually got a blue screen that says

"A fatal exception 0E has occurred at 0028:C0FF2897 in VXD
ESDI_506(01) + 00001633. The current application will be terminated."

Is this because of some sort of hardware mismatch? It's a Mitsumi floppy drive from a late 90s Gateway.

I would take a step back and run memtest overnight before going any further. Just to rule it out. I think V4 should work on your machine.

I downloaded the img and wrote it to a disk, booted up the 486 with the disk in but once it gets to the test screen my computer reboots, every time.

I've seen V4 do that sometimes. Go older, like V2.

Reply 31 of 32, by DOSdm

User metadata
Rank Newbie
Rank
Newbie

My floppy drive just doesn't work at all now. I've tried 3 floppy drives and 2 data cables and I can't get it to work reliably. Sometimes DOS lets me change to A:, but usually it says it's not ready. I was able to copy the cute ouse driver from a disk to the hard drive, but then it wouldn't work after that. Now I am totally stuck.

Reply 32 of 32, by BitWrangler

User metadata
Rank l33t++
Rank
l33t++

When it boots it's cold, by the time it has thrashed it's way into windows it has warmed up a bit... so clean IO card connector, ISA slot, check pins of slot for dry joints, cracked off traces or through holes, also try different slot... further toward the right from front if possible. Suspecting DMA 2 is going flaky somewhere.

Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.