Digital Workshop

I have tried unsuccessfully to launch a publication that I produced with OpusProXE 04 from another publication that I produced with OpusProXE 04. The publication I want to launch is on the same CD in the resource directory. In looking at your documentation, I can't find any examples of a path to use for launching the file so I used SYSTEM_CD_DRIVE. What am I doing wrong?

Terry

Terry,

The best variable to use is the <SYSTEM_PUBLICATION_DIR> this variable stores the location
the publication is running from and is the most reliable option.
The Problem with SYSTEM_CD_DRIVE is it will always default to the first CD present on the
end users machine. Most current machines have more that one optical drive so there is room for error.


Regards

Brenden Knifton

The first time I published the program I used the SYSTEM_PUBLICATION_DIR but it didn't work. Do I need to put a back slash after DIR>\ and state where the file is located?

Terry

Terry,
I use a backslash.

After several attempts and advice from Robin, I was able to get exe files to launch from an OpusPro exe publication but it appears that with current antivirus software it isn't a practical function. That is, unless you turn off the users antivirus software because if you don't, it takes forever for the file to execute. If you turn the software off it comes up within a reasonable period of time. I would suspect the same holds true with launching web pages from an exe publication and doc files? Therefore, unless someone else has an answer for this, the only practical thing to do is recreate the program (in this case a quiz) within an existing publication but don’t try to send test scores because the antivirus software will send a warning that the program is sending information outside the network. It makes it difficult to provide solutions. KISS: Keep it Simple Stupid!

Terry Degner

Thank you for your reply.

I suspect that this is a similar issue to that experienced by 'kmartin' in this thread:

viewtopic.php?t=569

One of the solutions for this problem was to publish the executable with a separate data file (this option is available under Settings during the Publish Wizard).

Any installed antivirus software will still scan the publication executable when it issues the Launch File action, but as the executable is now much smaller in size, this scan should complete very quickly and allow the external file to launch without delay.

Please let me know if you encounter any further problems.

Kind regards,