Xref: news2.mv.net comp.os.msdos.djgpp:2994 Newsgroups: comp.os.msdos.djgpp From: mdruiter AT cs DOT vu DOT nl (Ruiter de M) Subject: Re: DJGpp compiling in 4megs Nntp-Posting-Host: galjoen.cs.vu.nl References: <4lfgjk$o89 AT anarchy DOT io DOT com> Sender: news AT cs DOT vu DOT nl Organization: Fac. Wiskunde & Informatica, VU, Amsterdam Date: Mon, 22 Apr 1996 14:31:13 GMT Message-ID: Lines: 25 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp hexorlex AT io DOT com wrote: : I'm trying to compile some stuff with DJGPP 2.0 in my puny little 4meg : 486. Trouble appears when I try almost anything in C++ and especially : with C++ and the GRX20 libs (i.e. internal errors out the wazoo!) : : I read that in the archives that this might be caused by CWSDPMI's small : heap size, so I tried heapfix, but that didn't do a bit of good -- though : it did produce internal errors at slightly different places. : : Has anyone else had experience compiling with such restrictions on their : memory? Or do I just have to go up to 16 meg? With my humble 386SX, I can compile small (C++) progs with only 2 Meg of memory. But sometimes my computer locks up (just like that) mostly during cc1plus.exe, contiuously trying to PrintScreen (int 5 or something?) This causes BEEP*BEEP*BEEP*BEEP until I reboot or huge amounts of screen dumps if I redirect my printer to a file with a TSR. Does anyone know WHAT causes the PrintScreen-interrupt to be invoked? GCC, CC1PLUS, CWSDPMI, DOS, BIOS, whatever. -- Groeten, Michel. http://www.cs.vu.nl/~mdruiter \----/====\----/ \ / \ / "You know, Beavis, you need things that suck, to have \/ \/ things that are cool.", Butthead.