No need if my package works, thanks! So sound is working ok now, and video after installing my package?
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...)
Everything is great! Thanks so much for your help!
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.
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...
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?
when run from the terminal, zsnes tells me:
I tried installing some sdl pakages that were suggested, and it nothing.Code: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 firstname.lastname@example.org. 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.
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
@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:
EDIT: not quite the same error, I see:Code:-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
Last edited by dfreer; October 23rd, 2007 at 03:24 AM.