Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!uokmax!servalan!rmtodd
From: rmtodd@servalan.uucp (Richard Todd)
Newsgroups: comp.unix.aux
Subject: Re: AUX problems and documentation
Message-ID: <1990Nov22.044114.996@servalan.uucp>
Date: 22 Nov 90 04:41:14 GMT
References: <1990Nov21.233958.2682@nntp-server.caltech.edu>
Organization: Ministry of Silly Walks
Lines: 32

allen@nntp-server.caltech.edu (Scott R. Allen) writes:

>First of all, there is some discussion with the people that I work
>with concerning the subject of running Macintosh applications under
>AUX.  They said that AUX supports Mac software written for MAC/OS.
>Is this so?  
  
  It supports most MacOS software.  Programs that directly diddle the hardware
(e.g. your fancy SCSI utilities and the like) won't work.  

>If you can run MAC/OS intended software under AUX does that mean that
>the software will use disk storage in the MAC/OS partition of the 
>disk or in the AUX partition of the disk?
   Yes, to both.  The A/UX filesystem appears as a MacOS drive to the MacOS
programs (just click on the "Drive" button on the file dialogs and you'll
see the "/" disk drive).  

>If the MAC/OS software running under AUX using the AUX partition of
>the disk, is it smart enough to respect the unix file/directory
>permissions that are in place?

Yep.  (Doing a "chmod 444 System" is a wonderful way to get rid of the
Creeping System Corruption disorder MacOS seems to be inordinately fond of...)

>We are using AUX 2.0 with MAC X and we are 'lauching' windows to
>run the mac software in.  ('lauching' is greek to me.)  We have the
  Well, it helps if you spell "launching" right. :-).  "Launching" is the 
term Apple uses for starting up a MacOS program.  Don't ask me why they don't
just call it "starting up a MacOS program"...
--
Richard Todd	rmtodd@uokmax.ecn.uoknor.edu  rmtodd@chinet.chi.il.us
	rmtodd@servalan.uucp