Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!cg-atla!fredex
From: fredex@cg-atla.UUCP (Fred Smith)
Newsgroups: comp.sys.ibm.pc
Subject: Re: ZIP question
Message-ID: <8200@cg-atla.UUCP>
Date: 27 Dec 89 14:30:51 GMT
References: <1989Dec25.084953.12149@uwasa.fi> <891@thor.wright.EDU>
Reply-To: fredex@cg-atla.UUCP (Fred Smith)
Distribution: comp
Organization: Agfa Compugraphic Division
Lines: 21

In article <891@thor.wright.EDU> sdawalt@wright.EDU (Shane Dawalt) writes:
>in article <1989Dec25.084953.12149@uwasa.fi>, ts@uwasa.fi (Timo Salmi LASK) says:
>> 
>> I wouldn't think this is so.  The 1.02 version is a fix of some
>> special bugs in 1.01.  It is not a true upgrade.  Get 1.02 by all
>> means (I have done so), but unless the problem was what 1.02 fixed,
>> this probably won't help. 
>> 
>   Again, I'm not certain which version it occured in (I think I skipped
>the 1.01 release), but there are incompatabilities between v0.92 and v1.0x
>.ZIP files. 



The incompatibility occurs, as Shane states, across the 0.92 to 1.0x boundary.
The difference between 1.01 and 1.02 is minor, as I recall, the documentation
mentions a bug fix for ceratin 386 users in 1.02. Otherwise, I believe 1.01
and 1.02 are the same. Both of them should be able to create/decode files
created in the "new" format (called "imploding").

Fred