Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!princeton!chiu
From: chiu@princeton.UUCP (Kenneth Chiu)
Newsgroups: net.micro.amiga
Subject: Re: Memory && Disks && Flicker
Message-ID: <2205@princeton.UUCP>
Date: Sun, 26-Oct-86 07:59:35 EST
Article-I.D.: princeto.2205
Posted: Sun Oct 26 07:59:35 1986
Date-Received: Mon, 27-Oct-86 01:23:52 EST
References: <2834@garfield.UUCP>
Reply-To: chiu@princeton.UUCP (Kenneth Chiu)
Organization: Princeton University Computer Science Department
Lines: 24
Keywords: *subject_line

In article <2834@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
>. . .if it[Manx] gets low on memory while compiling, it just does less
>optimizing, builds smaller tables, and sometimes doesn't delete the .asm file.
>It knows it is running out and takes steps to prevent it. However, . . .if not
>enough memory can be saved by the above steps, it seems like it crashes. . .

Hmm. . . I've never had it crash on me like that.  Mine says "Out of memory!"
BTW, how do you know it takes these economizing steps?

>Off the topic: when I receive files Kermit-wise, they become double spaced. Any
>way to avoid this?

Make sure both ends are on the same wavelength, either image or CR/LF.

>Blue disks work. Tan-coloured ones don't. This is not theory, it is (suitably
>disclaimered) fact. Blue disks, whether they have some company's name on them
>or are no-names, last forever. . . Tan coloured disks, whether they have some
>company's initials on them or are no-names, cannot stand up to writing.

Maybe blue disks aren't as permeable to cosmic radiation.  Why don't you try
putting the tan ones under a pyramid. :-)
-- 
Kenneth Chiu                                              UUCP: princeton!chiu
Princeton University Computer Science Department        BITNET: 6031801@PUCC