Thanks for the information, this saves me time and trouble. We are working on this.

Regards,
Mike

-----Original Message-----
>From: Art Hunkins 
>Sent: Nov 8, 2007 12:25 PM
>To: Developer discussions 
>Subject: Re: [Cs-dev] OSC on Windows float installers
>
>Steven and Michael:
>
>Dropping msvcr80.dll into the csound\bin directory does not work for me.
>
>I still get WARNING: could not open fluidOpcodes.dll and rtpa.dll messages;
>and later, error: unknown rtaudio module: 'pa'.
>
>Art Hunkins
>
>----- Original Message ----- 
>From: "Steven Yi" 
>To: "Developer discussions" 
>Sent: Wednesday, November 07, 2007 11:46 PM
>Subject: Re: [Cs-dev] OSC on Windows float installers
>
>
>> That sounds like really good news then if we can just drop msvcr80.dll
>> in a directory.  Maybe you could put a copy of it somewhere for others
>> who have had problems with 5.07 like Tim to download and try putting
>> in their csound/bin directory to see if that will alleviate their
>> problem?  (If you want to send me a copy via email, I can post it on
>> my site for others to download and try).
>>
>> steven
>>
>>
>> On Nov 7, 2007 7:21 PM, Michael Gogins  wrote:
>> > Thanks for the explanation. For some reason I rarely have FTP failures
>and
>> > the other steps seem routine.
>> >
>> > The advantage, for me, is that when this is done there is never any
>doubt or
>> > ambiguity about where to go or what is what.
>> >
>> > By the way, I think that we can simply drop msvc80.dll into the Csound
>bin
>> > directory. It now looks like the manifest business only applies to
>programs,
>> > not DLLs. I am using the Microsoft "depend" tool to verify that the DLL
>is
>> > being loaded from this location for rtpa.dll and fluidsynth.dll. I will
>> > upload new point releases as soon as I have verified this. It is only
>> > portaudio_x86.dll and fluidsynth.dll that are being built with Visual
>C++ at
>> > this time.
>> >
>> > This all happened because I applied Service Pack 1 to my Visual C++
>Express
>> > Edition to be sure I had the latest version, and I did not understand
>that
>> > this brought in the manifest files, msvcr80.dll, etc., because of course
>> > Service Pack 1 put msvcr80.dll und so weiter into the WinSxS directory
>where
>> > they just worked for me.
>> >
>> > Best,
>> > Mike
>> >
>> > ----- Original Message -----
>> > From: "Steven Yi" 
>> >
>> > To: "Developer discussions" 
>> > Sent: Wednesday, November 07, 2007 9:18 PM
>> > Subject: Re: [Cs-dev] OSC on Windows float installers
>> >
>> >
>> > > Well, for me, from all the releases I've done with blue, I always find
>> > > myself anxious when doing releases with SF as the FTP system has been
>> > > telling me the upload failed even though it didn't, plus having to
>> > > upload, then go in and select all the files to add the release, then
>> > > going to mark them for file types is much more work than uploading to
>> > > an FTP and saying "here they are!".
>> > >
>> > > On Nov 7, 2007 6:08 PM, Michael Gogins  wrote:
>> > >> What do you mean about the file release system being hard to use? All
>we
>> > >> have to do is add "BETA" to the filename. I find this is a very easy
>> > >> system
>> > >> to use.
>> > >>
>> > >> Regards,
>> > >> Mike
>> > >>
>> > >> ----- Original Message -----
>> > >> From: "Steven Yi" 
>> > >> To: "Michael Gogins" ; "Developer discussions"
>> > >> 
>> > >>
>> > >> Sent: Wednesday, November 07, 2007 7:10 PM
>> > >> Subject: Re: [Cs-dev] OSC on Windows float installers
>> > >>
>> > >>
>> > >> > Hopefully that will work, if not, is there a technical reason that
>you
>> > >> > switched to VC++ versus staying with MinGW?  Or are there any
>> > >> > objections to building for release using MinGW?
>> > >> >
>> > >> > Taking into account Dr. B's email regarding Seoul and missing
>.dll's,
>> > >> > I am thinking as a post mortem to this whole 5.07 experience that
>we
>> > >> > might want to invest in doing at least one public beta build versus
>> > >> > going straight to release and to try to catch problems with that.
>I
>> > >> > think it would help make expectations be what they should plus it
>> > >> > would give us time to fix any issues for a "release" quality build.
>I
>> > >> > think there are users in our community who would be willing to try
>out
>> > >> > betas and give feedback.
>> > >> >
>> > >> > For a new release, I think we should do one as soon as possible as
>> > >> > Victor has fixed diskin and I think we can probably research and
>fix
>> > >> > turnoff2 and those affect everyone.  For the windows build, I can
>> > >> > install NSIS and will try to get involved with building and testing
>> > >> > that (will have to wait until after tomorrow though!).
>> > >> >
>> > >> > For the betas, we can use sourceforge but as we all know who have
>used
>> > >> > the file release system that it is not very easy to use.  It might
>be
>> > >> > worth creating an ftp site just for downloading betas.
>> > >> >
>> > >> > Thoughts anyone?
>> > >> >
>> > >> > Thanks!
>> > >> > steven
>> > >> >
>> > >> >
>> > >> > On Nov 7, 2007 10:07 AM, Michael Gogins 
>wrote:
>> > >> >> It's not that simple... VC++ binaries now always have a manifest,
>and
>> > >> >> the
>> > >> >> CRT in the manifest must be where and what version the manifest
>says.
>> > >> >> Just including msvcr80.dll in the installer and putting it where
>the
>> > >> >> manifest says should would do the job, and I will indeed try that.
>But
>> > >> >> I'm not sure this is the best solution; Windows in general wants
>to
>> > >> >> find
>> > >> >> these libraries in WinSxS, which is where the redistributable
>> > >> >> installer
>> > >> >> puts them.
>> > >> >>
>> > >> >> Regards,
>> > >> >> Mike
>> > >> >>
>> > >> >>
>> > >> >> -----Original Message-----
>> > >> >> >From: Steven Yi 
>> > >> >> >Sent: Nov 7, 2007 11:35 AM
>> > >> >> >To: Developer discussions 
>> > >> >> >Subject: Re: [Cs-dev] OSC on Windows float installers
>> > >> >> >
>> > >> >> >Is it the game plan to package the msvcrt80.dll with Csound so
>that
>> > >> >> >users won't need to download separately?
>> > >> >> >
>> > >> >> >On Nov 7, 2007 5:24 AM, Michael Gogins 
>wrote:
>> > >> >> >> This is not my doing, it is Microsoft's. I expect this to be a
>> > >> >> >> permanent
>> > >> >> >> situation. Microsoft's reasoning is that they need to tie
>binaries
>> > >> >> >> to
>> > >> >> >> specific versions of libraries for stability and security
>reasons,
>> > >> >> >> and
>> > >> >> >> this
>> > >> >> >> is how they chose to do it. The same problems do indeed exist
>on
>> > >> >> >> Linux, but
>> > >> >> >> the Linux solution is qualified sonames, e.g. csound32.so.5.1
>or
>> > >> >> >> csound32.so.5.0. I guess this was too simple and Linux-like for
>> > >> >> >> Microsoft to
>> > >> >> >> copy.
>> > >> >> >>
>> > >> >> >> Sorry.
>> > >> >> >>
>> > >> >> >> Regards,
>> > >> >> >> Mike
>> > >> >> >>
>> > >> >> >> ----- Original Message -----
>> > >> >> >> From: "Tim Mortimer" 
>> > >> >> >> To: 
>> > >> >> >>
>> > >> >> >> Sent: Wednesday, November 07, 2007 4:45 AM
>> > >> >> >> Subject: Re: [Cs-dev] OSC on Windows float installers
>> > >> >> >>
>> > >> >> >>
>> > >> >> >> >
>> > >> >> >> > My XP installation is Service Pack 1
>> > >> >> >> >
>> > >> >> >> > 1) do i still need to do this?
>> > >> >> >> >
>> > >> >> >> > 2) the link to the microsoft download Visual C++ site (i.e.
>your
>> > >> >> >> > link
>> > >> >> >> > Mike)
>> > >> >> >> > says
>> > >> >> >> >
>> > >> >> >> > "Supported Operating Systems: Windows 2000 Service Pack 3;
>> > >> >> >> > Windows
>> > >> >> >> > 98;
>> > >> >> >> > Windows 98 Second Edition; Windows ME; Windows Server 2003;
>> > >> >> >> > Windows
>> > >> >> >> > XP
>> > >> >> >> > Service Pack 2"
>> > >> >> >> >
>> > >> >> >> > if 1) == "yes" then i guess this means i'd better find a
>service
>> > >> >> >> > pack 2
>> > >> >> >> > update - just so i can continue to run Csound? (my music PC
>was
>> > >> >> >> > not,
>> > >> >> >> > is
>> > >> >> >> > not,
>> > >> >> >> > & never will be online...)
>> > >> >> >> >
>> > >> >> >> > I don't like to be picky, but i am starting to get a hunch
>that
>> > >> >> >> > this
>> > >> >> >> > is
>> > >> >> >> > not
>> > >> >> >> > an "ideal" solution....
>> > >> >> >> >
>> > >> >> >> > An avid watcher of this thread (who understands little other
>than
>> > >> >> >> > it
>> > >> >> >> > has
>> > >> >> >> > some potentially major implications beyond my level of
>expertise
>> > >> >> >> > &
>> > >> >> >> > understanding) awaits further input & developments....
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >> > Michael Gogins wrote:
>> > >> >> >> >>
>> > >> >> >> >> I have discovered the cause of these problems with rtpa.dll
>and
>> > >> >> >> >> the
>> > >> >> >> >> Fluid
>> > >> >> >> >> opcodes.
>> > >> >> >> >>
>> > >> >> >> >> In Csound 5.07's Windows installers, I built the PortAudio
>DLL
>> > >> >> >> >> (used by
>> > >> >> >> >> rtpa.dll) and the FluidSynth DLL (used by fluidOpcodes.dll)
>> > >> >> >> >> using
>> > >> >> >> >> Microsoft
>> > >> >> >> >> Visual C++ Express Edition, Service Pack 1, instead of with
>> > >> >> >> >> MSYS/MinGW or
>> > >> >> >> >> MSVC++ Express Edition before the service pack, as I used to
>do.
>> > >> >> >> >> The
>> > >> >> >> >> result
>> > >> >> >> >> is a more complete, up to date, and probably faster build.
>> > >> >> >> >>
>> > >> >> >> >> However, with Service Pack 1, Visual C++ creates a
>"manifest"
>> > >> >> >> >> for
>> > >> >> >> >> all
>> > >> >> >> >> applications and DLLs that tightly ties the binary with a
>> > >> >> >> >> specific
>> > >> >> >> >> version
>> > >> >> >> >> of the Microsoft C runtime library (msvcr80.dll, in this
>case).
>> > >> >> >> >> This DLL
>> > >> >> >> >> has
>> > >> >> >> >> to be just exactly the right version (specified in the
>manifest)
>> > >> >> >> >> and it
>> > >> >> >> >> has
>> > >> >> >> >> to be installed in the just right location (also specified
>in
>> > >> >> >> >> the
>> > >> >> >> >> manifest).
>> > >> >> >> >>
>> > >> >> >> >> The best way for you and other users to resolve these issues
>is
>> > >> >> >> >> to
>> > >> >> >> >> download
>> > >> >> >> >> and run the following installer, which installs the required
>> > >> >> >> >> runtime
>> > >> >> >> >> library
>> > >> >> >> >> and other DLLs as "side by side" assemblies in the Windows
>> > >> >> >> >> directory:
>> > >> >> >> >>
>> > >> >> >> >>
>http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
>> > >> >> >> >>
>> > >> >> >> >> I recommend that you do this, and please let us all know if
>it
>> > >> >> >> >> works!
>> > >> >> >> >>
>> > >> >> >> >> Alternatively, you could try to download msvcr80.dll from
>> > >> >> >> >> http://www.dll-files.com/dllindex/dll-files.shtml?msvcr80
>and
>> > >> >> >> >> copy
>> > >> >> >> >> it
>> > >> >> >> >> into
>> > >> >> >> >> your Csound bin directory as a "private assembly". The
>manifest
>> > >> >> >> >> for
>> > >> >> >> >> portaudio_x86.dll is:
>> > >> >> >> >>
>> > >> >> >> >> 
>> > >> >> >> >> > > >> >> >> >> manifestVersion='1.0'>
>> > >> >> >> >>   
>> > >> >> >> >>     
>> > >> >> >> >>       name='Microsoft.VC80.CRT'
>> > >> >> >> >> version='8.0.50608.0' processorArchitecture='x86'
>> > >> >> >> >> publicKeyToken='1fc8b3b9a1e18e3b' />
>> > >> >> >> >>     
>> > >> >> >> >>   
>> > >> >> >> >> 
>> > >> >> >> >>
>> > >> >> >> >> So, I think if you ended up with this it should work:
>> > >> >> >> >>
>> > >> >> >> >> csound/bin/Microsoft.VC80.CRT/msvcr80.dll
>> > >> >> >> >>
>> > >> >> >> >> I will attempt to put msvcr80.dll into the installer in the
>> > >> >> >> >> correct
>> > >> >> >> >> directory as a private assembly. If that does not work, I
>will
>> > >> >> >> >> include
>> > >> >> >> >> the
>> > >> >> >> >> redistributable installer in the Csound installer.
>> > >> >> >> >>
>> > >> >> >> >> Hope this helps,
>> > >> >> >> >> Mike
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >>
>> > >> >> >> >
>> > >> >> >> > --
>> > >> >> >> > View this message in context:
>> > >> >> >> >
>http://www.nabble.com/OSC-on-Windows-float-installers-tf4762094.html#a13623974
>> > >> >> >> > Sent from the Csound - Dev mailing list archive at
>Nabble.com.
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >>
>> -------------------------------------------------------------------------
>> > >> >> >> > This SF.net email is sponsored by: Splunk Inc.
>> > >> >> >> > Still grepping through log files to find problems?  Stop.
>> > >> >> >> > Now Search log events and configuration files using AJAX and
>a
>> > >> >> >> > browser.
>> > >> >> >> > Download your FREE copy of Splunk now >>
>http://get.splunk.com/
>> > >> >> >> > _______________________________________________
>> > >> >> >> > Csound-devel mailing list
>> > >> >> >> > Csound-devel@lists.sourceforge.net
>> > >> >> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >> >> >>
>> > >> >> >>
>> > >> >>
>>> -------------------------------------------------------------------------
>> > >> >> >> This SF.net email is sponsored by: Splunk Inc.
>> > >> >> >> Still grepping through log files to find problems?  Stop.
>> > >> >> >> Now Search log events and configuration files using AJAX and a
>> > >> >> >> browser.
>> > >> >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > >> >> >> _______________________________________________
>> > >> >> >> Csound-devel mailing list
>> > >> >> >> Csound-devel@lists.sourceforge.net
>> > >> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >> >> >>
>> > >> >> >
>> > >> >>
>>-------------------------------------------------------------------------
>> > >> >> >This SF.net email is sponsored by: Splunk Inc.
>> > >> >> >Still grepping through log files to find problems?  Stop.
>> > >> >> >Now Search log events and configuration files using AJAX and a
>> > >> >> >browser.
>> > >> >> >Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > >> >> >_______________________________________________
>> > >> >> >Csound-devel mailing list
>> > >> >> >Csound-devel@lists.sourceforge.net
>> > >> >> >https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >>
>>> -------------------------------------------------------------------------
>> > >> >> This SF.net email is sponsored by: Splunk Inc.
>> > >> >> Still grepping through log files to find problems?  Stop.
>> > >> >> Now Search log events and configuration files using AJAX and a
>> > >> >> browser.
>> > >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > >> >> _______________________________________________
>> > >> >> Csound-devel mailing list
>> > >> >> Csound-devel@lists.sourceforge.net
>> > >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >> >>
>> > >> >
>> > >>
>> -------------------------------------------------------------------------
>> > >> > This SF.net email is sponsored by: Splunk Inc.
>> > >> > Still grepping through log files to find problems?  Stop.
>> > >> > Now Search log events and configuration files using AJAX and a
>browser.
>> > >> > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > >> > _______________________________________________
>> > >> > Csound-devel mailing list
>> > >> > Csound-devel@lists.sourceforge.net
>> > >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> >
>>> -------------------------------------------------------------------------
>> > >> This SF.net email is sponsored by: Splunk Inc.
>> > >> Still grepping through log files to find problems?  Stop.
>> > >> Now Search log events and configuration files using AJAX and a
>browser.
>> > >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > >> _______________________________________________
>> > >> Csound-devel mailing list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >
>> >
>> -------------------------------------------------------------------------
>> > > This SF.net email is sponsored by: Splunk Inc.
>> > > Still grepping through log files to find problems?  Stop.
>> > > Now Search log events and configuration files using AJAX and a
>browser.
>> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > > _______________________________________________
>> > > Csound-devel mailing list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>>
>> -------------------------------------------------------------------------
>> > This SF.net email is sponsored by: Splunk Inc.
>> > Still grepping through log files to find problems?  Stop.
>> > Now Search log events and configuration files using AJAX and a browser.
>> > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Would there be the same problems if Csound was being built with MinGW, 
just curious.

Rory.



Michael Gogins wrote:
> Thanks for the information, this saves me time and trouble. We are working on this.
> 
> Regards,
> Mike
> 
> -----Original Message-----
>> From: Art Hunkins 
>> Sent: Nov 8, 2007 12:25 PM
>> To: Developer discussions > http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net