Digital Workshop

I am using a dummy SCO on an LMS to launch files too large to launch from the LMS. Of course, the action is "launch drivename/filename."

Anybody recommend a way to stop everything and return an error to the user if this file is not found?

It's probably easy, but my brain is fried...

Dave

Mack - Any LMS has to play to its weakest link. In our case, most of our target group, rig crews, are at the weakest link where we can only assume around 35KBps from the dish reliably as we have the lowest data priority. So, even a small, say 10mb, sim, is not going to happen.

So, I worked out a way to use the LMS to launch the sims from a local drive (loaded/updated via BG task) and then the local app passes data to the LMS on exit.

Some of our sims are 100mb or so, and since it's a single executable it all has to be there for anything to happen. This way, we get delay free response to the user.

This is probably the easiest issue I've faced making this work...but I'm tired and brain dead.

Dave

Is that background task run from w/i Opus?
If you have previously used the 'OpenFile()' action/command in Opus, it is a good idea to execute the 'CloseFile()' when you've completed things.

Try something like the fileExists function to check for the existence of the file...
Similar to...

if (FileExists("drivename/filename"))
{
// launching code here... launch ("drivename/filename");
}
else {
message = "file missing..."
}


Paul

Hi Dave,

FileExists won't work from a web-based publication. BUT then neither should launching a local file...???

Mack

You are correct, Mack. Opus prevents this as do most responsible codes...but we have an extraordinary IT department that found a work around for our intranet. I am not going to say how as this is a sensitive area but since we are working in our on intranet it's OK.

Dave

I'm sure there are 'safe' ways to achieve this.

In answer to you question and as you have a clever IT department, here's one such idea.

Use something like a cron job to run a script that checks for the file and if found write a value to a database that is designed to track your packages. The web publication can access the database without problems.

Regards,

Mack