I've been trying to install wine-20041201 in Debian-like Knoppix 3.6, Kernel 2.6.7 for a while now but my pre-existing wine version (2004516) didn't change at all. Naturally, I've tried winehq site and google for any potential help but in vain. Successfully installed latest Winetools anyway, but I needed to update my wine. I then removed my previous wine and tried to install 20041201. Option 1: ./configure, make depend, make, and make install led to [msvcrt.dll.so] error 2 the first time, and to [winetest/__install__] error 2, the second time. When I used ./tools/wineinstall [Option 2], the installation went all the way with no errors, but later when I typed wine --version, I kept getting the following: "wine: failed to initialize: /usr/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory". And wine doesn't even start! Tried cvs update all the way to compilation and installation, an! d still the same error message. I do have 20041019.tar.gz in store but I haven't tried it yet. Any help will be very appreciated. Thanks in advance. Adam --------------------------------- Post your free ad now! Yahoo! Canada Personals -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20041226/c1b6b4f3/attachment.html
Since I have resolved my own problem, I have decided to share my results just in case someone is having the same installation problem in Debian. Also, and this is for David Gümbel who tried to help me fix some pre-compiled file path for a program I have designed in Windows that didn't work with wine-20040615: thanks David for your help, my Windows program and its sound file work fine now with wine-20041201. The error messages mentioned in my email seem to result from a CONFUSION in the FILE PATH ASSIGNEMENT or LOCATION during wine installation. I frankly don't have any good explanation for it because my Linux and wine installations were done according to readme files. No interference at all. I have simply logged in as a root, reconstructed the full path used by wine-20040615 in a second computer, and then copied all the files to the right directory for wine-20041201. That's it. No more error messages including the one mentioned in my email on WINE and Pre-Compiled Path. The lesson here is to make sure that the files are installed in the right directories. Unfortunately, the file path or location is not always provided in the readme file. In my situation, even after following the installation instructions, wine installed itself in some other places, and I had to play Hide-and-Seek for several hours in order to reconstruct the right path. Anyway, wine is wine, and I love it. Adam ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca