PDA

View Full Version : desmume


rustysail
February 10th, 2008, 07:47 PM
Hey
I have a nearly fresh copy of gutsy and I tried to install DeSmuME from the package manager and it won't open. Here is the result of doing it from the terminal.

rusty@rusty-desktop:~$ desmume
Nbr of joysticks: 0

The program 'desmume' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
(Details: serial 258 error_code 154 request_code 143 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

Thanks for the help

FrozenFox
February 10th, 2008, 08:28 PM
Your best bet is to use No$GBA in Wine. It currently works wonderfully with wine 0.9.55, much better than desmume in general. 2.6a is especially awesome and much faster if you can "donate" the 2.50 to the author for the download link.

heatblazer
February 12th, 2008, 05:09 AM
I tried it too. However neither of these emulators are working. I have no idea. I have the ROMS of the DS but the emus crush!

FrozenFox
February 12th, 2008, 06:58 AM
Really? That's very strange. Did you decode them before you tried to run them in either emu? Kirby canvas curse, Diamond, and Pearl all work flawlessly for me in no$gba 2.6 in wine.

rustysail
February 12th, 2008, 08:47 PM
no$gba appears to load the rom, but then it shows just what I think is japanese writing on the top screen. Maybe I have a bad rom?

FrozenFox
February 12th, 2008, 08:49 PM
It just might not be able to play your game. What are you trying to run? And for the record, what version of wine are you using?

rustysail
February 12th, 2008, 08:56 PM
I was trying to run pokemon pearl

I got a new rom. Same screen but this time in english. It says
"The data could not be read.

Please turn off the power, then remove and reinsert the DS Game Card.

As for wine, I'm not sure. it must be new cuz it is a brand new version of ubuntu.

FrozenFox
February 12th, 2008, 08:59 PM
Games that crash or where "data cannot be read" typically have not been decrypted. Search for endcrypts advanced (im not sure if it works in wine) or get one that's patched already.

FrozenFox
February 12th, 2008, 09:02 PM
Please see your private forum msgs, rusty. User CP --> private messages.

garukun
May 9th, 2008, 09:26 PM
I'm running in Hardy, I am experiencing the exact same problem. Any experienced mind giving a "why" this is happening?

GumbyX
May 26th, 2008, 12:12 PM
Got the same problem as you guys. I am doing NDS development and I can't get desmume to work at all. Same error as the first post on both 8.04 i386 and AMD64. :(

Zairinho12
May 28th, 2008, 04:34 AM
Fixing the "data could not be read" problem is usually very simple. What you need to do is Change the Save Type on your No$gba to Flash 512Kb. To do this, open your diamond/pearl rom in no$gba

then click on the options tab and emulation setup. in the dialog box labelled "nds cartridge backup media" click on FLASH 512 Kbytes.then click ok.

then click on file>reset cartridge. this usually should fix the data could not be read problem.

hope i've helped

Sockerdrickan
May 28th, 2008, 10:12 AM
Also try compiling the new DeSmuME 0.8 to get other results www.desmume.org

FranMichaels
May 28th, 2008, 12:40 PM
Hey
I have a nearly fresh copy of gutsy and I tried to install DeSmuME from the package manager and it won't open. Here is the result of doing it from the terminal.

rusty@rusty-desktop:~$ desmume
Nbr of joysticks: 0

The program 'desmume' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
(Details: serial 258 error_code 154 request_code 143 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

Thanks for the help

Are you using compositing?

Try this, should work. :)

desmume --disable-3d