forde@EGLIN-VAX.ARPA.UUCP (01/27/87)
If you are currently using COMMWORKS you may be interested in this potentially expensive bug. A friend of mine who runs a local BBS was using COMMWORKS recently to call his BBS support line (long distance). After logging off the remote board he entered the COMMWORKS editor to re-read and edit some of the stuff he had just downloaded. When he went to save the file he was asked if he wanted to return to terminal mode. He picked up a handset and sure enough the line was still open. It seems that COMMWORKS had not broken the connection even though the carrier was no longer present. When my friend checked with the local phone company he discovered, much to his dismay that unless the initiator breaks the connection it will remain connected and guess who pays? As a result, my friend's 5 minute call ended up being a 20 minute call (could have been worse, I guess). Here's an APPLEWORKS tip, too. If you routinely print your documents as a text file onto a disk, you can retain the formatting (margins and <CR> at the end of each line) by adding a Silentype printer as one of your three printers and specify 'print to disk or another Apple' when prompted for the slot #. Next, to avoid excess line feeds at the end of each 'page' specify a page length of .1 (yep, point 1) inches. This is the best way I've found for composing bulletins such as this one and then uploading them rather than having to type them in on-line. Eric S. Ford FORDEEGLIN-VAX.ARPA Eglin AFB, FL ------