Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!jade!saturn!ssyx.ucsc.edu!koreth
From: koreth@ssyx.ucsc.edu (Steven Grimm)
Newsgroups: comp.sys.atari.st
Subject: Pexec() innards
Message-ID: <767@saturn.ucsc.edu>
Date: Thu, 10-Sep-87 03:40:22 EDT
Article-I.D.: saturn.767
Posted: Thu Sep 10 03:40:22 1987
Date-Received: Sat, 12-Sep-87 06:44:49 EDT
Sender: usenet@saturn.ucsc.edu
Reply-To: koreth@ssyx.ucsc.edu (Steven Grimm)
Organization: University of California, Santa Cruz
Lines: 26

Can anyone give me information about the innards of Pexec()?  I have the
following program...

#include <osbind.h>

main()
{
	long basepage;

	basepage = Pexec(3, "test.tos", "", 0L);
	printf("basepage = %08lx\n", basepage);
	Pexec(4, 0L, 0L, basepage);
	printf("done\n");
}

(test.tos is a single printf statement.)  The Pexec(4,...) bombs.  I've tried
putting the "basepage" parameter in each of Pexec()'s parameter positions,
with the same results all the time.  Jumping directly to the text segment
bombs, too.  What do I need to set up before executing a program?  I'd hate
to have to waste time writing my own memory management and process management
system, but if necessary I'll do it.

-------------------------------------
Steven Grimm,	koreth@ucscb.ucsc.edu
		koreth@ssyx.ucsc.edu
-------------------------------------