Im stuck on insalling stuff
Where do i put $ cd ~ ?????

More information will be helpful. What exactly are you trying to do and where did you get stuck.

Im trying to install some drivers for my EDIMAX EW-7128g PCI card but as im a i dont know how to install things on linux
i Have downloaded the drievrs but i dont know where to start could someone please help me i read another post on this forum that u had to put $ CD or sommet like that but where do u put $ CD ????/

First off, check this:

http://www.linuxquestions.org/hcl/sh...p?product=2361

Second:

Is the driver you've downloaded for Linux? I did a quick check on their site and don't see one for Linux.

There the drivers i got but i carnt installe em

Edimax dont make any drivers for linux but i think these ones work http://www.linuxquestions.org/hcl/showproduct.php?product=2361

according to your link, this card only work using ndiswrapper. Ndiswrapper is an appsthat allow you to load a windoze driver under linux.

Btw, there is no easy "next-next-finish" way to install something in Linux, if you want help about how to install the drivers, it would be somewhat a good idea to tell us some details about the "drivers" you downloaded ( name, extension, where did you found it at very least...)

I tried to put where i got it from but i dident have 5 post so i couldent post links

I Have got the these drivers http://www.linuxquestions.org/hcl/sh...p?product=2361
Drivers main page http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page
And download frome ere http://rt2x00.serialmonkey.com/wiki/index.php/Downloads i downloaded the Latest BETA rt2500 driver: v1.1.0-b2 (http://prdownloads.sourceforge.net/r...ar.gz?download)

This is a command that should be typed into a terminal. You can get to the terminal by clicking on the Fedora icon (often in the bottom left corner), and selecting System Tools, then Terminal. (The exact location varies between different distributions of linux so you might have to look around those menus to find it). Once you have opened a terminal you will see a prompt (on my machine it is looks like this 'dan@ringmaster:~$', which means the current user is 'dan', the machine is called 'ringmaster', and the current directory is '~' (my home directory). The $ at the end indicates im a normal user, a # would mean I was the super user)

In the command you mention the at the start $ isnt meant to be typed, it is merely there to show you should be a normal user at this point, so you should type . At some point in the instructions it will mention the 'su' command and the $ that is normally shown in the instructions will change to a #, this indicates that the command should be run as the super user (the 'su' command will have changed the current user)

ok, so the drivers you downloaded is a "source" (mean you have the open source code in your hand weee!). I don't know much about this drivers but I'll gave you basic information.

First, you need to make sure you have gcc on your linux. Open a terminal (the text mode thingy) and type :
su - (will prompt you a password, you are root, so be careful)
gcc -v if you get lot of text and version number, you are fine... if not, you will need to install GCC... if it's the case, tell us, we will guide you.

Assuming you have GCC, now you need to compile the drivers, the usual way to compile is the following :
(assuming you have the tar.gz package in the same directory as you are. If bot use "cd" to change directory, like : cd /home/bob will get you into /home/bob)
OF COURSE these command will need some editing for the name of directoey and such.

tar -xjf the_driver_thingy.tar.bz2 ( this decompress the driver)
cd the_driver_dir_created

NOW you might want to take a look in this directory. There is probably a file named "README" or "INSTALL" you want to read, (or is there documentation online?), start your favorite text editor and READ IT, there is probably some step you need to follow to install the driver.
The USUAL way from now is to type :
./configure
make
make install
BUT dont expect this to be that simple on a beta driver. READ the README file or the docu, I'm pretty sure it just wont be that easy. If there is something in docu/readme you dont understand, ask us (but try something and use your head first :P )