Digital Workshop

When you right-click on an executable file in Windows, selecting Properties opens an information box that includes a tab for Version, where the file's version, description, copyright and other information is displayed. I've never found a way to create an Opus publication that includes data into these fields. A publication with this data included in such a way would be very useful (not to mention looking more professionally produced).

Is there any way to do this in Opus Pro XE 05?

Is there a "hack" that can accomplish this?

Are there any plans at DW to include this capability?

I'm afraid that the compression and code protection that we use on our player prevents this data being modified. Without that compression the player is almost 13Mb - which is not practical for many users.

We used to include generic information that mentioned Opus and Digital Workshop, but people complained that their customers could "find out how they did it", so it was removed.

In that case, is it possible that a new release of Opus Pro XE might include the ability to fill in these fields prior to publishing?

No - once the player has been compressed for release not even we can edit it. We would have to produce players on a per customer basis; which we would possibly consider but it would have to involve some sort of charge to cover the time involved.

If you could simply provide an uncompressed player ...

Ah ... so the Windows display of program properties derives its data (in this case) from the Opus player.

Would it be possible to design the next release of the Opus player so that when s file is ready for publication, Opus automatically retrieves the licensed user name (my company name, for example) and some sort of version data (e.g. stored under Publication Properties in a field within the source *.IMP file) and incorporates them into the player for final output?

Just a thuoght.

... or mebbe a thought. Uh.

This is not the issue. When Opus creates a finished publication it is made
up of two parts, the executable code and the data. The executable is
copied from the Opus\players folders and the data is added to this to
create a single exe. The information on the properties comes from the
exe player. When we build the original player we have the option to add
this information, once this data is set there is no way to change it unless
you rebuild it. This is to prevent somebody changing the author
information on an exe that they did not develop.

So what Duncan was suggesting is we could build a custom version on a
per customer basis but we would need to make a charge for this service.

I hope this clears this up.


Regards

Brenden Knifton

Ah ... so if the player is untouched when it is incorporated into the published executable, it can't be amended (en route to final *.EXE) with any other data. Got it.

Brenden

If an uncompressed player were provided, the info could
be added and then the player could be compressed and placed
in the proper directory before publish. Or could be used
with .ilm files

Chris

:D. Click Me!

Chris,
you never cease to amaze me.

Hex Editors are very useful

cheers
Paul