Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!sun-barr!lll-winken!lll-crg.llnl.gov!berry From: berry@lll-crg.llnl.gov (Berry Kercheval) Newsgroups: comp.graphics Subject: Re: MiniVas Message-ID: <40769@lll-winken.LLNL.GOV> Date: 7 Dec 89 01:23:58 GMT References: <89120107514469@masnet.uucp> <1825@dgl.cam.nist.gov> Sender: usenet@lll-winken.LLNL.GOV Reply-To: berry@lll-crg.llnl.gov.UUCP (Berry Kercheval) Organization: Lawrence Livermore National Laboratory Lines: 39 In article <1825@dgl.cam.nist.gov> rfree@cam.nist.gov (Richard Freemire) writes: >In article <89120107514469@masnet.uucp>, alan.kennedy@canremote.uucp (ALAN KENNEDY) writes: >> I'd really like to hear from anyone who has used the Lyon Lamb - MiniVas >> VTR controllers. >We have a VAS IV which is a precurser to the miniVas. I had the same problem >that you describe. I have a MiniVas and have had no problems in several hours of animation. What kind of VTR's are you guys using? I have found Sony BVW-40's to be rock-solid machines. >I'd like to have all the Vas users talk together. I got NO software for >my system, I had to write my own. I never got any support from >Lyon-Lamb. Is this what other people had to put up with? I got some software from L/L for the MiniVas that claimed to be Unix compatible, but it was written in a weird ANSI-ish dialect of C, had horrid system dependencies (like #include ) and assumed PC-ish architecture. It turned out to be worse than completely useless. Only took me about 1/2 a day to write my own bare-bones library for it. The worst part was remembering to turn off ECHO on the tty port. (When you send 'I' to init the MiniVas, it replies with 'I' when done, which is echod to the MiniVas by the tty driver. So the MiniVas inits itself again, and again, and again....) >I'm new on the net so I don't have a logo/signoff yet. What you have is just fine. (I promise not to do any .sig bashing in comp.graphics...) --berry -- bERRY Kercheval :: berry@lll-crg.llnl.gov