Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ogccse!blake!callisto
From: callisto@blake.acs.washington.edu (Finn)
Newsgroups: comp.os.cpm
Subject: Re: MEX using MP/M
Keywords: Help!
Message-ID: <3660@blake.acs.washington.edu>
Date: 16 Sep 89 20:19:25 GMT
References: <1832@sactoh0.UUCP>
Reply-To: callisto@blake.acs.washington.edu (Finn)
Organization: University of Washington, Seattle
Lines: 15

In article <1832@sactoh0.UUCP> ianj@sactoh0.UUCP (Ian R. Justman) writes:
>Has anyone used MEX with MP/M?  I'm currently doing it, but I can't
>do any other tasks otherwise I will lose characters.  I'll probably
>have to write some sort of interrupt driven routine, but MP/M needs
>interrupts in order to process calls from other consoles.  Any help
>on this matter will be definitely appreciated.

 I used MEX with MP/M on an Altos 580 for quite some time, and found:
 Mex worked fine up to about 1200 baud, then gave up and lost characters.
 Sometimes, particularly after using x-modem, a "phase of the moon"
 type error caused mex to lock up that user when exiting to system.
 Sometimes the problem could be solved by killing the process from another
 terminals, and sometimes it was necessary to re-boot the machine.  I
 suspect this resulted from mex writing into the common memory above
 C000.