Digital Workshop

When launching an executable - say "THIS_FILE.exe" from within a folder that has already been stored in the published directory
using <SYSTEM_PUBLICATION_DIR>

What should be typed into the
"The file will be found at this location box"

I'm trying.....

<SYSTEM_PUBLICATION_DIR>:\FOLDER

Tired and it's late!!!!

Remove the colon (:) from that path and everything should be fine.

Thanks I will try that

Pete

This appears to have reared its ugly head again.

I have an executable in a sub folder (also contains qtvr's) the reason I chose a sub directory was because the Opus renaming facility was overwriting qtvr file names when placed in the root folder.

But
<SYSTEM_PUBLICATION_DIR>\folder

No longer works - The executable will not run.

Ideally I would like Opus not to rename the qtvr files 000001.mov etc and use the original file names. Then I could put all files in the root pub.
But cannot see how to do this.

Pete

Managed a workaround using the resource manager - retaining the original file names for the qtvr's - However that does not explain why the

<SYSTEM_PUBLICATION_DIR>\folder

didnt work.

Any ideas anyone?

Pete

Hi Pete,

Works fine here using Opus Pro XE 5.5

Are you using any optional parameters that could be causing a problem?

The renaming of the MOV files should be able to be changed to how you want in the Resource Manager, so original filenames are used.

Steve,

Hi,

I remembered about retaining file names - so in essence I was able to overcome the problem.

However, regarding the folder within the publication.
No not using any other parameters.
<SYSTEM_PUBLICATION_DIR> works fine
<SYSTEM_PUBLICATION_DIR>/folder does not

I am using XE 5.5
I may try a new pub from scratch and see if it is still "broken"

Pete

Ermmm

<SYSTEM_PUBLICATION_DIR>\folder

On a new publication - it works!!!

Bizarre - the original publication was started in version XE v 5
Perhaps thats it?

I recall now a similar issue when I produced a publication with a slideshow with images extracted from a folder in the publication directory.

Again, starting from scratch resolved the issue.

Must be going mad.

Thanks for the input Steve.

Regards
Pete