Xref: utzoo comp.sources.d:6538 comp.sources.games.bugs:1800
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!nstar!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.sources.d,comp.sources.games.bugs
Subject: Re: MDG is NEAT! Um...
Message-ID: <1991Feb24.182503.3387@jwt.UUCP>
Date: 24 Feb 91 18:25:03 GMT
References: <1991Feb21.021206.1085@coplex.uucp> <1991Feb23.191404.4767@hotb.radig.de>
Organization: Private System -- Orlando, FL
Lines: 15

In article <1991Feb23.191404.4767@hotb.radig.de> thomas@hotb.radig.de (Thomas Brettinger) writes:
>I did not notice this, but another problem relatet to screen io:
>on the console or the virtual screens, the game is running fine.
>But it hangs on a serial line at a fputs(SOMETHING, stderr) statement.

I found possibly the same problem with ESIX.  The game runs fine from the
console.  I ran it from a serial port, and it would always hang during one
of the initial fputs(WHATEVER, stderr) calls when mdg first loads.  But --
I replaced the serial driver with FAS 2.08, and the problem went away.
I wonder if the ESIX and ISC asy drivers have common heritage, and have
some sort of bug?  Did you try a test program that just does
fputs(WHATEVER, stderr) to see if it hangs?  I've no longer got the stock
asy drivers in my kernel, so I can't test this.
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)