Checking for updates

[Worm]

Re: Checking for updates

The only thing I can think of is to use the subst command in a file.execute to set the path to the root of a virtual drive. (i.e. subst Q: "C:\Program Files\Authorware"). You'd have to find a free drive letter, and have to make sure you deleted the drive on close (subst Q: /d).

Maybe the Authorware won't run from the virtual drive though. That'd be something to test I guess.

[eric_darling]

Re: Checking for updates

Ah... I finally had a chance to get around to this. Indeed - when the Authorware project ran from the root C directory, everything was peachy. Any further help much appreciated!

[Worm]

Re: Checking for updates

I hear ya... it looks to be a long week here too.

[eric_darling]

Re: Checking for updates

Now why didn't I think of that? I'm at home tonight, but I'll check it on the office machine in the morning, and report back. Thanks for the espresso mind shot, Worm. It's been a long week.... What? It's only Monday? [img]/ubbthreads/images/icons/smile.gif[/img]

[Worm]

Re: Checking for updates

Could the Authorware be using non relative paths? If you put the Authorware in the root of the HD, does it work?

[eric_darling]

Re: Checking for updates

Sounds like it work, but there is a wildcard at work, unfortunately. I cannot get the Authorware project to run from the HD at all - even after I build the project. However, after I create the CD, and place all project files in the right places (for Authorware, that means the root directory), everything runs great. Perhaps this is something to do with the coding of the Authorware project? But why would it not work from the Distribution folder on the HD?

[Worm]

Re: Checking for updates

When there is an update, could you copy the Authorware project to the HD, download the update and overwrite, set a Registry value to indicate whether the Authorware app is run from the CD or HD. Have the AMS project check the registry ro determine where to run it from.

[eric_darling]

Re: Checking for updates

Updates will be downloaded via HTTP.

That's the thing. Since it's Authorware, it's a lot like AMS. There are many associated files to make the project run. Then, what has me hung up is that the "old" version on the CD-ROM needs to be supplanted by the "new" version from the web site, along with all its associated extra files, although the AMS project will always run from the CD-ROM.

My brain hurts a little bit.

[Worm]

Re: Checking for updates

Eric,

Do you know how the updates will be delivered? Will there be a file to check against on a web site for version? I have some ideas, but without a tad more info, can't put it all together.

[eric_darling]

I am trying to produce a project for a client that provides a link to an existing Authorware executable on the same CD-ROM that I am deploying the AMS files on. It works fine as a file.execute command.

Now, this is where things get complicated. I do not author the Authorware project - that's another company's baby. Periodically, new releases of this project will be made available. So, how do I program into the AMS project a button that a user can click which will check for an update to this third-party software? Remember that because this will run from a CD-ROM, I need to find a way to download the new version to a user's hard drive, and then to have AMS reference this new version on the local hard drive instead of the one that gets distributed with the CD.

I have no idea. Any suggestions greatly appreciated!