Digital Workshop

I have a publication for a major client that is distributed throughout Europe. A number of users have reported a warning message: This publication may have crashed last time. with options to disable various Active X controls.
There does not appear to any common reason for this message being displayed (other than it only appears for opus programmes) and it does not happen every time the programme is run.

My client has requested we fix this. So any thoughts on how to resolve this ?

Thanks.

What version of Opus are you using? And which release?

There was an issue with the initial release of 05 that could cause this dialog to display in error but the issue was resolved in Service Release 1.

The warning may well be indicating a problem with the end-users PCs (particularly if it is only some of their machines), in which case upgrading to the latest graphics drivers and/or DirectX version may solve the problem.

Hi Duncan

I've also spent a lot of time supporting users of my publications that get the DirectX dialogue. I must emphasise that this is with publications made with earlier versions of the program. For non-technical users the idea of updating drivers and DirectX is pretty much a no no. Moreover, the publications often seem to work absolutely fine if they just cancel out of the DirectX warning anyway.

Couldn't it be an option, when creating an Opus publication, to not display the DirectX warning following an unexpected termination? It seems to serve only to confuse some of my users. They tend to use its advice to disable various options when they'd be better just ignoring the warnings and cancelling the DirectX dialogue. We often end up rooting around in their registry to re-enable bits of DirectX that they have turned off following the warning. That's never a good idea with non-technical users.

Andrew

Hi Duncan
The publication was created on an older version and is about to updated.
I am now running version 5.14 so I hope that your comments about latest version has fixed this issue are well founded.
Whilst I understand that this may be a client machine problem, I echo Andrews comments that the publication appears to run perfectly if the message is just cancelled without action and does encourage users to disable functions unnecessesarily. So the ability to disable the warning message is a great Idea.

My client has raised this concern as the single (for single read only) largest reported system problem, so I hope you are correct.

I will keep you informed of any future occurances.

Martin

See my post (and resultant replies from DW) of July 6th.

I experienced this problem, but it definitely doesn't occur in version 5.14