RMA
Member
As mentioned in another Thread, the wonderful new PC I've been given to work with has a habit of crashing at regular intervals. Now that I've got back into the habit of saving regularly, it hasn't been causing me too many problems.
However, this time it caught me in a GRAPH7 program that I was checking out because I wanted to use it as basis, slightly modified for a new program (an Abort as opposed to a Controlled Shutdown).
After killing the GRAPH7 Editor with the Task Manager, I then tried to copy the FB and got a message saying that "a Text Library with this name already exists" - message 299:172 of Insert Function Block, and the copy aborted. (No change after rebooting, etc.)
I managed to work around the problem by creating a new GRAPH7 FB and then using cut & paste to copy the program over, but I'm not too happy about having this sort of problem lurking around. It has the feel of one of those things which can come back and bite you some time later.
Has anybody any idea of how I can clean things up? I've found a bunch of files in the "meldeom" sub-directory of the project called "TEXTABLE.*", "TEXTLNK.*" and "TEXTOM.*" with timestamps which look about right for the crash time - can I try just deleting them (after doing a backup of course!)? I tried doing a reorganise (because quite a f ew of the files have .DBF and .DBT extensions), but that hasn't helped.
I'm beginning to think I might be better off waiting till I get the new project laptop with 1280 x 1024 resolution, which they've promised me for next week, but still, all suggestions welcome!
However, this time it caught me in a GRAPH7 program that I was checking out because I wanted to use it as basis, slightly modified for a new program (an Abort as opposed to a Controlled Shutdown).
After killing the GRAPH7 Editor with the Task Manager, I then tried to copy the FB and got a message saying that "a Text Library with this name already exists" - message 299:172 of Insert Function Block, and the copy aborted. (No change after rebooting, etc.)
I managed to work around the problem by creating a new GRAPH7 FB and then using cut & paste to copy the program over, but I'm not too happy about having this sort of problem lurking around. It has the feel of one of those things which can come back and bite you some time later.
Has anybody any idea of how I can clean things up? I've found a bunch of files in the "meldeom" sub-directory of the project called "TEXTABLE.*", "TEXTLNK.*" and "TEXTOM.*" with timestamps which look about right for the crash time - can I try just deleting them (after doing a backup of course!)? I tried doing a reorganise (because quite a f ew of the files have .DBF and .DBT extensions), but that hasn't helped.
I'm beginning to think I might be better off waiting till I get the new project laptop with 1280 x 1024 resolution, which they've promised me for next week, but still, all suggestions welcome!