walton@ametek.UUCP (Steve Walton) (12/17/86)
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]
drew@cgfsv1.dec.com (Steve Drew) (12/18/86)
> 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. Were you by any chance running Shell 204M as well. Because this is the same problem I was having Track 40, Surface 0. Since I was able to reproduce read errors with Shell as I mentioned yesterday, with my 5 1/4 " drive I'm assuming that the bug I found in 1.2 was also causing the 3 1/2" trashing, but just not able to reproduce it on df0: or df1: So be careful not to blame VT100 for this one. If you were using Shell 2.04M get the fixed version that I just posted. If you were'nt using Shell 2.04M please let us know maybe there's other problems lurking out there! /Steve Drew.
billd@crash.UUCP (Bill D'Camp) (12/19/86)
[]
hmmm, the problem which you describe with multiple disks getting
read/write errors on the same track and offset happened to me last
night, only I wasn't using vt100 2.3, it happened with vt100 2.2,
C-kermit, and Starterm. MAYBE there is something other than vt100
causing these problems. I was running the RELEASED version of 1.2
at the time, and Diskdoctor allowed me to read all of the disks
again, though some of the files did died.
--
_ /|
\`o_O'
( ) Aachk! Phft!
U
(borrowed from B.C. & Zot)
Opinion? I thought you said onions.
UUCP: crash!pnet01!billd
ARPA: crash!pnet01!billd@nosc