Well, actually no.  I did the fixing on the fly.  I only compiled it so   
one of our QA people could test a reported bug with telnet.

The way I got everything functional was by replacing every offending   
error_message with a printf.

What was/is happening is the error_message function, the author of TIN   
wrote, accepts two parameters.  Most of the time the author properly   
passes two parameters to error_message.  But occasionally the author only   
passes one parameter, which the gcc compiler doesn't like.  So the   
fastest way to fix the problems was to replace error_message with printf   
in those cases!

I was not able to get TIN to use NNTP.  So I compiled TIN to be run on   
the news server.  I really didn't have time to investigate this problem.

I got a mail message form someone else stating that there is a newer   
version of TIN, you might go I search of it.

jam
 ----------
From:  Jeffrey Wheat[SMTP:jeff@tad.cetlink.net]
Sent:  Friday, December 15, 1995 5:56 PM
To:  JohnAM
Subject:  Re: compiling TIN 1.1 patch10 why wont curses compile!!!

>
> I'm sorry I took up so many peoples time on this, the problems was in   
    

> some sloppy code (the error_message function) the author's inconsistent   
    

> use of this function.
>
> sorry and thanks for all the attempt to help me.
> jam
>

        So do you have patches now? I'd sure be interested in the   
changes.

 -jeff