uncompress and enhanced diagnostics

[Mike Proicou]

In article <785 at bagend.UUCP> jan at bagend.UUCP (Jan Isley) writes:
>
>-rw-r--r--  1 jan     users      3328 Jul  3 00:01 README 
>-rw-r--r--  1 jan     users   7022592 Jul  3 00:22 s4diag 
>-rw-r--r--  1 jan     users     82737 Jul  3 00:07 s4diag.Z 
>-rw-r--r--  1 jan     users    115772 Jul  3 00:06 s4diag.Z.uue 
>-rw-r--r--  1 jan     users     55081 Jul  3 00:02 s4diag.Z.uue.1 
>-rw-r--r--  1 jan     users     60691 Jul  3 00:02 s4diag.Z.uue.2 
>
>I think I'll stick with my version of s4diag!  Anyone else EVER see
>uncompress do this?
>
>unix-pc rev G, release 3.51, 3.5 MB memory, P5.1 and WD2010, ST4096 drive.
>

I've seen uncompress act up many times on .Z files that get corrupted. My
favorite is forgetting binary mode in Kermit or ftp.  The file is pretty
much guaranteed to be more than 5 Meg if you let it finish!

Here's the sizes I get:

total 401
-rw-r--r--  1 mike    users      2084 Jul  3 19:50 Install 
-rw-r--r--  1 mike    users      3328 Jul  3 19:50 README 
-rwxr-xr-x  1 mike    users     82673 Jul  3 19:51 s4diag.Z*
                                  ^^^
-rw-r--r--  1 mike    users     55081 Jul  3 19:50 s4diag.Z.uue.1 
-rw-r--r--  1 mike    users     60691 Jul  3 19:50 s4diag.Z.uue.2 

And the result after uncompress is:

-rwxr-xr-x  1 mike    users    150478 Jul  3 19:51 s4diag*


Your s4diag.Z file is corrupted.

Mike
-- 
Mike Proicou                                 | The supreme irony of life is
mproicou at blackbird.afit.af.mil               | that hardly anyone gets out
osu-cis!n8emr!captain!mike                   | of it alive.   -- R Heinlein