Xref: utzoo comp.sys.ibm.pc.misc:8410 comp.windows.ms.programmer:1753 Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord From: mlord@bwdls58.bnr.ca (Mark Lord) Newsgroups: comp.sys.ibm.pc.misc,comp.windows.ms.programmer Subject: Re: Using Borland C++ Message-ID: <6427@bwdls58.bnr.ca> Date: 9 Apr 91 14:12:26 GMT References: <1991Apr5.171426.28904@SanDiego.NCR.COM> Sender: mlord@bwdls58.bnr.ca Reply-To: mlord@bwdls58.bnr.ca (Mark Lord) Organization: Bell-Northern Research, Ottawa, Canada Lines: 49 In article <1991Apr5.171426.28904@SanDiego.NCR.COM> davel@booboo.SanDiego.NCR.COM (David Lord) writes: <... Overall I like the compiler and the IDE a lot bc20p1.zip <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. This is *much* faster outside of Windows on my 386SX. One idea is to either close all of your ELVIS windows first, or assign 100% of CPU to the foreground. ELVIS is a real CPU hog, using a polling loop to read the keyboard. Perhaps TAME could be of help here. <2) Using the debugger TDW causes my mouse cursor to vanish in Windows. The < result is that I have to exit Windows everytime I finish with the Somebody else has also noticed this bug. < I have now found a rather kludgy way around it, I wrote a windows < program which calls ShowCursor(1). After exiting the debugger I < run this program and it gives me my cursor back. Post it!!