Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!usenet From: mcdonald@aries.scs.uiuc.edu (Doug McDonald) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Problems with GCC for DOS and Windows 3.0 Message-ID: <1991Feb26.185447.6576@ux1.cso.uiuc.edu> Date: 26 Feb 91 16:38:31 GMT References: <1991Feb26.163831.15110@sis.uucp> Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana Lines: 29 In article <1991Feb26.163831.15110@sis.uucp> doug@sis.uucp (doug berry) writes: >In article > cwinemil@keys.lonestar.org (Chris Winemiller) writes: >[...] >>20MHz clone, 4M memory, running Windows 3.0 in 386 enhanced mode. When >>I crank up the gcc compiler, it blasts my whole system out of the water >[...] > >The same thing happens here when i try to use JOVE to do a compile >with gcc using make... i think gcc wants the *whole* machine. > >-- It does. It is a 386 native mode thing - and so are products made with it. This is a problem with ANY 386 product - AutoCad 386, MAthematica, the Phar LAp 386 extender and things that use it, commercial 386 compilers such as Microway. There was a standard method acctepted before Windows 3.0 for accessing 386 extended memory called VCPI. Microsoft simply ble that off and devised a new, incompatible method that locks out older VCPI products. The gcc may not even obey VCPI, I don't know. Many commercial products are promising to make their things run under the new "standard", but, of course, most of these people are going to want you to pay money for an "upgrade". Doug McDonald