csound~ Error 998 on WinXP

View: New views
4 Messages — Rating Filter:   Alert me  

csound~ Error 998 on WinXP

by dp51 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I've been trying to figure out a problem related to the loading of Csound5 dll's.
When using csound~, MaxMSP 4.6, and Csound5 (floats and doubles), compiling
an orc will produce this error:

WARNING: could not open library 'C:\Program Files\Csound\plugins64\minmax.dll' (-1)

The error isn't fatal (no crashes) and the user is able to continue working with csound~
(as long as they don't use any opcodes in minmax.dll).  

With Max 5.0.4 and Csound5 (doubles), the errors are:

WARNING: could not open library 'C:\Program Files\Csound\plugins64\harmon.dll' (-1)
WARNING: could not open library 'C:\Program Files\Csound\plugins64\minmax.dll' (-1)
WARNING: could not open library 'C:\Program Files\Csound\plugins64\osc.dll' (-1)
WARNING: could not open library 'C:\Program Files\Csound\plugins64\shape.dll' (-1) WARNING: could not open library 'C:\Program Files\Csound\plugins64\stdutil.dll' (-1)


With Max 5.0.4 and Csound5 (floats), the error is:

Error 998 loading external csound~

In this situation, csound~ just doesn't work.  I figured out that all the errors are the same type of error.
Using the program Dependency Walker, I get this:

DllMain(0x058C0000, DLL_PROCESS_ATTACH, 0x00000000) in "CSOUND32.DLL.5.1" called.
First chance exception 0xC0000005 (Access Violation) occurred at address 0x9E4C0000.
LoadLibraryW("C:\program files\cycling '74\max 5.0\Cycling '74\msp-externals\_my_externals\csound~.mxe") returned NULL by thread 1. Error: Invalid access to memory location (998).


It's the same pattern for minmax.dll, hamon.dll, etc... .  I have a feeling it has something to do with the
fact that Max uses a different compiler that Csound5 on Windows.  I'd appreciate any help. Thanks.

Davis

Re: csound~ Error 998 on WinXP

by dp51 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I've done some more testing.  The LoadLibrary() errors only appear when using release 5.08.2 (doubles and floats) on Windows.  I tested with 5.03 - 5.07 and there were no problems.  

I downloaded Csound5.08.zip and compiled with:

MSYS 1.0.10
MinGW 5.1.4
gcc 3.4.5
scons 0.98.5
Python 2.5.1
libsndfile 1.0.17
portaudio v19 20071207
fltk 1.1.x-r5953
pthreads-w32 2.8 (2006_12_22)

So far, I've been unable to reproduce the LoadLibrary() errors.

One thing that caught my eye was the size of csound32.dll.5.1 and csound64.dll.5.1.  The dll's installed by Csound5.08.2-gnu-win32-f.exe and Csound5.08.2-gnu-win32-d.exe are nearly 4 MB in size, whereas the ones I compiled (and those in earlier releases) are less than 800 KB.  

I hope this information is of some use.  I've got my fingers crossed hoping that this problem doesn't appear in 5.09.

Davis

Re: csound~ Error 998 on WinXP

by Victor Lazzarini :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The DLLs are probably not stripped, that is why they are big. They should
have been stripped, IMHO. I reckon this something to do with the toolchain
used. If you follow this list, you'd have see similar problems with the Java
wrappers, which were removed with the package compiled under
a different toolchain.

Just to confirm, is this Windows only or are you getting same behaviour on
OSX?

Victor
----- Original Message -----
From: "dp51" <dmpyon@...>
To: <csound-devel@...>
Sent: Monday, July 28, 2008 12:25 AM
Subject: Re: [Cs-dev] csound~ Error 998 on WinXP


>
> I've done some more testing.  The LoadLibrary() errors only appear when
> using
> release 5.08.2 (doubles and floats) on Windows.  I tested with 5.03 - 5.07
> and there were no problems.
>
> I downloaded Csound5.08.zip and compiled with:
>
> MSYS 1.0.10
> MinGW 5.1.4
> gcc 3.4.5
> scons 0.98.5
> Python 2.5.1
> libsndfile 1.0.17
> portaudio v19 20071207
> fltk 1.1.x-r5953
> pthreads-w32 2.8 (2006_12_22)
>
> So far, I've been unable to reproduce the LoadLibrary() errors.
>
> One thing that caught my eye was the size of csound32.dll.5.1 and
> csound64.dll.5.1.  The dll's installed by Csound5.08.2-gnu-win32-f.exe and
> Csound5.08.2-gnu-win32-d.exe are nearly 4 MB in size, whereas the ones I
> compiled (and those in earlier releases) are less than 800 KB.
>
> I hope this information is of some use.  I've got my fingers crossed
> hoping
> that this problem doesn't appear in 5.09.
>
> Davis
>
> --
> View this message in context:
> http://www.nabble.com/csound%7E-Error-998-on-WinXP-tp18624895p18681859.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@...
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel

Re: csound~ Error 998 on WinXP

by dp51 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The problem only appears on Windows.  No problems on OSX.

Victor Lazzarini wrote:
The DLLs are probably not stripped, that is why they are big. They should
have been stripped, IMHO. I reckon this something to do with the toolchain
used. If you follow this list, you'd have see similar problems with the Java
wrappers, which were removed with the package compiled under
a different toolchain.

Just to confirm, is this Windows only or are you getting same behaviour on
OSX?

Victor
LightInTheBox - Buy quality products at wholesale price