kal@cbnewsj.att.com (kevin.lyons) (04/09/91)
I've been reading the net for some time, and I've learned a lot (thanks, folks!) but this is my first time writing. I hope I don't embarrass myself. I frequently use my 3b1 to download files from commercial services, and UMODEM works just fine with XMODEM. In these cases I use the vt100 terminal emulator and call umodem with the shift-Cmd keys. Now I'd like to use umodem to move binary files between the 3b1 and another computer I own. They're connected via a null-modem cable, the serial port on the 3b1 is optioned for Terminal, and I can log in from the other computer just fine. I start umodem on the 3b1, then I start xmodem on the other computer ... then I wait. Eventually they time out and blame each other. Has anyone been able to get umodem/xmodem to operate over the serial port connection? If so, how? (Honest, I DID read the manual.) Thanks, Kevin
ostroff@Oswego.EDU (Boyd Ostroff) (04/09/91)
In article <1991Apr8.221615.1195@cbnewsj.att.com> kal@cbnewsj.att.com (kevin.lyons) writes: >In these >cases I use the vt100 terminal emulator and call umodem with >the shift-Cmd keys. > >I start umodem on the 3b1, then I start xmodem on the other >computer ... then I wait. Eventually they time out and >blame each other. I don't use the emulator, but I use a Mac running various telcom programs as a terminal at 9600 baud and it works great for me. I just use umodem -st filename or umodem -sb filename (for binary files) and then hit "receive file" on the mac and away it goes. The only problem I've noticed is that there are often a bunch of NULLs appended to the end of the file, as though the two programs couldn't agree on where the file ends... |||| Boyd Ostroff / Tech Director / SUNY Oswego Dept of Theatre / 315-341-2987 |||| SysAdm at cboard.UUCP / Serving the Performing Arts / 315-947-6414/8N1 |||| ostroff@oswego.oswego.edu / cboard!ostroff@natasha.oswego.edu
vince@tc.fluke.COM (Craig Johnson) (04/16/91)
In message <1991Apr8.221615.1195@cbnewsj.att.com> kevin.lyons writes: [...] > I frequently use my 3b1 to download files from commercial > services, and UMODEM works just fine with XMODEM. In these > cases I use the vt100 terminal emulator and call umodem with > the shift-Cmd keys. > > Now I'd like to use umodem to move binary files between the > 3b1 and another computer I own. They're connected via a > null-modem cable, the serial port on the 3b1 is optioned for > Terminal, and I can log in from the other computer just fine. > I start umodem on the 3b1, then I start xmodem on the other > computer ... then I wait. Eventually they time out and > blame each other. > > Has anyone been able to get umodem/xmodem to operate over the > serial port connection? If so, how? (Honest, I DID read the > manual.) I struggled with a similar problem for a while a couple of years ago and finally beat it. The umodem on the Unix PC wants to communicate over standard in and standard out. Status and error messages are sent to standard error. In my case I wanted to run umodem while logged into a remote Unix machine using cu. Well cu couldn't cut it, but I finally wrote my own cu clone with a ~$ escape to fire up a process with standard in and out connected to the port while standard error was allowed to come to the console. I suspect your problem is related. When you log into the Unix PC from another machine and run umodem, I suspect the status messages coming to standard error are getting in the way. Try directing umodem's standard error to a file or /dev/null. P.S. Please excuse me if I accidentally get this wrong. It been a long time since I fooled with it, and I'm too lazy to go check it just now. Craig V. Johnson ...!fluke!vince John Fluke Mfg. Co. or Everett, WA vince!tc.fluke.com
kal@cbnewsj.att.com (kevin.lyons) (04/17/91)
Several people have posted and emailed help on this one, so I suppose I should report that I solved my problem. Way back in the dark ages, when I set this port up, I only wanted to move ASCII files between the 3B1 and an old Epson Geneva CP/M portable. Reasoning that the Geneva would be running a terminal emulator, I optioned the port for a Terminal connection. It worked fine for sending ASCII files for years. Recently I put an Amiga on the port and wanted to use umodem to send and received bianaries. No luck. I posted here, and also downloaded kermit from OSU (more folks to thank!). Kermit didn't work either, but left diagnostic files. I finally took it all down and put it all back up, this time telling it the connection was to a Computer. Ta-DA! Works fine now. Kevin