|
Michael,
Pursuant to your suggestions, I uninstalled 6.03.2,
downloaded a fresh 6.03.2 installer directly to my Windows 7 machine and
reinstalled it while not checking Python-feature installs. (I had checked the
Python features during the previous install to make sure this was not part of my
problem!) Doing so naturally got rid of the Python advisory popup when
running Csound. Otherwise, the result of running "csound Test.csd" was as
before, with fatal error "Illegal instruction."
I also downloaded a second copy of
depends.exe, and proceeded to run it with csound and then with Test.csd. I've
again attached the resulting .dwi file (but not to the full Csound list).
(Incidentally, I had to run depends from within WinZip, as it again would not
permit me to extract it.??)
Regarding the OS: it announces itself as Windows 7
Professional, and I purchased the machine, with OS installed, used, on eBay
(it's a Compac Evo with Intel Pentium 4, 2.4GHz, with 1.5GB RAM). System
Properties says Windows 7 Professional, and that it is a 32-bit OS. I am the
only user and admin.
I got the machine purely to run Csound6
(and test my projects - including Cabbage versions), because Csound6 wouldn't
run on my Windows XP computers. I wonder if there are any special system
settings I need to enable/disable?
Art Hunkins
----- Original Message -----
Sent: Tuesday, July 15, 2014 9:23
PM
Subject: Re: [Csnd] Realtime Csound6 on
Windows System 7
I see two potential problems. One is that according to the Dependency
Walker, py.dll, which contains the Csound Python opcodes, is looking for
Python 2.7. Either remove the py.dll file, or install Python 2.7 32 bit
version.
The other potential problem is that you are running the following operating
system:
Microsoft Windows NT/2000/XP/2003/Vista based Media Center (32-bit),
version 6.01.7601 Service Pack 1.
This appears to be a 32 bit operating system. I think it might be the
"personal edition" of Windows 7, which isn't really Windows 7 at all. Windows
7 and 8 are normally 64 bit/32 bit operating systems. I don't think this is
the problem in your case however, I think your OS should be able to run this
build of Csound. I think the warnings about files whose names start
with API-MS-WIN- can safely be ignored. But I could be wrong.
Try moving the py.dll file away first.
Regards,
Mike
On Jul 15, 2014 8:42 PM, "Art Hunkins" < abhunkin@uncg.edu>
wrote:
Hi Michael,
I have followed up on your suggestions, on my Windows
7 desktop.
1) No competing libsndfile or portaudio DLLs
exist.
2) Changing PATH to what you suggest made no
difference.
3) Going the depends.exe route yielded results. The
image yielded by profiling Test.csd within Csound is attached (if does not
come through to you, please advise; the list will receive this message
without the sizeable attachment). There appear to be multiple problems (in
red type). Probably they will indicate to you what has been going
on.
Two additional observations:
4) I notice that previously I had installed your 6.02
edition (I found this Setup download still among my files - though 6.02 had
been thoroughly uninstalled before installing 6.03.2.) I don't this this
matters, but who knows . . .
5) A curious thing happened when I downloaded and
attempted to unzip (with WinZip) the depends archive (depends32_x86). I
wasn't authorized to extract it (though I'm the admin). Tried multiple times
to several locations; I ended up running it from within WinZip, which seemed
to work just fine. This particular machine seems to have some peculiar
quirks about it, and I am not the original owner. So, another "who knows" .
. .
Please let me know of any diagnosis!
Thanks so much -
Art Hunkins
----- Original Message -----
Sent: Monday, July 14, 2014 7:15
PM
Subject: Re: [Csnd] Realtime Csound6
on Windows System 7
I just tried Art's test CSD on my Windows 8 machine where I
built it, but in the installation environment. It worked fine.
I'm afraid I don't have a clear idea what's going on here. Possibly
there is some DLL conflict. You can try to get a handle on this by using
depends.exe from here:
First try just loading csound.exe into depends. Then try running your
file using the "profile" menu.
I have seen DLL conflicts with Reaper, which uses different builds of
some of the same DLLs that Csound uses.
Another, perhaps easier way of getting a handle on this is to
temporarily change your Windows PATH environment variable to include only
the Csound bin directory. If the problem goes away in that case, it means
that either Csound, or one of Csound's DLLs, tried to load a DLL that
conflicted with one that was already loaded, or that was built wrong for
Csound.
Another idea is to look and see if some other program has installed
its own portaudio DLL or libsndfile DLL which conflicts. Some of the mingw
or gtk DLLs (in the Csound bin directory) may also conflict.
Hope this helps,
Mike
|