Tyler,
I have upgraded with the Service pack 1.41. This still did not appear to have
any advantages either.
 However I ran all day yesterday without any crunches (excel is up, and I was
measuring backgrounds regularly on instrument control as well), and my
observation is that as long as you don't try and do things quickly (i.e. with
the mouse, and definitely dont touch anything at all while the printer is
doing a job) the software will stay afloat.

Janet Hope
Isotope and Organic Geochemistry
Petroleum and Marine Division

Geoscience Australia
ABN: 80 091 799 039

Tel: (02) 6249 9487 / 9594
Fax: (02) 6249 9961
email:   [log in to unmask] <mailto:[log in to unmask]>
web site: http://www.ga.gov.au


-----Original Message-----
From: Stable Isotope Geochemistry [mailto:[log in to unmask]] On Behalf
Of Tyler B Coplen
Sent: Thursday, 7 October 2004 11:54 PM
To: [log in to unmask]
Subject: Re: [ISOGEOCHEM] Isodat running problems

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]
                      UK>                      cc:
                      Sent by: Stable          Subject:  Isodat running
problems
                      Isotope
                      Geochemistry
                      <[log in to unmask]
                      UVM.EDU>


                      10/07/2004 07:05
                      AM
                      Please respond to
                      Stable Isotope
                      Geochemistry






Hello

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?

John Hill

John Hill
Mass Spectrometry Facility
University College London
Chemistry Department
20 Gordon St.
London
WC1H 0AJ

Tel: 020 7679 4605