Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!bullwinkle!uw-beaver!uw-june!entropy!dataio!bright
From: bright@dataioDataio.UUCP (Walter Bright)
Newsgroups: net.sources
Subject: Re: Micro Emacs
Message-ID: <932@dataioDataio.UUCP>
Date: Fri, 21-Mar-86 20:54:55 EST
Article-I.D.: dataioDa.932
Posted: Fri Mar 21 20:54:55 1986
Date-Received: Tue, 25-Mar-86 03:13:07 EST
Reply-To: bright@dataio.UUCP (Walter Bright
Organization: Data I/O Corp., Redmond WA
Lines: 20

In article <9936@ucla-cs.ARPA> stiber@ucla-cs.UUCP writes:
>After successful linking & compilation, I tried to edit
>a file (approx 30K).  I got a "stack overflow" error.
>I then tried rerunning emacs with successively larger
>stack sizes.  Sizes that cause that message to go away
>cause another, "Unable to read xx bytes" (xx = 16 or 64, usually),
>to appear.
>Has anyone gotten this to compile & run properly, with
>non-trivial files?  If so what's the secret?  The only
>things that I can think of are using a larger memory model
>(I'm using S, so it'll be fast), or a later version of the
>compiler (I'm using Microsoft C, ver 2.03).

I got it to run using Datalight C version 2.01. If you use the 'S'
memory model, you cannot edit files greater than about 25k bytes.
To edit large files, use the 'D' memory model.

MicroEMACS can be made to run MUCH faster if a driver is written to
write directly to the screen. If you do this, display.c should also
be modified to eliminate the 'physical' screen, it isn't necessary.