Gp2x Bootchart

[theoddbot]

0.0.3 is out, it's been posted in the news forum to raise the profile a bit. I don't think we've had any major complaints yet

 

[DaveC]

Just installed .0.0.2 just fine with the gpu script. I installed it over 0.0.1 without flashing to GPH's kernel first. So far so good.

I've been messing around with games to see which ones get broken by the updated kernel. Here is a partial list that lock when I try to run them.

Memory
Mess
Gnuboy
Scummvm
n-tris
Falldown (This one hurts as we have frequent competitions here)

The thing is, I like all these programs very much, but I am willing to leave them all behind in favor of the faster boot times. In a perfect world the devs could update these programs so they don't write to the nand (I'm assuming that's why they don't work right.). Perhaps a redirect layer could be written so that calls to the nand get sent to the sd card? I'm no programmer so I'm not sure if that makes any sense at all.

Thanks for the continued effort theoddbot! Fantastic work!

CoinOp

​

Why are people writing to the NAND with their apps? That sounds kind of stupid to be writing to and wearing out a soldered in non-replaceable chip :blink:

Bad idea me thinks.

 

[BBTroll]

It is standard practice in a multi-user unix/linux systems to write setting to "$HOME/.{app_name}/"

For example:
If you are running as "root"(like the gp2x), and you start an app called "car", it will write its "settings" to "/root/.car/settings".
If you are running as "my_user", and you start an app called "car", it will write its "settings" to "/home/my_user/.car/settings".

It is also standard practice to write temporary files to /tmp

So... when porting an existing linux app, the porter has to change all of those to "/mnt/sd" or better yet "$PWD" that way we can put the app in any folder we want on our sd.

I hope that answered your question.