X6 MU2 crash

[Nils N]

I’ve installed MU2 about 4 times now. Each time I remove every trace of X6 I can find, even ran a utility I got form the local Mastercam rep to remove X6.

Everything works fine up through the installed MU1 but when I install MU2 and start X6 I get this--- Has anybody had this problem and gotten it to work?

[Guest]

for starters, you don't need to install MU1

 

MU2 will give you everything.

 

Try uninstalling again, clean it up, reboot

 

DO the X6 DVD, start it once, then do MU2

 

See if that gets you through,

 

If that does NOT work, I'd wager your .net is screwed and needs to be pulled out and re-installed

[Nils N]

I for got to mention that I did do that install, X6 to MRU2 twice and still got that crash message. So now I am running X6 MR1.

 

What do you mean my .net is bad. Do you mean .net Utitlies or microsoft .NET Framework 1.1

[Guest]

.net 4. is what X6 uses

[Thee Awbade™]

This is the guy that works with nils. He went to run an errand. I'm updating the computer right now to Net Framework 4. When he gets back we'll do the un-install and reinstall of X6 with MU2, and keep you updated on how that works for us. Thanks for the info JParis!

[Thee Awbade™]

So we updated the .net framework. Uninstalled, reinstalled x6, worked. Installed Mu2, (didn't add any of our previous set-up folders) worked fine with new framework.

Replaced the default "My Mxcam6, Shared Mxcam6" Folders with ones that we had saved in a separate folder. (with our settings etc etc.) Then when we tried to reopen Mcam6 MU2 again, it crashed. we got this

Problem signature:

Problem Event Name: APPCRASH

Application Name: Mastercam.exe

Application Version: 15.2.1.2

Application Timestamp: 4fc4e9f4

Fault Module Name: MCMachineDef.dll

Fault Module Version: 15.2.1.2

Fault Module Timestamp: 4fc4ea11

Exception Code: c0000005

Exception Offset: 000000000005ffd0

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Additional Information 1: 693f

Additional Information 2: 693f17baaefe04f2e4c3adb273f8e42c

Additional Information 3: 0e2c

Additional Information 4: 0e2c0811fc8ab2786a13acd350ce5dad

[Guest]

Are you using the DVD or the web download?

[Thee Awbade™]

We're using the Web Download for X6 AND Mu2.

 

We can get Mu2 running fine (stock machine def's etc etc.) But the issue comes when we copy over our settings(config/cnc machine files/mill/Posting preferences).

 

In my opinion there's something in there that changed with the most recent update that MU2 doesn't like. We're going to try bringing over all the individual files one by one, and checking each time to see exactly which file it is that MU2 doesn't want to co-operate with. Hopefully this should narrow down our problem and we'll be able to fix it by redefining it in Mcam itself.

 

*Fingers crossed*

 

Which is better to use? The DVD or Web Download?

[Thad]

Using the DVD install for X6, then the web MU2 download here with no problems. Not sure what's "better."

[Thee Awbade™]

So nothing in particular? I Would assume that Web DL would be best just because of it being more recently updated?

 

We're in the process of reinstalling everything fresh, then we're gonna try selecting our files carefully to switch, will keep you guys updated.

[Guest]

Here's the problem with the web download

 

If your systems, Windows installer routine needs to be updated, the DL doesn't have the ability

 

The DVD checks the installation requirements and prerequisites to make sure everything is on your system that needs to be there.

 

It is ALWAYS better to use the DVD

[Thad]

We can get Mu2 running fine (stock machine def's etc etc.) But the issue comes when we copy over our settings(config/cnc machine files/mill/Posting preferences).

 

Where did you get these files from? A working install of X6 MU2? X5?

[Thee Awbade™]

I don't believe it's the Windows installer that's the problem. Like I said we can install/run MU2 fresh out the box with the Web DL and have it run fine, the .net framework problem solved that.

 

The issue now comes when we move our custom config/post/machine definition files from our saved folder (that was working in MU1) over to the "My Mcamx6/Shared Mcamx6"

[Guest]

DO NOT COPY CONFIG FILES!!!!

 

 

We've all been talking about that for 2+ years

 

There's your problem right there

 

.mtb

.kmp

all your control, machine defs, posts, tool libraries, op defaults, op libraries

 

ALL good

 

DO NOT JUST DROP the .config and expect it to run

 

Delete the config, start Mastercam again and let it create a stock config file

[Gilberto]

I have seen this today in a customer PC.

The problem was a .MMD-6 that did not exist...

 

Check the "Mastercam event log" in the task bar.

It shows what file is causing the problem.

[Thee Awbade™]

Ok so we're up and running now with MU2.

We didn't try to move any of the files that weren't the ones you specified and it worked well.

 

Thanks for the advice!

[Guest]

Most people config files only have a handful of changes, screen colors, a few settings and maybe some paths, the toolbar file(.mtb) that really handle how your screen is laid out, that's an important, in some cases fairly complex file but you can tale that

 

But, yeah just dropping that config, headaches galore, as you've seen

[Thoob]

You can do update folder with the config. Thats what I did and it was fine.

[Thee Awbade™]

hmm, we might try that later. Right now we have a big project we're working on, and we already spent all morning messing with it >.< We've got a workable version now so we're gonna stick with that for the time-being. We'll let ya know when we start messin with stuff again haha.