Mail Archives: djgpp/1993/06/23/06:11:02
Mark Pflaging writes:
MP> I would also like some help with compiling a sample program. The
MP> "samples" directory contains a few samples but they are pretty lame. I
MP> tried to compile "compress.c" and it took like 10 minutes! Is this
MP> correct? The file is only 42k! I have a 486/33 with 8 meg & a fast 300
MP> meg hard drive. I have it set up so that 6 meg RAM is extended memory. I
MP> do not have qemm or 386max or any other junk like that. I took emm386 out
MP> of my config.sys. I do have a hard drive cache set up with "SMARTDRV.EXE",
MP> could this be causing the problem? Also I am using DOS 5, is that a
MP> problem? (DOS is loaded high).
I have experimented with a lot of CONFIG.SYS and AUTOEXEC.BAT settings
on various hardware using DJGPP. I think on a 8 Mb system the following
settings should work fine (DOS 5 and DOS 6):
config.sys:
===========
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE 5120 RAM (DJGPP now uses VCPI memory)
DOS=HIGH,UMB
autoexec.bat:
============
LH C:\DOS\SMARTDRV.EXE 2048 2048 /Q
DJ Delorie writes:
DJ> Run "mem". The search order for memory is as follows:
DJ>
DJ> 1. expanded memory
DJ> 2. XMS memory
DJ> 3. extended memory
DJ>
DJ> The first one found will be used. You want around 4M free to keep gcc
DJ> from paging. Programs such as SmartDrive and ramdisk eat away at your
DJ> memory very quickly.
MP> I am coming from the world of Borland C++ and maybe it has spoiled
MP> me a little bit.
Last days a lot of questions appeared on this list regarding the
usage of MAKE.EXE which comes with the latest Borland products.
(Borland C++ 3.1 and Turbo C++ 3.0).
Be aware that the standard MAKE.EXE which comes with these packages
tries to use all available DPMI memory if not instructed otherwise.
You'll notice this by a dramatic slow performance of DJGPP compiles.
There are two solutions to this problem:
(1) if you still want to use MAKE.EXE (and let it use extended memory)
include the following line in your environment (AUTOEXEC.BAT):
SET DPMIMEM=MAXMEM 2000
(2) But better: use the MAKER.EXE version which also comes with these
Borland products. To avoid typos, I renamed MAKE.EXE to MAKEE.EXE,
and MAKER.EXE to MAKE.EXE myself...
I have never encountered problems using the real-mode version MAKER.EXE.
I hope this solves the speed problems reported by various users
of DJGPP and Borland compiler products.
.^^^^^^^^ _____________________________________
| | / Pieter Kunst (P.J.) \
| _ _| / Philips Research Laboratories, \
.--(o)(o) / Building WY3, Prof. Holstlaan 4, \
|@ _) / 5656 AA Eindhoven, The Netherlands. |
| ,___| / e-mail: kunst AT prl DOT philips DOT nl /
| / \_______________________________________________/
/____\
- Raw text -