> "Due to a bug in winegcc, and the confusion regarding where 32bit wine dlls go > on the various 64bit linux distributions, I've hardcoded support for > /usr/lib/wine and /usr/lib32/wine into the makefile" > i dont know if is writted for 32 or 64 but it dont care to me > i know u are very smart but i am just asking if someone what know more than me can help me if u dont want, ok dont do it[/quote][/code] I have no problem helping you, but in order to do that - you need to listen, instead of asserting things that are *clearly* incorrect and then ignoring what i've written. Let me explain the /lib vs. /lib32 thing. it's actually pretty simple; 1. x86 (32bit) does not contain /usr/lib32 - it only exists on 64bit. So by default on a 32bit system you will have /usr/lib (and that is it). 2. x86_64 RPM distros have /usr/lib32 and /usr/lib64 ~ which was a standard put out by Redhat. However - Debian, Archlinux and many other distros use /usr/lib for 64bit libraries on a 64bit system (ie: there is no /usr/lib64, in most cases), while adopting /usr/lib32 for their respective 32bit libraries. So don't install the .dll.so into /usr/lib - that is for 64bit libraries on a debian-based system (which ubuntu is). Is this clear and concise of an explanation for you? (it also might cause confusion when trying to register the .dll later). What you want to do is; (1)make sure you have all of the dependencies you need, all the mutilib/lib32 dependencies required. most if not all should be installed, as wine pulls them in excluding jack. I think you can verify your installed jack is supporting both 32/64bit by looking in /usr/lib32 <- there should be jack-related files in there. if they exist, you can check that off of your list. (2) make sure that your home/username/.wine is 32bit, so that it links to your 32bit libs. - which i've already told you how to do (3) after that wineasio.dll.so is installed in the correct location, and not in /usr/lib - you can then register the .dll. ~if it still doesn't register, type the fullpath when registering it. (ie: regsvr32 /usr/lib32/wineasio.dll.so). it should pick it up. after that to test it -> run jackd, start your windows app that supports ASIO, find the preferences and switch the driver to ASIO. After that you should see (jack) ports appear in qjackctl, Ladish or whatever tool you are using to handle connections... VSThost for windows is a good choice (because it is small and i know that it works). you may want to run your wine application from a terminal, then you can see (possibly) why it is failing (if it still isn't working. if it doesn't work, your next step to take that ouput && also run; env WINEDEBUG=+asio wine *your-app* from a terminal ... this tells wine to spit out all of the debugging info for ASIO(wineASIO). -> this might help someone else identify your issue, on the wine-list or elsewhere. you can save it from your terminal into a text file, and post it somewhere like pastebin (.com) - then post on the wine-list with a link to your pasted debugging info. cheerz
