w8sdz%brl@sri-unix.UUCP (12/12/83)
From: Keith Petersen <w8sdz@brl> Bob, it sounded to me as if you might be thinking about updating MDM714 to include the RUGMDM routines and then possibly releasing it as MDM715. I'm all for that and now that Irv has released his iron hold on the program I would like to encourage you to do just that. However, I would like to see as many of the known problems fixed as possible at the same time. Toward that end, I am including a collection of some "bug" reports (some not really bugs, just annoying things). I hope others on this mailing list will send you notes (with copies to INFO-MODEM7@MC) about any other problems they have encountered. Here we go: ------- Date: 10/17/83 From: Dave Hardy To: All Re: MDM7 bugs? Two things that I've found in MDM7xx that I consider to be bugs: 1. Program hangs with CPM option when there is modem input 2. Program will not pass control characters to console that are necessary to run a video editor remotely, etc. Are these known "bugs," or am I the only one having these problems? I'm using standard MDM712 with SmartModem overlay and no special modifications. [NOTE FROM KEITH: It should be made clearer in the DOC file that the overlay must be configured to allow control characters from the modem to reach the console. Irv set all the overlays to "filter" unwanted control characters, apparently thinking that most people don't use the terminal mode with video-oriented text editors. Also the "gathering of available characters" from the modem should not be allowed to occur when the CPM command is given. The reason is that if the carrier is gone at this time (typical after completing a call) some I/O ports seem to lock up when DCD (Data Carrier Detect) goes false. I believe this is the cause of the lock-up condition that happens to some people (me included, on the system at work) under these conditions.] Date: 10/17/83 From: Tom Bering To: Dave Hardy Re: MDM712 The problems you're having with MDM712 are not peculiar to your system. MDM7xx will hang in a CPM command if there is data coming from the modem, but will drop to CPM shortly after the last character has been sent. I'll look at the source if I can make time and figure out what it's doing. Regarding the control characters you can't get to the terminal, there is a label IGNORCTL in the front end of the main pgm (and in the overlays) that will kill sending of control characters above ^M in terminal mode if it is set 'YES', which it is in these files. Maybe that's the problem?? My system is an H89 w/ZCPR2 and CP/M 2.2 and I'm getting the same things you describe. Walt Jung has mentioned similar problems with the CPM function of MDM712. Date: 23 Nov 1983 04:20-PST From: David Kirschbaum To: Keith Petersen Re: MDM714 terminal mode problems MDM714 works fine except I got a bug in the LOCMSG character (the one that I think lets you send a local command like ^E in HERMES) while telling MDM714 to ignore it. For some reason the SHFTYPE procedure is NOT changing that character back to ASCII in the menu, and ^^ (per the original code) does weird things on my Freedom 100 screen! Changed it to ^\, so it no longer blows my menu away, but still don't have it working quite right. I'll figure it out though. Date: 25 Nov 1983 1400-PST To: Keith Petersen From: David Sternlight Re: Security of ALDS code with MDM714 MDM714 (and its predecessors) displays the alternate LD (Sprint, etc.) number and code on the screen when dialing [which could be a security problem if there are others near the terminal]. A simple fix is to comment out the 'CALL TYPE' instruction in MDM714.ASM after DIALAD2: and add three (3) NOP instructions after it (to keep the code the same length). --end--