God, oh God, do I hate this!!!!!!!!!!!!!!!!

[ag1979]

I have had this problem before. I am currently usnig WorkerGonePostal
v3.7mr3. I just finished writing a program to verify a fixture. PC-Dmis crashed when about half way through saving the program. After PC-Dmis crashed and shutdown there was no autosave file to go back to and everytime I try to open the program I get this error:


................... Any help would be greatly appreciated. (I have already checked to see if it was my probe file.)

[Underspec]

Dumb question but, did you restart your PC after this crash and tried again?

[Wes Cisco]

CNTRL + S


Make it a firm habit.

Every couple of minutes.


Or every feature/dimension.

Do Not Rely on Autosave.

[jon_dav_uk]

I go one step further and use CTRL + S every 5 mins and then save every 30 mins or so with an incremental number on the end of my program, i.e. _001, _002 etc

[ag1979]

The problem arose when I tried to save. I finished writing the code, I pressed save, and half way through saving it crashed. Now because I didn't save the program as a different name, I beleive my save file is corrupt. I was hoping someone might have had this issue in the past. And yes I have tried restarting the computer(and controller).

[ag1979]

I am also neurotic about saving but when Crashy McCrashalot crashes during saving it does something really bad to the .prg file.

[Wes Cisco]

Jon, I do that too, but usually only twice a day. So if a program takes three days when I am done I might have ...MonAM, MonPM, TueAM, etc.

ag1979 you speak as if 3.7MR3 is crashing often on you. There may some kind of conflict or problem with your computer. I have been using that version since it came out over 6 months ago and if I see two crashes in a month that is a lot! Is your graphics card up to snuff? Do you have enough memory. Did you get the hot patch for sp2? Just some ideas. HTH

[jon_dav_uk]

Crashy McCrashalot....think he lives just up the road from me (only 90 miles from Scotland)

I was just about to ask the same question Wes, since switching to MR3 I get maybe one or two issues a month. My incrementing numbers started on V3.5 which crashed like once every minute or so but the habit has stayed with me.

On long programs I sometimes end up at 030 increments. Normally bin most of em once completed but keep a backup of working program somewhere safe as you never know when Crashy may turn up uninvited

[ag1979]

Thanks alot for the input. I will have to look at what might be causes the numerous errors that I run into. As for the computer: P4 2.4GHz HT, 1.0GB DDR 333, GeForce 6600 GT 128MB.

[Jan d.]

You are toast man. I never found recovery from this. It happened daily to me some time ago. After installing the hotfix for XP SP2 "only" once per month.

I wrote myself a little .BAT program that I run before closing down my computer EVERY day. It copies all .PRG files to the file server. So now I "ONLY" loose a maximum of 8 hours of work...

This is a disgraceful issue. Every time I get this one, I feel like going postal too. Hexagon should work around the clock to fix this one. Bugs are one thing, but this one can wipe out weeks of work, no matter how religiously you press ctrl_s. These types of failures are unexcusable!

The problem is of course how to reproduce it and bring it to Hexagon's attention. I can never reproduce it. It just happens out of the blue. I do something, press save and all he!! brakes loose. I usually shut my computer down and go home. Get a cold one.


Jan.

[Wes Cisco]

Your hardware specs look ok, but it could be a windoze problem. Are you using XP with SP(service pack)2? Do a search here, or just go to the microsoft site and look for a patch. I know some people had problems with that. If all else fails try 1-800-343-7933 and give them all of you details, they may know of an issue or setting that is the culprit. HTH

[ag1979]

I always make sure that Windows is up to date. But I may try the 800 number. I am also going to write a little program in vb for incrementing my saving. I didn't really want to do this just because of the shear volume of data that will be generated, but I would rather have excess amount of data than lose everything I have. Thanks.

[Johnson]

Calling tech support they may just ask you if you have a corrupted probe or CAD file.

I do not think I ever was able to get a program back from that type of an error.

You could try saving it if you have a cad file with it just open it without the CAD. Take a look at your probe files quick and make sure they are all over 1kb.. Just some hopeless thoughts for ya to try...

Good luck

[Underspec]

You are toast man. I never found recovery from this. It happened daily to me some time ago. After installing the hotfix for XP SP2 "only" once per month.

I wrote myself a little .BAT program that I run before closing down my computer EVERY day. It copies all .PRG files to the file server. So now I "ONLY" loose a maximum of 8 hours of work...

This is a disgraceful issue. Every time I get this one, I feel like going postal too. Hexagon should work around the clock to fix this one. Bugs are one thing, but this one can wipe out weeks of work, no matter how religiously you press ctrl_s. These types of failures are unexcusable!

The problem is of course how to reproduce it and bring it to Hexagon's attention. I can never reproduce it. It just happens out of the blue. I do something, press save and all he!! brakes loose. I usually shut my computer down and go home. Get a cold one.


Jan.

This is one of Hexagon's marketing strategies to sell SMAs !!! Thought you knew

[ag1979]

The first thing I tried was the cad file, the second was the probe file. Well atleast I only lost 6.5Hrs of work.