shani@taurus.BITNET (03/13/91)
Hello. I've installed the MacX server that comes with A/UX distribution, and it's working fine, except for several problems I hope you can help me with: 1. clients only appear B&W. This could be a hardwer problem (no, I do have a color monitor :-), because I've had problems with other applications, but just to be sure, what should I check? 2. I've installed MacX under /mac/bin/MacX, and I seem to have problems with the fonts folder - Every time I start MacX, it says that it scans the fonts directory, and then a warning message appear, about having problems with writing to the fonts directory file. I guess it has do do with file permissions, but I tried chmod 777 the fonts dir file, and I tried using setuid, and it doesn't seem to help. Advise anyone? 3. Is there a way to change the mac window management to another one, say olwm? Thanks in advance, O.S.
abm@oxydol.aux.apple.com (Alan Mimms) (03/14/91)
In article <2413@taurus.BITNET>, shani@taurus.BITNET writes: |> Hello. |> |> I've installed the MacX server that comes with A/UX distribution, and it's |> working fine, except for several problems I hope you can help me with: |> |> 1. clients only appear B&W. This could be a hardwer problem (no, I do have |> a color monitor :-), because I've had problems with other applications, |> but just to be sure, what should I check? This has gotta be THE most common problem with people who have not read the manual or the release notes and getting started with MacX. (Note the hint: RTFM.) You'll want to specify that your clients connect to the server defaulting to screen #2 (rootless) or #3 (rooted) for color windows. This can be accomplished by using <hostname>:0.2 or <hostname>:0.3 for your DISPLAY enviroment variable. Or you can choose the screens in the "Display:" popup in the remote command dialog for rooted or rootless color. |> 2. I've installed MacX under /mac/bin/MacX, and I seem to have problems with |> the fonts folder - Every time I start MacX, it says that it scans the |> fonts directory, and then a warning message appear, about having problems |> with writing to the fonts directory file. I guess it has do do with file |> permissions, but I tried chmod 777 the fonts dir file, and I tried using |> setuid, and it doesn't seem to help. Advise anyone? Make EVERYTHING in the /mac/bin/MacX hierarchy be writable and readable to the world or at least yourself. This is because MacX wants write access to itself (or at least the Finder does sometimes) and to many of the fonts and folders in the MacX hierarchy. This is the easiest solution. |> |> 3. Is there a way to change the mac window management to another one, say |> olwm? Yes, you can use screen #1 or screen #3 and run the olwm window manager there. This is called "rooted" and is quite thoroughly documented in the manual. |> |> Thanks in advance, |> |> O.S. -- Alan Mimms (alan@apple.com, ...!apple!alan) | My opinions are generally A/UX X group | pretty worthless, but Apple Computer | they *are* my own... Art without engineering is dreaming. Engineering without art is calculating. -- Steven K. Roberts in "Computing Across America"