OK, what I have is an old casino type game called Reel Deal Slots by Phantom EFX, Inc. My wife bought this game about 3 or 4 years ago. It is suppose to be Linux compatible (hey there is the Linux penguin on the box). That's just it, back when she bought it I tried for awhile to load it and gave up. Mainly because back then I was still pretty green with Linux. Now that I feel a little smarter I have been trying to get this thing to work/run/whatever and it is giving me fits. I e-mailed Phantom EFX tech support and they really don't have much of a clue now as they don't have anybody that really knows Linux. At first I couldn't even get the program off the cdrom to a directory I created going by their instructions. So, I changed their path to what I figured must be right and it worked. That is I got it off the cd and into the dir I wanted. Now before I continue I will pause and give you their directions word fer word and I'll comment after.
1. Installation Instructions.
Windows: any caveman or less could do it . :-|)
Linux: Mount the CD-ROM and run the setup.sh script on the CD-ROM. "./setup.sh /usr/local/dirofyourchoice" from the directory the CD is mounted on. The installation script will install to /usr/local/rdslots if you do not choose a directory. The installation requires around 400 MB of disk space on the target partition. If you are not running as root, you may have to run the setup.sh in the install directory to setup the to setup the library symlinks and make the available. Make certain /usr/local/lib is in your libray path, typacally set in the /etc/ld.so.conf , remembering to run ldconfig as root, after editing that file. CD to the bin directory off the install directory and run "./rdslots" to run Reel Deal Slots in windowed mode or "./rdslots -fs" to run the program fullscreen.
Enjoy!
Yeah right. In order to get it into my box I ran " cd /mnt/cdrom " then I did "ls" and noticed that the "setup.sh" is actually "SETUP-LINUX.SH", so then I did "SETUP-LINUX.SH /home/me/rdslots" and it is now in there (by following their directions it would not work; maybe it was written for Redhat or SUSE or ????). But, now that it is in there I cannot run the game. By following their directions (at least I think I understand what they are saying) I get nowhere. AKA: bash, bash bash. I have cd'ed to /rdslots/bin and then typed "./rdslots" and get a "bash: rdslots: No such file or directory ". Also, when I do "ls" when I am in bin I get what must be the "bin" for my OS, because nothing pertains to rdslots. I can't do "./rdslots/bin" as it is bash'ed". When I am in rdslots and do "ls" I have these things in it: (in green writng) ACKNOWLEDGEMENTS.txt* , MANUAL.pdf* , LICENSE.txt* , README.txt* , setup.sh* . (In blue writing) gfx/ , save/ , sounds/ , bin/ , fonts/ , (In write writing) config.ini . I might be wrong also, but when I (in windowed mode, i.e. Konqueror) go to rdslots-bin there are 9 files that end with ".so" and 1 item with the Konq gear and when I put my cursor on it and look at the bottom of the page it says " rdslots (1.6 MB) Excecutable File ". I might be mistaken but I get the feeling that this was almost written for Linux. And if no one has a clue I will be willing to burn a copy of this DA*$ game and have someone else give it a hack.
Oh yeah, I have a socket "A" mobo with an AMD 1.33 GHZ cpu, 512 megs of ram, an nVidia GeForce 4 FX 5200 128 meg vid card, and Mandrake 9.1 PowerPack.
Good luck thinking and merry christmas.
Later. Pepse.
I did run this whole shebang as root.
Pepse
12-26-2004, 04:42 AM
I cannot give you an answer because I cannot get anywhere with the command you gave me, except that I don't think it created a "lib/ directory" I tried your command in root and non-root and I get BASHed every time. "No such file or directory". It is possible that maybe I don't have the right command for this situation or I need a different command.
Later. Pepse.
bwkaz
12-26-2004, 07:26 PM
bash is a shell, not an error condition. ;)
Please post the exact commands you're trying to run, and the exact errors you're getting when you run them.
Pepse
12-27-2004, 05:25 AM
OK, just so you know the rdslots directory is in my "/home/me". In order for me to get to rdslots I have to "cd /home/me/rdslots", because if I just do "cd rdslots" (su or non su)I get BASH'ed. I.E. "no such file or diectory". OK, so once I am in "/home/me/rdslots" I am (according to the instructions) supposed to just type "./rdslots". And I get "bash: ./rdslots: No such file or directory". So, when I tried "cd /home/me/rdslots/bin" it gives me "[root@localhost bin]" and when I type "./rdslots" I get "./rdslots: error while loading shared libraries: libSDL-1.1.so.0: cannot open a shared object file: No such file or directory". Now being in that "bin" directory I did "ls" and here is what is in there: libappconf.so libesd.so libSDL_image.so libSDL.so libstream.so libaudiofile.so libmstrandom.so libSDL_mixer.so libsge.so & (in green writing) rdslots*. So, I am still clueless as to why I can't get anywhere.
Later. Jim.
bwkaz
12-27-2004, 10:15 AM
You probably already have SDL installed -- but it wants SDL version 1.1, not any other version.
It probably has that version right in that directory, although the file has the wrong name (and since you didn't say it was in "green writing", I'm assuming it also wasn't executable, which is another problem).
So, first chmod 755 /home/you/rdslots/bin/lib*.so to make all the libraries executable. Then cd /home/you/rdslots/bin and ln -s libSDL.so libSDL-1.1.so.0 to create the symlink that it seems to want.
Then try running it again. If it still says it can't find libSDL-1.1.so.0, then (from the same directory) do an export LD_LIBRARY_PATH=$(pwd) to add the current directory to the list of directories searched by the runtime linker. Then try running it again. If you have to do that at all, then you'll have to do it every time you start the program -- but it can be automated with a script if necessary.
Pepse
12-28-2004, 04:01 AM
bwkaz, I did everything you mentioned and still get the same error: ./rdslots: error while loading shared libraries: libSDL_image-1.0.so: cannot open shared object file: No such file or directory . But, the commands you gave me worked to a point, the point is the game still doesn't run. I went to windowed mode and looked in the rdslots directory and there is an addition of another Konqueror gear and under it it has "libSDL-1.1.so.0 . When I put the mouse over it it shows (at the bottom): libSDL-1.1.so.0->libSDL.so Shared Library (Link) . And when in Konsole in "rdslots/bin" I did "ls" I have: libappconf.so* libaudiofile.so* libesd.so* libmstrandom.so* libSDL_image.so* libSDL_mixer.so* libSDL.so* libsge.so* libstream.so* and rdslots* (those 10 items are all in green), and libSDL-1.1.so.0 is in blue. So I figure the commands you gave me turned most everything green, which is apparently good and the additional item is in blue which I think is good. I did everything in root.
Later. Pepse.
bwkaz
12-28-2004, 10:33 AM
Originally posted by Pepse
./rdslots: error while loading shared libraries: libSDL_image-1.0.so: cannot open shared object file: No such file or directory. That's actually a new error. Notice how the library's name is now different (it was libSDL-1.1.so.0, now it's libSDL_image-1.0.so). :p
What you need to do now is create a symlink to libSDL_image.so named libSDL_image-1.0.so:
cd /home/you/rdslots/bin
ln -s libSDL_image.so libSDL_image-1.0.so
Then try it again. If you get another error regarding libSDL_mixer, then create a symlink for that file also:
ln -s libSDL_mixer.so <filename in the error message>
Then try it one last time.
Actually, you could automate some of this by doing an:
ldd ./rdslots
to see which libraries it's looking for. Any ones that say "not found" that have versions in their names are going to need symlinks created for them, pointing at the non-versioned names in the /home/you/rdslots/bin directory.
Pepse
12-28-2004, 03:45 PM
Just a quick note before I leave for work. Did the "ldd ./rdslots" and 7 of 10 items have the "not found". I will be working on them tonite when I get home from work and will post thereafter.
Later. Pepse.
Pepse
12-29-2004, 03:41 AM
Well, I created symlinks for everything that needed a link and I still don't have a working game. After creating the symlinks and doing "./rdslots" I got the usual? error: ./rdslots: error while loading shared libraries: libSDL-1.1.so.0: cannot open shared object file: No such file or directory . Then I went to the rdslots/bin directory in windowed mode and libSDL-1.1.so.0 is a shared libray link. So, I went back to Konsole and did "ldd ./rdslots" and here is what is in there:
I'm still taking suggestions if you are willing to continue.:D
Later. Pepse.
bwkaz
12-29-2004, 10:19 AM
OK, now you just have to set LD_LIBRARY_PATH to the rdslots/bin directory:
cd /home/you/rdslots/bin
export LD_LIBRARY_PATH=$(pwd)
and try the ldd again. If the symlinks are there, the libraries should all show up as found.
Pepse
12-30-2004, 01:13 AM
OK, I am gaining ground. I now only have 2 items not found when I did ldd ./rdslots : libSDL_image-1.0.so.0 => not found & libSDL_mixer-1.0.so.0 => not found . Although I am not sure why since I linked these once already. Any ideas??
Later. Pepse.
bwkaz
12-30-2004, 10:36 AM
What does ls in that directory say?
(Are you sure you got the .0 on the end of those filenames? I'll miss that sometimes.)
Pepse
12-31-2004, 03:18 AM
OK, by doing ls here is what I have: (in green) libSDL_image.so* (in blue) libSDL_image-1.0.so@ and (in green) libSDL_mixer.so* (in blue) libSDL_mixer-1.0.so@ . So, as far as I can see I didn't confuse my 0 with a o. Funny thing though when I did ldd ./rdslots a couple minutes ago I had the reply that 7 of 10 items were not found; like before. But, then I did export LD_LIBRARY_PATH=$(pwd) and only the 2 I mentioned earlier are not found. I did shut down my computer after doing these things Wednesday nite. So, maybe somethings afoot with this game.
Later. Pepse.
bwkaz
12-31-2004, 11:14 AM
Originally posted by Pepse
libSDL_image-1.0.so@ That should be libSDL_image-1.0.so.0 -- you're missing the .0 at the end. Same with libSDL_mixer. ;)
To fix it:
cd /home/you/rdslots/bin
mv libSDL_image-1.0.so libSDL_image-1.0.so.0
mv libSDL_mixer-1.0.so libSDL_mixer-1.0.so.0
Funny thing though when I did ldd ./rdslots a couple minutes ago I had the reply that 7 of 10 items were not found; like before. But, then I did export LD_LIBRARY_PATH=$(pwd) and only the 2 I mentioned earlier are not found. I did shut down my computer after doing these things Wednesday nite. LD_LIBRARY_PATH is a per-shell variable. It only gets set in the current shell when you do the above export. It does not get preserved across a shell restart, let alone a system restart.
The export is only a temporary thing, just to get the game working. When it works once, we can put a script together that sets LD_LIBRARY_PATH and runs the game, so you don't have to keep doing it manually.
(Incidentally, this is the way that from-source Mozilla, Firefox and friends work -- they have a wrapper script that sets LD_LIBRARY_PATH and a few other shell variables, then runs the binary. The reason is the same -- by default, Mozilla/Firefox/etc. put dependent libraries in the same directory as their executable, so to get the system to find them, they need LD_LIBRARY_PATH set.)
Pepse
12-31-2004, 11:25 PM
:D All right that did it. I at least got in the front door of the game; I left it to reply to let you know that it works. I wish I would've seen my error when I was doing things a couple days ago and we could've saved some time. I'll just blame that on old age.:D Anyway, now what? It would seem things are heading to your comment from your last post pertaining to having the library keep the info permanently.
Later. Pepse.
bwkaz
01-01-2005, 10:38 AM
OK, now to create a script. :D Something like this should work -- put it in /usr/local/bin or /usr/bin and make it executable:
#!/bin/sh
cd /home/you/rdslots/bin
export LD_LIBRARY_PATH=/home/you/rdslots/bin
exec ./rdslots "$@" (this will even allow you to pass arguments to the rdslots program, if needed). Then, just run the script to run the game.
Pepse
01-02-2005, 12:31 AM
:( No luck. I tried to set it in "/usr/local/bin" and then "/usr/bin" and it came back with " : No such file or directory ". I know I got your commands right. And when I did "ls" in /usr/local/bin and the only thing in there is lbreakout2* and lbreakout2server*; which might be from when I got the latest upgrade for lbreakout2 (which I play a bit:D ). And when I did "ls" in /usr/bin, well I guess just about everything possible is in there pertaining to Linux.
So, I am not sure why it isn't working. But just to be sure when I did the commands starting with " ' " and pressed enter my next line had " > " so I put in the next command pressed enter and would get " > " and then put in the next command and would get " > ", and so on and so forth until the last command of " ' " and pressed enter and then the ": No such file or directory" would come up.
Later. Pepse.
bwkaz
01-02-2005, 01:53 PM
Ehh? I didn't have any single quotes in that script...
(And you don't type those commands in anywhere except a text editor -- create a new text file and put that in it, then save it to /usr/local/bin and chmod a+x it.)
So I guess I'm not sure what you're doing there...
Pepse
01-03-2005, 03:09 AM
Unless I wasn't supposed to use it you have a single bar to lead off the commands > ' < (not being a smart arse, just showing you what I used, which is everything you had there), and at the end > ' < . I wasn't aware that I was not supposed to be in a konsole when doing that set of commands. To me "creating a script" is just another way to say "put the commands like this". So, if I understand right I go to Kate, or KEdit, or KWrite? And I do not use those single bars > ' <?
Later. Pepse.
bwkaz
01-03-2005, 07:46 PM
Originally posted by Pepse
To me "creating a script" is just another way to say "put the commands like this". Ah, I think that's the disconnect.
"Creating a script" means opening up an editor and typing the text in. Don't type it into a shell.
Any of KWrite, KEdit, or Kate should work, yes. You could also use gvim or vim or emacs or pico or nano. Or any other text editor. Or heck, if you really wanted to, you could do it with cat -- but don't. ;)
And no, you don't use single quotes (' characters) at the start and end of a script. :)
Pepse
01-04-2005, 01:40 AM
You are gonna wanna shoot me for this but, I really don't know what to do after I type this stuff into any editor. I assume I would cut or copy or paste or save or save as, but that is guessing. I would understand it if I gotta save or save as, but them first 3 things have always been Greek to me ( I never knew how/what to do with those 3 things even when I ran whinedoze). So, if you want to save your bullets and not have to clean up the mess:D :D , what next?
Pepse.
bwkaz
01-04-2005, 07:31 PM
Save as. If you're running the editor as your non-root user, then save it in your home directory (you can call it anything you want, just remember what you call it). If you're running the editor as root, then you can save it in /usr/local/bin (actually you could save it anywhere else too, if you want, but /usr/local/bin is the Right Place to put stuff like this).
Then, become root from a console:
su
<type in your root password at the prompt> If you saved the script into your home directory, then move it to /usr/local/bin:
mv /home/you/whatever-you-called-the-script /usr/local/bin And then, in either case:
chmod a+rx /usr/local/bin/whatever-you-called-the-script Then, anyone will be able to run it.
Once it's there and you've done the chmod, then you can test it -- run whatever-you-called-the-script and see if the game starts.
Pepse
01-04-2005, 11:12 PM
OK, I'm stupid. If I understand you I should go to Kate, or KWrite or KEdit through a console?? Because when I am at my desktop and go KDE-Applications-Editors-Kate and put in the commands I can't save it anywhere. And when in a console I can't cd to any of the editors. So, if you ain't sick of me yet you will have to walk me through this, also. And we will use whatever editor you want and do it in KDE or Gnome or whatever. Remember I am running Madrake 9.1 PP.
Pepse.
bwkaz
01-05-2005, 07:49 PM
I don't know much about Mandrake 9.1 PP, since I've never used it, but if you say you have those editors available, then this should work. Open a terminal (it really doesn't matter which one, so try Konsole from inside KDE). Then:
kedit rdslots-wrap A new kedit window should come up. Type in the script. Then do whatever kedit does for a save (I use vim myself, but vim isn't very easy to explain, so I'll try to muddle through kedit instead ;)). Since you gave kedit a filename when you started it up, it should carry that over. Once you've saved it (double check that by opening another (temporary) Konsole session and checking whether a new rdslots-wrap file was created), exit kedit.
Now, back in the original Konsole session, start at the beginning of my previous post. (You will need to go through all the code sections, including the mv. In this case, whatever-you-called-the-script will be replaced with rdslots-wrap.)
Pepse
01-06-2005, 03:53 AM
Something somewhere got screwed up. I did what you said. I went to a konsole and as SU I did kedit rdslots-wrap. It worked. I verified it as you said to do. I then did the mv commands and the chmod a+rx /usr/local/bin/ commands and that is where it got goofy, because I had to do "chmod a+rx /usr/local/bin/home/me/rdslots/bin". And the whole game went to "/usr/local/bin/bin/rdslots" and I can't do a thing with it. At the moment in konsole I am in /usr/local/bin/bin and when I typed ./rdslots the reply is: ./rdslots: error while loading shared libraries: libSDL-1.1.so.0: Cannot open shared object file: No such file or directory . So, then I did "export LD_LIBRARY_PATH=$(pwd)" and then typed ./rdslots and thew reply is: Fatal signal: Sementation Fault (SDL Parachute Deployed) . If you are still with me and if you think I can redo this in midnite commander (mc) I can follow that OK. All the things you referred to as editors are familiar to me vi, vim, pico, nano, emacs, and so on. mc is the one I started using when I was running Mandrake 8.1, so I can find my way around in it. That is if it ain't too late.
Pepse.
Should I delete the game from my computer and start all over again??
bwkaz
01-06-2005, 07:51 PM
Originally posted by Pepse
I had to do "chmod a+rx /usr/local/bin/home/me/rdslots/bin". Huh? That doesn't make any sense. The game is in /home, not /usr/local/bin/home. Are you sure you got the mv command correct? Do you still have a /home directory? It wouldn't surprise me if you don't...
And the whole game went to "/usr/local/bin/bin/rdslots" Sounds like you may have gotten the mv command wrong.