Article View: adobe.acrobat.reader
Article #13722Re: The memory could not be "read"/"written"
From: RyanSlimmon
Date: Mon, 13 May 2002 21:59
Date: Mon, 13 May 2002 21:59
7 lines
1425 bytes
1425 bytes
I think I may be getting somewhere with this... Inside our program, when you call the reader for the second time (changing the pdf that is currently being viewed), it throws the error: "Memory could not be read" & "Memory could not be written". Now I can't get the Reader to throw these messages itself. However, if I open a pdf in the Reader, then try to open another one. The reader seems to freeze. What it does is spawn's another process. What is the weird part is once again it will only happen in a terminal server session, if I go directly to console it will work fine. Has anyone gotten any farther with this problem?
Technical Details
Message-ID:
<ef8643a.3@WebX.aaQKaf7vad4>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!supernews.com!telocity-west!TELOCITY!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!netnews.com!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<ef8643a.-1@WebX.aaQKaf7vad4>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109513,970fea558a115ee7 X-Google-Attributes: gid109513,public X-Google-ArrivalTime: 2002-05-13 15:07:40 PST From: RyanSlimmon <RyanSlimmon@cssionline.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!supernews.com!telocity-west!TELOCITY!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!netnews.com!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.acrobat.reader Subject: Re: The memory could not be "read"/"written" Message-ID: <ef8643a.3@WebX.aaQKaf7vad4> Date: Mon, 13 May 2002 14:59:29 -0700 References: <ef8643a.-1@WebX.aaQKaf7vad4> Lines: 13 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit