Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
David Gillett <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Mon, 4 Jan 1999 10:12:50 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
On 31 Dec 98 at 12:59, Elliott Ryder wrote:

>   I recently upgraded from Eudora 2.2 to Eudora 4.0.1. Since then
> whenever I close Eudora I get a Norton Crashguard (v1.27)window
> telling me that "there was an access violation  by OleRPCNotify
> Oxffc3e163 which tried to examine invalid data." (Occasionally it
> says hat Eudora.exe is responsible for the violation.) I cannot
> find any program like this on my computer and have no idea what the
> problem is; can anyone help me out? I am operating a Pentium 166
> with 48Meg RAM and WIN95 Thank  you.

  "OleRPCNotify" is not a program, it is an API (Application
Programming Interface).  It's part of the "OLE" subsystem, probably
part of OLE 2.0 (which for a while was called ActiveX and is now
called COM, for those keeping score...).
  OLE (or whatever) allows one program to look like a component in
another.  [It does a bunch of other stuff too.]  Programs that can
use other applications ("containers") need to initialize OLE support,
and need to remove it when they exit.  Programs that can be
"embedded" using OLE ("controls") need to check for activation via
OLE when started, and need to tell OLE to go back to the container on
exit.
  I suspect that this newer version of Eudora is an OLE container
(making it easy to look at, say, Word or Excel files sent as
attachments, from apparently inside Eudora), and that it may have got
a step or two out of order in the shutdown code, passing a reference
(handle or pointer) that has already been freed.
  You'd think that Qualcomm would catch this, but you're only seeing
it through CrashGuard which they may never have tried it with.  Odds
are good that the API call, given an invalid reference, fails quietly
(perhasp with a memory/resource leak...), so even if it returned an
internal error code, they may not have considered it serious enough
to stop production.


David G

             PCSOFT maintains many useful files for download
              on our web site - visit our download page at:
                     http://nospin.com/pc/files.html

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV