X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.lang.misc,comp.os.msdos.djgpp Subject: Re: ANN: Seed7 Release 2011-11-11 Date: Thu, 17 Nov 2011 22:10:54 -0800 (PST) Organization: http://groups.google.com Lines: 19 Message-ID: References: <7037d719-14a3-4e62-8ebc-0fdbdbdf1db1 AT r9g2000vbw DOT googlegroups DOT com> <7LqdnYyCWN_TE1jTnZ2dnUVZ_v2dnZ2d AT earthlink DOT com> NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1321596771 11499 127.0.0.1 (18 Nov 2011 06:12:51 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Fri, 18 Nov 2011 06:12:51 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: b32g2000yqn.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0,gzip(gfe) Bytes: 2244 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pAI6U3WA007835 Reply-To: djgpp AT delorie DOT com Hi, On Nov 17, 4:44 pm, "Charles Sandmann" wrote: > >"Rugxulo" wrote in message > >news:a9b37d4c-a83d-4d88-be23-174d4fe9072a AT k10g2000yqn DOT googlegroups DOT com... > > It mostly (but not fully) seems to work. I can't remember why DJGPP > > will sometimes say "No swap space!" > > That message is from CWSDPMI.  It shouldn't appear, but adding > more memory or disk space should make it go away. I don't know what Seed7 was trying to do exactly, but I'm 99% sure it wasn't lack of RAM (as I had oodles). Now, disk space, maybe, because I was (at the time) running all atop a 100 MB RAM disk, including the (temporary) DJGPP install. But who knows, maybe he was intentionally trying to malloc a lot of space. (Well, I haven't messed with it again, and he never commented back, so I haven't worried too much about it.)