I recently installed WINE on my Slackware 10.2 box. I'm trying to run "MIDI Orchestrator Plus", a Windows 3.1/95 application. It gives me two errors: 1) in the console err:ntdll:RtlpWaitForCriticalSection section 0x405374a0 "syslevel.c: Win16Mutex" wair timed out in thread 0009, blocked by 000a, retrying (60 sec) and 2) in a popup window: MIDI Orchestrator Plus requires VCTL.DLL version 1.66.

I have installed on a Windows box, so I copied VCTL.DLL into /usr/lib/wine and it still gives me the same error. Any hints?

I have no clue how it's setup right now. It appears it's mostly configured.. ~/.wine exists and appears to contain a registry system and a mock Windows file system. But no config file, which I thought was supposed to exist.

I'm completely new to WINE, so can anybody help me out here? The manpages weren't much help and neither was the website, considering I did move the DLL where I thought it needed to go..

put the dll in one of two places. either a) in the same folder as the .exe or b) in the same location as it was on the windows machine (i.e. if it was in c:\windows\system\ then copy it to /.wine/drive_c/windows/system/ so its exactly where windows would put it)

i tend to put dll's into the applications folder, iirc wine uses the same search paths in windows, and the first place a program looks for its dll's are in its own folder.

oh, and run winecfg and in the libraries pane, add a new override for your dll (just type in the name of the dll, then press add, and it should do it fine)

<warning>
if i make no sense, its cause ive just dragged myself out of bed, i need foccee.... coffee is good.
</warning>

okay, i put the DLL in the same folder as the .exe and it didn't bring up the same popup error. it complained about not having any midi inputs setup, but that's fine considering i havent yet tried.

however, the error in the terminal window remains. it also brings up some more errors when i try to do such things as open files, etc.

yeah, welcome to the world of wine you will usually get some errors shown in the console, i havent seen a single program that doesnt generate some output. i basic rule i tend to follow is that if the program works, then ignore the errors (unless you want to fix them and submit them to wine, lol)

wine is still in beta stage, even though its been out for a while, its a big complex black art of a thing, but when it works, it works great

if your able to do things like open files, etc, successfully, then you should be able to turn a blind eye to the errors. try having a search on the wineHQ wiki, they have the explanations and solutions to a lot of console errors on there.

<warning>
i need more caffeine
</warning>

Well I'll be darned; as soon as I put the file to open in the pseudo Windows filesystem, the program loads it just fine. Probably a good plan, I think.

I'll try to keep in mind the fact that Wine's beta. Thanks for the help.