Please download the latest ISODAT 2.0 Service Pack (1.41) and advise the
list if the problem persists. Thank you.
J T Hill
<[log in to unmask] To: [log in to unmask]
Sent by: Stable Subject: Isodat running problems
<[log in to unmask]
Please respond to
We are running Finnigan's IsoDat 2.0 system with Service Pack 1.39 to
control a Kiel Device and MAT253, on a Windows XP platform with 256Mb
RAM. We are getting persistent software failures, of two kinds. The first
is spontaneous termination of an Aquisition sequence, with the log-file
message that the system has tried to start a script that is already
running. This is Fatal and the sequence terminates.
The second type of failure is that the Aquisition application simply seizes
up. No error message appears on the log-file and the current scripts
appear as "running" in the ISLScript window. In fact nothing is
happening. A variant of this is that when we start Aquisition from the
main Isodat menu, it starts but after a few seconds we get a Microsoft
error window saying that it should be shut down. Shutting it down leaves
Isodat in an unstable state and Aquisition cannot be started again unless
the whole system is shut down and the computer rebooted. Running Task
Manager at this stage indicates variable memory use, but never complete
usage of all the memory.
Is anyone else experiencing problems like these? Any suggestions as to
actions we could take to improve the situation?
Mass Spectrometry Facility
University College London
20 Gordon St.
Tel: 020 7679 4605