> Last night I wrote a little utility for X-servers on
>WIndows.
>It reports all the extensions installed on your X. On unix you can run
>xdpyinfo.
>On Exceed xdpyinfo they ship with exceed, does not even do anything, you
>execute it, and it will
>return the command prompt again.  My utility can be useful in finding out
>what
>actuall extensions the x-server has.  To my suprise, Exceed has only 9
>extensions, including GLX.... compared to 23 on Linux with Xfree.
>

I found a file called Xlib.log at the C: level (even though Exceed is under
Program Files), that reports a bunch of errors followed by what looks like
the output of xdpyinfo. I'm sure this was created a couple days ago when I
was having trouble (before reinstall), so I don't know what event created
it (it implies that Exceed could do an xdpyinfo if one pushed the right
button). The errors are all of the form "translation table syntax error:
Unknown keysym name: osfActivate, etc.  etc. which also happened visibly in
the console that started the dx -edit (Editor) batch file. These problems
seemed to finally be squelched only after we modified and ran the Registry
file you provided, so I think that while it is definitely possibly
dangerous, it also probably has to be run to make DX and Exceed talk to
each other nicely on NT.

Greg, I'll bet this was the thing you tweaked on your machine that made
your build work for the VDE conference, but we ran into this same sort of
problem last month and never got your build running. Sound familiar?


>I left it there intentionally, and did not write anything about it
>intentionally.
>To be on safe side, users who knows how to hack around RegEdit, they would
>recognize it from its icon immediately and will look at it... So they do not
>need
>explainations... but if I write details then novice will experiment, have
>their Window
>totally messed up then yell at me... therefore I decided not to talk about
>it, leave it their
>for others to discover it and find out how I have DX and Exceed integrated
>on my NT and Win2K.
>

Undoubtedly wise: it was one of our sysadmins who explained it to me when I
asked "what the heck is that for and why isn't it in the registry instead
of the Exceed directory?" (:-)  He agreed that screwing it up could have
"ramifications" (which I think in Microsoftese freely translates to
"reinstall the OS" or something) (:-o


>
>It works sorta for me.  I could never figure why when i chose save as
>ImageImagick Format, I get
>coredump on Linux and Windows and even SGI....
>

OK, sounds like the ongoing problem with the IM 5.2 issue maybe.


>
>The modules are blue and fonts are big with my Xfree86 ported X-servers.
>You can custimize your colors by making your own rgb.txt file and
>recompiling rgb datase using xrdb.


OK, I'll try that.

Chris Pelkie
Vice President/Scientific Visualization Producer
Conceptual Reality Presentations, Inc.
30 West Meadow Drive
Ithaca, NY 14850
[EMAIL PROTECTED]
(607) 257-8335 or (607) 254-8794

Reply via email to