FScommand

Sofware

• Abode Flash CS3

Problem Description

We have recently run into an interesting problem while creating an interactive launcher CD for one of our clients.  Our Flash designer reported that he used exactly the same code (adjusted for the new file names) used in the previous project, yet FScommand refused to launch the new EXEs.

Solution

This problem was caused by the naming convention we picked for the files…

1. FScommand would NOT launch files with dashes in the file name… Use underscores instead.
2. Under Vista, if file names contained words like Setup and Install, the OS automatically slapped a little shield on the files’s icon and would not allow FScommand launch the file.

Simply rename the files to solve this issue.