in reply to How to run MacOS Classic app in OSX? system() can't run it..

system( "open .../myapp" ) should work. See man open.

Update: The ... was meant as ellipsis to indicate the full path to the app, not a literal ... in the path.

Replies are listed 'Best First'.
Re^2: How to run MacOS Classic app in OSX? system() can't run it..
by Anonymous Monk on Feb 03, 2006 at 16:06 UTC
    Thank you for your answer!

    When I run in while in the same directory where app resides, and run as open ./myapp
    I get

    2006-02-03 08:08:59.110 open[396] LSOpenFromURLSpec() returned -10814 
+for application (null) path /Volumes/Untitled 2/myapp
2006-02-03 08:08:59.114 open[396] Couldn't open file: /Volumes/Untitle
+d 2/myapp

    [download]
    When I run
    open .../myapp
    I get 
    2006-02-03 08:17:49.352 open[429] No such file: /Volumes/Untitled 2/..
+./myapp

    [download]
    What the case #1 means - is it a bug in the app I run, or something is wrong with the binary file?
[reply]
[d/l]
[select]

      I'd guess something's wrong with myapp. I just verified that open does start Classic apps (ran the OS 9 versions of SimpleEdit and Graphing Calculator using it fine). 

      perl -le 'system( "open", "/Applications (Mac OS 9)/Graphing Calculato
+r" )'

      [download]
[reply]
[d/l]
        In my case, I guess './myapp' has lost resource fork information (I've copied it using ftp program). Can it be the reason why it doesn't run? I'd like to put the 'myapp' to CD with ISO9660 filesystem, so resource forks won't be available there. Are there any special commands for running OS9 binaries without resource forks available?

        Thanks in advance for your answers!

[reply]

In Section Seekers of Perl Wisdom