How old is the PC? On some of the 5 yr old systems, we ended up moving
the communications board from a slot on the daughter board to one on the
main part of the Dell motherboard. I think Gilles mentioned here
problems with PC power supplies getting weak over time and causing
problems (same issues, slightly different remedies). We also had a
flaky motherboard once too.
Didn't have your exact problems--but general and intermittent weirdness...
You may also have a corrupted registry--which re-installing rewrites for
On 6/21/2011 11:46 AM, Greg M Michalski wrote:
> also at one point a error of "no GiDsp.bin file found" but that file exists in ISDAT directory so I dont know...
> ----- Original Message -----
> From: "Greg M Michalski"<[log in to unmask]>
> To: [log in to unmask]
> Sent: Tuesday, June 21, 2011 12:43:22 PM
> Subject: [ISOGEOCHEM] Fwd: ISODAT crash
> Our ISODAT has crash, giving an error of "The System> couldn`t
> find any scanable hardware part. Check the entries of X/Y-Hardware in the
> scanmaker section". This happened earlier year and there was alot of discussion, but seems like no absolute resolution. There is communication between the valves, source, magnet etc, but the cups are maxed and in says ÏNVALID. Connections are fine, rebooted many times, tried Giles suggestion of reactivating "Re-register OCX". has anyone figured out this bug or is yet another reinstall the only option?
> ----- Forwarded Message -----
> From: [log in to unmask]
> To: "Stable Isotope Geochemistry"<[log in to unmask]>
> Sent: Monday, December 20, 2010 6:37:13 PM
> Subject: ISODAT crash
>> Our ISODAT has done its annual crash, giving an error of "The System
>> find any scanable hardware part. Check the entries of X/Y-Hardware in the
>> scanmaker section". This happened the same time last year, and I noticed
>> posts that it has also coincidentally happened during the same time to
>> Thermos Christmas present? The computer is communicating with the IRMS
>> I can turn on the source, open peripheral valves, do peak centers, but its
>> to acquisition and instrument control functions. The default seems to be
>> reinstall, but I tend to lose custom interfaces when we do that...has anyone
>> determined the root cause?