Beta Stuff For Testing !


fusion_power said:
Laurent said:
This might be due to the use of what ARM calls "UNPREDICTABLE" instructions or behaviours. I've seen such instructions used on GBA, and some of them won't behave the same on Cortex-A8. For instance, LDR r0,[r0],#12 shouldn't be used.

Is this a problem that can be fixed?
Yes, that'd be no problem to fix it. But I took a *very* quick look at Cyclone sources and it does not seem to use the UNPREDICTABLE example I gave.
 
Last edited by a moderator:
notaz said:
Sure about that? There should be no problems with Cyclone, lots of projects use it without problems, including MAME and Amiga emus. The last time I looked at gngeo code it was using some old cyclone version, make sure you use one from here. There also might be problems with glue code between Cyclone and the rest of emu.


I think also that it's a bug in the glue code. But I don't see why it work on the gp2x and not the pandora.

@Cpasjuste: Did you enable the arm asm optimized video function?
 
Last edited by a moderator:
'notaz' said:
'Cpasjuste' said:
there is a bug with the cyclone asm core
Sure about that? There should be no problems with Cyclone, lots of projects use it without problems, including MAME and Amiga emus. The last time I looked at gngeo code it was using some old cyclone version, make sure you use one from here. There also might be problems with glue code between Cyclone and the rest of emu.

'Laurent' said:
This might be due to the use of what ARM calls "UNPREDICTABLE" instructions or behaviours. I've seen such instructions used on GBA, and some of them won't behave the same on Cortex-A8. For instance, LDR r0,[r0],#12 shouldn't be used.


I'm quite sure I haven't used anything like that.

it's probably not a cyclone problem, but rather the "glue" (man, I like this term, lol) in between... many other projects have used it before, it was expected to also be really compatible with the A8... it has invalid opcode callback anyway, so you would notice it
 
Last edited by a moderator:
Epic bump! (sorry)

Cpas' site doesn't work anymore and he himself hasn't been posting for well over a month, but he seems to be still lurking - Cpas, if you're reading this, would it be possible for you to pack up your stuff as pnd's (first post here mentions snes & gngeo), so we can enjoy some nice videos from some lucky early adopters bastards loading your apps up? :)
 
Ok, now I'm feeling like the Pandora was designed exclusivly just to make me feel like a retard.

I can't get gngeo to run my ROMS, I'm launching it from the terminal with ./gngeo /roms/nam1975.zip
and it complains about unsupported romset.

Any help would be greatly appreciated! (I feel great shame that I'm seeming to have problems with something that should be quite straight forward). In my defense, I have managed to launch Zelda Oot in Mupen64plus on the pandora and check it out - so I'm not a complete idiot.

Thanks,
Mqark.
 
laurens said:
maybe zipped roms aren't supported?

Thanks, but I've tried that and it didn't work for me. I need a sanity check on the method I'm using to try to start it and access the ROMs. It really does just seem to spit out most of the things I try. What Command line arguments are other sucessful users using to launch a game?
 
Last edited by a moderator:
Mqark said:
Ok, now I'm feeling like the Pandora was designed exclusivly just to make me feel like a retard.
That's because you're not yet using it the way it was designed.
Once a PND is properly setup, I'm sure you'll feel less like a retard. :)
 
Last edited by a moderator:
Is it possible to get PNDs to create a NAND overlay that puts man pages for the PND in the system? (but not actually writing them to the NAND) This would be incredibly useful for situations like this, because Mqark would just be able to say "man gngeo" to check the proper way to run it. I use the man pages all the time, and would definitely like some way to have them for my PNDs.

-God Ginrai
 
God Ginrai said:
Is it possible to get PNDs to create a NAND overlay that puts man pages for the PND in the system? (but not actually writing them to the NAND) This would be incredibly useful for situations like this, because Mqark would just be able to say "man gngeo" to check the proper way to run it. I use the man pages all the time, and would definitely like some way to have them for my PNDs.

-God Ginrai

I see what you're saying, but to heap even more shame on and to promote myself to a greater level of retardedness I have read the readme but it didn't make a great deal of sense. All I need is an example of how someone has launched the emu with an idea of how they use their romset. Just something like:

Romset (a zip file called nam1975) in /roms folder or in the root folder of the emu
Launch command = ./gngeo /roms/nam1975.zip

I just don't know what's happening behind the black box - what input is it expecting and does it have the intellegence to find roms in a folder or does it want a specific file. Also am I really being crap at linux and not realising I need to do something special like encapsulate a string or something...?
 
Last edited by a moderator:
Mqark said:
Romset (a zip file called nam1975) in /roms folder or in the root folder of the emu
Launch command = ./gngeo /roms/nam1975.zip
You mean "root of the emu" as in the directory ("folder") containing the emulator program? In that case it's not /roms/nam1975.zip you want, but simply roms/nam1975.zip
 
Last edited by a moderator:
SteveM said:
Mqark said:
Romset (a zip file called nam1975) in /roms folder or in the root folder of the emu
Launch command = ./gngeo /roms/nam1975.zip
You mean "root of the emu" as in the directory ("folder") containing the emulator program? In that case it's not /roms/nam1975.zip you want, but simply roms/nam1975.zip

Yes - that's what I mean.

I've tried your suggestion and I get the message "unknown or unsupported romset" back. It could be as simple as the fact that I'm just using an incompatible romset - but I think it should be ok.

Sorry for spamming this thread - but other equally ignorant people might be reading this and may benefit from learning some command line linux magic.

Also, thanks for taking the time to reply.
 
Last edited by a moderator:
Mqark said:
SteveM said:
Mqark said:
Romset (a zip file called nam1975) in /roms folder or in the root folder of the emu
Launch command = ./gngeo /roms/nam1975.zip
You mean "root of the emu" as in the directory ("folder") containing the emulator program? In that case it's not /roms/nam1975.zip you want, but simply roms/nam1975.zip

Yes - that's what I mean.

I've tried your suggestion and I get the message "unknown or unsupported romset" back. It could be as simple as the fact that I'm just using an incompatible romset - but I think it should be ok.

Sorry for spamming this thread - but other equally ignorant people might be reading this and may benefit from learning some command line linux magic.

Also, thanks for taking the time to reply.

From my experience gngeo requires specific romset versions.
 
Last edited by a moderator:
God Ginrai said:
Is it possible to get PNDs to create a NAND overlay that puts man pages for the PND in the system? (but not actually writing them to the NAND) This would be incredibly useful for situations like this, because Mqark would just be able to say "man gngeo" to check the proper way to run it. I use the man pages all the time, and would definitely like some way to have them for my PNDs.
It would be far easier to simply overload man. First it checks the real man pages and if it finds it, displays it through the traditional man program. If it doesn't find a related application, it can then check for PNDs of that name and then less the help file inside. If it finds neither it tells you the regular "no man pages found" error, or something.
 
Last edited by a moderator:
Mqark said:
God Ginrai said:
Is it possible to get PNDs to create a NAND overlay that puts man pages for the PND in the system? (but not actually writing them to the NAND) This would be incredibly useful for situations like this, because Mqark would just be able to say "man gngeo" to check the proper way to run it. I use the man pages all the time, and would definitely like some way to have them for my PNDs.

-God Ginrai

I see what you're saying, but to heap even more shame on and to promote myself to a greater level of retardedness I have read the readme but it didn't make a great deal of sense. All I need is an example of how someone has launched the emu with an idea of how they use their romset. Just something like:

Yes, but my point is that if the readmes were actually formatted like man pages, they would have examples of how to call the program with its many different parameters.

WizardStan said:
God Ginrai said:
Is it possible to get PNDs to create a NAND overlay that puts man pages for the PND in the system? (but not actually writing them to the NAND) This would be incredibly useful for situations like this, because Mqark would just be able to say "man gngeo" to check the proper way to run it. I use the man pages all the time, and would definitely like some way to have them for my PNDs.
It would be far easier to simply overload man. First it checks the real man pages and if it finds it, displays it through the traditional man program. If it doesn't find a related application, it can then check for PNDs of that name and then less the help file inside. If it finds neither it tells you the regular "no man pages found" error, or something.

I'm not interested in one of those ubuntu-style hacks. I want something solid. Also, by telling the author that it will overlay into the man pages, it will hopefully get them to format their readmes as such.

-God Ginrai
 
Last edited by a moderator:
Back
Top