| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 270.1 | XModem currently needs V%! | RDGENG::KEANE | | Thu Oct 13 1988 11:44 | 14 |
| re my note 270.0 above
Using analyse, it can be seen that the Xmodem.exe expects the RTL
to be version 4 minor version E. On a v5 microvax this is so, on
our cluster at V4.7 the RTL.exe is at V4 minor version D, hence
it dont work!!
So if you have probs like me you will either need the Newer RTL
or get the XModem.exe linked to the 4.7 RTL
Cheers
Pat K.
|
| 270.2 | different problem with xmodem | SCOVAX::MICHAELS | | Sat Oct 15 1988 15:04 | 11 |
| I got xmodem to run on 4.7 by linking all of the obj files in the
backup saveset but I have a different problem with xmodem. In all
the versions I've tried, I always have a problem with the 18th
packet of ANY file I try to receive. It must be an obvious (not
to me) problem in the way I'm setting up something. I've tried
using various terminal programs on my ST (uniterm,st-talk,flash)
and I always get the same thing. Any help would be appreciated.
Thanks,
Dave M.
|
| 270.3 | Sounds like an XON/XOFF problem. | PRNSYS::LOMICKAJ | Jeff Lomicka | Mon Oct 17 1988 14:36 | 8 |
| The 18'th packet, eh? It sounds like you are have XON/XOFF enabled
somewhere. Try $ SET TERM/NOTTSYNC/NOHOSTSYNC before doing the
transfer. If you are using a DECServer to connect to your VAX, do a
SET FLOW DISABLE before connecting.
(17 is ^Q and 18 is ^S. WHACK will do this if you try to run it with
SSU disabled.)
|
| 270.4 | re .3 | SCOVAX::MICHAELS | | Tue Oct 18 1988 01:26 | 11 |
|
I just tried disabling XON/XOFF everywhere I could find it on the
server,vax, and the terminal program (in this case UNITERM). Still
no luck. The error message received is BAD COMP then TIMEOUT then
CHECKSUM ERR. I've been tring to get XMODEM to run for about a year
without any success. Since I don't have SSU (which I guess means
no STRANSF), its back to KERMIT. (oh well)
Thanks Jeff and still trying,
Dave M.
|
| 270.5 | | NEXUS::MORGAN | Snazzy Personal Name Upon Request | Tue Oct 18 1988 01:48 | 10 |
| Reply to .4, Michaels,
Did you break up the program into 128 byte blocks? If you don't
you'll transfer some amount of blocks and then get timeouts.
All programs under VMS have to be broken into 128 byte blocks before
they can be transfered via xmodem.
BTW are we speaking of xmodem ver. 3.6 which features xmodem 1k
and ymodem batch transfers.
|
| 270.6 | Umm, is that like "bulls*t"? Yah, but more polite. | BENTLY::MESSENGER | Dreamer Fithp | Wed Oct 19 1988 20:46 | 12 |
| Re: .-1
> All programs under VMS have to be broken into 128 byte blocks before
> they can be transfered via xmodem.
Excuse me? This turns out not to be the case. I don't know what
your version of Xmodem does, but the one we've got out here doesn't
need anything of the kind. If yours does, it's a bug in the way
it uses RMS. Trust me.
- HBM
|
| 270.7 | 18 is ^R | ISTG::ENGHOLM | Larry Engholm | Sun Oct 23 1988 02:42 | 7 |
| > < Note 270.3 by PRNSYS::LOMICKAJ "Jeff Lomicka"
> 17 is ^Q and 18 is ^S.
I think Jeff meant to say that 17 is ^Q and 19 is ^S. But a flow
control problem still seems likely.
Larry
|
| 270.8 | Could be the LAT... | BENTLY::MESSENGER | Dreamer Fithp | Thu Oct 27 1988 15:22 | 6 |
| By the way -- if you're using a LAT for the transfer, you _may_
have to disable flow control manually. It turns out (I discovered
this the hard way) that inbound ^S and ^Q are replaced will nulls
*even if the session is set to PASSALL*. If this is what is happening,
you must disable inbound flow control on the LAT.
- HBM
|
| 270.9 | re -.1 | SCOVAX::MICHAELS | | Sat Oct 29 1988 03:36 | 4 |
| re -.1
Thanks. I'll try it again and report results. I'd really like
to get xmodem to run on my machine.
Dave M.
|