Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Restored\s+Zip\s+Files\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Restored\s+Zip\s+Files\s*$/: 3 ]

Total 3 documents matching your query.

1. Restored Zip Files (score: 1): Author: "Moir,Betsy" <betsy.moir AT ABBOTT DOT COM>; Date: Tue, 21 Apr 1998 14:42:57 -0500; One of our customers has noticed that "sometimes" when he restores zip files and tries to run them they don't work any more. He gets an error message that the file has been corrupted. Has anyone ever; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-04/msg00903.html (10,377 bytes)
2. Re: Restored Zip Files (score: 1): Author: Tony White <tony.white AT GTRI.GATECH DOT EDU>; Date: Wed, 22 Apr 1998 19:49:26 -0400; Speculation: Compressing an already-compressed file adds characters to the end, and ADSM stores them. Restoring the file, ADSM doesn't strip all of the added characters because it doesn't expect comp; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-04/msg00964.html (11,517 bytes)
3. Re: Restored Zip Files (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 23 Apr 1998 11:49:21 -0400; I don't think ADSM client compression is involved here. Some possibilities that come to mind: 1) The file was corrupt before ADSM backed it up, and it was just noticed after the restore. 2) There is; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-04/msg01007.html (11,268 bytes)

Current List: 1 - 3
Page: [1]