Digital Workshop

Hello and sorry,
here is my next problem.
when i use a anim gif as video in my pub, opus the following error message gives after publish and close opus.



The finished application run under WinXP but not under Win 2000.

I have tested this problem with 3 Computers.

It emerges only if I animated GIF as video use.

Do I make somewhat wrong?

Please help.

Hi,

I think your English is better than the German of most folk on digital grapevine

Could you translate the error message for us please?

Thank you.

My translation:
The instruction in "0x1005eebc" refers to memory in "0x02daaf74". The
procedure "READ" could not be accomplished on the memory.

Click on "ok" around the program to terminate.

Couple of ideas..you may have tried already.
search the forum for 'graphics drivers', Using search for all terms and see if there is any similar problems in the past. Have you tried changing the video options in your publication to see if it makes any difference??


Sandy

I regularly receive the attached message, which specifies the same instruction each time, but references a different memory location. I'm guessing that this might relate to the issue raised by tiaetsch. This has been happening to me for almost 2 years, and occurred in v5.5 as well as v6.

It might be worth noting that no other installed program throws up a memory allocation error.

Currently, I can generate the message when I exit Opus after publishing. If I don't publish, I don't get the message. Another point: I do not get this message after every exit after publishing.

The error message might display for a few days, then disappears only to randomly return sometime later.

I have no recollection of the message being related to animates GIFs, because I rarely use them.

Over a period of about 18 months, I have never been able to link the message to a problem in the published work, which in my case is always a standalone .exe. I'm not saying that there is no problem in the finished pub -- I'm just saying that I haven't yet found a link.

I've searched both Google and the MS Knowledgebase for Error message "0x1005eebc", and found nothing.

Possibly it's one of those arcane messages that programmers like to scatter about just to confuse and worry us mere mortals

I've taken this practical approach: it appears; it apparently does no obvious harm; I haven't a clue what it does or why; I can't fix it; therefore I'm not going to worry about it.

I too get this error message in the same way as Ray describes. However, I also get it after I have saved a publication and then exit (without publishing).

I find that animated gifs can pose some difficulties for Opus. I am currently working on an Advent Calendar (nearly finished) which has 24 animated gifs for each of the doors. When editing some of them just show the background and not the gif. However, everything is fine when previewed or published. This is not a problem with memory or graphics as it happens on both laptop and desktop.

I tend just to ignore it

If you search microsoft support for the general error "The instruction at '<address>' referenced memory at '<address>'. The memory could not be read"
There are 200 results of similar problems with just about every application you can think of.
Each one seems to have a different cause specific to the application. Generally, there are many different instruction addresses and memory addresses, in other words---the addresses seem to be specific to the applications.
Now, since several Opus users have seen identical errors and if you search the Microsoft knowledge base for the 'Opus' error addresses, there are no references in the knowledge base, so there is a strong probability that it's Opus which causes the problem---which may be stating the obvious.
Perhaps the people who suffer this problem can find a common factor which causes it to happen?

Sandy