>From: Zuo Dong Zheng <address@hidden> >Organization: CCNY >Keywords: 199907271334.HAA25174 McIDAS-X Fkey UNIMENU.DEF Zuodong, >>o making sure that the user running the session has a copy of UNIMENU.DEF >> in his/her mcidas/data directory (workdata for the user 'mcidas') >>o restoring the defaults from the McIDAS command line: >> >> TENTER "UNIMENU.DEF >i did that, but it still not working... If you recall, I also noted that the NCEP GRID menus would not work because there is no longer the GRID files in the Unidata-Wisconsin datastream.: >>After you have this setup, you will run into another problem: the GRID >>files that were in the Unidata-Wisconsin datastream were removed on >>July 1. Since the Fkey menu GRID actions were specifically geared to those >>files, they will fail. I have put a module into the McIDAS-X 7.60 >>distribution (not released yet) that can create those data files from >>GRID files decoded by XCD decoders. Once you have 7.60, you will be able >>to add a cron entry that will kickoff this routine and create the GRID >>files needed by the Fkey menu. Additionally, for the past several days, >>I have been ADDEizing the Fkey menu for 7.60. I will assume that you realize that you will not be able to do the NCEP functions, and that you are still having problems with running other things that use ?BGKMAP. If this is the case, then I suspect that you did not exit your invocation of the Fkey menu and restart it after running: TENTER "UNIMENU.DEF If this is true, then the failure is understandable as the menu must resolve the strings on startup. If this is not true, I need more information about how your account is setup to run McIDAS-X. Tom
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.