Linux - GamesThis forum is for all discussion relating to gaming in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I tried this on Debain 32 which worked fine with no problems. I ran the shell script I downloaded from Id's FTP and it created the doom 3 directory in /usr/local/games/doom3.
Then I just copied all files from the win32 disks.
Now I have since upgraded to Debian 64 and can't even run the shell script from Id.
Code:
gamebox:/home/carlos/Desktop# sh doom3-linux-1.3.1302.x86.run
Verifying archive integrity... All good.
Uncompressing DOOM III............................................................................................
./setup.sh: line 192: /root/.setup11334: No such file or directory
./setup.sh: line 192: /root/.setup11334: No such file or directory
Bump for any help? This only happens on my Debian 64 system but when I reformat this and use Debian32, it works but sounds like crap. Any help is greatly welcome.
I know this thread is pretty old but did you fix this? Because I'm having the same problem. I can extract the thing but the setup won't run. I can't believe they can't even get the installer right. Talk about incompetence.
All the thing has to do is copy some files. I'm sorry, but this is really stupid. I was about to debug the script when I realized it was so much easier to reboot and play it from Windows. It was done in 5 minutes.
I'm glad it worked for you. That doesn't help me though. Neither does your stupid uninformative reply.
I realized it was so much easier to reboot and play it from Windows.
Glad you found a solution. It was probably just a permissions issue or something simple as the installer does in fact work, for me and probably a thousand or so other people who run Doom 3 in linux but since you didn't provide any information in your post, I thought I'd just follow suit. Was it as fun for you as it was for me? Judging by your reply I'm guessing not but by gosh I enjoyed it
I ran it as root just to make sure btw. And it was looking for something in ~/.setup<randomnumber> . So it was looking for something that it should have created but didn't. That's all I can make of it. That's also all the information that would be useful to somebody who could help me. I hate it when people ask for more information and when they get it they fail to be of any use.
I didn't find a solution. My problem is that the binary installer won't work. It still doesn't.
I don't know why I'm still replying since the only person replying has no idea how to fix my problem. And apparently he thinks this is funny somehow.
I hate it when people ask for more information and when they get it they fail to be of any use.
You only just provided any info so who has failed to be of any use? The guy who almost posted but didn't? You need to sort your attitude out big time, you sound like an idiot putting endless amounts of shit on people who actually port their software to linux and then people posting on the forum you're getting all your support from (for free in case you forgot).
According to Google, this problem comes up when you don't have enough free space on the partition it's extracting to. Dunno if you've checked this or not but since you didn't say I'll assume you haven't so try using the --target option to extract it to somewhere else.
Alright, you win whatever this is. I can't be a space problem, no drive had less then 5 gig available. Google didn't help me at all on this one. Seems to be pretty rare.
Last edited by Haiyadragon; 06-03-2006 at 09:54 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.