From:	"Michael Stewart" <mike AT reggin DOT freeserve DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP beginner's question - clrscr()
Date:	Fri, 6 Aug 1999 15:09:38 +0100
Organization:	(Posted via) Netcom Internet Ltd.
Message-ID:	<7oeqd6$2g5$1@taliesin.netcom.net.uk>
References:	<7oedln$uf2$1 AT nnrp1 DOT deja DOT com>
NNTP-Posting-Host:	hgty.capgemini.co.uk
X-Trace:	taliesin.netcom.net.uk 933948646 2565 194.42.240.2 (6 Aug 1999 14:10:46 GMT)
X-Complaints-To:	abuse AT corp DOT netcom DOT net DOT uk
NNTP-Posting-Date:	6 Aug 1999 14:10:46 GMT
X-Newsreader:	Microsoft Outlook Express 4.72.3155.0
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3155.0
Lines:	22
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

haphillips AT my-deja DOT com wrote in message <7oedln$uf2$1 AT nnrp1 DOT deja DOT com>...
>In my first try at using the DJGPP C compiler, I compiled and ran in a
>Win98 DOS box a short C program that I had compiled using Turbo C v. 2
>(yes, I still have it!).  gcc compiled my program without
>error, but clrscr() produced a runtime error.  I don't have a clue why
>and would appreciate anyone's help.


Can you post the smallest snippet of code which will produce this error.

>The Turboc C exe file was 17,910 bytes, and gcc's 137,789 bytes.  Why
>such a big difference?


gcc produces protected mode code. As such there is additional code to enter
protected mode, set up things etc. I seem to remember Turbo C being a real
mode compiler.

There was a discussion on this subject a while ago, try looking in the
archives for the thread.

- Raw text -