Path: utzoo!utgpu!watmath!clyde!att!osu-cis!killer!mjbtn!raider!dana.holt From: dana.holt@raider.MFEE.TN.US Newsgroups: comp.sys.amiga Subject: ST PROGRAMMING Message-ID: <36@raider.MFEE.TN.US> Date: 25 Nov 88 12:51:00 GMT References: <3009@sugar.uu.net> Sender: bbs@raider.MFEE.TN.US Organization: RaiderNet Public Access (#2), Murfreesboro, TN Lines: 49 This reply is directed toward the cooment you made about the Atari ST inability to survive a ^C in any of the built-in input functions. Well, this message is to set that straight. I do assembly,Pascal,and 'C' on an ST and there are built-in functions (in the OS) to allow for input which will ignore the ^C keys. If you are stupid enough to write a trap handler to fix the ^C problem I feel sorry for you. I can write a piece of assembler off the top of my head to do that: m start: move.w #$ff,-(sp) ; Function value to test keyboard move.w #6,-(sp) ; function number trap #1 ; call GEMDOS addq.l #4,sp ; correct stack tst.w d0 ; char arrived? beq start ; not yet cmp.b #3,d0 ; is it a ^C beq END ; if so then end if not go on move d0,-(sp) character for putput on the stack move #6,-(sp) ; function trap #1 ; call GEMDOS addq.l #4,sp bra start ; get new char end: clr.w -(sp) ; clear stack trap #1 ; call GEMDOS $00 (TERM) to exit (end assembly) That is off the top of my head. I magine what you could do with some time and planning. That was using GEMDOS function $06 which is not the best but it is the first that comes to mind as I do not have a list at this time.. ||| ||| //|\\ --------- % ATARI % --------- Dana Holt Rt.5 Box 119 M'boro, Tn 37130 VOICE: 615-896-5668 DATA : 615-896-6254 ' Amiga? What the hell is an Amiga? ' - ME