Buffer Overrun MR2

[MMT-USA]

I tried changing my configuration setting while a project was open and completely corrupted MR2. I tried "repairing" the installation with no luck. MR1 works fine but it looks like MR2 is dead.

[Steve Zirtzman]

MMT-USA,

Which Config setting were you changing? Did you save your install directory when loading MR2.

[MMT-USA]

Steve, I had to uninstall it and reload it to get it to work.

 

All I changed was the MRU from 10 to 20

[TyK]

I've had the same problem. Three times. It doesn't seem to matter which setting I change, any small thing and bam. Is there a solution for this bug?

[Kelly Burns]

Had this happen for the first time this morning.

Changed an old program for a haas to a different machine def for a fadal, and got the same message, buffer overrun, corrupt file and all.

Went ahead and posted it and just edited out what I needed to get it to go. What gives?

[Thad]

I realize this doesn't solve your problem, but I always start a new session of MC when making config changes. MC grabs all current settings (data paths, origin marker on, autocursor settings, etc) and saves them as default. I don't like that. A new session allows me to keep all my settings when making changes. Kind of a pain, but it works. I've also never experienced your problem.

 

Thad

[rdshear]

I have had this problem for some time as well. I have noticed also that it seems to happen much less when 1st started before opening a job. I have a config file that will generate the buffer overrun upon load if anyone is interested. Also, I save my config as a different name and use that as my active config file that way when the corruption happens, I just copy the original mcamx.config to my config file name and I'm back up and running with the original defaults.

 

Rick

[Keith @ Solid Code Solutions]

When a buffer over run occurs it buggers up the default config. So if you make a back up of the config, you can replace it after the overrun happen without having to uninstall and reinstall the application.

[Keith @ Solid Code Solutions]

Or if you would like to just go back to factory defaults just delete you default config and the restart McamX. It will create a new factory default config when restarted.

[rdshear]

I first started having this problem right after the update. see this post. The problem went from failing to load resources to buffer overrun's. I finally have all my settings finished so I'll be staying away from the config unless it's just on a fresh boot.

[rdshear]

Has anyone officially acknowledged this problem from Cad/Cam? Just wondering if they are working on it.

 

Rick

[Keith @ Solid Code Solutions]

As far as I know QC has been made aware of the issue.

[gmenzies]

I reported this Bug a while back. Got a call from cnc software and was able to reproduce over and over again.

 

lessons learned :

 

1)only mak config changes at start up.

 

2) do not use Alt -d for dimension changes

X will blow up

 

3) make a couple of config file backups under differant names. just incase things blow up

along the way

 

4) still waiting for the fix

 

Gord

[Keith @ Solid Code Solutions]

Hey Gord,

 

How's it going? I'm back over at Innovative.

[gmenzies]

Hi Kieth

 

going good. trying to keep up with my 11 year old

were are riding the hills of whistler, took a hugh

dump near the bottom of the gondola. the people in the beer garden gave me a ten for the landing.

 

I heard you went back to Inovative. hows the comute?

 

Best regards Gord

 

[Keith @ Solid Code Solutions]

Hey if your going to bail, do it with style grace and .....humility. If you don't bail every now and then your not riding hard enough.

 

The commute isn't too bad, I'm on this side of the creek..up 99 towards White Rock.

 

How is everything at PH?