Hi Atlanta-

Yep, this one bit me (on Mac OS X), too. To fix it, I had to go to
/usr/local/ccp4-6.1.2/share/ccp4i/etc/UNIX and edit my configure.def file.
Almost at the end of the file, there is a line that says
"USE_DBCCP4I_ON_STARTUP". Change the value from 1 to 0. This should
"refresh" your project directories in the ccp4 GUI.

HTH-
Brad

On Tue, Aug 25, 2009 at 9:49 AM, Atlanta Cook <[email protected]> wrote:

> Hi,
>
> I am running  CCP4 version ccp4-6.1.1 on Mac OS X.  I was working without
> any problems until the gui crashed and when I tried to start it up again it
> lost my PROJECT directory information. I restarted the computer and now I
> can't even get the gui up, if flashes up for a second and then I get the
> following message:
>
> Top level CCP4 directory is /sw/share/xtal/ccp4-6.1.1
> Using CCP4 programs from /sw/share/xtal/ccp4-6.1.1/bin
> Error in startup script: wrong # args: should be "dbccp4i_open_project
> project args"
>    while executing
> "dbccp4i_open_project"
>    ("eval" body line 1)
>    invoked from within
> "eval dbccp4i_open_project $project $args"
>    (procedure "DbLoadFile" line 12)
>    invoked from within
> "DbLoadFile $project"
>    (procedure "DbOpenDatabase" line 13)
>    invoked from within
> "DbOpenDatabase $project"
>    (procedure "DbOpen" line 30)
>    invoked from within
> "DbOpen -init"
>    (procedure "DbInitialise" line 19)
>    invoked from within
> "DbInitialise"
>    (procedure "taskbrowser" line 38)
>    invoked from within
> "$system(RUN_MODE)"
>    ("default" arm line 9)
>    invoked from within
> "switch  $system(RUN_MODE) \
>  script {
> # Run a script ($CCP4I/scripts/project.script) with parameters from def
> file
>
>    source [file join $env(CCP4I_..."
>    (file "/sw/share/xtal/ccp4-6.1.1/ccp4i/bin/ccp4i.tcl" line 163)
>    invoked from within
> "source [file join $env(CCP4I_TOP) bin ccp4i.tcl]"
>    (file "/sw/share/xtal/ccp4-6.1.1/ccp4i/bin/ccp4i" line 5)
>
> I can access ccp4 programs by a script so its just the gui that doesn't
> work
>
> Atlanta
>

Reply via email to