Page 1 of 1
computer freezes while using Agilent Chemstation software
Posted: Thu May 07, 2009 7:49 pm
by PigmentQueen
I am running version B.03.02 of the Chemstation software for Agilent 1200 series HPLC and MS. We are using an HP Elitebook 8730w (laptop) to run the instrument. We have been having serious issues with the computer completely freezing up and having to "hard shut down" the computer. All of the powersave options are turned off. The sync to the MS website for the time has been turned off. In fact, the laptop is not connected to the internet or network at this time. We were thinking that maybe software updates needed to be performed.
Are there any other suggestions as to what would cause the computer to freeze?
Thanks!

Posted: Fri May 08, 2009 7:34 pm
by Gremlin76
I don't have any specific knowledge of chemstation but here are a couple of computer specific things to look at.
You may try to see if there are any processor specific settings for the laptop. I have an old HP laptop that has processor speed control for power savings that are separate from the normal powersave settings.
Any computer back-up software may cause hiccups. Windows XP has a built in back-up program and it may be worth while to shut it down for a bit.
It also may not be a bad idea to run a serious RAM memory checking program/application. Memory errors can be very troublesome but hard to track down.
Good Luck, It sounds like the problem is more with the computer (hardware or software) and those problems can be very difficult to track down.
sTeven
Posted: Sat May 09, 2009 4:06 pm
by GasMan
I am running GC ChemStation on the same model laptop without problems with XP professional. The latest versions of ChemStation need the Windows service pack 3 installed. I presume it is the same for the LC Chemstation, so check this out.
I have had problems with the latest version of EZChrom installed on the same laptop that made the GC ChemStation unusable.
Gasman
Posted: Wed May 20, 2009 6:12 pm
by Ron
You are streaming large amounts of data, I suspect that there may be an updated communications driver that could resolve this problem. Another possilbility is that the communicaitons settings on the laptop and the instrument do not match.