Incredibly frustrated: GUI.EXE has stopped working

[CW-HAL9000]

Make sure you are running the programs as an administrator.

[TravBWest]

Gentleman with Mr. Harris's help pointing me in the right direction,most of my issue has been resolved-while looking into my favorites i discovered somehow -idk the favorites menu has saved itself in quadriplicate. i was unaware of it until i clicked onto my favorites and noticed 4 copies of favorites-each pattern in each sub category copied 4 times! after going to documents Carvewright and locating them and deleting them i am normal and now can create patterns again!! Yay Thank You again Mr. Harris for heading me into the right direction. I need to tell you that in documents under Carvewright there should only be one favorites not multiples or numbered ones Ex.Favorites23798

[fwharris]

Gentleman with Mr. Harris's help pointing me in the right direction,most of my issue has been resolved-while looking into my favorites i discovered somehow -idk the favorites menu has saved itself in quadriplicate. i was unaware of it until i clicked onto my favorites and noticed 4 copies of favorites-each pattern in each sub category copied 4 times! after going to documents Carvewright and locating them and deleting them i am normal and now can create patterns again!! Yay Thank You again Mr. Harris for heading me into the right direction. I need to tell you that in documents under Carvewright there should only be one favorites not multiples or numbered ones Ex.Favorites23798

Good catch and yes getting duplicates will bog things down. Most times the duplicates are created when you have double clicked (tried to open) the .MPN file.

Glad you got your problem fixed!

[t-townwilson]

I am experiencing the same problem on a specific carve using both MAC and WINDOWS 8 software I am trying to carve the nameplates for my grandchildren as described in the tutorial for the 2D upgrade of Designer 2.xxxx. I successfully designed one on my MAC running Mavericks, but subsequent attempts using different names crashed every time when I get to the step of adding "path offset." The only way I can even reopen Designer is to do a "force quit" on "fontgen." I have tried the fixes listed in this forum of the app nap and also clicking on system preferences on MAC and selecting "CarveWright" in privacy/accessibility window. These solutions don't work in this issue.

So, I loaded Designer 2.xxx on my wife's WINDOWS 8 machine and tried the same design. Guess what? At the same point in the design I received a message that "GUI.EXE has stopped responding", and the program ultimately shut down. I am very frustrated! Anybody have a clue why this is happening? Strange that it happens on this particular step, and that I was successful one time.

Thank you in advance for any help you can give. I have had my machine for about two months, and it has not worked properly for most of that time. After three weeks of frustration talking to tech support and finally sending in parts for checking that proved fine, I sent the entire machine back a week ago. I'm looking forward to getting it back, and am trying to get some carves ready. Thanks for letting me vent. I have been really frustrated by the combination of these hardware and software problems!

[bergerud]

Could you post the project file?

[t-townwilson]

Well, after watching the tutorial video one more time, I realized the problem is not with Designer, but with ME! I was selecting more vectors for offset path than I should have, and he program was confused . Glad it wasn't the software, as I supposed!!

[Capt Bruce]

We're glad you were able to track that down t-townwilson. Once again that dastardly Operator Error has crept up and bit one of us. It is always lurking out there and bites all of us occasionally. Good to hear you survived the attack and will be warned in the future. Happy carving.

[bergerud]

Well, after watching the tutorial video one more time, I realized the problem is not with Designer, but with ME! I was selecting more vectors for offset path than I should have, and he program was confused . Glad it wasn't the software, as I supposed!!

Any time the program crashes, it is the program, not the operator. If you we doing something that should not be done, the program should tell you, not crash.

I call this a bug. Could you explain what you did to make the program crash?