TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: Kevin Darling 76703,4227 (X)
from: Kevin Darling 76703,4227
date: 1991-07-28 09:13:18
subject: #11516-you better read this

#: 11517 S10/OS9/6809 (CoCo)
    28-Jul-91  09:13:18
Sb: #11516-you better read this
Fm: Kevin Darling 76703,4227
To: Kevin Darling 76703,4227 (X)



 "Nothing covers F$SSWI.  When the SVC issues SWIn, do we "tack on" behind the
SWIn instruction with an OS9-like SVC Number?  If so, who "skips" over this
extra byte?"

Yes, you'd use a number (only if you needed one).  Here it gets tricky. When
the kernel jumps back to your program space, the passed SWI 1 or 3 registers
are, of course, on your own stack... and you'll need to load them from there.

What I don't understand, is how using F$SSWI is supposed to help?  All you'd be
doing is calling your own program code, which a LBSR could do easier :-)

What am I missing here?  Oh.  Are you talking about using those as extra vector
storage (like F$Icpt) into your process?  Or ?   - kevin

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.