home *** CD-ROM | disk | FTP | other *** search
- (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA66402;
- Thu, 20 Apr 95 16:48:39 -0700
- X-Sender: tg3@homer21.u.washington.edu
- Date: Thu, 20 Apr 1995 16:48:39 -0700 (PDT)
- From: Thurman Gillespy <tg3@u.washington.edu>
- To: Executor Discussion Group <executor@nacm.com>
- Subject: Executor Features
- Message-Id: <Pine.A32.3.91i.950420163146.89471O-100000@homer21.u.washington.edu>
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- Sender: owner-executor@nacm.com
- Precedence: bulk
-
- I'm new to this discussion group, but received no info on a FAQ or source
- of additional information. So here goes.
-
- I only use Macs, but I am distributing an image display program for
- medical images. People always want to know about a PC version, and I'm
- obviously interested in having my program run with Executor. Someone in
- our department got NIH-Image to run on a PC, which greatly peaked my
- interest. Unfortunately, I require some System 7 features, actually just
- the 4 required apple events, and the calls to CustomGetFile,
- CustomPutFile. So question 1, what are the plans for System 7 support? If
- you only supported the 4 required apple events, a lot more programs could
- run under executor.
-
- Question 2. How feasible would it be to specify a (bogus) system call
- that actually pointed to some 386/486 code that would run in native mode?
- This code would make no calls to the Mac API, but could do a processing
- intensive task that normally takes a real hit when run in emulation. With
- the release of the Metrowerks CodeWarrior Platinum system next month,
- this kind of mixed development will actually become very easy on the Mac.
-
- Thank-you for your attention.
-
- Thurman Gillespy III | Dr Razz, 16 bit image display program
- Department of Radiology | ftp://ftp.u.washington.edu/public/razz
- University of Washington
- Seattle, Washington
-
-