We have been made aware of this issue and we are working on looking into it. We do believe this is occurring after running the migration utility. The problem is this is NOT happening to everyone who runs the utility. We are trouble shooting what might be causing this. For those that have received this, please provide details about your install process - did you have a beta or test drive version installed or is this a fresh install? What products do you have installed in your X6? Where are your files located? The more information about your X6 & X7 installs the better.

Please report any error messages as well as explain how you installed - the entire process. Also if you had X7 installed prior through beta or test drive, If you do NOT clean up properly it is possible to have files or registry settings left around that may cause weird issue like this. Refer to this thread for instructions on uninstalling and installing X7. http://www.emastercam.com/board/index.php?showtopic=72523 In those instructions we have you rename folders instead of deleting in case there are some files you don't want to lose. If you had previous X7 installed, rename the folder. If not and this is a fresh install, delete the folders instead. You have to do ALL the steps to ensure nothing is being left around that may conflict with the released files and install. If you are getting the standard windows crash dialogs, please include your contact information before sending the report. Then send an email up to [email protected] and let us know you submitted it and when it comes up we can have someone look at it.

One thing to look at is are your current systems Win7 32 or Win7 64? Mastercam X7 will only run on windows8 x64 and not on the 32bit platform. In the near future I would expect us to drop support for Windows7 32 as well. I don't have a specific time frame, but that is what I see happening with other companies and we have discussed it as well.

An updated version of the Mastercam X7 Technology Preview is now available for users to test drive. Please read the information and steps below before downloading. Read Before Installing Mastercam X7 Technology Preview By downloading and using this Beta software, you are agreeing to our Beta terms of use and accepting all risks associated with it. With the release of X7, we are dropping support of the Windows XP and Vista operating systems. With X7, we will only install on and support Windows 7 and Windows 8 operating systems. Windows 7 support will be for both 32-bit and 64-bit. Windows 8 support will be 64-bit only. The Technology Preview will not run without active maintenance. The Technology Preview will expire on 04/30/13, meaning it will need to be completely uninstalled before installing the release version of X7. The folder structure will also need to be deleted. Mastercam X7 does not allow you to save files to a previous version of Mastercam format. Please see the ReadMe.pdf for more information. It is only possible to run the Mastercam products currently active on your SIM. We encourage users to use the Industrial Forum on eMastercam.com to discuss this X7 preview. CNC Software staff will be actively interacting on eMastercam.com during the X7 preview, providing answers and updates that everyone can see. We do expect delays in responding to the feedback so please be patient. As this is beta software, part files created with it may not be compatible with the final version of X7. To uninstall a previous Mastercam X7: Open Windows Control Panel, Programs and Features. Right click on Mastercam X7 and select Uninstall. Delete the following folder: C:\Program Files\Mcamx7 or C:\Program Files (x86)\Mcamx7 Rename the following folders: C:\Users\your logon\Documents\my mcamx7 to my mcamx7 backup C:\Users\Public\Documents\shared mcamx7 to shared mcamx7 backup Delete the following registry entries: HKEY_CURRENT_USER\Software\CNC Software, Inc.\ Mastercam X7 HKEY_LOCAL_MACHINE\SOFTWARE\CNC Software, Inc.\ Mastercam X7 Note: By renaming the folders above, you will ensure that the necessary files for this technology preview get installed and you can still move over any files you may have edited or customized for use during your testing. To install X7: Click on this link and log in http://mastercam.com/Support/Downloads/MastercamX7/Default.aspx. Download the appropriate file for your operating system. After the file has downloaded, double-click the .exe to begin the installation. (It does take a minute or two for the install to launch so please be patient.) Follow the instructions during the installation. Run Mastercam X7 Beta 5 and please select the option to allow the Customer Feedback Program to collect data from your system. Download the MastercamSimulatorDefaults.zip file and extract the MastercamSimulatorDefaults.xml file to the root of \my mcamx7 overwriting the existing file – this file addresses an issue with incorrect stock display in the Mastercam Simulator. For information on editing your Registry. Backup your registry: http://windows.microsoft.com/en-us/windows7/back-up-the-registry How to backup a registry: http://pcsupport.about.com/od/windows7/ht/backup-registry-windows-7.htm How to create a restore Point: http://windows.microsoft.com/en-us/windows7/create-a-restore-point How to delete Registry Keys: http://pcsupport.about.com/od/windows7/ht/delete-registry-keys-windows-7.htm

Thanks Jason. We got the part and development is looking into it. For some reason it is in a loop using the slot number and it just goes round and round and round. I'll let you know what we find. Thanks again for sending the file, it really helps. Jim

Can you send the part to us? If so please send it to [email protected]. We might be able to do something with it. How long did you wait for the file to open? Was there every any message or dialogs that popped up? Check in the event log as well and see if there is anything in there that might be of use.

Sounds like you might have gotten the Safenet 6.55 driver update that was bad. It could have occurred as part of a windows update - it was an optional update or if you plugged your hasp into another port and it found new hardware and hit the web for the latest driver. I swore SafeNet pulled that driver update down just after a few days so it should not be available anymore.. You can go into your device manager and scroll down to the Universal Serial Bus Controllers section and expand it. Then right click on the SafeNet Inc. Hasp Key item and select priorities. Then click the driver tab and look at the version number. See the attached PDF file for more instructions on fixing the issue. Please let me know what you find out. If you need help, please contact our support staff at [email protected] or 860-875-5006. Safenet driver solution.pdf

good news/bad news. Finally duplicated the issue on an XP 32 machine (actually two of them so far) - bad news is I am still trying to figure out why that machine failed many others did not. More to come

Thanks to all that have sent information in on this issue. So far we have NOT been able to reproduce this in house. I have viewed the videos from Chris at In house and have used the exact same steps and I can't duplicate the issues. My network drives are mapped, but I also tried accessing a network driver using UNC and everything has worked fine. Now there are multiple permissions for the network where you could have Read/Write but not modify. Don't know if that matters yet or not but everything I have tried works just fine. Some how we need to find a common denominator with those having the problem and as of yet I have not. There was a change made in MU2 as to the function we call to do the save and rename to address an access issue that was reported, but again there is no one in the building here at CNC that has been able to reproduce. Those that are having the issue it would be nice to see it either via a web meeting or a video clip. If you have the issue and are willing to participate in a g2m web meeting or create a video please email us at [email protected] and let us know that you are available and when. Thanks for all the help with this one.

Can you cans put describe HOW you went about editing the control definition? Were all of you storing them on a network? Just tried a bunch of editing and no problems, so it must be something in common with the way all three of you are doing something so we need to look for the common trigger.

you can turn off the N output in the control definition and then in the post force output of sequence number (*n$) on the line where you want it to output. Ofcourse you need to setup some logic to assign the current tool number into the sequence number variable (ie n$ = t$) and you need to account for if you repeat the tool numbers how do you want them coming out, etc. Easy enough to do once you lay it all out.

Attached is the X6 MU2 readme file that contains a list of the bugs fixed in the X6 MU2 release. I'll see about getting this file linked on the download pages. ReadMe.htm

Label Not defined: Variable has not been defined or defined incorrectly String literal missing quotes$ missing from predefined variable $ missing from pre-defined variable Variable declaration missing or commented out.

Mick, The problem is probably related to the the output_z variable being used in the if statement. Search the entire post for output_Z and see if it is defined or declared in a NON postline there should be some line similar to this. output_z : 0 Because there is no $ on the variable MP recongizes this as a user_defined variable and all user_defined variables need to be defined. Find the output_z lines in your post and post them to the thread. It's always easier to have the post itself to see the entire set. Jim

Mick, Most likely the issues that are being reported are syntax type errors and all would have existed prior to MU2. The error reporting was broke in previous version, but the error files was still created and could be viewed. Post in X6 MU1 and look for the .err file in the NC folder and see for your self. Posting just the lines sometimes isn't enough and we need to see the lines around the line reporting the error as there could be something simple as a missing brace or comma that triggers the problem on the offending line. I put together a long explanation of how MP handles errors it encounters and will see if I can dig it up on the forum somewhere, but basically MP does it's best to solve the error and continue processing. So you could have errors that have NO effect on your NC code because the sections of code with the errors could potentially never be called. You wouldn't see an issue in the NC. I always suggest fixing these errors and they are normally very easy to address for a post guy. You can have your reseller fix it for you and you should get them fixed. I sent you a PM. Jim

For those that have seen this or have a part with this issue, please, please send QC the files - zip2go everything. Yes many times if we regen the file the issue goes away, but we do pass those files on to development to see if they can find something in there to help decipher what is causing the issue. I have to ask, do you run with multiple instances of mastercam open at the same time? What other programs do you have open? What 3rd party programs do you have installed and run? The more information the better as it will help us try and chase down potential causes when trying to reproduce the issue.

Go to the "HELP" Menu and click the "ABOUT" menu and the version will displayed in the upper left corner under the Mastercam logog along with the build date. Another way to access this is to use the ALT+ V keys.

Error 2727 - mystery so9lved. See the new thread on this issue. Can a mod please pin that thread. Thanks!

If you are installing X6 MU1 and you receive a Installer Error (See Attached image) 2727 - Directory Entry 'HRIZ4FRONT' does not exist in Directory Table the reason is because you have the wrong version of X6 installed. The re-release of X6 was version 15.0.4.3 and you must have this version installed to run the X6 MU1 install. Most likely if you receive this error you have the original X6 release 15.0.3.28 installed. You must uninstall the 15.0.3.28 release of X6 and reinstall the 15.0.4.3 release of X6 before installing X6 MU1. The 15.0.4.3 version is the only version available on our download site. NOTE: if you have modified any of the user customizable files (ie tools, defaults, posts, MDs, etc) that were installed with Mastercam you will want to back them up prior to performing an uninstall. The uninstall will remove all files installed during the install of X6 Mastercam regardless of if they were modified or not. Any user created files will be left in tact after running the uninstall.

It is located in the documentation folder in the main Mcamx6 folder (ie on my 64 machine C:\Program Files\mcamx6\documentation)

The X6 MU1 readme contains a list of bug fixes, minus one that forgot to be included - here it is - 107146 I(GES - The attached IGES file is from SDRC - It reads into X5 MU1 and X6 with all of the trimmed surfaces handled nicely. In X6 MU1 and X7 all of the trimmed surfaces error out and come in un-trimmed.)

The issue isn't MU1 overwriting the user customizable files, it was the uninstall, required for the beta testers, that was unistalling any modified installed file. For example if you use and modify the default installed files say for a tool library or default or post the X6 uninstall will remove them and then when you reinstall the default installed files are now what you are using. eXample: user changes a setting in mill_inch.defaults-6, then unistall x6, the changed file - mill_inch.defaults-6 - is removed (in my opinion it should stay). This issue was only related to the default installed files. The problem is not the MU1 but the X6 install and once in the field not so easy to fix. I checked and it did the same thing in X5. Development is looking into it and looking for a way to fix it if possible. Suggest you back up ALL user modified files prior to an uninstall or better yet, create a restore point as mentioned earlier. More to come as I get more information.

We seen this 4 times out of hundreds of installs so far. 3 were resellers and we still don't know why or what caused it. in all 4 cases the user was able to install after performing the following. uninstalling X6 Deleting the X6 folders (shared mcamx6, program files mcamx6) Cleaning the registry of all X6 items in both current user and local machine reinstall X6 from DVD Install MU1 The folder is correct and available, but the directory table that is used by the install project (install shield files) somehow has a kink in it and it can't find what it is looking for. Haven't found another way around it yet. You are now number #5. Sorry. Note: uninstalling X6 will remove any user modified installed files (defaults, posts, md, tools) so if you mad modifications to the default installed customizable files like mill_inch.defaults-6 then the X6 uninstall will remove them and when you install X6 you get the original ones which is confusing people in the beta program as MU1 overwriting them.

What are you using to get your programs to the machine? We had some problems at world skills with bad flash drives that would somehow not provide a valid NC file to the machine, but they were valid on the computer prior to copying to the flash drive. We grabbed new flash drives and everythign ran fine. If the program is not stopping at the same point then it could be memory related or something in the communication to the machine. If you ahve access to additional editors, open it up and display in hexidecimal mode and look for a character that shouldn't be there. Start looking at the lines around where it stopped.

Thanks for the files Glenn. I was able to produce the same findings. Files loaded fine in X6 XP 32, some crashed X6 Win7 x64. many of the 50 came in fine. If anyone else runs into this, please, please send int he files to QC so we can get them logged.