Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!husc6!necntc!ames!ucbcad!ucbvax!DMRHRZ11.BITNET!HAHN_K From: HAHN_K@DMRHRZ11.BITNET Newsgroups: comp.sys.atari.st Subject: Pexec() description needed Message-ID: <8707162033.AA05828@ucbvax.Berkeley.EDU> Date: Thu, 16-Jul-87 16:34:25 EDT Article-I.D.: ucbvax.8707162033.AA05828 Posted: Thu Jul 16 16:34:25 1987 Date-Received: Sat, 18-Jul-87 08:44:49 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 19 Is there anybody in NETland who could provide me with a somewhat complete description of 'long Pexec(a,b,c,d)' ??? I understand that the first parameter can be 0 (i.e. load'n'go) or 3 (i.e. just load and return the basepage's address), but some rumours i heard claimed that there's a possibility to set it to 4 (i.e. take the basepage's address and execute the 'child') and even to five (perhaps that means 'disconnect the drive and rewrite the ROMs' or something else...)! I need to load a child-process (maybe two of them) and execute it/them some time later, but all the time they have to remain in memory, because they are incorporating interrupt-routines. So; what could Pexec() do for me? I'm sure you know. Thanks to all who reply. Klaus. -- Klaus Hahn -- Department of Psychology Gutenbergstr. 18 University of MARBURG D-3550 Marburg, West-Germany