Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!wuarchive!cs.utexas.edu!hellgate.utah.edu!uplherc!giga!unislc!dgb
From: dgb@unislc.uucp (Douglas Barrett)
Newsgroups: comp.sys.next
Subject: Re: Mac emulator
Message-ID: <1990Oct29.005935.18129@unislc.uucp>
Date: 29 Oct 90 00:59:35 GMT
References: <1990Oct21.045745.4446@midway.uchicago.edu>
Organization: Unisys, SLC Utah
Lines: 26

From article <1990Oct21.045745.4446@midway.uchicago.edu>, by gft_robert@gsbacd.uchicago.edu:
> ----- 
>>if anyone wants but I know it doesn't require Mac roms.  It reads them from
>                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>disk and puts them into memory.                                            
>  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Danger, danger Will Robinson: the above technique is HIGHLY illegal.  Whether
> you like Apple or not, their ROMs are their property.  Copying them is a BIG


The technique described above does not *require* the copying of Mac ROMs.
It is legal to sell an app which contains calls into what on the Mac is
os space.  it is legal to write software to perform exactly the same
function as existing software (ie rewrite the os from its external spec,
yes reverse engineer the sucker).  these software only emulators (if done
legally) preload an app with Mac os calls so that the calls are into the
space of the emulator's written from scratch new os calls.  all quite legal.
difficult to keep 100% compatible. slow.  so it all hinges on what is on
disc.  if it *is* (as stated above) really the Mac os it can only be done
with Apple's ok.  if the stuff on disc is a clone - then no problem.

----------------------------------------------------------------
Douglas Barrett                              I speak for myself
Unix Systmes Programmer
Unisys SLC Utah