> The main problem was to replace the hardware accesses (interrupts, keyboard
> etc) in the OS itself with something that worked on an ST.
> Figuring out a way around the protected lower memory wasn't easy either.
> QDOS has system call vectors down there that applications in user mode
> might read, and I know MacOS has similiar problems. On >='030 processors that
> can be fixed via the MMU, though (not yet done in QLem).
Hm, yes, this is a problem, though I don't quite understand how user
applications can access first 32k of the memory. Some Super() and
Supexec() equivalent is available perhaps?
The question is if Mac applications can access these variables directly.
If not, they don't have to be at the original place. If they can, some MMU
stuff is really needed.
MacOS itself causes copyright problems I guess. But it is avoidable. At
least, we have a fully featured operating system, so perhaps it can
emulate MacOS calls only with some code between the application and the
Atari OS. It would be completely nice, if a Mac application could run in
parallel with Atari applications under GEM. Well, to think about anything
on reliable way we need some Mac knowledge for sure, without any good
documentation about Mac system all this is only a theory.
Thanks for the QL notes, without a knowledge of _ANY_ command I could
only watch that white&red screen. Could you consider adding the same as
you wrote in the previous mail (about QL) to the emulator documentation?
BTW. I know its hard to write a doc for a well-known system :) I had
similar problem...
--
Konrad M.Kokoszkiewicz
|mail: draco_at_mi.com.pl | Atari Falcon030/TT030/65XE |
|http://www.orient.uw.edu.pl/~conradus/ | *** FreeMiNT 1.14.8. *** |
** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.
Received on on. april 29 1998 - 17:15:00 CEST