KXH105@PSUVM.BITNET ("Ken Hornstein 862-7007", 814) (08/29/90)
Two questions: I am trying to write some assembler programs that can be executed as immediate commands. I know all interrupts are masked, but does the program receive control under normal Standar Linkage Conventions (ie - R14 has return address) or is the return PSW stored somewhere? And if the return PSW is stored somewhere, then where is stored (I assume it's in NUCON)? On a different note, I am trying to get a console beep WITHOUT that funky "RRRIII....IIINNN....NNNGGGG" message generated by CP (or "BEEEEEEEPPP" if you are on a XA system). I am using SIO with a CCW control code of X'0B' to generate a console printer ring ... is there a better/easier/harder way that doesn't generate that message by CP? --- Hypocrisy is the Vaseline of social intercourse. Ken Hornstein kxh105@psuvm.psu.edu Phone: 814/862-7007
TROTH@RICEVM1.RICE.EDU (Rick Troth) (08/29/90)
>On a different note, I am trying to get a console beep WITHOUT that funky >"RRRIII....IIINNN....NNNGGGG" message generated by CP (or "BEEEEEEEPPP" if >you are on a XA system). I am using SIO with a CCW control code of X'0B' to >generate a console printer ring ... is there a better/easier/harder way that >doesn't generate that message by CP? You're right that it's generated by CP. I thought that by doing SIO with command code X'0B' I'd be able to avoid the text, but NNOOOOO. Legend says that it's kind of an inside joke with the VM developers in that one of the real consoles on some older model of 370 (who's number escapes me) had an obnoxious fire alarm style bell. GONE EXEC (and probably others) mask it by SAYing '1D1C'X before and '1DF0'X after invoking BEEP. Those are 3270 orders which set the attributes to "no display" and "display" respectively, so the verbose "RRRR....RING....GGGG" still shows up in your console log (if SPOOLed), but not on your screen. You could probably write your own BEEP which would spit those out using X'09' with the X'0B' in between. Rick Troth <TROTH@RICEVM1.RICE.EDU> ------------- Rice ONCS VM Systems Support
JIM@AUVM.AUVM.EDU (Jim McIntosh) (09/01/90)
In article <ASM370%90082908493406@OHSTVMA.BITNET>, Rick Troth <TROTH@RICEVM1.RICE.EDU> says: > You're right that it's generated by CP. I thought that by doing >SIO with command code X'0B' I'd be able to avoid the text, but NNOOOOO. >Legend says that it's kind of an inside joke with the VM developers in >that one of the real consoles on some older model of 370 (who's number >escapes me) had an obnoxious fire alarm style bell. The 360/40 console had an alarm bell that would wake the dead, but that would have been before VM (even as CP-67) was around. --- Jim McIntosh (JIM@AUVM) The American University Washington DC 20016 USA
PROHVK05@TREARN.BITNET (Bahri Bora BALI AG) (09/02/90)
If You don't want to see 'RRRRRINNNNNNNGGGGGGGGG' or 'BEEEEEEEEEEEEPPPPP' on your screen after terminal shouting, you can make it invisible by writing '1d4c'x before pinching your screen by X'0B'.. Happy hacking. -Bahri Bora Bali Someone
jwagner@phoenix.Princeton.EDU (John Wagner) (09/04/90)
In article <9008311950.AA28633@ucbvax.Berkeley.EDU>, JIM@AUVM.AUVM.EDU (Jim McIntosh) writes: |> In article <ASM370%90082908493406@OHSTVMA.BITNET>, Rick Troth |> <TROTH@RICEVM1.RICE.EDU> says: |> > You're right that it's generated by CP. I thought that by doing |> >SIO with command code X'0B' I'd be able to avoid the text, but NNOOOOO. |> >Legend says that it's kind of an inside joke with the VM developers in |> >that one of the real consoles on some older model of 370 (who's number |> >escapes me) had an obnoxious fire alarm style bell. |> |> The 360/40 console had an alarm bell that would wake the dead, but that |> would have been before VM (even as CP-67) was around. Before VM, yes, but not before CP-40. The original CP and CMS were developed on a modified 360/40. The modification was for a DAT (dynamic address translation) box. John Wagner