i have the same exact stupid message and error, and no damn config file!!! and i cant open wc3, it says its windows 95, im also using the binary version RPM... sigh wine u suck balls

i re installed the wine using the source but it gives this error when i do
#wine notepad
wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory

# wineprefixcreate
wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory

# winecfg
/usr/local/bin/wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory

whats do i need to do .

i did
#tar zxvf Wine-20040615.tar.gz
went to the created directory
#./configure && make depend && make && su -c "make install"

when i login to any user and do
wineprefixcreate
/usr/local/bin/wineprefixcreate: line 155: 7211 Segmentation fault ${WINEL OADER:-wine} rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 win e.inf


please help me out

I posted this in the Software section, this is a detailed explanation of my problem

Wine is so stupid! I don't care, at this moment, I'll even download a warez version of WineX, as long as I can run the game i payed for...

guessme:
You do need to install wine-devel package.The wine-devel package is the source code if you have wine installed using rpms and you want other programs to use the libraries of wine. If you get segmentation faults, you have to recompile. Before you compile delete files that has an extension of o. Using normal rm will not work, so you have to do combination of commands like rm and find. To do this type:

find wine-20040615 -name '*.o' -exec rm -vf {} \;

Reboot to get a clean compile. Make you run "ldconfig -a" but wine should have ran ldconfig during the processs of make install.

davidfes:
Wine is still in its development stages, so not all windows programs will work on the first try. You have to edit a few lines here and there to get windows programs working. I suggest running a simple program like notepad to make sure wine is installed correctly. Then you can try to hack at it until Warcraft 3 is working. To force wine to imitate a Windows or DOS version add or edit a few lines in ~/.wine/config like:

I would just stick with win98 for stability and reliablity issues. For DOS, 6.22 should not give you any problems if you are going to run DOS programs like old versions of DOOM.

You have to be patient and search the internet for some hints when using Wine.

please can u give me the exact steps and files u installed and steps u did to install wine as i am going to re -install fedora core 2 and want wine to work this time. i have already re-installed fedora many times.

thanks for your help Electro

guessme

yes, me too, i have tryied notepade and it works fine, wc opens too but blizzard warcraft3 doesnt run on windwos 95, and for some reason my wine is windows 95..., and since i cannot get to the config file, im kinda SCRWED!

guessme:
Re-installing Linux does not help. You just have to do more work. I recommend forcing yourself not to re-install and stick to fixing it if need to. When I want to compile programs, I choose a program to test my system setup if it can compile. I usually pick mplayer or tvtime. Usually these programs that needs a particular library other programs may also need that particular library. After I got mplayer compile correctly and skipping the make install step, I know that compiling other programs will work too. I use kpackage to help me install rpm files that have problems with dependencies or programs that I want to keep.

Sorry, I do not know what library that Wine needs.

All I did to compile wine:

change to wine directory
./configure
make depend
make
make install

As a normal user and ran wine notepad. It give me a problem about my video card permissions because wine has compiled opengl with it. I logout and logged back in again.

davidfes:
Did you copy and paste the example config file in this thread into "~/.wine/config". The directory .wine is a hidden directory. I already helped you.

I don't remember where I saw it, but it seems that there was a problem with the Mandrake RPM's about putting libwine.so.1 in the wrong directory. I don't know if that has been fixed yet. You could "google" that exact error message to try to find this. It would then be a simple matter of moving the file to the "right" directory.

As far as the original error of "L c:\\windows......not available. It seems there was a problem with the way that wine "decided" what was a windows device and what was a logical volume. If wine chose the exact mount point for a device, you would get this error. That has been fixed in the latest snapshot 20040716.

I would recommend compiling wine and not using rpm's. If you're having trouble with the config file, first untar wine in your home directory then This will configure, make and install wine PLUS configure it AND assign drives and so forth. Once you have the basics then the rest of the configuration, if you need any, becomes easier.

GURU--I have some questions about system.reg and IE6, but I don't have time to post them now. From the directory structure you published, it looks like you have a successful install. I don't necessarily want to run IE6, just have it for those windows programs that depend on it.

P.S. For the initial test of the wine installation, I use "winemine." I tried the sol.exe stuff like it says in the README, but found out that sol.exe is not supplied with wine.

my problem with wine is that
>>>>>>>>>>>>>>>>
err:module:load_builtin_dll failed to load .so lib for builtin L"x11drv.dll": libXv.so.1: cannot open shared object file: No such file or directory
Could not load graphics driver 'x11drv'
err:module:LdrInitializeThunk Main exe initialization for L"c:\\windows\\system\\winecfg.exe" failed, status c0000142
[notam@radio bin]$ whereis wine
wine: /usr/bin/wine /etc/wine /usr/lib/wine /usr/share/wine /usr/share/man/man1/wine.1.gz
<<<<<<<<<<<<<<<<<<<<<<<

I am very much new to these. pls. help me.

mchitrakar, the error saids you do not have X11 driver library installed. You can try to use locate if you have updated it or the more LINUX way using find. To use find to search for x11drv, type "find / -iname '*x11drv*' 2>/dev/null".

You do not have to include 2>/dev/null if you are running find as su or root. The 2>/dev/null saids hey if you receive any error messages or permission denied messages just redirect them to /dev/null (aka the blackhole).

I suggest removing WINE rpm file and compile WINE from source code. You do need a lot of devel packages like gcc, kernel, XFree86, gtk.

Do you mean me or someone else. If you mean me, WINE comes with regedit that you can edit just like in Windows. There are files that you need that the IE package comes with.

I have not yet installed IE in WINE. I'm too lazy although I have VMware. VMware works 100% of the time, but when it comes to 3D or sound it is pretty sloppy. Wine is good for OpenGL applications, but you have to install your video card first and make sure it is doing hardware 3D rendering.

If something or I have compiled a desktop manager and it goes in the wrong place, sometimes I just make an symbolic link. Some program do not mind and other programs do. Symbolic links are nice work arounds.

I'm sorry, electro, I did mean you and I wasn't paying attention. Thanks for responding anyway.

I think that my questions about the registry have been overtaken by events. I know about regedit.exe, but I don't understand the registry or its entries and dinking around in it scares the ever livin' dog doo outta me. I'm fooling around with wine because three of my favorite applications aren't supported in Linux and I don't think they ever will be. However, I think I'm caught between upupgraded wine dll's and older HOWTO's right now.

I have not yet gotten IE6 to run--although my system now neither freezes nor crashes . I learned about wineboot the other day. I haven't found anything to back this statement, but I think it's a "reboot" simulator that updates the registry. I also think that it's not called automatically when you install something in wine so that everytime an application is installed the user should run wineboot.

This is just going to take more time and testing. Sometimes it's frustrating.

Thanks again for the response.

Thnx guys for suggestions.
I use "find \ .........." to search x11drv. but the system couldnt find it.
What furhter steps shlould I take?
thnsx

I do not know what results to expect from <find /iname...>. I use the find command differently. Soooo, assuming that the x11drv???.so is not on your system OR your ~/.wine/config isn't quite ready, I have the following suggestions.

1. IF YOU INSTALLED A WINE PACKAGE: use the appropriate command, for example and remove wine. Download the latest wine snapshot and untar the file in your home directory.

2. IF YOU INSTALLED WINE FROM SOURCE BUT DID NOT INSTALL IT USING ./tools/wineinstall: AFTER REMOVING WINE USING EITHER 1 OR 2: Install and configure wine using <./tools/wineinstall> from the top of the source tree--usually ~/wine. This will take awhile--20 min to 1/2 hour and there are a series of questions to answer.

Any other way of installing wine leaves a lot of configuration work to do. If you're comfortable doing that, it's fine. Getting started with "wineinstall" gives a good starting point from which you can do a lot of tweaking if you so desire.

If you want to do the configuration yourself, I highly recommend reading the chapter "Configuring Wine" (it talks about problems with configuring the x11drv) in the "Wine User's Guide." You can download it from winehq.org or put it together yourself. The instructions are in the README in the top of the wine source directory.

I think that these are very important documents with which to be familiar. Except for "winmine" (not "winemine"), I have not gotten any application to run in wine "out of the box." I think that it's important to understand what's in the ~/.wine/config file so that once you get an application to run, you can make the appropriate additions to the config file and not have to "recreate the wheel" everytime you want to run that application. The man pages are also quite important.

Basic answer to the problems people have been having here: always install Wine from the source NOT rpms nor debs nor ebuilds. People break Wine in all kinds of ways when they package them. Virtually none of the errors given here are Wines fault, they are almost all the result of bad packaging.

Congrats guys!!! And BIG THANK YOU. I did installed wine
from source and it worked. I am now happily fiddling around with
applications written for windows without touching that darned windows!!
THANK YOU ONCE AGAIN.
In fact, all the fuss for wine was because I wanted to play a game
( Nemesis Evil 2 in Linux). I had a windows version (and i dont want to buy
another-linux ver). But unfortunaltely, the game didnt worked in linux
because it reqd. DirectX6. so, i tried to install DIRECTX6, but no no avail.
produced error: "Unimplemented function atl.dll dllserviceregister called at
addres 0x70b460e6. Do u want to debug?" Wish i could debug.
Do you guys have any idea? thnxs.