Agilent RID G1362A - Win 16 Subsystem Insufficient Resources
Posted: Mon May 12, 2014 1:57 pm
				
				We have two Agilent G1362A RIDs running on A.10.02 Chemstation on Win XP. We are experiencing the same error message on two separate 1100s:  Win 16 Subsystem has insufficient resources to continue. It's making both of our RID systems almost useless to run. Is there a solution? I've reset the detectors, rebooted the PCs, and I've flashed the firmware on both detectors to a more recent revision, A.06.10. Power cycling the detector and PC doesn't help. We have other detectors on these LCs (VWD and DAD) that run just fine. Only the RIDs have this problem. Any ideas?
To describe these two 1100s a bit more, each system has two detectors:
1100#1: RID + VWD
1100 #2: RID + DAD
When we use either system, we only use 1 detector. In the Chemstation system access, we pull the detector we're not using offline, then reboot the software to only use the 1 detector required for the analysis. So all of our RID methods don't even show the VWD or DAD since we pull these detectors offline. The VWD and DAD methods on both LCs work fine. The "Win 16 Subsystem Insufficient Resources" message only occurs when the RID is connected and running. We have over 20 other 1100s here, all running A.10.02 Chemstation on Windows XP and I'm not seeing this problem on any of our other systems.
Thanks for any suggestions!
			To describe these two 1100s a bit more, each system has two detectors:
1100#1: RID + VWD
1100 #2: RID + DAD
When we use either system, we only use 1 detector. In the Chemstation system access, we pull the detector we're not using offline, then reboot the software to only use the 1 detector required for the analysis. So all of our RID methods don't even show the VWD or DAD since we pull these detectors offline. The VWD and DAD methods on both LCs work fine. The "Win 16 Subsystem Insufficient Resources" message only occurs when the RID is connected and running. We have over 20 other 1100s here, all running A.10.02 Chemstation on Windows XP and I'm not seeing this problem on any of our other systems.
Thanks for any suggestions!