Path: utzoo!attcan!uunet!lll-winken!brutus.cs.uiuc.edu!unix.cis.pitt.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!mmdf
From: EVERHART@arisia.dnet.ge.com (Glenn Everhart: 215 354 7610 (8*747 7610))
Newsgroups: comp.sys.amiga
Subject: Re: AnalytiCalc woes
Message-ID: <13459@baldrick.udel.EDU>
Date: 10 Mar 90 16:56:59 GMT
Sender: mmdf@udel.EDU
Lines: 15

AnalytiCalc (Absoft fortran actually) didn't get along at all
well with Conman V1.3 release 1. There has been a later release
of Conman 1.3 (release 2); there may have been even a third release.
The problem does not occur with the later conman releases. The
workaround if you have conman 1.3 release 1 is not to use it as a
con: replacement (ok to use it for a shell replacement if you wish).
The other workaround is to get conman 1.3.2 or later. Has to do with
some packets being rejected by conman that were OK for the real con:
driver. Nothing I tried would allow conman 1.3 release 1 to work with
fortran applications. I suspect it has to do with the rewinds of the
console device Absoft makes necessary.
   The error 209 is probably illegal packet type and is due to conman.
It then acts as if control-C were typed and causes the program to be
aborted. 
Glenn