You'd better extract the gzipped archive (which is slightly different than a zipped archive by the way) to your hard disk. Your usb drive is likely FAT based, not UFS so the permissions might be wrong.

Ok I redownloaded the original tar.gz file from the link you gave me. I took it from my usb drive and copied it straight to the / working directory on my unix system. Now I tried to run gunzip and I'm obviously doing something wrong in getting it unzipped correctly....I did it as:

gunzip -cd /rf-2.6.2.tar.gz | tar xf-

It gave me an error of wrong syntax. Then I tried it as:

gunzip -cd rf-2.6.2.tar.gz | tar xf-

Still an error Then I did it as:

gunzip -cd /rf-2.6.2.tar.gz | tar xf -

That time it returned with wrong syntax form or something to that effect. I was following it directly from the readme file the other day. From what I can tell I have it correct but the xf- is acting like I should have a filename after the "-" I know I'm almost a hopeless case but the first way of typing the gunzip should have worked. Instead I'm getting the message tarblocks=0 I guess I'm not understanding correctly... Once again if possible I'd love to have some help on this again....Sorry to be such a bother. I never knew learning this stuff again would be so hard to accomplish.... thanks again

Ok I finally got the gunzip command to run correctly now I moved down and followed all steps...down at the spot of the testing in the readme file which I posted earlier I ran the /usr/ccs/bin/make install..it went fine it gave me the message new owner root....i386/rf installed as /kernel/drv/rf then I realized I screwed up im on amd64 so I started over with therm Makefile then ln _s Makefile.amd64_gcc Makefile....it all went again but now when I do the command /usr/ccs/bin/make install it shows i386 driver installed same as above but it also says /usr/sbin/install -f /kernel/drv?amd64 -m 755 -u root -g sus amd64/rf new owner is root....amdgd/rf installed as /kernel/drv/amd64/rf....now it looks good...til I try ./adddrv.sg after that it says nothing to do....so I tried modload obj/rf but since iys reallly /amd64/rf should I have done that instead? Then I tried devfsadm -i rf and it said drver failed to attach...so then I tried devsadm -i amd64/rf same deal failed to attach....im at a loss agaon...when I do ifconfig -a it still only shpws the lo0 interface.....im lost again....

Ok another update....i reinstalled solaris 10 and then tried the whole thing over again...it all worked correctly...somewhat....the driver add with ./adddrv.sh but when I try to attach it with devfsadm -i rf it still gives me the errot drver failed to attach rf....so maybe this driver is not the one for my card after all....any ideas as to why everything else loads and works properly except the devfsadm command?? I even tried using drvconfig and same issue...driver fails to attach......so still needing help if anyone has some ideas....

What says ?

It says:
ixgbe "pciex8086,10ec"
rge "pci10ec, 8169"
rge "pci10ec, 8110"
rtls "pci10ec, 8139"
rf "pci10ec, 8129"
rf "pci10ec, 8138"
Thats all it says and I have no clue what it all means....

Okay, your card isn't listed in the ones supported by the rf driver. You can add it using that command:

Please be careful with the double/single quotes syntax

Ok so with that command ----- update_drv -a -i "'pci10ec,8138'" rf ----- I run it from the terminal prompt and then should I completely redo the /usr/ccs/bin/make install and then the devfsadm -i rf ??? or should I just run the devfsadm -i rf command ? since I'm a newbie I have trouble knowing what to do right after this... could you help me understand what to do next?

After this command is run, either the driver is happy with your hardware andwill show up your rf0 interface or it isn't and the result is undefined, something between an error message at boot to a kernel panic.

ok I'm now guessing that its either not the right driver for the card I have or that card will not work on solaris 10 because I ran the update_dev command and it gave me a message....driver failed to attach
Warning: driver (rf) successfully added to system but failed to attach......
I checked with ifconfig and same issue as before lo0 is the only thing showing so its one of the two options mentioned above I believe.... I found another driver online that I downloaded but it is a bz2 zipped file and my computer does not support bz2 yet so I'm looking for a bz2 zip program to update my system so I can unzip it and maybe see if a different driver makes a difference...Thanks for all the help and if I get the bz2 program I may be coming back on here and asking more questions....I really appreciate all the info I have received! Thanks again!