Path: utzoo!news-server.csri.toronto.edu!rpi!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: Re: VLT instalation questions Message-ID: <91077.121627WGLP09@SLACVM.SLAC.STANFORD.EDU> Date: 18 Mar 91 20:16:27 GMT References: Distribution: na Organization: Stanford Linear Accelerator Center Lines: 25 When VLT complains about "srx", it means you have programmed something (most likely the "beepfunction") to use that command. In the old version of VLT, the srx command was implemented to mean "synchronous RX", i.e. send this to REXX now, and wait for the reply. This was sometimes necessary, since it wasn't possible to have more than one command pending at any time. Since VLT does two beeps after a transfer, the second beep would be ignored with a simple RX command, since the first one would still be pending (no time to pick up the reply message until the next full loop over everything). Nowadays VLT's scripting is completely multithreaded and the simple RX command works fine both times. At that time, the command set was rationalized to get rid of all the strange stuff that crept in, and the SRX command diappeared. There is still an equivalent: RX SYNC, but you shouldn't need that very often (and it's a little dangerous in the current version: it can block VLT completely). What's all this mean, you ask. Well, to fix it, select Program Mode On, and select Beep Volume. You will likely see the beep command start with a tilde followed by something like srx "address 'PingServer' BEEP" . Change srx to rx, hit return, select Program Mode Off, and save the configuration. Poof, all done... 8) Willy.