| Author |
 Topic  |
|
|
melissa.slavin
BIAC Alum
Australia
44 Posts |
 Posted - May 29 2003 : 2:18:51 PM
|
I know this has been brought up before, but it seems like it is getting worse. Despite restarting Kulpe prior to starting our experiment every time, we still get a memory error occasionally when loading the paradigm, and have to restart again. Then once we start our experiment we have three runs and we are consistently having problems with the final run, despite which actual file it is (we counterbalance the order). Once the paradigm is loaded and we start the scanner, no stimuli come up and we have to crash out of the program. I'm not sure if it is the computer or the operating system. Has anyone had similar problems? Does anyone have a potential solution?
Thanks, Melissa |
|
|
diaz
BIAC Alum
USA
212 Posts |
Posted - May 29 2003 : 3:34:51 PM
|
I have a similar memory problem with Cigal on the 4T, where the displayed font on the screen will change after 4 or 5 (3 minute) runs. I quit and restart cigal, and that seems to fix the problem for a few more runs.
|
Michele T. Diaz, Ph.D.
Associate Director
Brain Imaging and Analysis Center |
 |
|
|
wang
BIAC Alum
USA
57 Posts |
Posted - May 29 2003 : 4:23:43 PM
|
I experienced similar memory problem when running Cigal using Win98 computer in 4T. Then I decided to use WinXp, I never have a problem with WinXP. The only inconvenience of WinXP is that there is no trigger. If somebody can help to make a trigger connected with WinXP, then WinXP is the best choice.
Lihong |
lihong |
|
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - May 30 2003 : 10:07:12 AM
|
I reconnected the trigger cable today to make CIGAL on the Windows NT system at the 4T triggerable from the scanner. (It is still Windows NT there, not Win XP yet).
I don't understand the memory problem you describe on Win98. It sounds like something may not be releasing memory as it should. If it is a CIGAL problem then restarting CIGAL after a few runs should prevent the hangup.
It may be something unusual about your specific paradigms. We may need to go through your paradigms together in detail in order to figure out what is happening. I've never seen the symptoms you're describing. Has anyone else seen similar problems? We can fix this if we can identify what's happening.
You will probably be better off running on the bigger PC.
Jim |
|
|
|
melissa.slavin
BIAC Alum
Australia
44 Posts |
Posted - Jun 17 2003 : 1:58:48 PM
|
| Jim, I went to migrate the paradigm files across to the NT computer on the right so that we can run the experiment from that one, however Ben informs me that it does not connect to the button box we have been using (we confirmed this with an I/O test). Obviously we cannot switch to the mouse now (which does work with that computer) as we have collected a fair amount of data using the buttons. The problem on the computer to the left still exists - yesterday I had to restart twice, which means delays during the scan. It is also very slow to open anything up, e.g. windows explorer. Is there any possibility of connecting the button box with the more reliable computer on the right, and/or fixing the problems with the computer on the left (not sure if converting to NT would help???). Thanks, Melissa |
|
|
| |
Topic |
|
Problems with computer at 4T
