Digital Workshop

I'm having some trouble with the 'troubleshooting dialog' window that appears next time you try and run an opus publication after crashing.

My main question about this is:

- Is this dialog supposed to appear every time the user tries to run a 'digital workshop' publication, or just the publication that crashed? or is it supposed to appear just the one time after the crash, but keep the settings that were set in it's first appearance?

I would guess that it is supposed to appear just the once for only a publication of the same name and keep the direct X settings every time the same publication is run?

My problems seem to show however that the direct x settings from the troubleshooting dialog are kept even when the publication name is changed, which is surely not as intended?

I say this because of my experience on a publication I have been developing on and off for some years now. Recently, the autonarrate function stopped working when running the publication (but was OK in preview). This had me puzzled for a long time, thinking that I'd installed some conflicting software etc etc.

Then out of the blue when running the publication, the troubleshooting window appeared, I unticked the disabled options on direct X sound and direct X graphics and the autonarrate worked again! Then I remembered that 6 months ago when I last worked on the publication (this is a long time for my memory), I had some problems with a GIF animation that was freezing and must have tried direct X disabled when the troubleshooting dialog appeared.

6 months later when I started more development, it appears that every time I was running the publication Direct X sound and Direct X graphics were disabled BUT there was nothing to tell me this was happening!

Note that the publication name WAS changed during the development ( _v10, _v11 etc was added each time I made significant changes), but the direct x disabled settings seemed to have been carried over every time.

Not really sure why the troubleshooting dialog finally decided to re-appear, but possibly because I had reached the end of my current development on it and made a more substantial name change?

This is a bit worrying as a similar thing could happen to a customer, i.e. the troubleshooting dialog could appear, they turn off direct X graphics and sound, then can't turn them back on again when I send them another version, in fact they don't even know they are still disabled.

.......or am I missing something?

/Mark

Mark,

I have had this problem for years now. I have been developing with Opus/Illuminatus for over 12 years and I've created 110 programs (just went back and counted them). I've had this problem a dozen times. I have hoped that it would be fixed by DW, but most of the time I can't get an answer from them on this subject, in fact I wrote to them AGAIN today about this very matter. Good Luck to me and you both on getting an answer. I'm just affaid that it's a problem that they don't want to have to answer since I've never gotten a straight answer from them on it.

viewtopic.php?t=3419&highlight=troubleshooting+window

As you guess, the dialogue appears after a crash due to a system or publication problem. The box should stay hidden if the option is checked but as this value is written to the registry then I suppose it's perfectly feasible that either it's not recognised due to a registry problem or something else is a miss with the publication that is stopping it recognising that it has already been displayed.

If you have tried running and publishing under a different machine and the problem disappears then this would suggest a registry problem which may or may not be related to DW. I've had various pieces of software over the years that due to some form of registry corruption often refuse to save settings.

Try locating and deleting the DW keys (caveats apply) and or use a registry cleaner / defag such as uniblue to keep such problems at bay. If the problem does occur on multiple machines, then it's likely publication based, and as Denn will attest tracking the problem down then becomes an art.

Mack