jtreworgy@eagle.wesleyan.edu (03/17/91)
In article <910316.180915.CST.C506634@umcvmb.missouri.edu>, C506634@UMCVMB.MISSOURI.EDU (Eric Edwards) writes: > In Message-ID: <2147@public.BTR.COM> > thad@public.BTR.COM (Thaddeus P. Floryan) said: >>Hmmm, wondering about all the recent flak over HandShake 2.20c, I recovered >>it from floppy (after doing "CLI> delete hand >>it (using the ARTM monitor ... great program, by the way) was the ONLY thing >>on my system bringing in the ARP library. And HandShake 2.20c is the ONLY >>thing on my system(s) that causes a guru without undue provocation. >> >>Are we "on" to something here? Just curious. > Doubtfull. The only part of ARP that Handshake uses is the file requester. > The major problems that people have been having with Handshake is with XPR's > especially Zmodem. > > For the record, here's another handshake bug that's been there since at least > 1.60b.. Under very low memory conditions or heavy fragmentation, try to open > the phonebook. LOCKUP. No messages, no guru. No problems with the rest of > the system but now you have a large application dead in the water, eating > memory. For those of us with only 1 meg, the only real option is a three finger > salute. I have found that Handshake is just not a stable program as long as I have tried to use it... I have had the same lockup problems with or without external protocols. The phonebook, as you said, causes lockups sometimes, I haven't noticed any correlation with low memory though... but the most annoying thing (I just don't use the phone book to avoid that one) is that random input (i.e. someone picks up the phone while modeming, or random line noise) can often cause a crash!!! This is not good. In my situation it crashes often enough to make it not very usable, or at least very frustrating, so I rarely use it nowadays and use VLT instead. (By the way I use the same Zmodem external protocol on both programs, and VLT has NEVER crashed on me under any circumstances. A very sound program.) This is fine for me since a VT100 is good enough for my needs.... another (peeve) about handshake is that it produces a vertical line on the right of the character position when there should be a space sometime. I don't know why; the circumstances are when running VMS news and a couple others. I don't know if there is some alternate space character which he didn't define properly, but it's not there on a REAL VT220. Well, that's enough whining for one day... -- James A. Treworgy -- No quote here for insurance reasons -- jtreworgy@eagle.wesleyan.edu jtreworgy@WESLEYAN.BITNET
C506634@UMCVMB.MISSOURI.EDU (Eric Edwards) (03/18/91)
In Message-ID: <1991Mar17.014544.40347@eagle.wesleyan.edu>
jtreworgy@eagle.wesleyan.edu said:
>In article <910316.180915.CST.C506634@umcvmb.missouri.edu>, C506634@UMCVMB.MISS
>> 1.60b.. Under very low memory conditions or heavy fragmentation, try to ope
>> the phonebook. LOCKUP. No messages, no guru. No problems with the rest of
>
>I have found that Handshake is just not a stable program as long as I have
>tried to use it... I have had the same lockup problems with or without external
>protocols. The phonebook, as you said, causes lockups sometimes, I haven't
>noticed any correlation with low memory though... but the most annoying thing
>(I just don't use the phone book to avoid that one) is that random input (i.e.
>someone picks up the phone while modeming, or random line noise) can often
>cause a crash!!! This is not good. In my situation it crashes often enough to
Did the program actually crash or did the keyboard just seem to go dead?
Like any good vt220 many of Handshake's settings can be changed with escape
sequences. For example, if you log into a VMS system in vt100 or vt102 mode
the host will interogate the terminal, discover that it's really a vt220 and
tell handshake to switch to vt220 mode! The problem is, sometimes line noise
can duplicate these sequences and put ther terminal in a very strange state.
The standard solution from 2.12 is to toggle to vt52 and back. (I don't
remember if reset terminal works or not)
Eric Edwards: c506634 @ "The 3090. Proof that by applying state of the
Inet: umcvmb.missouri.edu art technology to an obsolete architecture,
Bitnet: umcvmb.bitnet one can achieve mediocre performance."jtreworgy@eagle.wesleyan.edu (03/18/91)
In article <910317.154305.CST.C506634@umcvmb.missouri.edu>, C506634@UMCVMB.MISSOURI.EDU (Eric Edwards) writes: > In Message-ID: <1991Mar17.014544.40347@eagle.wesleyan.edu> > jtreworgy@eagle.wesleyan.edu said: >>(I just don't use the phone book to avoid that one) is that random input (i.e. >>someone picks up the phone while modeming, or random line noise) can often >>cause a crash!!! This is not good. In my situation it crashes often enough to > > Did the program actually crash or did the keyboard just seem to go dead? > Like any good vt220 many of Handshake's settings can be changed with escape > sequences. For example, if you log into a VMS system in vt100 or vt102 mode > the host will interogate the terminal, discover that it's really a vt220 and > tell handshake to switch to vt220 mode! The problem is, sometimes line noise > can duplicate these sequences and put ther terminal in a very strange state. > The standard solution from 2.12 is to toggle to vt52 and back. (I don't > remember if reset terminal works or not) I've had that happen and have done that... but what I mean is a real lockup, where the menus don't pop down anymore so I can't even try to reset the terminal. -- James A. Treworgy -- No quote here for insurance reasons -- jtreworgy@eagle.wesleyan.edu jtreworgy@WESLEYAN.BITNET
ewilts@janus.mtroyal.ab.ca (Ed Wilts) (03/20/91)
> enough for my needs.... another (peeve) about handshake is that it produces a > vertical line on the right of the character position when there should be a > space sometime. I don't know why; the circumstances are when running VMS news > and a couple others. I don't know if there is some alternate space character > which he didn't define properly, but it's not there on a REAL VT220. Well, > that's enough whining for one day... > -- > James A. Treworgy -- No quote here for insurance reasons -- > jtreworgy@eagle.wesleyan.edu jtreworgy@WESLEYAN.BITNET The vertical bar syndrome is also present when using VLT. Willy claimed that this is an OS bug; hopefully he has reported it to Commodore through the appropriate channels. It is there in both 1.3 and 2.0 (36.207/36.69). -- .../Ed Preferrred: Ed.Wilts@BSC.Galaxy.BCSystems.Gov.BC.CA Ed Wilts Alternate: EdWilts@BCSC02.BITNET (604) 389-3430 B.C. Systems Corp., 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
eric@haberfel.uucp (Eric Haberfellner) (03/27/91)
I have never seen this left over bar problem. Could you please capture
a session where this happens and mail it to me?
This is a good policy in general for people reporting HandShake bugs.
If you can capture the incoming data that causes the problem (Using
Amiga-C) I can then reproduce the problem here.
Eric :{)eric@haberfel.uucp (Eric Haberfellner) (03/27/91)
I see that my address looks a little strange in the last article I posted.
it should be one of:
eric@haberfellner.uucp
eric@haberfellner.uucp@uunet.uu.net
...utgpu!mnetor!becker!haberfellner!eric
Eric :{)dave@unislc.uucp (Dave Martin) (03/28/91)
From article <1991Mar17.014544.40347@eagle.wesleyan.edu>, by jtreworgy@eagle.wesleyan.edu: > In article <910316.180915.CST.C506634@umcvmb.missouri.edu>, C506634@UMCVMB.MISSOURI.EDU (Eric Edwards) writes: >> >> For the record, here's another handshake bug that's been there since at least >> 1.60b.. Under very low memory conditions or heavy fragmentation, try to open >> the phonebook. LOCKUP. No messages, no guru. No problems with the rest of > ... > enough for my needs.... another (peeve) about handshake is that it produces a > vertical line on the right of the character position when there should be a > space sometime. I don't know why; the circumstances are when running VMS news > and a couple others. I don't know if there is some alternate space character > which he didn't define properly, but it's not there on a REAL VT220. Well, > that's enough whining for one day... This line occurrs when the BOLD attribute is set and a space is printed. And now for my pet peeve: Soft characters (a reprogrammable font) DO NOT WORK! We have several home grown applications and games that use soft characters to turn a dull VT220 text terminal into a really snazzy graphics display. These programs work with real VT220's, VT320's, VT330's VT340's, and wyse 75 and 99gt's (although not as well on the 99gt's) Does the author read this group? I'll have to try mailing him a uuencoded example that he can copy into handshake through the serial port and watch handshake produce spaces galore instead of the reprogrammed characters. If anyone knows how to make this work in handshake please let me know. -- VAX Headroom Speaking for myself only... blah blah blahblah blah... Internet: DMARTIN@CC.WEBER.EDU dave@saltlcy-unisys.army.mil uucp: dave@unislc.uucp or use the Path: line. Now was that civilized? No, clearly not. Fun, but in no sense civilized.
ccplumb@rose.uwaterloo.ca (Colin Plumb) (04/01/91)
dave@unislc.uucp (Dave Martin) wrote: >Does the author read this group? I'll have to try mailing him a >uuencoded example that he can copy into handshake through the serial port >and watch handshake produce spaces galore instead of the reprogrammed >characters. Well, he's active in c.s.a.datacomm. eric@haberfellner.uucp, route it through uunet or bang it to utgpu!mnetor!becker!haberfellner!eric. I remember it being documented that either downloaded characters or keyboard maps didn't work, so it may be more of an enhancement request than a bug report, but let him know anyway. -- -Colin
jms@tardis.Tymnet.COM (Joe Smith) (04/17/91)
In article <102@haberfel.uucp> eric@haberfellner.uucp (Eric Haberfellner) writes: >I have never seen this left over bar problem. Could you please capture >a session where this happens and mail it to me? I run one application that repositions the cursor each time a character is input. The VT100 program does not handle this well; it leaves little bits of ghost cursor all over the place. The junk shows up as vertical bars at the border between two adjacent character positions. HandShake V2.20c has no problem with this. Good job Eric. 0000: 1B5B3231 3B394800 0000001B 5B306D74 .[21;9H.....[0mt 0010: 1B5B303B 353B376D 201B5B48 00000000 .[0;5;7m .[H.... 0020: 1B5B3231 3B313048 00000000 1B5B306D .[21;10H.....[0m 0030: 681B5B30 3B353B37 6D201B5B 48000000 h.[0;5;7m .[H... 0040: 001B5B32 313B3131 48000000 001B5B30 ..[21;11H.....[0 0050: 6D691B5B 303B353B 376D201B 5B480000 mi.[0;5;7m .[H.. 0060: 00001B5B 32313B31 32480000 00001B5B ...[21;12H.....[ 0070: 306D731B 5B303B35 3B376D20 1B5B4800 0ms.[0;5;7m .[H. 0080: 0000001B 5B32313B 31334800 0000001B ....[21;13H..... 0090: 5B306D20 1B5B303B 353B376D 201B5B48 [0m .[0;5;7m .[H 00A0: 00000000 1B5B3231 3B313448 00000000 .....[21;14H.... 00B0: 1B5B306D 691B5B30 3B353B37 6D201B5B .[0mi.[0;5;7m .[ 00C0: 48000000 001B5B32 313B3135 48000000 H.....[21;15H... 00D0: 001B5B30 6D731B5B 303B353B 376D201B ..[0ms.[0;5;7m . 00E0: 5B480000 00001B5B 32313B31 36480000 [H.....[21;16H.. 00F0: 00001B5B 306D201B 5B303B35 3B376D0A ...[0m .[0;5;7m. 0100: 201B5B48 00000000 1B5B3231 3B313748 .[H.....[21;17H 0110: 00000000 1B5B306D 611B5B30 3B353B37 .....[0ma.[0;5;7 0120: 6D201B5B 48000000 001B5B32 313B3138 m .[H.....[21;18 0130: 48000000 001B5B30 6D201B5B 303B353B H.....[0m .[0;5; 0140: 376D201B 5B480000 00001B5B 32313B31 7m .[H.....[21;1 0150: 39480000 00001B5B 306D741B 5B303B35 9H.....[0mt.[0;5 0160: 3B376D20 1B5B4800 0000001B 5B32313B ;7m .[H.....[21; 0170: 32304800 0000001B 5B306D65 1B5B303B 20H.....[0me.[0; 0180: 353B376D 201B5B48 00000000 1B5B3231 5;7m .[H.....[21 0190: 3B323148 00000000 1B5B306D 731B5B30 ;21H.....[0ms.[0 01A0: 3B353B37 6D201B5B 48000000 001B5B32 ;5;7m .[H.....[2 01B0: 313B3232 48000000 001B5B30 6D741B5B 1;22H.....[0mt.[ 01C0: 303B353B 376D201B 5B480000 00001B5B 0;5;7m .[H.....[ 01D0: 32313B32 33480000 00001B5B 306D201B 21;23H.....[0m . 01E0: 5B32323B 32480000 00001B5B 303B353B [22;2H.....[0;5; 01F0: 376D201B 5B480000 00001B5B 32323B0A 7m .[H.....[22;. 0200: 32480000 00001B5B 306D5379 6E746178 2H.....[0mSyntax 0210: 20457272 6F72202D 20747468 69732069 Error - tthis i 0220: 73206120 74657374 20697320 6E6F7420 s a test is not 0230: 61207661 6C696420 736C6F74 206E616D a valid slot nam 0240: 652E0A1B 5B32333B 32480000 00001B5B e...[23;2H.....[ 0250: 303B353B 376D201B 5B480000 00000A1B 0;5;7m .[H...... 0260: 5B32333B 32480000 00001B5B 306D2028 [23;2H.....[0m ( 0270: 50726573 73205245 5455524E 20746F20 Press RETURN to 0280: 636F6E74 696E7565 291B5B30 6D0A continue).[0m. -- Joe Smith (408)922-6220 | SMTP: jms@tardis.tymnet.com or jms@gemini.tymnet.com BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms PO Box 49019, MS-C51 | BIX: smithjoe | CA license plate: "POPJ P," (PDP-10) San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga 3000 speaks for me."