Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!slacvm!wglp09
From: WGLP09@SLACVM.SLAC.STANFORD.EDU
Newsgroups: comp.sys.amiga.datacomm
Subject: VLT 5.034 bug when run from WB.
Message-ID: <91050.145729WGLP09@SLACVM.SLAC.STANFORD.EDU>
Date: 19 Feb 91 22:57:29 GMT
Organization: Stanford Linear Accelerator Center
Lines: 18


        So, there's this bug in VLT 5.034 that snuck in when I added
tooltype support from the Workbench. If you run VLT from the CLI, ignore
this message, otherwise read on.
        The bug is kind-of nasty, especially under 1.3. Some versions of
2.0 mask the bug entirely and that's how it was able to sneak by. What it
is is a number of reads from location zero, and maybe some other things.
It will most definitely show up if you run enforcer, but there is at least
one condition in which it can cause a spurious Read/Write Error requester
to pop up: spurious because there really isn't an error anywhere. Just
cancelling the requester will make things run along just fine.
        Yet, at this time I cannot recommend running VLT from the Workbench.
I will upload a fixed version to BIX in the next week or so, and I'm sure
that version will show up on a BBS near you shortly after.
        Meanwhile, if you know of any other bugs that might be fixed at
the same time, let me know.

        Willy.