Xref: utzoo comp.lang.postscript:9136 comp.periphs.printers:1364 comp.sys.ibm.pc.misc:10769 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!hardy From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) Newsgroups: comp.lang.postscript,comp.periphs.printers,comp.sys.ibm.pc.misc Subject: Re: MS-DOS WP 5.1 -> Unix-attached HP LaserJet III w. PostScript Message-ID: Date: 26 Jun 91 03:55:34 GMT References: <91168.135650SCHDAVZ@YaleVM.YCC.Yale.Edu> <91175.205539SCHDAVZ@YaleVM.YCC.Yale.Edu> Organization: University of California, Irvine, USA. Lines: 18 Nntp-Posting-Host: golem.ps.uci.edu In-reply-to: SCHDAVZ@YaleVM.YCC.Yale.Edu's message of 25 Jun 91 00:55:39 GMT There is a simnple explanation (I hope): MS-Kermit in Ascii mode (like all DOS programs handling text) introduces extra CR-LF characters at the end of each line; look at a file transferred this way with emacs, and you'll see the ^M-s. Binary (or Image) mode will produce an exact image of the .ps file (or a binary file). havee set my MS-Kermit to binary by default (same on the NeXT kermit), and let the Unix box handle the resulting files; this way I had no problem with postscript, dvi-files, or others. Annother useful hint: Usse the unix compress available for MS-DOS (compressed at 14 bits) and then uncompress the files at the other end. This not only speeds up things, but avoids CR-LF problems. Greetings, Hardy -------****------- Meinhard E. Mayer (Hardy); Department of Physics, University of California Irvine CA 92717; (714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNET