Path problem with fscommand "exec"

[ncorbett]

I'm trying to launch an application nested one directory down from the Flash projector. The fscommand code works when the application is in the same directory, but when I move it into the subdirectory - logos - it can't access it anymore.

What am I doing wrong with the path name????

on (release) {
fscommand ("exec", "logos/CA_BLK_S.SEA");
}

Please help!

ncorbett

[pixelwit]

Not sure, but have you tried switching the "/" to a "\"?

[ncorbett]

Yes I've tried:

on (release) {
fscommand ("exec", "logos\\CA_BLK_S.SEA");
}

too. No luck yet.

[Jesse]

one dir down?
well if this is your structure:

root dir
--current dir
----projector file
--logos
----SEA file

you'll need you path to be soemthing like:
../logos/CA_BLK_S.SEA

but if youcan't get that to work look into the output of:

myURL = _url;

this will allow you to build a full path.

[ncorbett]

Thanks for your replies all.

If anyone is interested, here's how it was resolved - plus a little more detail about the issue....

The project was to be delivered on two CD-ROMs - 1 Mac and 1 PC. I was doing most of the coding on the Mac side, and then pulling over to the PC for any changes.

I could not get the Mac version to use fscommand "exec" beyond any application (in this case Self Extracting Archives - SEA) in the root directory. My work around solution was to create aliases in the root directory for all the SEAs in the sub directories (yes, one level down). As this was being delivered and played on a CD-ROM, I was able to make all the aliases in the root directory invisible when I burned the disk. Worked seamlessly and like a charm.

The PC side was able to recognize path names with no problems. They were written in this form:

logos\\filename.exe

Thanks again for your help everyone. I'm new around here, but expect to be around quite often.

-ncorbett