[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050823: mcidasx problem



>From: "John Hobbie" <address@hidden>
>Organization: NMSU/NSBF
>Keywords: 200508232209.j7NM9mjo016851 McIDAS-X startup

Hi John,

Sorry to take so long getting back to you...

Did you ever get McIDAS started using my recommended invocation:

mcidas -config

(not mcidasx)

If not, I would recommend that you do the following:

1) since you now have multiple .mcidasrc* files in your HOME directory,
   I recommend deleting them

2) after 1), start McIDAS using:

mcidas -config

   and make sure that the radiobutton at the bottom of the startup GUI
   says to save values in the defaults file

3) make sure that you configure your session with at least 16 frames

4) you will probably want to make the frames you use larger, but this
   is optional.

Please let me know if you continue to have problems.

Cheers,

Tom

John Hobbie previous wrote:
>I have just done a clean install of mcidas2005 (make all), had set the
>environmental variables and started up mcidasx.  The GUI came up and I
>clicked on the Micellaneous tab and unchecked the Start GUI upon McIDAS
>startup box;  I saved the settings then clicked  Start McIDAS and got
>the following message:
>
>address@hidden src]$ mcidasx
>WARNING: only run as the user 'mcidas' for supervisory tasks
>Running McIDAS configuration GUI...
>address@hidden src]$ Error in startup script: invalid command name "fileToList
> "
>   while executing
>"fileToList $mcrcfile"
>   (procedure "readMcidasrc" line 139)
>   invoked from within
>"readMcidasrc "$home/.mcidasrc""
>   (file "/home/mcidas/mcidas2005/src/mcidas" line 667)
>
>There was no .mcidasrc  when I ran mcidasx; there are several  .mcidasrc*
>files now.   all are permissioned at 664
>
>What step did I leave out this time?   (I deleted all the newly installed
>stuff and did the procedure again, with the same results.)  
>
>Thanks in advance,
>
>Hobbie
>National Scientific Balloon Facility
>
--
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.


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.