Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!purdue!haven!uflorida!reef.cis.ufl.edu!jdb
From: jdb@reef.cis.ufl.edu (Brian K. W. Hook)
Newsgroups: comp.os.msdos.programmer
Subject: Re: TCC -S then using TASM and TLINK
Message-ID: <26776@uflorida.cis.ufl.EDU>
Date: 8 Feb 91 00:14:00 GMT
References: <1991Feb7.074923.1299@Solbourne.COM> <26755@uflorida.cis.ufl.EDU> <1991Feb7.194555.1080@Solbourne.COM>
Sender: news@uflorida.cis.ufl.EDU
Organization: UF CIS Dept.
Lines: 21


>If so, then you *MUST* link in C0.OBJ for your particular memory
>model.  This module gets executed first and will set up things like
>argc, argv, sets up global variables (eg _psp, _stklen, etc),  allows
>signal handlers to work, etc.  If you are getting program sizes of 37
>bytes, then there is no way you could be loading in this module as it

Well, when we were using argv and argc we looked at the .ASM and
determined that it was in fact trying to link in another module due
to an external declaration for __setargv (?).  This, instead of using
argv we grab the PSP using offset 0x80 from the current segment.  This
works fine when I use TCC the entire route instead of .ASM

>
>P.S.  It would help people answer your question if you *gasp* actually
>posted the source to the program you are having problems with. :-)

Didn't post the source since it was too long, and since I am uploading
and posting on a SUN and I have the MS-DOS machine at home...well, that
is kind of a pain.  Thought there would be a simple solution, but 
I guess not.