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
Show All Mail Headers

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

Print Reply
Subject:
Re: Isodat running problems
From:
Antonio Celso Jardim <[log in to unmask]>
Reply To:
Stable Isotope Geochemistry <[log in to unmask]>
Date:
Thu, 7 Oct 2004 19:59:03 -0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
Hello

I would recommend an updated virus checkup.

Regards

Antonio Jardim

----- Original Message -----
From: "J T Hill" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, October 07, 2004 8:05 AM
Subject: [ISOGEOCHEM] Isodat running problems


> 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
>

ATOM RSS1 RSS2

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