gulam's "mem" command will produce nonsensical results, since it looks
at the GEMDOS memory list directly, and according to GEMDOS all the
computer's memory is allocated to MINT.PRG. "mem" crashes under TOS 1.4
anyways, so this problem is not new.

Turtle reports an error in memory configuration; yet the configuration
printed out looks perfectly fine. I don't know whether this one is
turtle's fault or MiNT's.

QuickST works OK with MiNT, but there are some conflicts:
(1) if you run it before MiNT, it doesn't speed up text output under MiNT
(2) if you run it from MiNT (before running GEM), it works fine, but
    it grabs the BIOS Bconout() vector so that BIOS output can no longer
    be redirected to windows
Personally, I find (1) to be less of a problem, but if you never use
windowing systems (like mgr) then you may decide to go with (2).

A lot of programs don't act very nicely in a multi-tasking environment.
Programs that redefine the keyboard (eg gulam), run in supervisor mode,
or steal interrupt vectors can cause problems. (Programs in supervisor mode
tend to hog the processor, because MiNT won't pre-empt them -- this may
be excessively cautious of MiNT, but it serves to avoid any problems with
device drivers).
If you're not multitasking, of course, most of these problems don't arise.
