TIP: Click on subject to list as thread! ANSI
echo: cis.tandy.coco
to: Darrell Coffey 76106,767 (X)
from: Kevin Darling (UG Pres) 76703,4227
date: 1990-06-12 06:44:23
subject: #4274-#syscall blues

#: 4288 S10/Tandy CoCo
    12-Jun-90  06:44:23
Sb: #4274-#syscall blues
Fm: Kevin Darling (UG Pres) 76703,4227
To: Darrell Coffey 76106,767 (X)

Darrell,

You're real close. As I think I mentioned just before, SS.MpGPB is a SETstt,
not a getstt as shown in many early manuals. So that should be $8E, not $8D.

Also, some other tips:

1. Once you get it working, be sure to change it so that your process ID is
used as the group number... and Killbuff the group first so that any previous
attempts don't return an error. Oops! I see you're doing the ID bit. Good!

2. Check the returned error code.
     RUN syscall (blah, lah)
     IF land(reg.cc,1)0 then
       PRINT "Error number: "; reg.b
     PAUSE
     END
     ENDIF

3. There's an oddity with the Grfdrv length checking. You can't do a
GET(0,0,640,1) to get the entire line. But no problem for now, as the 639
actually ends up getting the last pixel into the buffer anyway (watch out for
PUTs tho). A lot of us do half the line at a time instead (320).

4. Get my GPMAP.B09 from Lib 10, if you don't have it. Good for checking on the
buffers.

5. If you do map in a buffer, and then later kill it... it may still be taking
up space in your basic09 map. Use PMAP to check, and if needed, save the
program and quit/restart basic09. Debugging a new program is about the only
time you should have to, tho.

6. If you need to post your program again, just send it and then do a "su" for
"store unformatted" in a message. So you don't have to type it in by hand or
make spaces on each line. Do this only for code, tho.

I think that's all for now. Keep at it! best - kev

There are 2 Replies.

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™.