C++ runtime error

May 24, 2007 at 10:13pm

C++ runtime error

Hi,

I am getting an extremely upsetting message when trying to load Max now
(image attached)

Could my graphics driver be causing this error – I updated the drivers
recently – Or any malicious patches I’ve installed?

I tried reinstalling max, as well as uninstalling jitter, but to no avail.

Andreas
WinXP, geforce8800gts, Max 4.6.3, Jitter 1.6.3

Ps: Sorry for any cross- or double postings that may have occured, my
email is extremely wonky, and I am feverishly looking for a fix for this.
thanks,
A.

#32088
May 24, 2007 at 11:49pm

didn’t get the picture file. can you just type what the error was?

#105050
May 25, 2007 at 7:58pm

Scott skrev:
> didn’t get the picture file. can you just type what the error was?
>
Sure, Scott:

Header read:
Microsoft Visual C++ Runtime Library

Body of text read:
“”
Buffer overrun detected!

Program c:Program FilesCycling ’74MaxMSP 4.6Max.exe

A buffer overrun has been detected which has corrupted the program’s
internal state. The program cannot safely continue and must now be
terminated.

“”
Again, any idea on how to fix this apart from a full reinstall of my OS
would be most appreciated… sigh.. I was just on a Jitter-roll…
Thanks.

Andreas.

#105051
Oct 26, 2007 at 4:21pm

Hi,
I am getting the exact same error message and it is impossible to open max.
this happens as the status under the splashscreen says “initilizing interface”. and the error message pops up.
Any solutions?

#105052
Oct 26, 2007 at 8:34pm

Hi Gimbal,

Are you able to start up Max/MSP Runtime? If the runtime works fine, it
may be that you need to reinstall the PACE drivers:

http://paceap.com/dldrvr.html

If you are still having problems, please contact support at cycling74
dot com.

All the best,
-Ben

gimbal wrote:
> Hi,
> I am getting the exact same error message and it is impossible to open max.
> this happens as the status under the splashscreen says “initilizing interface”. and the error message pops up.
> Any solutions?
>

#105053

You must be logged in to reply to this topic.