Xref: utzoo comp.sys.ibm.pc.misc:8498 comp.windows.ms.programmer:1794
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!emory!hubcap!ncrcae!ncr-sd!iss-rb!booboo!davel
From: davel@booboo.SanDiego.NCR.COM (David Lord)
Newsgroups: comp.sys.ibm.pc.misc,comp.windows.ms.programmer
Subject: Re: Using Borland C++
Message-ID: <1991Apr11.162855.10164@SanDiego.NCR.COM>
Date: 11 Apr 91 16:28:55 GMT
References: <1991Apr5.171426.28904@SanDiego.NCR.COM> <1038@stewart.UUCP>
Sender: rock1@SanDiego.NCR.COM
Reply-To: davel@booboo.SanDiego.NCR.COM (David Lord)
Organization: NCR Corporation, Rancho Bernardo
Lines: 57

davel@booboo.SanDiego.NCR.COM (David Lord) (that's me!) writes:

>1) Linking even a minimal Windows program on my 386SX takes twenty minutes.
>   Using Hyperdisk in Staged Write mode will cut the time down to about five.

I've gotten about a zillion suggestions on how to make this go faster, many
of which I haven't had a chance to try yet. First thing I found was that
adding a permanent swap file and switching from SMARTDRIVE to HYPERDISK gave
a moderate speed improvement. Running HYPERDISK in STAGED WRITE mode gave
an even bigger improvement. I gather from what other people have said that
this merely causes my swapping to be memory-to-memory rather than
memory-to-disk.

Other suggestions I have received:
1) Compile outside of Windows.

	Not really practical most of the time, didn't seem to make much
	difference anyway.

2) Same as 1) but use a memory manager.

	I'm running QEMM 5.1. System has 4 meg. One meg. is allocated to
	HYPERDISK.

3) Run BCX (protected mode compiler).

	This means running Windows in REAL mode. Sounds awful, but I'll
	try. Actually I thought I had tried this at one point, but I
	don't remember just what I was doing at the time. Since BC shows:
	"175k memory remaining" the whole time I'm linking I didn't
	think swapping was the problem.

4) Run BC in Windows using a pif file with 1.5 meg of EMS memory LOCKED.

	When I start BC as an Aporia Tool it starts up in the directory
	I'm currently working in (the one the Tree Tool is pointed at).
	When I tried to use a pif this didn't happen anymore, which is
	a real pain. Anyone know a way around this?

Oh, and I've heard that the problem I have with the mouse cursor dissapearing
doesn't happen if you are using Windows' Program Manager. Unfortunately
hell hasn't frozen over yet so I'm going to to keep using Aporia.


In article <1038@stewart.UUCP> jerry@stewart.UUCP (Jerry Shekhel) writes:

>I have a question about pre-compiled headers.  This feature is a miracle,
>but it seems like a new header image (.SYM) needs to be created during the MAKE
>process whenever a file is compiled which includes a set of headers which is
>different from the current .SYM image.  In other words, the project maintains
>only one .SYM image.  So if your project contains two files, each including
>a different set of headers, turning on the pre-compiled header option doesn't
>save you any time.  Is there a way around this, so that the project can
>handle multiple .SYM files (disk space is not a problem)?

Use the same headers in each module :-). Actually I think only the first few
have to be the same.