Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!rutgers!husc6!necntc!ci-dandelion!ulowell!walton From: walton@ametek.UUCP (Steve Walton) Newsgroups: comp.sys.amiga Subject: SERIOUS VT100 2.3 bugs Message-ID: <861@ulowell.UUCP> Date: Tue, 16-Dec-86 22:37:20 EST Article-I.D.: ulowell.861 Posted: Tue Dec 16 22:37:20 1986 Date-Received: Thu, 18-Dec-86 00:21:52 EST Sender: page@ulowell.UUCP Lines: 23 I have hit all of the VT100 V2.3 bugs which have been mentioned up to now: period masquerading as break, getting stuck in upper-case mode, and the lack of a beep of any kind. For completeness's sake, my setup is: VT100 V2.3 as posted to comp.sys.amiga by Dave Wecker himself, unmodified. Compiled with Aztec C 3.20a and running under the RELEASE version of 1.2 with the default "usa" keymap. I have also hit upon a far more serious bug, namely that V2.3 apparently is seriously trashing some important system locations. One symptom is that if VT100 is started from an icon, after I exit VT100 it appears as though it has done a CloseWorkBench() call; none of the Workbench icons are working any more. If I had started PopCLI, I can get another CLI, do another LoadWB, and clean up any pending work before rebooting, otherwise I'm stuck. Last night, I had TWO disks develop "bad" sectors in exactly the same place within a few minutes of each other (Track 40, surface 0 according to the DiskDoctor). I attribute this as well to a previous run of VT100. Further work after a reboot proceeded without incident. I think we should all avoid VT100 V2.3. V2.2, at least as patched up by the Mod.amiga moderator, seems to be relatively bug-free, and I am returning to it. [Ahem: maybe you mean the mod.amiga.sources moderator? --Bob]