Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!otter.hpl.hp.com!otter!pwt
From: pwt@otter.hpl.hp.com (Peter Toft)
Newsgroups: comp.windows.ms.programmer
Subject: Re: 386MAX and Borland C++ 2.0
Message-ID: <72170005@otter.hpl.hp.com>
Date: 19 Mar 91 09:04:59 GMT
References: <11880003@hpdmd48.boi.hp.com>
Organization: Hewlett-Packard Laboratories, Bristol, UK.
Lines: 32


 Even without any fancy memory manager like 386^MAX, bcx seems to consistently
 crash my machine. The setup: Northgate 486/33 w/ 8 megs, standard Windows/
 Himem/Smartdrv, no interesting TSRs. If I go into bcx and rearrange or add
 editor windows, I am almost guaranteed to quickly die with a global protection
 fault. Something (the DOS extender, I assume) issues some messages about not
 being able to remove TKERNEL.EXE (this is bcx's memory manager) and then
 either locks up the machine (sometimes beyond even the reach of the 
 three-finger salute) or leaves it with no available application memory. Does
 this sound familiar to anyone?

 Pat

Did you load the Borland tkernel.exe before starting windows in standard mode?
You need a line like 

'tkernel hi=yes kilos=1000'.

If you do this, your memory setup will be much the same as mine, and I've had
no problems.

Peter

===============================================================================

Peter Toft,				ARPANET	pwt@hplb.hpl.hp.com
Hewlett-Packard Laboratories, 		JANET	pwt@lb.hp.co.uk
Filton Road,				UUCP	...!mcvax!ukc!hplb!pwt
Stoke Gifford,				CSNET	pwt%hplb.csnet@relay.cs.net
Bristol.				HPdesk	Peter TOFT / HPC600 / 05
BS12 6QZ.				Phone	UK (0272) 799910 ext 24245
United Kingdom.					Int'l +44 272 799910 ext 24245