Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!dalcs!garfield!john13
From: john13@garfield.UUCP (John Russell)
Newsgroups: comp.sys.amiga
Subject: Conman strangeness
Message-ID: <4218@garfield.UUCP>
Date: Sun, 15-Nov-87 02:15:01 EST
Article-I.D.: garfield.4218
Posted: Sun Nov 15 02:15:01 1987
Date-Received: Tue, 17-Nov-87 03:19:45 EST
Distribution: na
Organization: CS Dept., Memorial U. of Newfoundland, St. John's
Lines: 25

--
There is a puzzling bug in the very late beta version of Conman which I am
wondering if it's present in the final version (I don't have that one).

My program fopen's a con: window, immediately locks IBase and grabs the
FirstScreen->FirstWindow pointer (this may not be failsafe, but it's not
vital that the correct window be found, just convenient). While IBase is
locked it redirects stdio from the con: window.

This has never given me any problems, yet when I ran it on a friend's machine
*2* identical con: windows were opened. The second one had its own cursor and
all, but it didn't receive or transmit any i/o to the program and remained
after the program exited and the other con: window closed. We identified
conman as the cause of this behaviour.

Could this be due to a non-implemented packet in conman, like the "no memory
in MORE" bug from a while back? And for anyone with release 1.0 or higher of
conman, have you ever seen a similar problem?

John

PS Anyone who mailed asking for my Panasonic printing program and hasn't
received it by the time you read this, please let me know by mail. I had
trouble reaching a few people, and tried under more than one path in some
cases. In particular wuphys!lel, Mike Schwager and Rick from QUCDNAST.BITNET.