MTM2.com

I get the following error message:

"The procedure entry point glDeleteTextures could not be located in the dynamic link library OPENGL32.dll."

Is there an updated OPENGL32 that I'm not aware of? Malibu's support files are no help.

When do you get the error message? When you first start binedit or when you try to open a model? What file gives the message?

As soon as I attempt to open the program.

Hello? Can't anyone help me with this problem?

I've been unable to reproduce the problem and seeing as nobody else has piped in with anything I'm assuming neither have they. So, back to a list of questions....

Which version of binedit are you using?
Where did you get the download? http://binedit.com/ is the only valid source
What operating system?
Where is binedit on your hdd? and where are the support files?
Since it happens when you first run it, I assume you haven't had a chance to set the preferences yet. Is this correct?
Is there anything else you can tell us?

Can you run a dependency viewer on the EXE and find out what is missing?

Which version of binedit are you using?

2.2

Where did you get the download?

Mal's site

What operating system?

XP

Where is binedit on your hdd? and where are the support files?

In my MTM2 folder, and the support files are with it.

Since it happens when you first run it, I assume you haven't had a chance to set the preferences yet. Is this correct?

Yes

Is there anything else you can tell us?

I also have BinEdit 2.0, which does work.

> BinEdit 2.2 does not works
> BinEdit 2.0, which does work
> binedit is in my MTM2 folder, and the support files are with it.

Ah, okay. Version 2.0 and 2.2 do not use the same support files. They were made with differenct programs. The support files from binedit.com are not the same as those on mal's beta page.

http://malibu350.com/m350/

Mal has 8 files there. Download all of them and put them in the same folder as binedit. Over-write anything already there. That should get you going. If it doesn't, then copy all eight to the C:\WINDOWS\system32 folder, and then reboot. Sometimes a program will install wonky dll files so reinstalling the proper ones (from mal's downloads) may help - that's a lesson taught me by Guitar Bill, and it's worked more than once for me.

That solved the problem - thanks.