Running multiple images on Intel Mac

For the life of me, I can't get my Intel Mac to launch 2 instances of  
the same image.  No matter what method I try, double click the image,  
drag the image, command prompt, shell script, it just raises the  
first one that is already running.  So far I've only been able to  
launch the aqua vm for one, and the X11 vm for the other to get them  
going.  Anybody know how to fix this?

Thanks,

Mike

The same thing happens on PPC Mac. I solved the problem on PPC Macs  
by duplicating the VM and use a different VM for each image. (Drop  
the image on each VM or right click on the image and use the "open  
with..." option. You will want to use copies of the image also so  
your .cha files remain correct.

On Mar 9, 2007, at 6:14 AM, Mike Hales wrote:


----
Roger Whitney              Department of Computer Science
[hidden email]        San Diego State University
http://www.eli.sdsu.edu/   San Diego, CA 92182-7720
(619) 583-1978
(619) 594-3535 (office)
(619) 594-6746 (fax)

Mike,

The problems may include things like stdin/stdout, copy/paste, that
weird Mac menubar thingy at the top of the screen (rather than at the
top of your windows), etc., I'm not sure. Keep the thread on the list so
others can keep contributing. You've got the sum total of my knowledge
on this topic anyway.

Dave

Mike Hales wrote:

> For the life of me, I can't get my Intel Mac to launch 2 instances  
> of the same image.  No matter what method I try, double click the  
> image, drag the image, command prompt, shell script, it just raises  
> the first one that is already running.  So far I've only been able  
> to launch the aqua vm for one, and the X11 vm for the other to get  
> them going.  Anybody know how to fix this?


I found the following solution:

Use a wrapper program to launch the VM, in the launching code pass a  
special flag to tell the OS to allow multiple instances.  
Associate .im files with this .app.

I have this half-baked visualworks launcher .app I once started  
coding,  kLSLaunchNewInstance is the extra flag that does the trick  
in this snippet:

        [...]
        LSApplicationParameters  appParams;
        appParams.version=0;
        appParams.flags=kLSLaunchNewInstance | kLSLaunchDefaults;
        appParams.application=&appref;
        appParams.asyncLaunchRefCon=NULL;
        appParams.environment=environment;
        appParams.argv=NULL; // ignored since Mac OS X 10.4
        appParams.initialEvent=NULL;
       
        err=LSOpenItemsWithRole(file,1,0,NULL,&appParams,NULL,0);
  [...]



I don't know whether this flag can be set in the Info.plist of the  
Vm's .app or maybe in the header of the VM binary. Any Mac coders  
here who know?

If not Cincom could make such a wrapper in the VM.app be the default  
executable declared in the Info.plist




HTH,

Reinout
-------

On Mar 17, 2007, at 1:45 PM, Reinout Heeck wrote:
>
> If not Cincom could make such a wrapper in the VM.app be the  
> default executable declared in the Info.plist

Forget that - it would require a .app inside a .app which is not  
possible AFAIK.

R
-

And if you don't like coding a wrapper .app you could try this as a  
workaround:

http://scrap.dasgenie.com/articles/2005/08/26/start-it-again-mac


R
-

My apologies for the monologue but I couldn't resist:


If I do a Google search for kLSLaunchNewInstance Apple's reference  
documentation comes in as the *very last* in the results.

Now I know where to look :-(


R
-