home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!mp.cs.niu.edu!uxa.ecn.bgu.edu!msjle
- From: msjle@uxa.ecn.bgu.edu (Joi L. Ellis)
- Subject: CDRom vx EMM386 on a DTK--??
- Message-ID: <Bz9LFE.5BH@uxa.ecn.bgu.edu>
- Summary: New conflict between EMM86 and MTMCDSA.SYS
- Keywords: CDROM EMM386 DTK MTMCDSA.SYS MSCDEX.COM EMS
- Organization: Educational Computing Network
- Date: Mon, 14 Dec 1992 19:42:49 GMT
- Lines: 49
-
-
- Does anyone know of an ftp'able source for documentation for the
- MTMCDSA.SYS and MSCDEX.COM CDROM drivers?
-
- AND/OR
-
- Does anyone know why EMM386 and MTMCDSA.SYS conflict with each other in
- a DTK 386/sx with a PPM2531D(s) motherboard and DTK BIOS?
-
-
- One of my users has a DAK CD-Rom using these drivers. She had it
- running fine in an older, slower DTK386sx. She recently upgraded to
- this new one with a different mother board, and is experiencing all
- sorts of new problems.
-
- The CPU BIOS arrived mis-configured to begin with, but fixing that has
- not solved the original problem, which is that the machine is very
- flakey and crashes during operation for no reason. It often complains
- about parity errors.
-
- Of course, both DAK and DTK point at each other as the culprit so I'm
- not getting much help there.
-
- I've narrowed the problem down to the fact that as soon as I load the
- MTMCDSA.SYS driver in combination with EMM386, the machine gets flakey.
- It totally fails CHECKIT's memory diagnostic with both loaded, but
- passes perfectly as soon as I remove one or the other. I've
- experimented with every BIOS and EMM386 and HIMEM setting I can, and
- nothing makes any difference. Neither does running in non-TURBO mode.
-
- From dumping the MTMCSDA.SYS code with a lister, I know that it will use
- EMS memory (from the error messages it contains) but I do not know how.
- DAK did not document ANY of the drivers in their manual and I'm
- suspecting that there is a conflict between EMM386 & the drivers that
- appears to cause a problem on this faster motherboard. However, I can't
- find anything so radically different between this new cpu and the
- original one that would explain this problem.
-
- If you have *any* thoughts or suggestions I'd appreciate hearing from
- you.
-
- Thanks!
-
-
-
- --
- Joi Ellis msjle@uxa.ecn.bgu.edu
- Student Residential Programs Western Illinois University
-
-