Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!think!nike!ucbcad!ucbvax!CORY!dillon
From: dillon@CORY (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: Easy fix to fexecv compatibility problems.
Message-ID: <8610230710.AA18375@cory.Berkeley.EDU>
Date: Thu, 23-Oct-86 03:10:44 EDT
Article-I.D.: cory.8610230710.AA18375
Posted: Thu Oct 23 03:10:44 1986
Date-Received: Thu, 23-Oct-86 18:58:17 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 21


>>	Or something like that.  Then, when you need specific BCPL stuff,
>>just look at _Startup_Regs instead of meandering through DOS.
>
>Ah, but can you be sure that the CLI will give you the same initial register
>values that it would give a BCPL program?  I do believe that they are quite
>different.

	Well, since the C startup registers and BCPL startup registers
don't conflict, I figure nobody will bother to check which type of
executable is being loaded (if it's even possible).  Besides, Manx's
(and my own) fexecv require the parent to have a CLI, and anything running
from a CLI will be given the BCPL startup enviroment in the registers on
startup.

	After about 30+ hours of hacking, I have finally got my SHELL
(V2.03) to do the right thing for every BCPL program except RUN (and
nothing has ever worked right with RUN redirection anyway so I'm not
going to bother).

				-Matt