Path: news1.icaen!apple2pd From: apple2pd@icaen.uiowa.edu (ISCA AppleII Librarian) Newsgroups: comp.sys.apple2.comm Subject: Spectrum 2.1 vt100 problem Date: 22 Nov 1997 04:16:30 GMT Organization: Iowa Computer Aided Engineering Network, University of Iowa Lines: 53 Distribution: world Message-ID: <655mau$5r0@server05.icaen.uiowa.edu> NNTP-Posting-Host: ground.isca.uiowa.edu Re: VT100 emulation in Spectrum 2.1 (Seven Hills software) I submitted a e-mail ? to 7-Hills tech support several months ago but I have never received a reply, so I will ask the users: Does anyone have a fix for handling the bell character (^G or \007) in vt100 mode in Spectrum 2.1? Spectrum drops several chars following a bell char if it is in a stream of chars. Eg, one of my oft used applics on my unix shell acct sends the following sequence (I'll use octal notation for and chars): \033[1;1H\007\033[7m No more pages \033[m\033[5;1H ...etc... This sequence positions the cursor at top left of screen, rings alert bell, and displays msg 'No more pages' in inverse (\033[7m turns inverse on) (\033[m turns inverse off/normal on) moves cursor down to fifth row etc. Proterm3.1 handles this faultlessly. Spectrum 2.1 shows 'No mor' in inverse, leaves cursor in wrong position, and the display left in inverse mode so all future chars received are inverse. Messy. At first, I thought Spectrum was mis-interpreting \033[m , but that is not the case. Spectrum misses several chars after a bell char. The above sequence works fine if the bell (\007) is left out. Also try this simple test from a ksh unix prompt: echo '1234567890\007123456789012345678901234567890' I get '123456789092345678901234567890' Spectrum missed 8 consecutive chars plus 1 more after the bell. So how can I fix Spectrum to handle a bell char in vt100 mode? My first untried guess is to use filtering and map \007 to NUL or something benign. But is there a more robust way to handle the bell? I would like to keep a warning sound. (My guess is that the Apple Bell routine is blocking interrupts too long, but that is just a guess.) Help? Suggestions? --Steve Nelson (apple2pd@isca.uiowa.edu) (steven-nelson@uiowa.edu) (snelson@mozart.peds.uiowa.edu) -- --Steve (apple2pd@isca.uiowa.edu) Path: news1.icaen!news.uiowa.edu!news1.chicago.iagnet.net!iagnet.net!newsfeed.direct.ca!newsfeed.dacom.co.kr!innfeed.telstra.net!nsw.news.telstra.net!news.syd.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!comp.vuw.ac.nz!news.actrix.gen.nz!dempson From: dempson@actrix.gen.nz (David Empson) Newsgroups: comp.sys.apple2.comm Subject: Re: Spectrum 2.1 vt100 problem Date: Sun, 23 Nov 1997 17:47:49 +1300 Organization: Empsoft Lines: 26 Message-ID: <1d06m84.14n2q4od7q0owN@dempson.actrix.gen.nz> References: <655mau$5r0@server05.icaen.uiowa.edu> NNTP-Posting-Host: news2.actrix.gen.nz X-Newsreader: MacSOUP 2.3 ISCA AppleII Librarian wrote: > Does anyone have a fix for handling the bell character (^G or \007) in > vt100 mode in Spectrum 2.1? Spectrum drops several chars following a > bell char if it is in a stream of chars. This will be due to the beep generation mechanism locking out interrupts. How is your system beep configured? Have you tried changing between using the built-in beep and a generated sound? One or the other may perform better. > Proterm3.1 handles this faultlessly. ProTerm almost certainly doesn't lock out interrupts while generating an application-defined beep. Spectrum is probably relying on the standard system beep mechanism, which may lock out interrupts. > My first untried guess is to use filtering and map \007 to NUL or something > benign. I think that is what I ended up doing with Spectrum 2.0. -- David Empson dempson@actrix.gen.nz Snail mail: P.O. Box 27-103, Wellington, New Zealand Path: news1.icaen!news.uiowa.edu!news1.chicago.iagnet.net!iagnet.net!newsfeed.direct.ca!Supernews60!supernews.com!nntp.primenet.com!news.asu.edu!hurry From: hurry@imap2.asu.edu Newsgroups: comp.sys.apple2.comm Subject: Re: Spectrum 2.1 vt100 problem Date: 23 Nov 1997 20:58:21 GMT Organization: Arizona State University Lines: 21 Distribution: world Message-ID: <65a5dd$anu@news.asu.edu> References: <655mau$5r0@server05.icaen.uiowa.edu> Reply-To: adam.myrow@asu.edu NNTP-Posting-Host: general2.asu.edu X-Newsreader: TIN [version 1.2 PL2] The problem you are describing is somewhat common among GS applications. What happens is that the ringing of the bell causes an "interrupt" that stops all other activity so that the bell doesn't sound funny if something else interrupts it in midstream. Unfortunately, this causes character loss. What ProTERM does and apparently Spectrum doesn't is to make a custom bell that doesn't interrupt the system. The way to fix this in Spectrum and any other application is to replace the bell sound system wide. After all that technical talk, the real answer is simple. Go to the FTP site apple2.archive.umich.edu. Look in the pub/apple2/gs/system folder for a file called something like irq.bell.bsq. Get it and use BinScii (I think Spectrum also will work.) This should produce either a Shrinkit file or a PIF. Unshrink if needed and place the resulting file (simply called bell) into your boot disk's system/system.setup folder and reboot. From now on, the bell sound should be a low beep and shouldn't conflict with anything else although it may sound a bit weird at times. Good luck. -- Adam Myrow Path: news1.icaen!news.uiowa.edu!news1.chicago.iagnet.net!streamer1.cleveland.iagnet.net!iagnet.net!news-xfer.siscom.net!news.bconnex.net!not-for-mail From: CUTjefbla@bconnex.net (Jeff Blakeney) Newsgroups: comp.sys.apple2.comm Subject: Re: Spectrum 2.1 vt100 problem Date: Sun, 23 Nov 1997 23:07:14 GMT Organization: Barrie Connex Lines: 35 Message-ID: <3478b139.3853922@news.bconnex.net> References: <655mau$5r0@server05.icaen.uiowa.edu> Reply-To: CUTjefbla@bconnex.net (Jeff Blakeney) NNTP-Posting-Host: pm8-161.barrie.connex.net X-Newsreader: Forte Free Agent 1.1/32.230 On 22 Nov 1997 04:16:30 GMT, apple2pd@icaen.uiowa.edu (ISCA AppleII Librarian) wrote: [snip] >My first untried guess is to use filtering and map \007 to NUL or something >benign. But is there a more robust way to handle the bell? I would like >to keep a warning sound. (My guess is that the Apple Bell routine is >blocking interrupts too long, but that is just a guess.) Well, you seem to have come up with my solutions on your own. :-) I had to tell Spectrum to strip the bell character a few years ago because I used to get a string of bells whenever I logged onto a certain BBS. Since I no longer call that BBS I've reset things to the defaults. This is the quickest method to get you working online again. My next suggestion would be to use the Sound Control Panel to change the System Beep to the SimpleBeep that is included with System 6.01. It is much shorter in duration that the standard beep. I remember that v2.0 of Spectrum would override the Sound CDEV's settings under certain circumstances which defeated this fix but I can't remember when it did this. I don't know if this was changed in v2.1 as I haven't upgraded yet. I should be upgrading in the next week or two so I can take advantage of SevenHills' christmas sale. And finally, the only other thing I could suggest is to ensure that you have a properly wired hardware handshaking cable and/or that the hardware handshaking checkbox in the Port Settings dialog is checked. Good luck. === I've had enough SPAM. Cut the obvious from my address to email me. ===