Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!mcsun!unido!rwthinf!cip-s08.informatik.rwth-aachen.de!pmk
From: pmk@cip-s08.informatik.rwth-aachen.de (Michael Keukert)
Newsgroups: comp.lang.pascal
Subject: Re: Alien programs within TP5
Keywords: Turbo-Pascal alien/external programs
Message-ID: <1323@rwthinf.UUCP>
Date: 25 Sep 89 13:33:44 GMT
Sender: news@rwthinf.UUCP
Reply-To: pmk@cip-s08.informatik.rwth-aachen.de (Michael Keukert)
Organization: Informatik RWTH Aachen
Lines: 33

In Article 1136 of comp.lang.pascal: Erik Liljencrantz writes:

> With this approach the exact path and extension has to be known (of course you
> don't have to hardcode the path...). The other way is to let the command
> interpreter do the work (that is what COMSPEC contains, normally COMMAND.COM):
>
>   Exec(GetEnv('COMSPEC'),'/C '+ProgramName);
>                           ^^
>                           Switch to COMMAND.COM,. Has to be there...

Yes, of course. I simply forgot this feature (you know, writing on the terminal
while looking 5m to the right on the screen of the PC isn`t as exactly as   
quoting directly via cut/paste...).

You`re entirely right about the `/C`.

The thing with the {$M x,y,z} option is still a bit foggy to me. Even the
Borland-Handbook will not elaborate it satisfactionary (to me).

In my application (starting various sub-programs within one, hmm, let`s call
it "program-server") I used all the following options: 
{$M 51200,0,0}
{$M  1024,0,0}
{$M  4096,0,0}
and I haven`t remarked any differences.

So if you can explain it once again, I might learn it.

Yours ....

PMK@CIP-S01.INFORMATIK.RWTH-AACHEN.DE     ! Warning! UNIX-Newcomer!
Michael Keukert of 2:242/2 (Fido-Net)     ! No flames please .... 
PMK@EIKO.ZER           (Zerberus-Net)     ! ... I'm still learning.