View Full Version : Anyone having trouble with Zsnes?
kevindubrow
October 20th, 2007, 07:47 PM
Hey, Zsnes wont run in Gusty for me. It opens as a black screen and than closes. It is version 1.5 (I got it from the package manager). I have the full text output, but it is huge, so I'll just put the end. Thanks in advance for any help!
"Aborted (core dumped)
"
I can put more of the output, just tell me and you will have it!
mister_k81
October 20th, 2007, 09:04 PM
Yeah, ZSNES didn't work for me either when I tried to install it from the repositories, I had the exact same problem on Gutsy. The only way I could get it to work, was by going to the ZSNES homepage and get the .tar.bz2 from there and install from source. But it works great for me now.
Website can be found here: http://www.zsnes.com/
acoustibop
October 20th, 2007, 10:10 PM
Does this thread (http://ubuntuforums.org/showthread.php?t=582289) help, kevindubrow? It helps to look for other threads on your problem before posting! ;)
kevindubrow
October 21st, 2007, 12:55 AM
Sorry, I did look for a thread, but found nothing like that. Also, that isnt my exact problem. :) Anyway, I am optimistic that acoustibop's way will fix my problem, but the problem is that I have no clue how to install ZSNES with the .tar.bz2 file. Any help? Thanks a lot for the replies!
disturbedite
October 21st, 2007, 01:12 AM
zsnes (1.51 & previous releases) work fine and always have for me. the one from the gutsy repo actually works better in one way: the audio works as expected.
i compile from svn & apparently with svn if one has an onboard sound card (chip) audio can be scratchy...
mister_k81
October 21st, 2007, 11:11 AM
Hmm... I haven't noticed any problems running it from source, sound and graphics all seem fine to me. Maybe installing it from the repo configured the sound differently for you though, disturbedite.
Sorry, I did look for a thread, but found nothing like that. Also, that isnt my exact problem. Anyway, I am optimistic that acoustibop's way will fix my problem, but the problem is that I have no clue how to install ZSNES with the .tar.bz2 file. Any help? Thanks a lot for the replies!
If you have to install from the .tar.bz2 file, here's some directions:
1. unzip zsnes_1_5.tar.bz2
2. open terminal and change directory to the "src" folder in the "zsnes_1_5" folder by typing:
desktop:~$ cd ~/Desktop/zsnes_1_51/src (or whatever directory your zsnes_1_51 folder is in)
3. run the "configure" file in the "zsnes_1_51/src/" folder. You can do that by typing:
desktop:~/Desktop/zsnes_1_51/src$ ~/Desktop/zsnes_1_51/src/configure (or yet again, to where ever your zsnes file is located)
(note, that it may ask for a certain dependency when running the configure command... it did for me, I forget what the dependency was called, but I easily found it in the repositories.)
4. Next, in terminal type:
desktop:~$ make
5. when that is done, type:
desktop:~$ make install
And that should be it. It doesn't create a shortcut by making it from source, but you can just start Zsnes by opening the terminal and typing: "zsnes" (without the quotes)... or you can just make a launcher and put "zsnes" in the command line. There are also icons in the zsnes src folder that you can use.
I hope that helps. :)
FranMichaels
October 21st, 2007, 12:50 PM
Hmm... I haven't noticed any problems running it from source, sound and graphics all seem fine to me. Maybe installing it from the repo configured the sound differently for you though, disturbedite.
If you have to install from the .tar.bz2 file, here's some directions:
1. unzip zsnes_1_5.tar.bz2
2. open terminal and change directory to the "src" folder in the "zsnes_1_5" folder by typing:
desktop:~$ cd ~/Desktop/zsnes_1_51/src (or whatever directory your zsnes_1_51 folder is in)
3. *snip*
Good directions, I'd like to recommend variations from step 3 on. :)
This will gather the required dependencies to build zsnes
sudo apt-get build-dep zsnes
sudo apt-get install libao-dev
./autogen.sh
./configure --enable-libao --enable-release
make
sudo make install
I just compiled zsnes an hour ago to get libao support, I don't think the one in the repositories uses it...
Best of luck. :D
P.S. If you have a dual core setup
make -j2
Will speed things up quite a bit. :KS
mister_k81
October 21st, 2007, 01:57 PM
^ Those are much better directions :D .
I didn't know that you could gather dependencies like that. I'm still new to Linux and have only been using it for about a month, so there's a lot I don't know.
Also, I have to ask, whats the name of that rom? It doesn't look like Zelda 3: Link to the Past.
kevindubrow
October 21st, 2007, 02:46 PM
Hey, no luck with those instructions, can I get some more help? Sorry if its a bother.
The first error came after the sudo apt-get build- dep zsnes:
E: Could not open file /var/lib/apt/lists/medibuntu.sos-sts.com_repo_dists_feisty_free_source_Sources - open (2 No such file or directory)
The next after the ./autogen.sh:
Generating build information using aclocal and autoconf...
./autogen.sh: 6: aclocal: not found
./autogen.sh: 7: autoconf: not found
Another error within that same code:
configure: error: You need NASM installed to compile ZSNES
Do any of these errors make any sense to you all? Thanks for all of the help!
-------------------------
Oh and hey FranMichaels, which Zelda is that? I have never seen that one...and it is even more confusing that is is in super nintendo!
dfreer
October 21st, 2007, 03:19 PM
@kevindubrow:
sudo apt-get install nasm build-essential libsdl1.2-dev zlib1g-dev libpng12-dev
There's an even EASIER way to install zsnes 1.51 in gutsy... *points at sig*
@FranMichaels - I like the Star Ocean pic, I wish I had more time to play that game...
FranMichaels
October 21st, 2007, 05:23 PM
@dfreer
Thank you, I made it rather quickly with GIMP. As for making time, save states might help ;)
@kevindubrow
dfreer gave the command you need. build-dep does work though, I'm not using medi-buntu, but the command is exactly:
sudo apt-get build-dep zsnes
No space between the hyphen. Try and see if that does the trick.
Also,
sudo apt-get install autoconf
that should take care of the autogen error
@mister_k81
Yes, there are a lot of great commands and tricks... You just kind of stumble upon them though... Unless you read a lot of manual pages. :KS
As for rom, and yes I know the forum rules, this is not a link to the rom itself, just a patch file:
http://www.romhacking.net/hacks/197/
It's fun and extensive zelda III hack (requires the original zelda III rom), much harder than the original... Although a few save states and cheat codes I made balance things out :biggrin:
Anyway, zsnes supports soft patching.
So just put the ips file with the same name as the rom, and you'll be good to go.
P.S. Dfreer, hope you don't mind me copying your response style :)
kevindubrow
October 21st, 2007, 05:38 PM
I'm really sorry, these codes are still not working. I now have a lot of new errors. I have gotten the repo that dfreer made but I don't know how I use that to get ZSNES. I thought it would be in the package manager, but I do not see it.
Oh and thanks for the info FranMichaels!
FranMichaels
October 21st, 2007, 05:47 PM
You are very welcome.
Let's get this working. :)
What do the errors look like.
Did zsnes used to work before, maybe you should backup the config files stored in .zsnes
kevindubrow
October 21st, 2007, 06:00 PM
It was working in Feisty, but stopped when I upgraded. I'll just put the whole output...I don't care if you guys know my name!
stephen@stephen-laptop:~$ cd ~/Desktop/zsnes_1_51/src
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ sudo apt-get build-dep zsnes
[sudo] password for stephen:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Could not open file /var/lib/apt/lists/medibuntu.sos-sts.com_repo_dists_feisty_free_source_Sources - open (2 No such file or directory)
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ sudo apt-get install libao-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libao-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libnl1-pre6 libnm-util0 dhcdbd
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ sudo apt-get install autoconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
autoconf is already the newest version.
The following packages were automatically installed and are no longer required:
libnl1-pre6 libnm-util0 dhcdbd
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ ./autogen.sh
Generating build information using aclocal and autoconf...
./autogen.sh: 6: aclocal: not found
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for nasm... nasm
./configure: line 3437: syntax error near unexpected token `1.2.0,,AC_MSG_ERROR'
./configure: line 3437: `AM_PATH_SDL(1.2.0,,AC_MSG_ERROR(SDL >= 1.2.0 is required))'
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ ./configure --enable-libao --enable-release
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for nasm... nasm
./configure: line 3437: syntax error near unexpected token `1.2.0,,AC_MSG_ERROR'
./configure: line 3437: `AM_PATH_SDL(1.2.0,,AC_MSG_ERROR(SDL >= 1.2.0 is required))'
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ make
make: *** No targets specified and no makefile found. Stop.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ sudo make install
make: *** No rule to make target `install'. Stop.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$
Thank you very much for your help!
FranMichaels
October 21st, 2007, 06:07 PM
It was working in Feisty, but stopped when I upgraded. I'll just put the whole output...*snip*
./configure: line 3437: syntax error near unexpected token `1.2.0,,AC_MSG_ERROR'
./configure: line 3437: `AM_PATH_SDL(1.2.0,,AC_MSG_ERROR(SDL >= 1.2.0 is required))'
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ make
make: *** No targets specified and no makefile found. Stop.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ sudo make install
make: *** No rule to make target `install'. Stop.
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$
Thank you very much for your help!
Okay, well it might be the new zsnes doesn't like your old config.
In nautilus, press ctrl + h (or view hidden files) go the .zsnes folder
rename your zsnescfg (or some file like that) to zsnescfg.old or move it to the Trash can. Try launching zsnes, and see if it works :)
Other options, you are close to compiling it, just missing libsdl-dev stuff according to the error.
sudo apt-get install libsdl1.2-dev
kevindubrow
October 21st, 2007, 06:15 PM
Ok, well I already had whatever your code was going to give me:
libsdl1.2-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libnl1-pre6 libnm-util0 dhcdbd
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I deleted the zsnesl.cfg file and when I opened zsnes, it rewrote the file in the .zsnes folder and I had the same issue occurred (zsnes opened with a black box and closed).
FranMichaels
October 21st, 2007, 06:20 PM
*snip*
I deleted the zsnesl.cfg file and when I opened zsnes, it rewrote the file in the .zsnes folder and I had the same issue occurred (zsnes opened with a black box and closed).
Hmm it must be another libsdl dev dependency, I installed mine more than 1/2 a year ago, so I don't rememeber exactly what's missing. Installing dependencies normally a one time thing.
sudo apt-get install libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libsdl-sound1.2-dev
Darn. :(
What happens when you type zsnes in terminal
does it show an error message?
EDIT: One other thought, did you change anything in your upgrade to Gutsy? Maybe enabling/disabling desktop effects will make a difference?
mister_k81
October 21st, 2007, 06:26 PM
stephen@stephen-laptop:~/Desktop/zsnes_1_51/src$ ./autogen.sh
Generating build information using aclocal and autoconf...
./autogen.sh: 6: aclocal: not found
I don't know if this helps, but you can get aclocal by typing: "sudo apt-get install automake".
kevindubrow
October 21st, 2007, 06:36 PM
Woh! The code mister_k81 gave me did the trick! I Ran the code, ran an uninstall on ZSNES, reinstalled it and all is well! Thanks so much for all of your help, all you guys are great! And thanks for all of your time, FranzMichaels!
I don't understand this....it is doing the same thing again!
Output:
ZSNES v1.51, (c) 1997-2007, ZSNES Team
Be sure to check http://www.zsnes.com/ for the latest version.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE.TXT' thoroughly before doing so.
Use ZSNES -? for command line definitions.
This is a work in progress build. It contains code which
May or may not be complete
If this is supposed to be an official release, you forgot to
run configure with --enable-release, go rebuild.
It runs fine in the terminal, it tells me that it can not find a mouse, but mine still works.
kevindubrow
October 21st, 2007, 06:39 PM
It will run fine if I run it from the terminal, but if I open it in the menu it will crash. Any clue what that is about?
FranMichaels
October 21st, 2007, 06:56 PM
It will run fine if I run it from the terminal, but if I open it in the menu it will crash. Any clue what that is about?
Right click on the Applications menu, choose Edit Menus
Go to Games
Right click on zsnes and choose Properties.
for the command make sure it's just
zsnes
Hopefully that's does it.
Glad you got it working again! :KS
kevindubrow
October 21st, 2007, 07:04 PM
Well, it is just ZSNES, here is all the info:
Name: ZSNES
Command: /usr/local/games/zsnes/zsnes
Occasionally ZSNES will crash and I get this error:
Segmentation fault (core dumped)
I guess I can live with it just working in the terminal...but apparently I can not go full screen...it makes my video output when I am done playing all odd. Also, the audio quality is very badr. Thanks for all of the help.
mister_k81
October 21st, 2007, 07:11 PM
are you typing it ZSNES with all caps? that might be the problem. it should be all lower case.
Oh, I just saw your edit, all you need to type is "zsnes" for the command...
I'm not sure what the problems could be with fullscreen, bad sound and other bugs? Really can't help you there. sorry. :/
kevindubrow
October 21st, 2007, 07:21 PM
When I type in the terminal I use lower case, and I must of made a typo, it is lowercase in the menu editor also.
FranMichaels
October 21st, 2007, 08:00 PM
Well, it is just ZSNES, here is all the info:
Name: ZSNES
Command: /usr/local/games/zsnes/zsnes
Occasionally ZSNES will crash and I get this error:
Segmentation fault (core dumped)
I guess I can live with it just working in the terminal...but apparently I can not go full screen...it makes my video output when I am done playing all odd. Also, the audio quality is very badr. Thanks for all of the help.
That's what I mean, the command
"Command: /usr/local/games/zsnes/zsnes"
change it to only
zsnes
not /blah/blah/zsnes
That will do it :)
As for the audio, try putting to 48000hz?
As for video, play with the settings, maybe try opengl ones ODR OD etc.
kevindubrow
October 21st, 2007, 08:09 PM
THANK YOU SO MUCH! It still occasionally crashes and the sound is still iffy, but don't worry about it, I am happy for what I have (honestly, you've done enough). I really appreciate all of the help you have given me. If I ever learn Linux well enough, I may be able to help you out one day in return. Seriously, thanks again everyone, you all are great.
dfreer
October 21st, 2007, 09:35 PM
I'm guessing, due to zsnes being in /usr/local/games/zsnes/, that you installed my zsnes package, and then compiled a version of zsnes as well? This may cause the error you are experiencing, although I don't know why my version would be seg faulting (I just made the gutsy packages, perhaps there is a problem).
Install libsdl1.2debian-oss has been known to help scratchy sound.
Alternatively, compiling 1.51 with --enable-libao, and then running zsnes with -ad oss has fixed my sound issues completely. EDIT: FranMichaels already showed how to do this in the first page of this thread
Compiling with --enable-release gets rid of the "WIP" error at startup, beyond that I'm not sure what advantages/disadvantages it presents.
Increasing the sound from 32000hz to 48000hz can, in some cases, improve sound quality (although zsnes developer's will not accept sound-related bug reports when using anything but 32000hz.
Play with the video modes, and make sure your video card drivers are installed correctly is about all I can say about graphical glitches.
The error you get when updating with apt-get is probably due to a typo in /etc/apt/sources.list, you should be able to see an entry concerning medibuntu.
I have gotten the repo that dfreer made but I don't know how I use that to get ZSNES. I thought it would be in the package manager, but I do not see it.
Using the repository should be as simply as copy+pasting, and should show up in the package manager if done right. But if you already got zsnes working, I wouldn't mess with it:
echo "deb http://packages.dfreer.org gutsy main" | sudo tee -a /etc/apt/sources.list
wget http://packages.dfreer.org/7572013D.gpg -O- | sudo apt-key add -
sudo apt-get update
sudo apt-get install zsnes
@FranMicheals - lol, I borrowed my commenting style from others on the forum, so whatever ;)
kevindubrow
October 21st, 2007, 09:43 PM
Do you think if I uninstall and use your code, I will have ZSNES running well? Thanks.
Hah, I ran the code and all is well! Thanks again!
dfreer
October 21st, 2007, 10:20 PM
Well, before you go through a uninstall, you can simply test my binary. If that works for you, THEN you can clean out zsnes completely and try my package.
So, to test my binary, create a folder on your desktop (like dfreer), and place this file in it:
http://www.dfreer.org/~dfreer/zsnes/binaries/zsnes_1.51
Then, just in case, backup your saved games like so:
sudo mv -v ~/.zsnes/ ~/zsnes_backup
Then, you can try out my binary (I'd appreciate it, if there is something wrong I'd like to know about it). Try running it like this:
cd ~/Desktop/dfreer/
./zsnes -ad oss
That will use the libao2 library, so hopefully you'll notice better sound quality.
If it crashes, post the output, and then run this command and post:
ldd ./zsnes
Thanks in advance, and I hope this helps you out as well!
kevindubrow
October 21st, 2007, 10:24 PM
Umm...I didnt use the codes you just put, but I have already used your codes from three posts ago and everything is great! Is that enough info for you, or do you want me to use these new codes?
dfreer
October 21st, 2007, 11:20 PM
No need if my package works, thanks! So sound is working ok now, and video after installing my package?
FranMichaels
October 22nd, 2007, 03:24 PM
I was very glad to help you. Just make sure to have fun. :)
Anyway, maybe it's time we make a bash script that handles downloading, building, and installing for zsnes.
Maybe dfreer you'd like to help with 64-bit (I don't have a 64-bit box at the moment...)
:KS
kevindubrow
October 22nd, 2007, 05:14 PM
Everything is great! Thanks so much for your help!
dfreer
October 22nd, 2007, 07:09 PM
I was very glad to help you. Just make sure to have fun. :)
Anyway, maybe it's time we make a bash script that handles downloading, building, and installing for zsnes.
Maybe dfreer you'd like to help with 64-bit (I don't have a 64-bit box at the moment...)
:KS
I can certainly help out, but it's far easier to build the binaries on a 32-bit OS, I have yet to figure out how to compile 32-bit binaries from a 64-bit host. (You can't actually build a true 64-bit version of zsnes, due to the way zsnes is currently developed. My ZSNES packages are 32-bit binaries in a 64-bit package, because current intel/amd 64-bit processors can execute 32-bit code).
I'll have more for you later tonight, one thing to look out for is the "can't create mcop directory" that a lot of gutsy users are having problems with. I have yet to hear a definitive answer on the cause and solution for that problem.
FranMichaels
October 22nd, 2007, 07:29 PM
Very cool, and thanks. :)
My sister ran into that mcop issue after upgrading to Gutsy.
I proposed a solution in another thread here, but can't really test it myself... :) Nor do I know the cause...
dfreer
October 22nd, 2007, 09:46 PM
I'm thinking it has to be specific to the gutsy package of zsnes in the main repos. I'll set up a virtual machine or live CD here, and see if I can replicate on a fresh version of gutsy.
As for the script, it wouldn't be hard at all. The only issue I'd have would be how to check for if there is any errors when compiling, and halt properly once something fouls up.
Maybe I'm bias, but AFAIK my packages already work fine for gutsy, is there a need for such a script?
Tuxoid
October 22nd, 2007, 09:54 PM
when run from the terminal, zsnes tells me:
mike@Mike:~$ zsnes
ZSNES v1.36 (c) 1997-2002, ZSNES Team (zsKnight & _Demo_)
Be sure to check http://www.zsnes.com/ for the latest version.
Please report crashes to zsnes-devel@lists.sourceforge.net.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE' thoroughly before using it.
Use ZSNES -? for command line definitions.
MMX support found and enabled.
Could not set 512x448 video mode.
I tried installing some sdl pakages that were suggested, and it nothing.
FranMichaels
October 22nd, 2007, 10:18 PM
I'm thinking it has to be specific to the gutsy package of zsnes in the main repos. I'll set up a virtual machine or live CD here, and see if I can replicate on a fresh version of gutsy.
As for the script, it wouldn't be hard at all. The only issue I'd have would be how to check for if there is any errors when compiling, and halt properly once something fouls up.
Maybe I'm bias, but AFAIK my packages already work fine for gutsy, is there a need for such a script?
Come to think of it, I agree :)
Considering how long zsnes 1.51 has been out.
Maybe if a new release comes out or the svn has some obvious benefits.
I guess I thought it might be handy since there seem to be a lot of "zsnes issues" threads in this section. Probably better handled by squashing outside bugs, I don't think zsnes is responsible for it, except maybe sound issues ;)
Thanks.
dfreer
October 22nd, 2007, 10:20 PM
@FranMichaels - That mcop error may very well be solved by using a custom bash script, but as a package maintainer I can't really (shouldn't is more correct) modify files in user's home directories. But I'm really thinking that the official package is to blame, not gutsy itself.
Didn't we just have this same error elsewhere?? Anyways:
My advice would be to backup, and then delete your existing ~/.zsnes/ directory. If that doesn't work, then try manually specifying the resolution you want zsnes to run in, either in your ~/.zsnes/zsnesl.cfg file, or when launching zsnes by passing it an argument like so:
-v # Select video mode :
0 = 256x224 R WIN 1 = 256x224 R FULL
2 = 512x448 DR WIN 3 = 512x448 DR FULL
4 = 640x480 DR FULL
5 = 256x224 O R WIN 6 = 512x448 ODR WIN
7 = 640x480 ODS FULL 8 = 640x480 ODS WIN
9 = 640x560 ODR WIN 10 = 768x672 ODR WIN
11 = 800x600 ODS FULL 12 = 800x600 ODS WIN
13 = 896x784 ODR WIN 14 = 1024x768 ODS FULL
15 = 1024x768 ODS WIN 16 = 1024x896 ODR WIN
17 = 1280x960 ODS FULL 18 = 1280x1024 ODS FULL
19 = 1600x1200 ODS FULL 20 = VARIABLE ODR WIN
21 = VARIABLE ODS WIN 22 = CUSTOM OD FULL
EDIT: not quite the same error, I see:
http://ubuntuforums.org/showthread.php?t=571666&highlight=zsnes
FranMichaels
October 22nd, 2007, 10:22 PM
when run from the terminal, zsnes tells me:
mike@Mike:~$ zsnes
ZSNES v1.36 (c) 1997-2002, ZSNES Team (zsKnight & _Demo_)
Be sure to check http://www.zsnes.com/ for the latest version.
Please report crashes to zsnes-devel@lists.sourceforge.net.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE' thoroughly before using it.
Use ZSNES -? for command line definitions.
MMX support found and enabled.
Could not set 512x448 video mode.
I tried installing some sdl pakages that were suggested, and it nothing.
Zsnes 1.36... Why? :) Try using 1.51 and see if it works for you.
Or is there a reason you want that particular version (old zmv file?)
Hope that helps.
dfreer
October 23rd, 2007, 04:09 PM
BTW, I just tested i386 package of zsnes on a Gutsy Live CD. I had no issues with the mcop directory missing, so it's definitely got to be an issue with the main repository package.
botulismo
October 23rd, 2007, 05:23 PM
I was having this problem... Let it go a couple days, then I remembered "Hey, run it from the terminal" and the mcops directory thing was the problem...
The solution? I made the directory it was having a problem creating for it. It's worked fine ever since.
Has this solution already been posted? If so, I apologize. I tried skimming the thread as quickly as possible without missing details, but I may have. It seemed like most of the solution involved compiling the program oneself, but to me, just making a directory for a (slightly) faulty program is easier.
Tuxoid
October 23rd, 2007, 06:53 PM
Zsnes 1.36... Why? :) Try using 1.51 and see if it works for you.
Or is there a reason you want that particular version (old zmv file?)
Hope that helps.
Won't upgrading the zsnes delete my state files?
acoustibop
October 24th, 2007, 03:48 AM
Unless you're using non-default locations, Tuxoid, your saves, save states, configuration etc should be in /home/<user>/.zsnes. Removing the rest of the installation shouldn't affect this folder. However, if you're wondering whether your save states will still work with a new version - quite possibly, they won't. Particularly with as big a jump between versions of this, the emulator may well be emulating games differently, which will mean save states, which are a 'snapshot' of the game at that point, may differ from version to version of the emulator.
It's not a good idea with most emulators to rely on save states exclusively. Errors can creep into a game when playing for some time, and these accumulate. Conventional saves usually just record the parameters of the game at that point, so errors should be stripped away by the save. Restarting the game and reloading the save is like starting anew but with different parameters that put you at the point in the game where you saved.
Save states, on the other hand, usually record the entire state of the game, including any errors that may have occurred. So when you load from a save state, it's like continuing the game you were playing before, errors included. Eventually, they can accumulate to the point where the game becomes unplayable.
This is particularly noticeable with emulators for consoles where games can last a considerable length of time - with Playstation emulators, for instance, it's a standard point to check when someone has problems late in a game - are you playing entirely on save states?
It would also be a good idea to delete your configuration files (in /home/<user>/.zsnes) if you upgrade and configure the new version afresh. Again, with the differences you can get with as big a jump as this, your old configuration could mess the emulator up, and it's not difficult or time-consuming to configure ZSNES.
Tuxoid
October 24th, 2007, 07:31 PM
- are you playing entirely on save states?
I do save through the natural game save screens, but I use save states for convenience.
dfreer
October 24th, 2007, 11:52 PM
If you wish to upgrade why not play each game that is currently at a save state through until you reach a save point, and then save. Delete the old save states, upgrade. Continue on using new save states with the new emulator.
disturbedite
October 25th, 2007, 10:49 PM
just to clarify, in my post a long time ago, i failed to mention why the audio was scratchy when compiling from svn source: it is a known problem for mobos with integrated sound cards (chips).
Tuxoid
November 12th, 2007, 09:36 PM
If you wish to upgrade why not play each game that is currently at a save state through until you reach a save point, and then save. Delete the old save states, upgrade. Continue on using new save states with the new emulator.
I wish I could but i can't even get the emulator to load.
EDIT: I actually have (oddly enough) both 1.51 and 1.36.
Now that I remember, before 7.10, 1.51 would run.
the 1.36 file never worked. In, I think
I had the same error in the terminal.
I don't how I could possibly have both, and I
have even less of an idea on how to remove the
1.36 one.
Tuxoid
November 15th, 2007, 03:22 AM
Alright, I have tried to run 1.51 via the terminal now and here's what it spits out:
ZSNES v1.51, (c) 1997-2007, ZSNES Team
Be sure to check http://www.zsnes.com/ for the latest version.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE.TXT' thoroughly before doing so.
Use ZSNES -? for command line definitions.
Starting Mouse detection.
ManyMouse: 2 mice detected.
Using ManyMouse for:
Mouse 0: SynPS/2 Synaptics TouchPad
Mouse 1: Macintosh mouse button emulation
Could not set 512x448 video mode: No available video device
dfreer
November 15th, 2007, 12:38 PM
Move your ~/.zsnes folder elsewhere, and try again. Example:
mv -v ~/.zsnes/ ~/.zsnes_backup
Tuxoid
November 15th, 2007, 04:57 PM
It's still showing out basically the same error after trying to move my .zsnes directory:
Be sure to check http://www.zsnes.com/ for the latest version.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE.TXT' thoroughly before doing so.
Use ZSNES -? for command line definitions.
Starting Mouse detection.
ManyMouse: 2 mice detected.
Using ManyMouse for:
Mouse 0: SynPS/2 Synaptics TouchPad
Mouse 1: Macintosh mouse button emulation
Could not set 512x448 video mode: No available video device
Everything else works, but most of my emulators don't work with my video adapter. The only emulator working is mupen64. I have a 945g intel graphics accelerator. It all worked with feisty, but it just won't work in gusty.
FranMichaels
November 15th, 2007, 06:17 PM
Could not set 512x448 video mode: No available video device
[/CODE]
Everything else works, but most of my emulators don't work with my video adapter. The only emulator working is mupen64. I have a 945g intel graphics accelerator. It all worked with feisty, but it just won't work in gusty.
That is odd, mine is a 945gm, and all works well... Did you do an upgrade from Fiesty to Gutsy? It's possible you might be using i810 driver, instead of the new mode-setting driver "intel".
Try editing your xorg.conf (make a backup though!), change "i810" to "intel"
Or use Screens and Graphics in System -> Administration.
Also, if you switch to this driver, the 915resolution hack is no longer needed. :)
Hope this is the solution you need. :razz:
jorgerosa
November 15th, 2007, 09:13 PM
Any znes trouble? Please try this first.
Install: "Applications" ---> "Add/Remove" (and search there for zsnes, check it, and click on "Apply")
or, in terminal: sudo apt-get install zsnes
ok, then: sudo mkdir -p ~/.kde/socket-yourname-desktop
try run it now, hope this helps. Cya.
Tuxoid
November 15th, 2007, 09:22 PM
i changed my drivers, and it still does cannot find my video adapter. I tried to change it through xorg.conf and Screens and Graphics.
Tuxoid
November 16th, 2007, 11:57 AM
I have tried re-installing my zsnes. still getting the same error.
FranMichaels
November 19th, 2007, 12:22 AM
i changed my drivers, and it still does cannot find my video adapter. I tried to change it through xorg.conf and Screens and Graphics.
Could you post your xorg.conf?
Tuxoid
November 19th, 2007, 02:56 AM
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 28-64
VertRefresh 43-60
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection
Section "DRI"
Mode 0666
EndSection
FranMichaels
November 19th, 2007, 07:01 PM
Hmm mine looks similar, same driver, different resolution, less modules loaded... I'm tempted to ask you to back yours up, and generate a new one from scratch...
So bizzare :(
Does
zsnes -v 2
From commandline do anything?
Here is mine, I can't help but wonder if it's just a resolution issue though...
Section "Files"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection
Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Boardname "intel"
Busid "PCI:0:2:0"
Driver "intel"
Screen 0
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Vendorname "Generic LCD Display"
Modelname "LCD Panel 1920x1200"
Horizsync 31.5-74.5
Vertrefresh 56.0-65.0
modeline "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
modeline "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
modeline "1280x768@60" 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync
modeline "1280x720@60" 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync
modeline "1280x800@60" 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync
modeline "1440x900@60" 106.47 1440 1520 1672 1904 900 901 904 932 -hsync +vsync
modeline "1600x1024@60" 136.36 1600 1704 1872 2144 1024 1025 1028 1060 -hsync +vsync
modeline "1680x1050@60" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -hsync +vsync
modeline "1920x1200@60" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -hsync +vsync
Gamma 1.0
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Monitor "Generic Monitor"
Defaultdepth 24
SubSection "Display"
Depth 24
Virtual 1920 1200
Modes "1920x1200@60" "1680x1050@60" "1600x1024@60" "1440x900@60" "1280x800@60" "1280x720@60" "1280x768@60" "800x600@60" "800x600@56"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
Inputdevice "Generic Keyboard"
Inputdevice "Configured Mouse"
# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Inputdevice "Synaptics Touchpad"
EndSection
Section "Module"
Load "glx"
Load "GLcore"
Load "v4l"
EndSection
Section "device" #
Identifier "device1"
Boardname "intel"
Busid "PCI:0:2:0"
Driver "intel"
Screen 1
EndSection
Section "screen" #
Identifier "screen1"
Device "device1"
Defaultdepth 24
Monitor "monitor1"
EndSection
Section "monitor" #
Identifier "monitor1"
Gamma 1.0
EndSection
Section "ServerFlags"
EndSection
Tuxoid
November 21st, 2007, 09:44 PM
zsnes -v gives me same error I have been getting all this time.
inversekinetix
November 22nd, 2007, 12:04 AM
i just use the windows version in wine, it runs fine.
Tuxoid
November 23rd, 2007, 10:15 PM
I think I've narrowed it down. I tried downloading the SDL port of Abuse. It did not work either. The zsnes uses SDL to operate some of the graphics with OpenGL handling the rest of them. So, I believe this is an SDL-related problem. I also tried Using OpenGL with similar results. here's what happened:
Abuse-sdl
mike@Mike:~$ abuse
Disabling memory manager, using libc instead
Abuse-SDL 0.7.0
Unable to initialise SDL : No available video device
zsnes under OpenGL:
mike@Mike:~$ sudo /usr/bin/zsnes -v 5
ZSNES v1.51, (c) 1997-2007, ZSNES Team
Be sure to check http://www.zsnes.com/ for the latest version.
ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE.TXT' thoroughly before doing so.
Use ZSNES -? for command line definitions.
Starting Mouse detection.
ManyMouse: 2 mice detected.
Using ManyMouse for:
Mouse 0: SynPS/2 Synaptics TouchPad
Mouse 1: Macintosh mouse button emulation
Could not set 256x224-GL video mode.
Tuxoid
December 4th, 2007, 11:00 PM
I copied your xorg.conf FranMichaels, into my xorg.conf. The zsnes still does not work. I did upgrade from gusty.
vBulletin® v3.7.4, Copyright ©2000-2008, Jelsoft Enterprises Ltd.