Still can't install X2. I called my reseller, but he can't figure it out. I'm using 64-bit XP and installed the correct .net2.0 file, but I get a few errors when installing X2: ERROR 1904. Module C:WINDOWSSYSWOW64MCDESCR.DLL FAILED TO REGISTER. HRESULT-2147010895 ERROR 1904. Module C:MCAMX2DIRECTMCIVENTOR.DLL FAILED TO REGISTER. HRESULT-2147010895 ERROR 1904. Module C:MCAMXCDIRECTMCSEDGEADDIN.DLL FAILED TO REGISTER. HRESULT-2147010895 ERROR 1904. Module C:WINDOWSSYSWOW64MCLSTCTL.OCX FAILED TO REGISTER. HRESULT-2147010895 I hit ignore on all these errors and continued with the installation. I double clicked on the new X2 icon and this error popped up. "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem" I reinstalled and had the same errors. Anyone have any ideas? Thanks!

Didn't work for me. I'll reinstall and see what happens.

Alright, I'm gonna try it. If you don't hear from me in awhile, obviously my foreman went postal again. Hehhehehe

Ok, before I upgrade, will my MR2 post, machine definitions, and control definitions work with X2?

Ya might wanna check for a loose or worn belt too if that spindle is belt driven. My late OKK had no problem with that same cutter and similar speeds and feeds cutting P-20 HH.

I have just noticed that if you hit the ESC key while selecting the holes, the temporary points will appear, but when you continue selecting more holes, the points disappear again. Hmmm, I wish there was a way to keep them points on.

Beardog is right. Just right click the center option rather than left clicking. It will lock that selection. I use it all the time

Jeff. She did it! I have different config files using different temp files and now I can have multiple sessions open without any problems so far.

Oh, sorry bout that. Thanks for the advice. I'll do that next time.

I added the file 11352_B_MAIN_HANDLE_LOWER.MCX to this forums ftp site in the MCX folder for review if anyone has time to look at it. Thanks! -Matt

I never have a problem getting the h and d value to match in all cases, except when importing the toolpath.

WARNING!!! I just did the same as you for the first time last week and the tool length offets weren't transfered. It defaulted to an H0. I didn't notice it till I slammed a ball mill into my part. Keep an eye on that. I also have the same problem you described and I hope someone here has a solution too.

Hello Thad. It shows 5373.5K. Hmmm... I checked the ftp sight from my tube at home and everything seems kosher.

Our IT lady just set it up that way Jeff but I didn't have time to test it. She did the same for V9 and it worked in the past.

Yep, the path is shown when I look in the spot edmbosto. But when I click "play", nothing happens. I added the file to our ftp site. ftp://24.123.83.50/YAMA/ 11352_B_MAIN_HANDLE_LOWER.MCX Roger, I sent qc an email with the ftp addy. Thanks!

I can't verify the toolpath either.

I can't seem to backplot a Surface Leftover toolpath after I edited it in the Toolpath Editor. Is this actually possible?

Jeff, that feature is great when selecting surfaces. It's not unusual for my cad data to have 1000+ surfaces, but with the polygon selection, I can select almost the minimum and my toolpaths will regenerate much faster than selecting "all surfaces".

Chris. That is the EXACT problem we have! I hope you nailed it! We'll be looking forward for the X2 upgrade. Thank you!

I hear ya! My partner just had to regen over 50 ops, about 30 of them were surfacing toolpaths. We are not the slightest bit pleased. We're already getting some heat from the management.

I still get dirty ops with the operations locked.

Hmmm. This certainly sucks! Mcamnut, I have the same video card that you're using. I also have the unified back buffer disabled. I hope this problem is fixed with X2. Thanks for the reply gentleman!

After reading the archives, I have realized that I'm not the only one having a problem with all of my operations going dirty. I have to regenerate several surfacing operations and this is getting ridiculous. I think I finally pinpointed what actually causes this problem, but I don't know how to fix it. If I have two MCX sessions open (different files), and read a new file, it causes the other session to wig out and cause the operations to go dirty. But.... if I close one session, and open a new file, I don't have the problem. Has there been a fix for this problem yet?

I am also running MCX MR2 on XP-64 without any problems.

I'll also look into that ref.pdf file. I don't understand why Mastercam doesn't package documentation regarding post modifications along with the software. Newer programmers (like myself) can sometimes struggle getting everything ticking like a clock while our employers only care about results. I've also learned much about modifying the post on this forum using the search feature. There are many great users on this forum that understand the frustration when things just don't go as planned.