Article View: adobe.acrobat.reader
Article #11682Re: File is damaged and could not be repaired
From: Kevin Stachowski
Date: Tue, 25 Jun 2002 13:05
Date: Tue, 25 Jun 2002 13:05
1 lines
914 bytes
914 bytes
I know about the workaround (Click OK --> Click Refresh --> Click Retry), but I would like my website visitors not to have to go through that process. Help!
Technical Details
Message-ID:
<ef91dd2.7@WebX.aaQKaf7vad4>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-05!sn-xit-06!supernews.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.freenet.de!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<ef91dd2.-1@WebX.aaQKaf7vad4>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109513,a346054dcfc03c65 X-Google-Attributes: gid109513,public X-Google-ArrivalTime: 2002-06-25 06:07:35 PST From: "Kevin Stachowski" <bioteachmrski@netscape.net> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-05!sn-xit-06!supernews.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.freenet.de!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.acrobat.reader Subject: Re: File is damaged and could not be repaired Message-ID: <ef91dd2.7@WebX.aaQKaf7vad4> Date: Tue, 25 Jun 2002 06:05:09 -0700 References: <ef91dd2.-1@WebX.aaQKaf7vad4> Lines: 3 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit