Path: utzoo!attcan!uunet!decwrl!sgi!shinobu!odin!harlie.corp.sgi.com!scotth From: scotth@harlie.corp.sgi.com (Scott Henry) Newsgroups: comp.windows.x Subject: Re: Problem:Cannot allocated color cells Message-ID: <1990Oct26.203000.9353@odin.corp.sgi.com> Date: 26 Oct 90 20:30:00 GMT References: <9010271719.AA01444@oz.solvit.co.kr> Sender: news@odin.corp.sgi.com (Net News) Reply-To: scotth@harlie.corp.sgi.com (Scott Henry) Organization: sgi Lines: 30 In article <9010271719.AA01444@oz.solvit.co.kr>, weon@oz.solvit.co.kr (Taehwan Weon) writes: |> Operating System : IRIX 3.2 |> |> I suffered from an X server problem - that is all that I can guess. |> My machine is Personal IRIS running X11R3 & NeWS from Silicon Grphics. |> When I invoked some X clients from remote machines, like FrameMaker, or |> acm, they complained and aborted with the message, "Cannot allocate color cells" |> Is there anyone who expreienced with the problem ? The SGI X-server uses the system-wide colormap. The default is to allocate 16 (under 3.3, anyway; I think it was the same under 3.2) cells as read/write, and the rest of the colormap is read-only. Many programs will fail because the server runs out of colormap cells it can allocate (the read/write ones). Read the Xsgi man page for a fuller discussion, but you can change the way the server shares colormap resources with the NeWS server at Xsgi startup time. `Xsgi -gl` will allocate most of the colormap as read/write cells to X, though GL programs can still step on them. The X-server performance has noticably improved from 3.2 to 3.3, so it would be very worthwile to upgrade. -- Scott Henry / Traveller on Dragon Wings Information Services, / Help! My disclaimer is missing! Silicon Graphics, Inc / Politicians no baka!