[AS2] Linking Flash (MAC) to an existing .exe file

[BOPT]

Hello,

I'm having trouble linking my Flash file to an existing .exe file.

I'm working in CS3 on a MAC. I've set up the link to the .exe file using the fscommand. I've also placed the existing .exe file into the fscommand folder that is contained in the same directory as the Flash file I'm working from. All of my other links (to PDFs and URLs) work just fine. I'm generating both a shockwave file and an .exe file of my Flash project in hopes that, when run on a Windows platform, the .exe of my project will link to the existing .exe file in the fscommand folder.

Yet, nothing is working. I've used the following code:

on (release) {
fscommand ("exec", "name of existing.exe");
}

Any thoughts or suggestions -- this seems pretty straight forward but I can't seem to make it work. Thanks!

J

[northcode]

Was the EXE you're tryinig to EXEC created with Flash or did it come from somewhere else?

What's the actual name of the EXE?

Are you trying this on Vista, XP, 2000... ?

[BOPT]

The .exe I'm attempting to link to was generated elsewhere, not on a MAC, though the details are hazy and have not been provided despite my requests. I do know that they work separately when used in XP or Vista.

I'm not entirely comfortable sharing the name of the file as that's private information but I can tell you that it is 5 words long, no underscores with some numbers in the title also -- in case that impacts things. They're also about 87MB a piece.

[northcode]

But are they Flash projectors? Flash CS3 doesn't like launching EXE files in some cases. You can read more here: http://www.northcode.com/blog.php/2007/08/14/FSCommand-EXEC-is-Broken-in-Flash-CS3. Spaces in the file name may also cause problems. You can use my FREE proxy tool (http://www.northcode.com/blog.php/2007/08/07/Conquering-FSCommand-EXEC-Part-1-Proxy) to get around these issues on Windows

The only reason I ask about the name is that, on Vista, some words trigger heuristics that make Vista think the app you're trying to launch is an installer or setup application and it automatically assumes it needs admin rights. You can tell if that's the case if the icon (when you view it on Vista) has a shield added. That's the visual clue.