-
- Posts: 35
- Joined: Wed Nov 28, 2012 3:46 pm
Environmental ChemStation G1701DA Version D.00.00.38 19-Nov-2001.
I realize this is old software. This software version is compatible with our equally as ancient LIMS software, so until we get a new LIMS (which is in the works) I'm stuck using the version listed above.
The problem:
When I power down my computer, ChemStation breaks. I receive a "Could not open XXXX.res file. The XXXX being the res file generated when I try to calculate generate report. This leads to a whole host of other errors such as COMPNUM, Array Index, Could not open result #x (x=whatever number it gets hung up on), etc.
This issue then persists and will be suffered by anyone who who attempts to use the file on the network, then "corrupting" other .res files in other folders they or I try to access.
The prior fix:
Have someone else log onto my computer with their account, calculate generate report on a method that has been untouched by my computer, the issue goes away, all the .res files that previously had issues are now accessible and anyone can work on that data file with no issue. Sometimes. Sometimes the issue persists and we can't find a method/sample data file to "clear" the issue.
This is particularly infuriating because I can't access the files when they are broken, can't replicate the issue once it's fixed, and I'm not even sure I'm actually fixing it with the method I used above.
Can anyone reach back into their 2001 memories and tell me, "Oh yeah, you just do this." and all my problems will go away?
I realize this is old software. This software version is compatible with our equally as ancient LIMS software, so until we get a new LIMS (which is in the works) I'm stuck using the version listed above.
The problem:
When I power down my computer, ChemStation breaks. I receive a "Could not open XXXX.res file. The XXXX being the res file generated when I try to calculate generate report. This leads to a whole host of other errors such as COMPNUM, Array Index, Could not open result #x (x=whatever number it gets hung up on), etc.
This issue then persists and will be suffered by anyone who who attempts to use the file on the network, then "corrupting" other .res files in other folders they or I try to access.
The prior fix:
Have someone else log onto my computer with their account, calculate generate report on a method that has been untouched by my computer, the issue goes away, all the .res files that previously had issues are now accessible and anyone can work on that data file with no issue. Sometimes. Sometimes the issue persists and we can't find a method/sample data file to "clear" the issue.
This is particularly infuriating because I can't access the files when they are broken, can't replicate the issue once it's fixed, and I'm not even sure I'm actually fixing it with the method I used above.
Can anyone reach back into their 2001 memories and tell me, "Oh yeah, you just do this." and all my problems will go away?
