Xref: utzoo comp.unix.i386:7390 comp.emacs:8785
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!emory!ogicse!milton!gichan@blake.u.washington.edu
From: gichan@blake.u.washington.edu (Gilbert Chan)
Newsgroups: comp.unix.i386,comp.emacs
Subject: Problems with emacs (or Memory ??)
Message-ID: <5741@milton.u.washington.edu>
Date: 31 Jul 90 11:36:50 GMT
Sender: news@milton.u.washington.edu
Distribution: na
Organization: University of Washington, Seattle
Lines: 28

I'm posting this message for a friend, please direct all your responses
to him at bchan@ddn-eur.ddn.mil

__________________________________
I downloaded a binary copy of epoch.tar.z from sequent.kent.edu. 
When I tried to run emacs using emacs -nw (as described in the README file)
on a Gateway 33-386 (ASIC Micronic motherboard) with 4 Meg of RAM + 
150 Meg CDC HD running AT&T System V3.2.2, I got an error message "(12) bad
system call - core dump". [I don't have a working X installed on my 
system, I just want to use emacs.]
 
I wrote a simple program to print system error numbers and error messages.
Error #12 relates to "Not enough space". Is that mean that I don't have
enough memory?  Can anyone tell me what's going on?
 
I also got an error message "file too large" when I tried to uncompress
large files (> 1.2Meg compressed) while the same file uncompressed fine
on a Sun Sparc WS. I also tried compiling the compress.c (from Simtel20) 
using different -DUSERMEM=xxxx. The compress program works fine on smaller 
files and bombs on the big ones. Is that a way to assign memory ceiling on 
virtual memory under System V so that it can fool the sysem with more
RAM? 
 
You helps are greatly appreciated,
 
Brian
bchan@ddn-eur.ddn.mil