This article is from the MachTen & CodeBuilder FAQ, by Jaime Julca firstname.lastname@example.org with numerous contributions by others.
MachTen ships with R5, but XTen ships with R6. MachTen with X11R6 is
available on the PPC Ported Apps CD. CU1 is also included on this disk and
should be installed before installing X11R6.
G10.h. I tried to launch XWindows with a ctrl-T, but I got the following
error: 'fatal IO error 32 (Broken pipe) on X server ":0.0"' What happened?
How do I fix it?
MachTen 4.0.x comes with X11R5, which supports only up to 256 colors. Make
sure that your monitor is set to 256 colors. An incorrect monitor depth is
usually the cause of the above error message.
G10.i. The background for the X Window is 'opaque', i.e. I can't see my
underlying Mac windows. How do I do this on the Tenon X Server?
There is no way to use "rootless" windows in MachTen. Dedicated X windows
enhances performance many-fold.
G10.j. Why does creating a new window from the File menu kill the X session?
It doesn't. Visit the window menu and reselect the X session as the window
you would like to view.
G10.k. System memory likes to bloat up to 20 or so MBs whenever I have more
than a few things running under XTen. Is this normal?
Traditionally, X assumes your system has limitless memory, so this is normal
behavior for any X system. Most of the memory allocation from MachTen/XTen
takes place in conjunction with the Code Fragment Manager, which allows us
to dynamically allocate memory in the System bar. Very little allocation
happens within the MachTen/XTen program space, which is why we ship with a
rather low amount of memory assigned to MachTen/XTen in the "Get Info" box.