Digital Workshop

Opus publications can on a very rare occasion crash, normally on less than 0.5% of users going on my calculations, but there is always one. As usual with clients, the most you can squeeze out of them is the operating system version, maybe the RAM size or that it is a laptop or Dell or something completely useless, not helpful in fixing the problem.

So can DW please develop a system variable, or script or DLL so we can have a button in Opus Publications that pulls all system details that are important for crash diagnose. This can then be emailed to us by the client via an email button and we can forward it onto DW if we cannot solve ourselves.

This would both help us, our client and of course DW, as it would result in a much more stable, although it's already very stable player.

I think at one time DW provided a program that gathered the same basic information that is provided when the user uses the Help|Contact Digital Workshop link in the Illuminatus/Opus program. It was provided because in some versions of Opus this feature fail to work.

I search my drives for such a file but came up empty handed. Maybe someone else remembers the program and could locate and post it.

Hi Leo, the utility file you are talking about is dwinfo.exe, which can be found here::

ftp://ftp.digitalworkshop.com/pub/support/

The utility(2005) needs updating -- Vista shows up as "Unknown Operating System!"
Also to be useful to Opus developers, DW would have to adapt it so the developer of the pub gets the support emails, not DW themselves.
We could then forward on relevant information to DW.

Paul

I want to be able to build it into my Opus Publications, not the editor. Similar to the System Variables available in Opus.

This would make it much easier to diagnose problems.

see
viewtopic.php?t=2934

this may be an option...very clunky, but worth thinking about as diagnostic which could be hidden in your pub until needed.

Sandy

That is great, thanks for the link to the post. I have just implemented this into my publication.

So using script I call MSINFO32.exe /report C:\TEMP\test.txt and then attach the create txt file as an email attachment. This will allow my clients to send me detailed system specs easily although the average 3 minutes time it takes Windows to pull the data is stupid.

I created an animation with a please wait text box, and then put a time out with a ticker, so script checks for the file every 10 seconds, and if after 600 seconds it does not exists it displays that unable to create support file.

Works good in testing. Does anyone know what versions of Windows supports MSINFO32.exe, I understand 2000, XP and Vista does, but does 9X?

Good to hear it works and the animation is a good idea. A quick search reveals:-
http://www.computertips.com/Windows/Win ... 916002.htm
so it seems to have been around since win 95.
Sandy