|
|
1.1 root 1: gulam's "mem" command will produce nonsensical results, since it looks
2:
3: at the GEMDOS memory list directly, and according to GEMDOS all the
4:
5: computer's memory is allocated to MINT.PRG. "mem" crashes under TOS 1.4
6:
7: anyways, so this problem is not new.
8:
9:
10:
11: Turtle reports an error in memory configuration; yet the configuration
12:
13: printed out looks perfectly fine. I don't know whether this one is
14:
15: turtle's fault or MiNT's. (Probably turtle's: the problem has also
16:
17: been reported on newer versions of TOS.)
18:
19:
20:
21: GFA Basic programs often (usually?) try to use memory they don't own.
22:
23: Needless to say, this can cause problems under MiNT, ranging from
24:
25: bus errors to a system crash.
26:
27:
28:
29: A lot of programs don't act very nicely in a multi-tasking environment.
30:
31: Programs that redefine the keyboard (eg gulam), run in supervisor mode,
32:
33: or steal interrupt vectors can cause problems. (Programs in supervisor mode
34:
35: tend to hog the processor, because MiNT won't pre-empt them -- this may
36:
37: be excessively cautious of MiNT, but it serves to avoid any problems with
38:
39: device drivers). If you're only running one program at a time under MiNT,
40:
41: these problems don't arise.
42:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.