| T O P I C R E V I E W |
| brent.warner |
Posted - Oct 27 2004 : 5:34:44 PM
I just finished running a subject a little bit ago, and had some really odd things happen. When I got there and logged into the XP computer it was running painfully slow. It would take ~30 seconds to open programs like matlab or explorer, and my paradigm was also heavily affected. After some fiddling I rebooted the computer and this seemed to help. We got through 4 runs with no problems -- everything at proper speed -- but halfway through 5 it slowed down again. I hadn't opened or closed any programs between these runs, so have no explanation for why it happened then. I rebooted again and got through half of run 6 before it slowed down again.
At the end of this run, the scanner popped up an error saying something about being unable to maintain proper scanner room temperature. Susan went in and said it felt too warm. I don't know if this could possibly have any effect upon the computer's performance, but figured it was worth mentioning.
Anyone else having any/some of these issues? |
| 2 L A T E S T R E P L I E S (Newest First) |
| francis.favorini |
Posted - Nov 05 2004 : 4:14:22 PM
I was unabled to detect any problem. The system seems to be operating normally at the moment. Heat could be a factor, but my guess is the network was being affected by the installation of new network connections prior to moving all the networking gear this weekend. Please report any further problems.
-Francis
|
| jim.voyvodic |
Posted - Oct 27 2004 : 10:10:44 PM
I noticed the slowness problem on the XP computer today, too.
Logging in was slow and even just scrolling through directories with
Windows Explorer was very slow. I rebooted in each session, which seemed to improve matters, but I didn't run very long so perhaps just was just lucky the problem didn't reappear.
The overheating in the scanner was a tripped circuit breaker that turned off the gradient coil cooling system. It's very unlikely that had anything to do with the Windows XP problem. Seems more likely
to me that it's either a network problem or a hardware problem of some sort. Either way the computer is very busy trying to do something that should take no time at all. I'll ask Francis tomorrow if he can luck into this. This needs someone with Windows diagnostic expertise.
Jim |
|
|
