Xref: utzoo comp.sys.amiga:17937 comp.sys.amiga.tech:451
Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!pike.cis.ohio-state.edu!mills-c
From: mills-c@pike.cis.ohio-state.edu (Christopher Mills)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Assembler Help
Message-ID: <11230@tut.cis.ohio-state.edu>
Date: 21 Apr 88 16:01:02 GMT
References: <12542@pbhya.PacBell.COM> <3664@cbmvax.UUCP>
Sender: news@tut.cis.ohio-state.edu
Followup-To: mills@baloo.eng.ohio-state.edu
Organization: The Ohio State University Dept of Electrical Engineering
Lines: 23

In article <3664@cbmvax.UUCP> steveb@cbmvax.UUCP (Steve Beats) writes:
>In article <12542@pbhya.PacBell.COM> hb@pbhya.PacBell.COM (Henry Bitter) writes:
>>...  I need to know how you get the command line information using 
>>assembler....
>
>
>If you need to access the name of the program (equivalent to argv[0] in 'C')
>you will have to open DOS library, find your task with FindTask(0) and fish
>the pointer to the command name out of the CLI struct in your process header.

	Or you could just link in c.o or astartup.obj and name the entry
point to your program __main.  Then it does all the workbench/CLI startup
for you.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 _____________________           |     Christopher Mills.
(_)________________   \          |     mills@baloo.eng.ohio-state.edu
  ________________|\   \         |     mills-c@pike.cis.ohio-state.edu
 (_)______________\_\   \        |     Current Thought: I really should be
   ______________________\       |          doing my thesis now...
  (_)____________________|       |     DISCLAMER: I really wish I could blame
                                 |          my thoughts on someone else...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-