I have this same issue with X6 as well, and after some testing I've determined it to be an issue with some Microsoft applications in Windows 7. Never used to happen with Windows XP 64 bit. It doesn't seem to occur when running all applications, mostly just Microsoft apps, for instance Adobe Reader or Google Chrome browser do not cause it. Another more annoying issue to me, switching from XP 64 to Win7 64, is that now when I double click on any field data in an operation to entirely highlight it and retype its value, it does NOT highlight / select the (-) negative sign symbol in the value and I end up with a negative value after typing the change, that which was intended to be a positive value or a double negative symbol in the field if I type a negative value. Only by clicking and dragging to the left or highlight + [backspace] key pressed twice can I get a negative value changed to a positive. Kinda breaks the workflow rhythm I had going while working in XP 64 and forces me to work slower to avoid having a potentially dangerous and costly typo mistake.

Hi Aaron, Thanks for the suggestion. I did try deleting the whole my mcamx7 folder but got the same results. I went ahead and did a full uninstall / registry sweep then reinstalled and got X6MU3 configured and working the way it was before the first install of X7. I then reinstalled X7 without any migration or other configuration file transfers, opened my most recent X6 file and it seemed to work fine although it did throw a corrupted tool alarm when opening the fle and ask me if I wanted to remove it, [yes] or [no]. It did that on my first attempt with X7, after which I clicked "yes" and Code Expert launched, did something then displayed a log file. After that instance is when I started getting the warning error when launching X6.This time I clicked "no" and launched X7 verify, which appeared to work correctly dispite the alarm and after which the same file verified and worked correctly in X6MU3 as well. As it stands now that everything is working again, I'll hold off on the auto migration and try to get time with Trevor (our reseller support) to recreate the issue and find an effective migration method as some of our customized libraries and machine definitions may be still referencing things as far back as X5. Thanks again for the support.

Hi ajmer, Thank you for the reply. After I ran the Migration Utility, I did Open \ Load my X6 config file in X7 and save it to the shared mcamx7 folder, as well as the my X6 Toolbar States and Key Mapping files. I did as you suggested and deleted the config files from the shared mcamx7 and my mcamX7 to let MasterCAM create a new default config file as it launched, (See: Cap1 image). I then proceeded to creat a quick rectangle chain and contour operation using Mill Default machine definition ( unaltered default ) and attempted to verify it and I got the same message. (See: Cap2 image). A new developement to this is that I am now getting a new error message when I launch X6 MU3: "Warning, Error opening INSERT.TBL" (See: Cap3 image) Any remedy short of a complete reinstall, manual migration and manual reconfiguration would be greatly appreciated.

Hi, I'm new to this forum but not to MasterCAM, this being my first post. Most of the issues I have had, I've been able to resolve by searching the forum or working with our reseller. I currently have an issue with X7 that I am not able to find an answer to by searching I just installed X7 from the .exe link on the downloads page. I ran the migration utility and got all my configuration settings imported and updated. I opened up a recent X6 file and saved it as an X7 then I tried to launch the Operation Verify and I recieve a pop up message dialog: "Error C-hook not found" with the contents of the dialog being a path "C:\PROGRAM FILES\MCAMX6\CHOOKS\MACHSIM.dll". Now this is confusing to me as I dont know why X7 would be looking in an X6 folder for a C-Hook, or why it would pop up the error at all when that praticular c-hook file DOES exists and reside in both the C:\PROGRAM FILES\MCAMX6\CHOOKS and C:\PROGRAM FILES\MCAMX7\CHOOKS folders. Can anyone please tell me what might be the cause of this?