installing wine and limwire

[Dolda2000]

I really don't know that much about Wine (since I don't use Windows programs), but I think you will have to add the modules that the PE loader must link to your wine config. The wine config can be located in several places. The ones I've seen include ~/.wine/config and /etc/wine/wine.conf.

[pmeg568c]

i still dont get it

can someone like explain it in like deep detail from like the time i enter the xterm

because the xwindows packages system doesnt work

sorry im stupid

[groot7000]

I don't have time to write a whole tutorial, so I'll just start with the really basic stuff. If I have time, and someone else hasn't posted how to install limewire, I might post it tomorrow.

First of all, the command prompt. The command prompt could be said to work in four levels.

User <-> Terminal <-> Shell <-> System

User: The highest level is you, the user. By this I mean actually you sitting at the keyboard, not a user account or anything. The purpose of the other levels is simply to give you some way to control the system.

Terminal: A terminal is simply a program that allows you to interact with the computer. All the terminal does is accept input from the keyboard, and print text back out to the screen. It may support other features, it may be a program running in X11, or any other number of things. The bottom line is that it allows you to enter text, and allows you to see text. The terminal itself generally does not actually DO anything with the text, but instead acts as an intermediary between you and the shell.

Shell: The shell is the interface program. It has the ability to take commands you input, parse them, and perform actions from them. It does NOT provide any support for the keyboard and mouse, but instead requires the terminal to provide this data for it. Any messages that they shell is going to display are also sent to the terminal program for it to display.

System: There is no practical way for the user to do anything directly with the system layer. The shell provides an interface to basic system functions, like the execution of programs.

Therefore, the only connection the shell and the terminal have is the passing of user input and output data. This way, pretty much any shell can be used with any terminal.

So, in short, using a different terminal will have no effect of how the underlying shell operates. Using a different shell, however, will.

It doesn't matter which type of terminal you use, though, whether it is an X-term, a console, an SSH session, a dumb terminal on a serial port, or anything else, that is why the shell is seperate from the terminal.

[pmeg568c]

ok i extracted the wine file into a directory /usr/include/wine

but now what do i do?

that ./configure thing and make install dont do anything when i cd to that dir in the terminal

[Mike/Pippin]

Hey when I ./configuration or w/e

I get

oot@cableone:/home/mike/Wine/usr/doc/Wine-20050310# ./configure
bash: ./configure: No such file or directory
root@cableone:/home/mike/Wine/usr/doc/Wine-20050310#

Help?

Ps. Im running Slackware 10.1

[dylunio]

You should read the README and INSTALL files in the WINE directory, you might not need ./configure but might go straight to make or it may be a binary?

dylunio

[privatesniper]

i pressume by the fact that you are compiling source that your distro doesn't support rpm and the likes??

[azazelka]

I use Limwire more than 3 yaers and can say that Limewire best p2p client of the world. You can easy download Limwire here : http://www.softdownloadz.com/free/download/limewire/
learn more about Limewire: http://www.limewireworld.info/