16 Jun
2013
16 Jun
'13
3:46 p.m.
On 16/06/2013 19:46, Tothwolf wrote:
On Sun, 16 Jun 2013, Pete Turnbull wrote:
No, because I don't have either. I'll go and ask Google where they are
tomorrow. A WDAT-240 doesn't have any memory, AFAIR, though. And it's
set to the standard floppy address (the motherboard controller is
disabled because it doesn't work very well).
--
Pete Peter Turnbull
Network Manager
University of York
At the moment, those two lines are commented out
because if they're
not, the floppies don't work properly. Has anyone got any idea why?
The CDROM works fine if I uncomment those lines (but the floppies
don't) and network shares work fine either way.
It sounds like memmaker added parameters that are loading the cdrom
driver into a memory region that conflicts with the floppy drive
controller. That wasn't an uncommon problem for third party I/O boards
and controllers that have their own BIOS and memory. Have you tried a
third party memory manager instead of memmaker such as 386MAX or QEMM?