| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3162.1 | Try using a script | DECWET::DAVIS | Mark Davis - 206.865.8749 | Wed Nov 29 1989 04:10 | 6 |
| I had the same symptoms intermittently with VLT. If I used a script
to dial in it worked fine. Try it with a script. The sysman said they
had a bad modem connected to the lat. I have not tried to type in the
LAT password lately since the script works quite well.
mark
|
| 3162.2 | Could be the bell | BELFST::MCCLINTOCK | Peter | Wed Nov 29 1989 12:33 | 10 |
| I had the problem with password on the LAT. It turned out to be
that the terminal server was transmitting a bell which was causing
VLT to respond with some ARexx text thereby messing up the password.
You don't see this 'cause it's not echoed.
Setting Programme Mode On cures it temporarily but I think that
deleting the configuration file distributed and starting again is
the only real cure.
Peter
|
| 3162.3 | | NAC::BRANNON | value added | Wed Nov 29 1989 19:06 | 10 |
| re .2:
cute. Yup, I've heard the beep when the # is displayed from the
terminal server I use.
What puzzles me is why would VLT be set up to send ARexx text if it
got a bell character. Seems like a rather dangerous default since bell
characters are pretty common.
dennis
|
| 3162.4 | | WJG::GUINEAU | Quantum Reality | Wed Nov 29 1989 20:17 | 10 |
|
It tries to send to an arexx process called "ping" or something like that
which will "make a nice ping sounding bell".
It's a downright pain in the a** since every bell causes that "cant find
arexx port" requestor to pop up.
Anyone know how to kill this beast? (besides buying Arexx :-)
John
|
| 3162.5 | not for me | NOTIBM::MCGHIE | Thank Heaven for small Murphys ! | Wed Nov 29 1989 20:50 | 4 |
| I haven't seen the requestor come up on my system and I don't have
arexx. Though I did start from scratch for the init file.
Mike.
|
| 3162.6 | Scrap OVLT.INIT | BELFST::MCCLINTOCK | Peter | Wed Nov 29 1989 21:19 | 2 |
| Like .5 I got rid of the requestor by deleting OVLT.INIT and starting
again.
|
| 3162.7 | Worth a try... | CIMNET::KYZIVAT | Paul Kyzivat | Wed Nov 29 1989 21:36 | 9 |
| I certainly didn't get any AREX requestor. Why would it be sending
anything out the COMM port as a result of this anyhow? I guess I will
experiment some more. At least this gives me another idea to try.
What I really need is something else to call besides my system with the
LAT. Then I could at least verify that things are otherwise working.
Thanks for the ideas,
Paul
|
| 3162.8 | Try deleting Arexx Dir | DECWET::DAVIS | Mark Davis - 206.865.8749 | Wed Nov 29 1989 22:42 | 13 |
| re:-2 or so>
I got rid of that ARexx message by getting rid of the directory that
had ARexx the scripts. I do not get any kind of ARexx messages now.
But...
I am getting aborted quite often during transfers with "PORT busy
use CTRL Q to reset". It "just" started happening recently. For large
transfers I have to restart ZMODEM or use Handshake. Any ideas.
mark
|
| 3162.9 | Try this... | CGOFS::CADAMS | Clint Adams - Calgary, Canada | Wed Nov 29 1989 23:38 | 15 |
| Now that we have deleted almost everthing that comes with the VLT zoo
except the executable.....;^)
What I did and I've also heard on the usenet is to select the "Program
Mode" to "ON" and pull down the "Beep Volume" from the Operation Menu.
Delete all the characters in the requester and save the configuration.
The other thing to do is to delete VTPrefs.dat and save a new one with
the Save Config making sure that the command for Beep volume is blanked
out.
Regards... Clint
|
| 3162.10 | | DICKNS::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Thu Nov 30 1989 12:46 | 4 |
| Port Busy Use Ctrl Q appears during my transfers too, but it has never
resulted in an aborted file transfer. I just ignore the message.
-Paul
|
| 3162.11 | Thanks! Seems to have solved the problem. | CIMNET::KYZIVAT | Paul Kyzivat | Fri Dec 01 1989 02:45 | 5 |
| I am finally in using VLT! I also turned program mode on. Somehow
this seems backwards: isn't it when program mode is ON that AREX is
used to run a program generating BEEPs?
Paul
|
| 3162.12 | Won't even run off the fred fish disk. | SHARE::DOYLE | | Wed Dec 06 1989 13:23 | 8 |
| I can't seem to get this program to even run, I get a -
"Error Initializing Screen "something or other"".
I looked for some type of installing documentation but could find none.
Any idea's?
Thanx
Toby
|
| 3162.13 | ctrl chars in scripts? Macro default directory change? | STAR::ROBINSON | | Wed Dec 06 1989 16:55 | 14 |
| Two questions about VLT:
How do you get the CTRL/X and CTRT/R needed for a TSN line
into a dialup script.
Is there a clean way to change the default VLT macro directory from
REXX:. Right now I do an ASSIGN REXX:: COMM:VLT from a CLI, before
I click on the VLT icon. I am running floppies so I can't do
a permanent assign in my startup sequence (hmm.. or can I. I just assumed
I'd get an error if "COMM:VLT" couldn't be found...). I could do an
ICONX script, I guess, but would like the cleanest solution.
Thanks in advance
Dave
|
| 3162.14 | CLI standard escapes | CIMNET::KYZIVAT | Paul Kyzivat | Wed Dec 06 1989 22:05 | 10 |
| > How do you get the CTRL/X and CTRT/R needed for a TSN line
> into a dialup script.
Somewhere in the doc file is explains that escape sequences in strings have
been made compatible with the CLI. Thus, you can put your special
characters in in hex. ("*X..") If the introducer character is changed
using ARP, then use whatever you changed it to. (I think the default is *,
but I don't remember for sure since I change it to \.)
Paul
|
| 3162.15 | got enough memory? | GIDDAY::LAWSON | | Thu Dec 07 1989 03:17 | 11 |
| re .12
If you are using the default screen (Interlace), Make sure that you
have enough memory.
Also, VLTjr is very good at downloading via zmodem. Trouble is, I cant
UPLOAD. This has only happened since I switched from 4.069 to 4.226.
I am using v2.0 of xprzmodem. I went back to 4.069 and all was ok.
Any suggestions out there?
Glenn
|