🚀 go-pugleaf

In article <2613@gold.gvg.tek.com> shaunc@gold.gvg.tek.com (Shaun Case) writes:
>In article <1991Jun24.133431.10280@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes:
>>In <i8Hrm1=@cs.psu.edu> melling@cs.psu.edu (Michael D Mellinger) writes:
>>>If my program is in someone's path, how can I tell where it's located
>>>so that I can get the supporting files that are needed with it?
>>
>>This is real easy in DOS.  argv[0] is the full pathname of the invoking
>>process.  I often do something like this:
>>
>
>... assuming you are using a version of dos above 2.10, which
>does not support argv[0].   People are still using it, unfortunately.
>
SoapBox: On

I would say to those running < DOS 3.1, "TOUGH!" We're THREE major
releases and a good 6 years from the time when 2.1 was released. I can
understand not fixing something that isn't broken, but if new software
breaks it, then the old DOS is broken, not the new program. Were it
the other way around, we would still be using dBASE II, Perfect Writer
and Perfect Calc on CP/M machines, or worse yet, TRS DOS.

SoapBox: Off


Cheers!
Steve

-- 
-------------------------------------------------------------------------------
        resnicks@netcom.com, steve@camphq, IFNA:        1:143/105.0, 
                 co moderator for comp.binaries.os2
 Real life: Steve Resnick. Chief Software Architect, Process Scientific, Inc
 Flames, grammar and spelling errors >/dev/null
 The Asylum OS/2 BBS - (408)263-8017 12/2400,8,1 - Running Maximus CBCS 1.2
-------------------------------------------------------------------------------