Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!emory!ox.com!math.fu-berlin.de!uniol!unido!pbinfo!pbinfo!wolff
From: wolff@pbinfo.uni-paderborn.de (Marcus Horstmann)
Newsgroups: comp.sys.amiga.programmer
Subject: WB2.0 SysTagList() (System()) Question
Keywords: WB2.0 System SysTagList
Message-ID: <1991May28.120933.4547@uni-paderborn.de>
Date: 28 May 91 12:09:33 GMT
Sender: wolff@pbinfo (Marcus Horstmann)
Organization: Universitaet-Gesamthochschule Paderborn
Lines: 24
Nntp-Posting-Host: dali

Hi,

I have a problem with the DOS-funktion Systaglist (older: System). It uses an own process for its work, so the shellrelated stuff like cd, prompt and so forth won't work correctly, i.e. a shell-script that puts me in a directory and leaves me there, works, but after Systaglist is completed I am back in my proccesec own currentDir.

So the question: How can I get the currentdir Systaglist uses at last?

I have tried it with the exitcodetag, but when the exitcode is run, it returns me
only a NIL(NULL)-lock from its processes currentdir. How can I get the correct one?

How works the Systags CustomShell and Usershell?

Thanx in advance

   Marcus

=======================================================================
==                         mail :  Marcus Horstmann                  ==
==       //  Amiga                 Liboriberg 22                     ==
==      //     is                  W-4790 Paderborn                  ==
==  \\ //     FUN!                 Germany                           ==
==   \X/   (Isn't it?)     Tel. :  ++49-5251-27406                   ==
==                         email:  wolff@uni-paderborn.de            ==
=======================================================================