VERICUT Users' Forum

paehv

Senior Member

From: Eindhoven, Netherlands

Registered: 2005-01-17

Posts: 167

Website

Saving a read-only controller

Before V7.0.3 
When saving a "read-only" controller, Vericut shows a file selection box because it can not overwrite this read-only file.

In V7.0.3 
When saving a "read only" controller, Vericut messages "Control file Saved "xxx"", indicating that the controller was saved, while it actually is NOT saved!!!!

---

Patrick Delisse
KMWE Aerospace -  https://www.kmwe.com
(Vericut V9.5, Siemens NX2206, Campost)

SergeV

Senior Member

From: Irvine, CA

Registered: 2004-10-08

Posts: 507

Website

Re: Saving a read-only controller

When you save an encrypted control, you are saving the current control and you are creating an encrypted version at the same time. You get a control with the .ctl extension and another one with the .xctl extension.

The current control referenced by the project remains the original control (un-encrypted). Therefore you can override it. The encrypted is not automatically loaded, this is by design.

If you open the .xctl encrypted control file in your session, you will not be able to override it. you will get the message: "Control modification not available because an encrypted control file is used in current setup"

SergeV

Senior Member

From: Irvine, CA

Registered: 2004-10-08

Posts: 507

Website

Re: Saving a read-only controller

OK, I completely misunderstood your initial posting, but I will leave my previous answer because it contains some good information.

you are talking about the file permissions that are read-only. I tested and was able to reproduce the problem. I will report the problem.

Thanks

Serge