Hi everybody,
Anatomist 2.3.5 was installed on windows XP and used to work very well. It started crashing after the installation of end note 8. You can start anatomist but it's impossible to show any volume. It'll never work again. I uninstalled end note...nothing. I reinstalled windows ...nothing again. I did it again with no result. Then a defragmentation of the harddrive and show volume still crashes by closing it self.
the show log tells :
Process Anatomist Show Volume 1 started on 2006/02/17 10:47
in Anatomist Show Volume 1 Exception: argument source_volume is mandatory
neuroProcesses.py (1612) in _processExecution:
result = process.execution( self )
AnatomistShowVolume.py (50) in execution:
return Anatomist.AnatomistImageView( self.read )
Anatomist.py (2196) in __init__:
self.object = self.a.loadObject( image )
Anatomist.py (1823) in loadObject:
self.processTransformation( argfilename, objects = newObject )
Anatomist.py (1425) in processTransformation:
if _transformWith( self, item, 'spm_template', objects, windows ):
Anatomist.py (1418) in _transformWith:
if _transformWith2( self, item, t, 'to', with, objects, windows ):
Anatomist.py (1389) in _transformWith2:
defaultContext().runProcess( conv(), trans, t2 )
neuroProcesses.py (1504) in runProcess:
apply( self._setArguments, (_process,)+args, kwargs )
neuroProcesses.py (1487) in _setArguments:
_process.checkArguments()
neuroProcesses.py (548) in checkArguments:
o.checkValue( p, getattr( self, p, None ) )
neuroHierarchy.py (588) in checkValue:
Parameter.checkValue( self, name, value )
neuroData.py (103) in checkValue:
raise Exception( _t_('argument <em>%s</em> is mandatory') % name )
Process Anatomist Show Volume 1 finished on 2006/02/17 10:47 (26 seconds)
What to do ?
Please help!
You're my only hope! (Obi Wan Kenobi)
Anatomist crashes on Windows XP (part 2)
- Yann Cointepas
- Posts: 316
- Joined: Tue Jan 20, 2004 2:56 pm
- Location: Neurospin, Saint Aubin, France
- Contact:
Did you install it in a directory containing a space in its name ?
See the following post http://brainvisa.info/forum/viewtopic.p ... ight=space
See the following post http://brainvisa.info/forum/viewtopic.p ... ight=space
Hi and thank
For Isa :
I can launch Anatomist and load a volume. then i can't show the volume. I don't know if the images are gis or analyse, but their extensions are .ima.
I don't know how to save the log file. But if I knew, the point is that when show volume crashes, anatomist crashes too and all the windows of anatomist close themselves. I guess it's not possible to see the log file when the desk remain only, isn't it?
For Yann :
Their is no space because the shfj-packstable is at the root of D:\shfj_...
I must format the harddrive ?
For Isa :
I can launch Anatomist and load a volume. then i can't show the volume. I don't know if the images are gis or analyse, but their extensions are .ima.
I don't know how to save the log file. But if I knew, the point is that when show volume crashes, anatomist crashes too and all the windows of anatomist close themselves. I guess it's not possible to see the log file when the desk remain only, isn't it?
For Yann :
Their is no space because the shfj-packstable is at the root of D:\shfj_...
I must format the harddrive ?
- Yann Cointepas
- Posts: 316
- Joined: Tue Jan 20, 2004 2:56 pm
- Location: Neurospin, Saint Aubin, France
- Contact:
I suspect a problem on your computer with OpenGL (the 3D library used in anatomist). Try to directly launch anatomist (from the "bin" directory of the package) and open an empty window with one of the buttons on the left (Axial, Sagittal, Coronal or 3D). If it crashes it means that OpenGL initialization fails badly.
Are other software using 3D working ? Try to install the latest 3D drivers of your graphic card. If it still does not work ... well ... use the force.
GIS format uses *.dim and *.ima and Analyse *.hdr and *.img.
Since BrainVISA crashes, the log file must not be erased. However, the content of the log "points" to other temporary log files that are grouped upon normal termination. Therefore, sending only the main log file may not be enough. But if Anatomist alone crashes, the log file will not give a lot of useful information.
Are other software using 3D working ? Try to install the latest 3D drivers of your graphic card. If it still does not work ... well ... use the force.
GIS format uses *.dim and *.ima and Analyse *.hdr and *.img.
Since BrainVISA crashes, the log file must not be erased. However, the content of the log "points" to other temporary log files that are grouped upon normal termination. Therefore, sending only the main log file may not be enough. But if Anatomist alone crashes, the log file will not give a lot of useful information.
Hi
I did what you told as to launch anatomist from the "bin" directory then to open an empty window. It crashed. The cmd window shows that it's all right up to "all python modules loaded". Then : QGL context : :chooseContext() : wglCreateContext failed: Une routine d'initialisation d'une librairie dynamique (ddl) a ùchouù." four times and stop rotating.
Maybe the installation of the latest 3D driver of the graphic card might be more eficient than the force.
Thank you
ER
I did what you told as to launch anatomist from the "bin" directory then to open an empty window. It crashed. The cmd window shows that it's all right up to "all python modules loaded". Then : QGL context : :chooseContext() : wglCreateContext failed: Une routine d'initialisation d'une librairie dynamique (ddl) a ùchouù." four times and stop rotating.
Maybe the installation of the latest 3D driver of the graphic card might be more eficient than the force.
Thank you
ER
Hi !
I had the same problem on my laptop. I figured out (by chance) that it works when I kill the process Apoint.exe in the processes list of task manager (Apoint is a program that manages some features of the touchpad). I don't really understand why, but it works for me.. Moreover, if I configure my machine not to start Apoint.exe when booting, it doesn't work.. I have to kill it by hand. Strange...
If you have an explanation for that let me know !
Anne-Sophie
I had the same problem on my laptop. I figured out (by chance) that it works when I kill the process Apoint.exe in the processes list of task manager (Apoint is a program that manages some features of the touchpad). I don't really understand why, but it works for me.. Moreover, if I configure my machine not to start Apoint.exe when booting, it doesn't work.. I have to kill it by hand. Strange...
If you have an explanation for that let me know !
Anne-Sophie