Slow Start From Menu

[Parkydr]

I have an application, which I'm starting from a script.

If I run the script from telnet or sterm, the application takes less than 10 seconds to start. If I launch it from gp2xmenu it takes about 20 seconds.

Anyone seen this before? Any idea what the problem is?

 

[woogal]

Is the app a .gpu or .gpe? When a gpe is executed the menu exits, but with a gpu the menu is left running (unless they've sorted that in newer firmwares). It could even be possible that they haven't added the 'return to 200mhz' code when a gpu is launched so it might still be running at 100mhz.

However, if you're running a .gpe I haven't got a clue what's going on

 

[Parkydr]

It's a .gpu

Thanks

Edit: Tried renaming it to a gpe, but it made no difference

 

[Micket]

Go in through telnet, kill the menu, start it again and open the file through your gp2x.
That way you should be able to see some output on whats actually happening. That could maybe help you find the problem.

 

[Parkydr]

That solved it, but I didn't have to look at any errors.

I can't telnet to my GP2X at work, so I did it from sterm and redirected the output to a file.

It worked fine.

Solution change the script to send output from the app to /dev/null

Don't know why it works, but I don't care.

Goes like proverbial through a goose

 

[Parkydr]

Ok, it still isn't working.

It works fine after I've run sterm, which is why I thought it was fixed, but not directly after power on

Edit: Works now I hadn't redirected stderr as well