Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!ucbvax!bloom-beacon!eru!hagbard!sunic!news.funet.fi!uwasa.fi!ts
From: ts@uwasa.fi (Timo Salmi)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Is there a MSDOS .Z uncompress utility?
Keywords: compress uncompress .Z
Message-ID: <1991Apr10.110952.13111@uwasa.fi>
Date: 10 Apr 91 11:09:52 GMT
References: <fictorie.671102802@freyr> <1991Apr8.172213.1606@midway.uchicago.edu> <1991Apr9.121315.1523@uwasa.fi> <1991Apr9.232659.22018@agate.berkeley.edu>
Organization: University of Vaasa
Lines: 25

In article <1991Apr9.232659.22018@agate.berkeley.edu> c60b-1eq@e260-3e.berkeley.edu (Noam Mendelson) writes:
>In article <1991Apr9.121315.1523@uwasa.fi> ts@uwasa.fi (Timo Salmi) writes:
:
>>   This is a common problem.  Unix and MsDos use different eolns (end
>>of lines) for text files.  Msdos uses ascii 13 10 while Unix uses
>>10.  Might it be that COMP430D just puts is the ascii 10 (^J).  
>
>No.  The lack of a CR is a UN*X trait.

Yes.  We actually mean the same thing, but I worded mine badly. 

>>   If this is the case, you can easily remedy the situation by
>>running the text file (after extraction) through a suitable text
>>editor, such as /pc/editor/qedit21.zip, or a suitable filter such as
>>unix2pc.exe in /pc/ts/tsfilt16.arc.  Try either to see what happens. 
:

I checked my above assertion yesterday evening about comp430d,
qedit21, and tsfilt16, and my suggestions work, all right. 

...................................................................
Prof. Timo Salmi        
Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.12.37
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun