Skip Navigational Links
LISTSERV email list manager
LISTSERV - LIST.UVM.EDU
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - ISOGEOCHEM Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

ISOGEOCHEM Archives

Stable Isotope Geochemistry

ISOGEOCHEM@LIST.UVM.EDU

Menu
LISTSERV Archives LISTSERV Archives
ISOGEOCHEM Home ISOGEOCHEM Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Stable Isotope Geochemistry <[log in to unmask]>
Date:
Fri, 23 Mar 2007 11:55:22 -0700
Reply-To:
Stable Isotope Geochemistry <[log in to unmask]>
Subject:
Re: Finnigan MAT252 Error Message?
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
<[log in to unmask]>
Content-Type:
text/plain; charset="us-ascii"
From:
Anthony Michaud <[log in to unmask]>
Parts/Attachments:
text/plain (108 lines)
I will throw in that another problem we had experienced in the past with
our delta plus, and just recently with our MAT 253, was an inability to
do a peak jump during a dual acquisition. It was from N to C on the
deltaplus advantage and then from H to O on the MAT 253. What made it
worse was that we were unable to create a new jump calibration as isodat
would crash every time we tried it (we did delete the old calibration
first).

After having this problem quite a few times in the past I would "solve"
it by copying isodat files from a working backup folder into the active
isodat folders. Eventually I was able to hone in on one single file that
was corrupted:

Isodat NT\Global\Databases\isodat gasconfiguration.iso

By simply shutting down isodat and then replacing this file with a
backup copy of it (from when the jump cal did work) we can get back to
our original setup.

Sounds like your system's symptoms were not quite the same (we could
never do a successful peak jump once this problem showed up), but this
might still be helpful.

Anthony


----------------------------------------
Anthony Michaud
KFLEB-1404
School of Earth and Space Exploration
Arizona State University
Tempe, AZ 85287-1404

Tel: 480-727-8033
Fax: 480-965-8102
Web: http://kfleb.asu.edu

***Windsurf Everywhere***
----------------------------------------


-----Original Message-----
From: Stable Isotope Geochemistry [mailto:[log in to unmask]] On
Behalf Of Harlow, Benjamin
Sent: Friday, March 23, 2007 10:37 AM
To: [log in to unmask]
Subject: Re: [ISOGEOCHEM] Finnigan MAT252 Error Message?

Dana,

I have had this happen before and it seems like it could be related to
many processes running and taxing the computer's RAM.

Some things that might help are to periodically fully shut down isodat
with the toolbar icon.  I've found that after I build a sequence and do
a jump cal isodat may start running sluggish.  Closing all programs and
restarting isodat seems to help.  If you do ctrl + alt + delete you may
see other programs are using up memory as well.

You could also try checking for software updates and if necessary,
reload isodat.  If you do reload isodat, make a version handler backup
first so you can reload your configuration.

Hope this helps,

Ben Harlow
Washington State University



-----Original Message-----
From: Stable Isotope Geochemistry [mailto:[log in to unmask]] On
Behalf Of Dana Miller
Sent: Friday, March 23, 2007 6:09 AM
To: [log in to unmask]
Subject: [ISOGEOCHEM] Finnigan MAT252 Error Message?

Hi Everyone,
We are running carbon and nitrogen dual-analysis using a Costech 4010 
EA/Conflo-III/MAT252 and ISODAT NT 2.0. After peak-jumping from N2 to
CO2, 
occasionally an error message shows up:

------------------------------------------

Microsoft visual C++ Run time Library

Run time Error!

Program:C:\Finnigan\Isodat NT\Global\bin\Workspace.exe

Abnormal program termination

-----------------------------------------------------

The peak-jump appears to be incomplete, and carbon isotope measurement
of a 
dual-analysis fails. The next run is ok. This occurs once every two or
three 
sessions.

Has anyone else experienced this issue? The Finnigan engineers have not
heard 
of this problem, nor do they know how to remedy it. Any suggestions are 
greatly appreciated. 
thanks,
dana

ATOM RSS1 RSS2

LIST.UVM.EDU CataList Email List Search Powered by LISTSERV