How do Iinstall Quake 3 linux demo?
 

Hello,

I have downloaded the Quake 3 Linux demo, but I don't know how to install it. I am using Ubuntu 7.4 feisty.

The file is called:
linuxq3ademo-1[1].11-6.x86.gz.sh

It's in my home folder. I use sudo for root access.

try this in the same folder as the above file, and let us know if it works
It may want you to be root to run, in which case run 'su' (give the root password) or 'sudo' (and give YOUR password) before running the above command

That looks like a shell script. The first thing I would do is look for a readme or instructions where you downloaded the file. To execute shell scripts you can use these.Again, look for some instructions first, there may be more to this package than just running the script.
Good luck. ;-)

I am sorry for the late response but the pc apears to be more or less dead right now (from a hardware point of view). When it is repaired I will got back to you on this.

Does it power up? Any other symptoms or error messages?
Good luck. ;-)

also you dont want a demo theres free full clones of it try OpenArena

We changed a lot of hardware. We slammed in a ATI 9600XT card to see what performance we could get with the new amazing 8.41 ATI drivers instead of the GeForce 4000 MX (GeForce 2 but hello marketing dep.). Changed to a 40GB Western Digital hdd. Putt in a Creative SB 5.1 Live!

We found out the SounbBlaster was dead. We removed it from the box and it booted the BIOS. Anything beyond the bios was pretty impossible so I changed the BIOS to safe defaults and we got... nothing. Probably nothing on the hdd? Wierd... So we slammed in the Ubuntu disk and it froze at the new ini screen.

Okay, maybe the latest Fedora then? "Block error" times infinity. So we removed the hdd and still it gives us block errors. "sr0" seems to refuse to work. What is sr?

Did you go through the bios detect to ensure the new drive had been recognized?

Device srX is your cd/dvd-rom. The block error could be caused by the bios not recognizing the drives properly. It could also be a bad disk.

With all of that new hardware, I'd suggest going through the bios very carefully and ensuring all settings are correct, and all drives, devices are recognized.
Good luck. ;-)

Not yet. It is all safe defaults. But at the post screen the BIOS does detect the names and under which configuration (primary, master, etc.) they reside.

I don't recal the disk brand but it had scored awesome tests in a few pc mags. Fedora could be a bad download but we had burned the Ubuntu disc with the same cd-writer before we changed hardware and it did just fine back then...

We had a lot of trouble with IDE cabel configuration. The cabels are like bended a thousand times and one of them is a very old cable that doesn't have as much wires as newer ones. For that reason we plugged the hdd to the cabel with more wires as primary master and the cd-drive to the cabel with fewer wires under secondary master (jumpers are set correctly to master).

Unfortunately the box is at a friend of mine and he has plans for the weekend so I have to wait at least for monday to work on the pc.

I'll keep you informed if we make any progress :)

Old shoddy cables can cause the same types of problems, however, if everything is getting recognized in bios that suggests the cables are fine.

Whenever I make hardware changes, especially to the extent that you have, I (usually) go through all the components on the mobo and double check that everything is seated correctly and securely even things I haven't touched. I also walk through all of my bios settings to check that everything is good there.
Thanks, Talk with you then.
Good luck. ;-)

Still nothing....
 

I plugged in a new IDE cable for the cdrom and I still keep getting sr0 errors :S.

Update: Ubuntu however is now bootable. In Fedora I keep getting something like "Buffer I/O error block: xxxxxxx". The Fedora disk is probably just corrupted. When I select "Check disk integrity for errors" or something like that it boots the Linux kernel and right after that I get the block errors so the disk utility doesn't even have a chance to start.

If the Ubuntu disk is booting ok, then you've probably just got a bad fedora disk or image.
Good luck. ;-)