Hi Paul, re: I _really_ don't have any theory how the REDIRECTion backing store file got damaged > This is explainable by my trying to add a string where I did not do /" > ahead of the string...it was only allowing me 12 characters... No worries. This would not damage the string table file STRTABLE. re: > but that was because I tried to create a string from the wrong directory. I > am still amazed that there are two string tables.... so now things look to > be remedied. One should only modify/add strings to the string table from one's $MCDATA directory. Running TE (te.k) from a different directory will result in another copy of STRTABLE being created. Only one will be used, however. re: MCGUI not working > This seems to be the last remaining problems. I just solved this one... it was a typo in the distribution's mcidas_env.sh file (installed in ~mcidas/admin/mcidas_env.sh). The code was setting the environment variable MBIN instead of MCBIN. MCBIN is used in the MCGUI applications as the location of Tcl/Tk files that need to be used by the GUI. Since MCGUI was not being set, its effective "value" was 'MCBIN=' (blank). When the MCGUI startup tried to use the value of MCBIN, it got nothing, so it did not source the needed Tcl script files. After correcting the typo in ~mcidas/admin/mcidas_env.sh and then logging off and logging back on as 'mcidas', I was able to bring up the MCGUI configuration GUI: <as 'mcidas'> cd $MCDATA mcidas -config Since this works, the full MCGUI should work also. I will be updating the McIDAS-X distribution to include the fix for my typo. Sorry for the incredible hassles!! Thanks for coming to our > rescue. I would like to help you shovel. Yech! > > Paul > > > > > > > > > > > > > > > > > > > > > > ============================ > > > Dave Bukowski -- NREMT-B > > > BLS Instructor (CPR & AED) > > > N9KPD > > > http://davebb.deviantart.com/ > > > address@hidden > > > address@hidden > > > > > > > > > address@hidden> wrote: > > > > > > > Hi Paul, > > > > > > > > re: > > > > > 1) OK...I think we fixed a few things too...The radar was not working > > > > > because it searched for the wrong directory. I found that our copy of > > > > > NEXRADDE.BAT was pointing to the wrong directory. I copied that to > > > > > NEXRADDE.BAT.OLD and took the old copy from the old server over. Now > > the > > > > > data files are where they are supposed to be. > > > > > > > > The DSSERVE invocations in files like NEXRADDE.BAT do not become active > > > > until 'mcidas' makes them active through actions like: > > > > > > > > <as 'mcidas'> > > > > cd $MCDATA > > > > batch.k NEXRADDE.BAT > > > > > > > > Also, if you copied over a file from the old machine, did you put it > > > > in the MCDATA directory for the user 'mcidas'? This is where > > > > files that get locally modified should live, not in ~mcidas/data. > > > > > > > > re: > > > > > Does this batch file get > > > > > replaced with new versions? Should my modifications be named > > something > > > > else? > > > > > > > > Not in the $MCDATA directory of 'mcidas'. It does get replace by new > > > > installations/updates if it is in ~mcidas/data. > > > > > > > > re: > > > > > 2) What does XCD.BAT do? I have this > > > > > address@hidden:~/data$ less XCD.BAT > > > > > REDIRECT ADD *.PRO "#MCDATA > > > > > REDIRECT ADD *.PTR "#MCDATA > > > > > > > > > > REM > > > > > REM Define needed REDIRECTions > > > > > REM > > > > > > > > > > REDIRECT ADD HRS.SPL "#XCDDATA > > > > > REDIRECT ADD *.IDX "#XCDDATA > > > > > REDIRECT ADD *.IDT "#XCDDATA > > > > > REDIRECT ADD *.XCD "#XCDDATA > > > > > ... > > > > > > > > XCD.BAT sets up McIDAS-XCD processing. > > > > > > > > re: > > > > > when I ran the command by hand, there were no strings defined. On > > the old > > > > > servers, it was XCDDATA =: /home/mcidas/data > > > > > I tried to enter the strings by hand using te.k but it would not let > > me > > > > use > > > > > more than 12 characters. > > > > > > > > The invocation from the Linux command line would be: > > > > > > > > <as 'mcidas'> > > > > cd $MCDATA > > > > te.k XCDDATA \"/home/data/mcidas > > > > > > > > re: > > > > > I was not sure what to do. > > > > > > > > I thought that decoding was working correctly on the new climate. > > > > Are you saying that it wasn't? > > > > > > > > re: > > > > > 3) When I run "mcidasx" I get two windows but do not get the menu. I > > get > > > > > > > > > > Error in startup script: couldn't read file > > "./tcl/lib/tk8.5/xmfbox.tcl": > > > > > no such file found.. > > > > > > > > > > That is weird. > > > > > > > > The error message is, indeed, weird. The Tcl/Tk widgets, etc. should > > > > get installed in ~mcidas/tcl/... > > > > > > > > re: > > > > > This is what I have so far. > > > > > > > > OK. > > > > > > > > Dave wrote: > > > > > > > > > Paul, as I mentioned on the phone I just installed tcl8.5 and tk8.5. > > Now > > > > > if there is a MCIDAS binary that needs to be recompiled then I need > > to > > > > know > > > > > what we are recompiling so I can add it to weather > > > > > > > > Tcl/Tk is included as part of the McIDAS distribution. The versions > > > > of tclsh and mcwish (a McIDAS-modified version of 'wish') get created > > > > as part of the McIDAS build process. Installations of Tcl/Tk in the > > > > OS are not needed as they should not be used by the McIDAS GUI/MCGUI > > > > if the user's environment is setup correctly, and if the McIDAS build > > > > succeeded with no errors. > > > > > > > > Comment: > > > > > > > > With three people making modifications, it is hard to know what works > > > > and what doesn't because of the rapidly moving target that is > > > > trying to be addressed. > > > > > > > > Cheers, > > > > > > > > Tom > > > > -- > > > > > > > > > > **************************************************************************** > > > > Unidata User Support UCAR Unidata > > > > Program > > > > (303) 497-8642 P.O. > > Box > > > > 3000 > > > > address@hidden Boulder, CO > > > > 80307 > > > > > > > > > > ---------------------------------------------------------------------------- > > > > Unidata HomePage http://www.unidata.ucar.edu > > > > > > > > > > **************************************************************************** > > > > > > > > > > > > Ticket Details > > > > =================== > > > > Ticket ID: OJB-462098 > > > > Department: Support ldm-mcidas > > > > Priority: Normal > > > > Status: Open > > > > > > > > > > > > > > > > > > Cheers, > > > > Tom > > -- > > > > **************************************************************************** > > Unidata User Support UCAR Unidata > > Program > > (303) 497-8642 P.O. Box > > 3000 > > address@hidden Boulder, CO > > 80307 > > > > ---------------------------------------------------------------------------- > > Unidata HomePage http://www.unidata.ucar.edu > > > > **************************************************************************** > > > > > > Ticket Details > > =================== > > Ticket ID: OJB-462098 > > Department: Support ldm-mcidas > > Priority: Normal > > Status: Closed > > > > > > > -- > Paul L. Sirvatka > Professor of Meteorology > College of DuPage - NEXLAB > http://weather.cod.edu > > Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: OJB-462098 Department: Support ldm-mcidas Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.