Code center > Bugs and fixes

Problem with 3.4 source code?

<< < (3/7) > >>

Ulciscor:
OK Microsoft support says the error can be generated as following:


Dllname is not a .dll or .ocx file. For example, typing regsvr32 wjview.exe generates this error message.

OR

Dllname may not be exported, or a corrupted version of Dllname may be in memory. Consider using Pview to detect the file and remove it.

I've no idea which of these is most likely.

PurpleYouko:
I had the same problem a while back with an excel utility that used a bunch of activex features.
I had to use the full path C:\WINNT\System\System32...ect. and actually be in the root directory at the time or the bloody dll just would not register.

I haven't tried this new version yet cuz I have been too busy. Maybe I will give it a shot today to see how it goes.

Ulciscor:
Just found this, don't know if it has any relevance.

Error: "C:\Program Files\SoftArtisans\WordWriter\WordWriter.dll was loaded, but the DLLRegisterServer entry point was not found. DLLRegisterServer may not be exported, or a corrupt version of C:\Program Files\SoftArtisans\WordWriter\WordWriter.dll may be in memory. Consider using PView to detect and remove it."
This error is the result of attempting to register the WordWriter.dll with regsvr32, which can be used to register COM objects, but not .NET ones.

I have some .net framework installed on my pc, and possibly a partial remnant of vb.net remaining from a previous installation. Would this cause the problems I am having? The site suggests running regsvr on the COM object not the DLL.

Ulciscor:
Lol sorry to post again, ut interestingly the DLL error disappears when I change

Declare Function FastInvSqrt Lib "FastMath" (ByRef x As Single) As Single

to

Declare Function FastInvSqrt Lib "FastMathDLL" (ByRef x As Single) As Single

but weird stuff is happening. Not sure if this is just because of wonky settings or the change I have made. But there are no dll errors now.

Numsgil:
There are so many changes, I have a feeling we'll be sorting through wonky things for quite a while.  Be sure to set all physics values to something real.  That's the most obvious solution.

After that start posting what you find weird.  This is a long road.

Navigation

[0] Message Index

[#] Next page

[*] Previous page