home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!not-for-mail
- From: CIR_TLW@VAX1.UTULSA.EDU (Tristia Watson)
- Newsgroups: comp.os.ms-windows.apps
- Subject: Undeliverable Mail
- Date: 4 Jan 1993 13:13:18 -0600
- Organization: UTexas Mail-to-News Gateway
- Lines: 89
- Sender: daemon@cs.utexas.edu
- Message-ID: <9301041913.AA24829@deepthought.cs.utexas.edu>
- NNTP-Posting-Host: cs.utexas.edu
-
- Greetings!
-
- I'd like to thank everyone who send me their "solution" to the problem of
- using Windows Terminal and Kermit on the VAX to transfer files! I posted
- the question to this newsgroup and got the following responses:
-
- --
-
- From ray <ray.chow@canrem.com>
-
- Windows Terminal does not understand Kermit server commands. However, you
- can still use it to transfer files to and from the VAX. Instead of using
- the SERVER command in VAX Kermit, use SEND or RECEIVE. Try the following.
-
- Download a file from the VAX to the PC:
-
- $ kermit
- Kermit-32> send filename.txt
- Start download from Windows Terminal. When the transfer is finished you
- will be returned to the VAX Kermit prompt (I used Kermit-32 as an example,
- but C-Kermit should be similar...)
-
- Upload a file from the PC to the VAX:
-
- $ kermit
- Kermit-32> set file type fixed
- Kermit-32> receive
- Start upload from Windows (it should ask for the filename). Use file type
- ASCII at the VAX end for text, fixed for DOS executables, ZIPs and other
- archive files.
-
- This should work, though I think Windows terminal can only handle packets up
- to 98 bytes in length. VAX Kermit-32 can use packets up to 1000 bytes.
- MS-Kermit for DOS can use large packets as well, but apparently doesn't run
- all that well under Windows (I have had no problems myself, though).
-
- --
-
- From: bmartin@maemaster.eng.uci.edu (Bryan Martin)
-
- Well, your main problem is that the windows terminal does NOT support the
- kermit 'server' option. You may only transfer ONE file at a time (very
- painfull) using that program. So... you have several choices.
-
- The solution you really want (no, really, I know you do!) is to get kermit
- on your windows machine, and run it in a dos window. It is quite easy
- to set up, and the latest version of kermit is designed to work well with
- windows. If you really can't do this, consider archiving all your files
- into one big file and sending that, it's really a pain to send each file
- over with WinTerm.
-
- Hope this makes more sense, WinTerm is a cute little program, but mostly
- useless as anything more than a paperweight on your desktop. :-P
-
- --
-
- From: tijc02!eri316@uunet.UU.NET (Ed Ingraham )
-
- On the VAX I type RUN KERMIT. It responds with kermit prompt and I type
- RECEIVE.
-
- On my PC I click on SEND BINARY FILE and select a file (happens to be
- ordinary ASCII text). The screen shows transfer going and finishing
- correctly.
-
- Back on the keyboard I type EXIT to Kermit-32 prompt and I am back to
- DCL.
-
- To sum up: don't use SERVE command. Use RECEIVE and SEND commands
- instead.
-
- --
-
- As you can see, the consensus is to not use the SERVE command as you
- normally would with Kermit. The other suggestion that I think is the best
- one of all, is to get MS-Kermit and run it instead of Win Terminal. MS-DOS
- Kermit 3.11 can be optained via FTP at WATSUN.CC.COLUMBIA.EDU
- (128.59.39.2). The Kermit files are in directories kermit/a, kermit/b,
- kermit/c, kermit/d and kermit/e. (This information from Info-Kermit
- Digest, Monday, 16 Sep 1991)
-
- Thanks for all the help!
-
- +---------------------------------------------------------------------+
- | Tristia Watson CIR_TLW@VAX1.UTULSA.EDU |
- | Client Support Coordinator HELP@VAX1.UTULSA.EDU |
- | Computing & Information Resources Help Desk Phone: 631-3500 |
- +---------------------------------------------------------------------+
-
-