Reply 20 of 42, by Deunan
feipoa wrote on 2024-05-07, 09:18:Deunan, your next project is setting up an Am386DX? At least put a DLC in there to make it more interesting.
Win95 on 386. I might even consider installing it from floppies for the fun of it. I'm sure I'll put a DLC in at some point as well (and also SXL) for testing. I've built a Debian machine out of my 386WB mobo (for which I had to set up my own package repository on a modern Linux box) but I doubt I'll be happy with the Win95 performance, so I'll probably end up imaging the card and reusing parts for different project.
feipoa wrote on 2024-05-07, 09:18:These two Symphony boards do demonstrate further strangeness
I guess these mobos have some quirks that make them unusable in some cases. I remember quite a few issues with HW even back in the DOS era (I/O cards somehow not working properly when trying to setup a daisy-chain "network" for Doom or Diablo using serial ports, my slow SVGA using 128k banks which most games didn't support even though VESA spec allows it, the stereo issue of SBpro and some clones, various problems with PnP cards and old BIOSes, etc).
I see you have a few shadow regions defined, is it for XTIDE? Disable the ones you don't use, might help. I'd also try enabling memory relocation if you have less than 16M of RAM installed, every bit helps.
The options I'd play with are I/O recovery time and ALE (should be ISA-specific but who knows) and fast A20 gate since I've dealt with mobos where this is broken. Though that would probably trip the kernel right away rather than cause issues with libraries.
BTW did you try de-turbo? How does this mobo implement turbo anyway, via CPU clock or extra RAM waitstates? If the former then it might just help the timings and solve some issues. Obviously it would not be usable like that but at least offer some extra info about the mobo.