Was re:lanching application

[Roberto]

Hi Bengt,
Sorry for the delay time...

Yes you are right i've missed some info about what i'm trying to do.

The application i'm trying to launch in multiple session is FileMaker Pro.
I'm pretty sure that the app when launched scan process and try to get is
proces name (fmpro3 is the name of the process) and if it find a new
instance will not open.

I've asked this because with the application FireDaemon this can be done.

Maybe running FileMaker as a subprocess of a python instance will prevent
the process name search?

Thanks for replying
-- 
Rob



I'm not sure what you mean by "natively multi-session." ISTM that's the
default. If an OS normally
launches programs in separate processes, UIAM the programs have to be
programmed specifically
to _prevent_ running simultaneously. Various tricks can be used to
accomplish that,
so if you have a program that "is not multi-session" because it is
successfully
noticing that it is not the first instance to run, and exiting (some might
communicate
parameters to the running instance before they do that), then ISTM you are
asking
how to interfere with that program logic. E.g., if it is mutex-based, can
you
prevent the second instance from seeing the mutex? What if it's based on a
lock file,
or scanning current windows for title text? If there's a DLL using a shared
memory section
to act as a mutex, maybe there's a way (OTTOMH I don't know of it, but I
wouldn't be surprised.
I haven't had to deal with that situation) to tell windows always to create
new instances of shared
sections for it, and maybe that's what you are asking, but then you'd have
to know that that's the
mechanism that makes your app "single session."

Maybe telling us what app are you trying to launch multiple instances of,
and on what windows version
would get more helpful responses? ;-)

Happy Holidays,

Regards,
Bengt Richter