Received: from Terminus (ppp-2.ts-7.hck.idt.net [169.132.49.146]) by styx.ios.com (8.6.12/8.6.9) with SMTP id BAA10094; Mon, 22 Apr 1996 01:05:53 -0400
Mime-version: 1.0
Message-id: <199604220505.BAA10094@styx.ios.com>
Cc: executor@ardi.com
Subject: Re: Windows95-Executor/DOS multitasking
To: Dave <dmh@cnct.com>, NO GOOD DEED GOES UNPUNISHED <DECLARKG@DEPAUW.EDU>
X-mailer: Windows Eudora Light Version 1.5.2
From: Ian Viemeister <vmeister@ios.com>
Date: Mon, 22 Apr 1996 01:04:22 -0400
Content-type: text/plain; charset="us-ascii"
X-sender: vmeister@ios.com
Sender: owner-executor@ardi.com
Precedence: bulk
At 11:57 PM 4/21/96 -0400, Dave wrote:
>On Sun, 21 Apr 1996, NO GOOD DEED GOES UNPUNISHED wrote:
>> Dear All,
>>
>> A while back, I asked if anyone had succeeded in getting multiple
sessions
>> of Executor to run in Windows 95. I was just wondering if I should interpret
>> the silence as a "no"?
>
>Correct me if I'm wrong (anyone?) but I beleive that Executor is designed
>to be have only one occurance running per cpu at any given time.
That's not the problem - the "Single CPU" means that you can't, say, put one
copy of the executor binary on a network and have multiple machines use it
at the same time.
The problem with running multiple instances of Executor/Dos (E/L and E/NS don't
have this problem), is that exsystem.hfv (and possibly other hfvs) are opened
with a mode that blocks another instance from opening it. Try this: make
exsystem.hfv Read-Only. You then should then be able to run multiple sessions,
_but_, you will not be able to:
1) Save the browser state
2) Install programs that add things to the system folders
3) Save Preferences in programs that use the system directory
Additionally,
4) You may still have conflicts/corruption if two sessions try to access
the same hfv (like tmp.hfv, the demos, or your own hfv)
