Path: utzoo!mnetor!uunet!husc6!hao!ames!pasteur!ucbvax!RADC-LONEX.ARPA!koziarzw
From: koziarzw@RADC-LONEX.ARPA
Newsgroups: comp.sys.zenith.z100
Subject: (none)
Message-ID: <8803120020.AA09863@radc-lonex.arpa>
Date: 12 Mar 88 00:20:20 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 73

Mail to:	info-hz100@radc-tops20.arpa	Date: Fri Mar 11 19:18:57 1988
From: koziarzw@radc-lonex.arpa
Sender: koziarzw@radc-lonex.arpa
Subject:	TurboC & Z100
cc:		none
Message:

Some clarifications seem to be in order here...


>        Well, Turbo C works on the Z-100.... sortof.  tcc, the command line
>version of Turbo C works without any emulation, produces normal DOS code,
>and has no problems.  You will obviously have problems if you try to use
>any of the obvious IBM specific calls (grapics, sound, bios...) will not
>work, but standard calls will definately, just like Microsoft C, or whatever.
>tc will work with ZPC very well...  I ran it in the monochrome mode once or
>twice, and had no problems... again, it will produce the same code, the
>intergrated enviroment is just a front end.

By using 'TCC.EXE' from VERSION 1.0 and sticking to ANSI C or K&R definitions
of C, it is possible to successfully develop programs.  This is ONLY TRUE of
Version 1.0!!!!!!!!! (If you still have your Version 1.0 -- KEEP IT --
Version 1.5 is totally MUCKED UP, I have little doubt that only the
dedicated Z-100 wizards at Clarkson University can save us all from the
evil I(nferior) B(ut) M(arketable) functions in the library of TurboC
Version 1.5.)

A partial list of useful functions which no longer work --

cprint..., cput..., getc..., putc..., and most relatives of these.

I have been attempting to graft portions of the Version 1.0 library
into the version 1.5 library and have had 'localized success' -- some
alterations will work; but others will not due to inter dependancies in
the library modules.  I am still trying to solve this problem...




>        NOTE --  All of these comments are relative to Turbo C 1.0.  I have
>1.5, but haven't been able to test it out... and I remeber that there may be
>aproblem with the default printf() <-- 'printf()' is one that does
					 still work.

>and all other screen writes in 1.5 from
>something they said in the update.  If this is the case, it would only
>involve setting the mode each time, or hacking the .h files...
						     ^
						   / | \
						     |
					       THIS DOES NOT HELP



The integrated development environment caused problems with my machine --
I got memory allocation errors and the system crashed.  Avoid use of this
version of the compiler!!!!
I used ZPC Version II, sure the programs seemed to compile correctly;
but DO NOT try to run them..... (from within the TC environment)

With luck the 1.5 problems will be solved, I have contacted Gern and
hopefully we can rectify this evil plot by Borland and the other followers
of the Big Blue Menace.....

                                                _____________
                                                  /
                                               --/ __ _______
                                              (_/ (_) / / / <_ Livingston
                                              { decuac,ihnp4 }!netsys!tsl


Comments by: Koziarz@RADC-multics.arpa
     AKA:    koziarzw@RADC-lonex.arpa