harrow@exodus.DEC (Jeff Harrow, NCSE LKG1-3/F16 DTN=226-7445) (02/08/86)
I have seen recent net articles indicating that Red Ryder's XMODEM will NOT work with XBIN, and indeed it won't. However, I'm a bit confused since it SEEMS to indicate that it will work with the MacBinary format. Isn't that the non- standard XMODEM used by MacTerminal? Also, I can't seem to get RR's KERMIT Receive to work when I put my VAX's KERMIT in SERVER mode, pick the 'Receive File - KERMIT' item from RR, and type in a filespec. It sends 1 block and I then get a dialog box indicating that the transfer failed, but NO idea as to why. Any ideas? TO SCOTT WATSON (RR's author): You have done a marvelous job on RR, but I wonder why you have not make it workable with XBIN. There are obvious advantages to letting the host un-binhex the file and just place the application file (document) on the Mac's desktop for you, without the extra binhex step. Also, a comment: when talking to the DEC Terminal Server in VT100 mode, there is some (unknown) problem that prevents the terminal server from understanding the commands sent to it. When I put RR in the TTY mode, all works well. Do you have any experience with this? Jeff
mlr0@bunny.UUCP (Martin Resnick) (02/10/86)
> I have seen recent net articles indicating that Red Ryder's XMODEM will NOT work > with XBIN, and indeed it won't. However, I'm a bit confused since it SEEMS > to indicate that it will work with the MacBinary format. Isn't that the non- > standard XMODEM used by MacTerminal? xbin is not a communications protocol. It converts a binhex file to one which can be transmitted by macput. macput uses the MacTerminal variant of XMODEM and can be easily modified to use the MacBinary XMODEM format instead. Other messages here indicated that someone else would be posting new versions of macput and macget that are compatible with MacBinary XMODEM. MacBinary XMODEM is a variant of MacTerminal XMODEM. MacBinary XMODEM sends in a single transfer the same information that MacTerminal XMODEM sends in 3 separate transfers. > Also, I can't seem to get RR's KERMIT Receive to work when I put my VAX's > KERMIT in SERVER mode, pick the 'Receive File - KERMIT' item from RR, and > type in a filespec. It sends 1 block and I then get a dialog box indicating > that the transfer failed, but NO idea as to why. Any ideas? > The receive command in a Kermit implementation is designed to receive from a send on the other end. The get command (which is not implemented in Red Ryder) is designed to receive from a server. > TO SCOTT WATSON (RR's author): > I don't believe that Scott Watson reads Usenet. Why not write to him at the address in the program.
phcalamai@water.UUCP (Paul H. Calamai) (02/10/86)
It seems as though a lot of people are talking about RedRyder 7.0 ! What bothers me is that I purchased RedRyder back in the version 5 days and have yet to receive anything else from Scott Watson (author of RR) even though I've sent him requests for upgrades as well as change-of-address information. I realize that this program can be downloaded from numerous bulletin boards but I don't think I should have to go through the trouble of doing so. I PAID for a SHAREWARE program that a lot of people are using as FREEWARE ! I am the software librarian for a large user group and I used to recommend RedRyder to people interested in purchasing a decent terminal program. Should I continue to make this recommendation ? Am I being unfair to Scott in expecting some upgrade info ? Are you out there Scott ??????
dafa@ihwpt.UUCP (David Fay) (02/11/86)
> I have seen recent net articles indicating that Red Ryder's XMODEM will NOT work > with XBIN, and indeed it won't. However, I'm a bit confused since it SEEMS > to indicate that it will work with the MacBinary format. Isn't that the non- > standard XMODEM used by MacTerminal? ------------------- > TO SCOTT WATSON (RR's author): > > You have done a marvelous job on RR, but I wonder why you have not make it > workable with XBIN. There are obvious advantages to letting the host un-binhex > the file and just place the application file (document) on the Mac's desktop > for you, without the extra binhex step. > In file transfers there are two issues that are more or less independent. The first is what format the transfered file should be in and the second is what transfer protocol to use. Both MacTerminal transfers and MacBinary transfers use XMODEM protocols. However, they use slightly different file formats. MacBinary transfers use a format in which an application is sent as a single file, which includes a header, data, and resource fork. MacTerminal transfers use a format in which each of the three forks is sent as a separate file. So MacBinary does one XMODEM transfer when MacTerminal does three. Since xbin unpacks a binhex'd file into three separate Unix files, it is easiest to use it with MacTerminal type transfers. However, as someone pointed out recently, all you have to do to transfer the files with MacBinary is to pad each file out to a multiple of 128 bytes, cat them together, and transfer them with straight XMODEM. Awhile ago I asked Scott Watson whether he planned to add MacTerminal transfers to Red Ryder. He said he was waiting to see whether it was dropped from MacTerminal 2.0. Since it wasn't, I suppose there is some possibility he will add that capability to Red Ryder. A better approach though would be to convert the Unix file management programs like xbin, macput, and macget to MacBinary. A friend of mine will be releasing some programs to do this shortly. I expect MacTerminal transfers to die a natural death before too long. By the way, I just discovered an annoying feature of MacTerminal 2.0. When you specify MacBinary as the mode of transfer, MacTerminal still scans for the MacTerminal transfer handshake (<ESC a>). If it sees one it goes right into MacTerminal transfer despite what you've told it. This means that if you want to set up macput to initiate MacBinary transfers with <ESC a> so that VersaTerm will automatically receive MacBinary transfers, you are no longer compatible with MacTerminal. It sure would be nice if the terminal program authors would get together and straighten out this mess. Does anyone know what Microphone does? -- -------------------- David Fay AT&T Bell Laboratories Naperville, IL 60566 ihnp4!ihexp!dafa
phil@sivax.UUCP (Phil Hunt) (02/12/86)
> I have seen recent net articles indicating that Red Ryder's XMODEM will NOT work > with XBIN, and indeed it won't. However, I'm a bit confused since it SEEMS > to indicate that it will work with the MacBinary format. Isn't that the non- > standard XMODEM used by MacTerminal? > > Also, I can't seem to get RR's KERMIT Receive to work when I put my VAX's > KERMIT in SERVER mode, pick the 'Receive File - KERMIT' item from RR, and > type in a filespec. It sends 1 block and I then get a dialog box indicating > that the transfer failed, but NO idea as to why. Any ideas? > *****The RR 7.0 does not understand server mode of Vax kermit. You must login to the vax, run kermit, give a command, such as 'SEND FOO.BAR', and then tell the LOCAL Mac term pgm to RECIEVE filename, when done, go back into term mode and KERMIT will repormpt > TO SCOTT WATSON (RR's author): > > You have done a marvelous job on RR, but I wonder why you have not make it > workable with XBIN. There are obvious advantages to letting the host un-binhex > the file and just place the application file (document) on the Mac's desktop > for you, without the extra binhex step. > > Also, a comment: when talking to the DEC Terminal Server in VT100 mode, there > is some (unknown) problem that prevents the terminal server from understanding > the commands sent to it. When I put RR in the TTY mode, all works well. > > Do you have any experience with this? > > Jeff *** REPLACE THIS LINE WITH YOUR MESSAGE ***
sam@ccitv3.UUCP (02/13/86)
> I have seen recent net articles indicating that Red Ryder's XMODEM will NOT work > with XBIN, and indeed it won't. However, I'm a bit confused since it SEEMS > to indicate that it will work with the MacBinary format. Isn't that the non- > standard XMODEM used by MacTerminal? > > Also, I can't seem to get RR's KERMIT Receive to work when I put my VAX's > KERMIT in SERVER mode, pick the 'Receive File - KERMIT' item from RR, and > type in a filespec. It sends 1 block and I then get a dialog box indicating > that the transfer failed, but NO idea as to why. Any ideas? > > ......... > Jeff Hello again, Jeff, Just a tidbit on your letter. First, I heartily agree; this is a fantastic product. A real nice piece of work. When on Compuserve and downloading xmodem, you do end up with a Mac application on the desktop. I'm not sure whether Compuserve or RR is un-binhexing it, but I think RR is doing most of that work. Sorry I don't know about your other questions. Good Luck! Sam Mantel -- Roch, NY