> Hey, it works! (As far as I've tested it). Again, I'm on NT 4 (SP6), Dell > 410, with Intergraph card. > > Suhaib was right: we really had to get the latest greatest Exceed and > Exceed 3D including all patches and we did a complete uninstall, reinstall > to be on the safe side.
I am good to hear. 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. > > Now, there are a couple things about installing it that the README leaves > to the imagination of NT newbies, probably old hat to hardcore > Microsofties. > > To wit: > That mystery file called > Opendx/bin/Exceed/user/ExceedXDKRegistrySettings.reg actually has to be > modified, then run. This is not mentioned in the README which simply says > to drag all the Opendx/bin/Exceed/user files to one's Exceed/user > directory. 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. > > We had to hack it slightly to change paths of our actual Exceed > installation, then of course run it (with sysadmin privileges) to update > the registry. BTW, on our systems, the install directory is called > Exceed.nt. Exceed.nt is default installation. I usually change it to Exceed to have not to many dots on screen :-) > > I still can't figure out why the X11/bitmaps are needed for DX but I > dutifully put them where they go. Where they go is also not > totally evident > if one reads the README and follows the instructions exactly. What Suhaib > means, I'm now sure, is that one copies or moves the directory called > Opendx/bin/Exceed/xdk/include/x11/bitmaps to one's Exceed/xdk/include/x11 > directory (I find a directory called Glw already there). You put it in the right place. Glw contains headers for GLw (GL for MOTIF) > > There is something I still don't understand. There is a file called > usCaps2Ctrl.kbf in the Opendx zip that purportedly goes to Exceed/user > directory. I don't know how this is invoked: experimentally trying to open > it with Exceed's keyboard configuration dialog yielded the error that > "Cap2Ctrl.kbt" could not be found. This is line 2 of the usCaps2Ctrl.kbf > file. Any ideas? I haven't figured out what this does vis-a-vis DX, yet. Another developers, who work on cygwin/xfree project gave me that file. Exceed supposed to have a utility to create *.kbt file from it. I will figure out how to do that.. never got time. > > > OK, all that stuff installed, registry updated, rebooted for the hell of > it, and launched OpenDX 4.1.1 on NT. Fired up some samples, then got down > to business and opened a 157x167x80 volume (lung cancer CT scan data) and > rendered a 191K triangle isosurface and a 355K polygon ShowBoundary around > an Included subset of the volumetric data and waggled them around in > hardware rendering in "real" time (just like being there). Cool... > > Lots more to test and try (haven't tried the ImageMagick stuff yet and > that's going to be important). 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.... > > Cool! > > Thanks Suhaib! and Greg! > > P.S. I also discovered an interesting problem that has nothing to do with > the NT build cause I've seen it on Irix as well: I'll report that > separately so as not to detract from the present euphoria. (:-) > > P.P.S The khaki modules are definitely going to make me hurl. Anyone know > where the UI gets its colors from? Can this be changed by end > users or does > it have to be recompiled pointing to a different Xrdb? No, it is X_server dependent. If you have alook at screenshot of opendx at http:/sourceware.cygnus.com/cygwin/xfree/screen.jpg 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. Suhaib > > > 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 >
