home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.hardware:4129 comp.dcom.modems:12687
- Path: sparky!uunet!olivea!hal.com!decwrl!mips!darwin.sura.net!blaze.cs.jhu.edu!whatever.cs.jhu.edu!swiet
- From: swiet@whatever.cs.jhu.edu (Alexander Swietlicki)
- Newsgroups: comp.sys.sun.hardware,comp.dcom.modems
- Subject: Re: tip - xmodem query
- Message-ID: <1992Aug28.204537.10307@blaze.cs.jhu.edu>
- Date: 28 Aug 92 20:45:37 GMT
- References: <kebIsTq00iQXQTAFgo@andrew.cmu.edu>
- Sender: news@blaze.cs.jhu.edu (Usenet news system)
- Organization: Johns Hopkins Computer Science Department, Baltimore, MD
- Lines: 14
-
- In article <kebIsTq00iQXQTAFgo@andrew.cmu.edu> ap10+@andrew.cmu.edu (Anand Patwardhan) writes:
- >
- >Hi all
- >
- >We are using xmodem (started from within tip, with ~C) to send a file.
- >This is on a sun4. The problem is that for some reason, the nl character
- >(hex 0a) does not get passed, whenever it appears in the file. Yes, we
- >are using binary mode for xmodem, and tip is being operated in
- >non-beautify and rawftp modes.
- >Any ideas why this might be happening?
-
- I use tip and zmodem with my NeXT. The way it works for me is having
- a ~/.tiprc file with the line SHELL=/bin/sh, and using the ~$ tip escape, with
- sz -1 or rz -1 (sz/rz -1b for binary). Hope this helps...
-