Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bu.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga.emulations
Subject: Re: Working JR-Comm w/a Datalink modem(MNP-5)?
Message-ID: <706@faatcrl.UUCP>
Date: 17 Jan 91 00:26:28 GMT
References: <9101141811.aa28058@orion.oac.uci.edu> <18875d77.ARN1307@venus.UUCP>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 14

wfaust@venus.UUCP (Wolf Faust) writes:

>As far as I know (is Jeff out here??) it's a bug wich can be fixed by
>a new set of eproms. Call AE for an eprom update. The problem can
>be fixed by the new eprom, anyway, it's caused by something
>unnormal in JrComm (so it's not AE fault, (don't ask what's
>exactly wrong)

  Why do people consistently manufacture drek such as this?

  The AE 2000 modem had a problem in that the serial.device driver could
not deal with the block buffered serial I/O that JR-Comm uses.

  -jack-