This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Chris, I would suggest checking to make sure you didn't reboot into a 24bit X configuration using the xdpyinfo command after making sure that no message queues are hanging around. You might also check that your LD_LIBRARY_PATH is set- some environmental variables may have been changed. Steve Chiswell Unidata User Support >From: address@hidden (Chris Hennon) >Organization: . >Keywords: 200002232021.NAA23701 >Steve - > >Today I rebooted my machine and now my gf driver is hosed again. Same >symptoms as before, until you copied your gf driver executable into mine. >I don't know what to make of this. Please advise. Thanks. > >Chris > >================================================ >| Chris Hennon Ohio State University | >| Tropical Meteorology address@hidden | >| | >| Dept of Geography Office: 1155 Derby Hall | >| 1036 Derby Hall Phone : (614) 292-2704 | >| Columbus, OH 43210 Fax : (614) 292-6213 | >================================================ > >On Mon, 7 Feb 2000, Unidata Support wrote: > >> >> Chris, >> >> I rebuilt the distribution, but get the same results when trying to >> set the display to shear:0. Sending to my machine here works ok. >> >> I copied over my solaris executable of $GEMEXE/gf (moved the one built >> on your machine to $GEMEXE/gf.old. All appears to work fine using >> or copy. You will want to verify this on your own of course. >> >> At this point, this result would lead me to beleive there is something >> in the X server that has either been patched or updated along the way. >> I will need to look at the library calls used by gf and see if any >> patches have been issued along the way. >> >> I also noticed that your ~ldm/decoders directory still has old versions of >> the dc executables in there (from last August, so you will probably want to >> make sure you are running updated version of the decoders). >> >> Steve Chiswell >> **************************************************************************** >> Unidata User Support UCAR Unidata Program >> (303)497-8644 P.O. Box 3000 >> address@hidden Boulder, CO 80307 >> ---------------------------------------------------------------------------- >> Unidata WWW Service http://www.unidata.ucar.edu/ >> **************************************************************************** >> >