Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!drutx!mtuxo!houxm!whuxl!whuxlm!akgua!gatech!ut-sally!topaz!caip!daemon
From: daemon@caip.UUCP
Newsgroups: net.micro.amiga
Subject: They Gotta Be Kidding!!!
Message-ID: <1291@caip.RUTGERS.EDU>
Date: Mon, 17-Feb-86 16:51:05 EST
Article-I.D.: caip.1291
Posted: Mon Feb 17 16:51:05 1986
Date-Received: Wed, 19-Feb-86 01:02:58 EST
Sender: daemon@caip.RUTGERS.EDU
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 17

From: Louis A. Mamakos <louie@trantor.UMD.EDU>

I noticed this too.  I was recompiling my GfxMem program under the new lattice
compiler, and noticed this very strange behavor.  What I did is redefine my
main(argc, argv) function as _main(args).  This replaces the _main.c 
file that does the argc/argv hacking along with the bogus behavor of opening
this additional window.  Since I didn't need any of the arguments, this worked
ok.  You have to be careful in that the lattice unix compatable I/O routines
for stdin/stdout/stderr probably won't work.  Then again, you probably won't
be using these in this type of application.

Is there any interest in my reposting GfxMem.c to the mailing list?  I put
this hack in, as well as only displaying a single bar graph when there is
no 'fast' memory in the system.

Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
  University of Maryland, Computer Science Center - Systems Programming