Problem With The 'beta' Fw 1.4

[TelcoLou]

Yep. The LCD Tweak program no longer works under this firmware. I need to over-clock to play some games in MAME and the tweak program does't set the speed that I select, so I'm going back to 1.2.1

Also, when I OC in the PC Engine emu and then exit, the display is SUPER bright, washed out . and strangely, if I go in the LCD tweak, then just exit ... it fixes itself (?????)

.. unles someone found a way to make it work, and I'm just being dim again ...

 

[yaustar]

I think the washed out screen is a problem with 1.2.1. 1.1.0 never had this problem...

 

[calqlater]

I'm running 1.1.0, and I get the same LCD problem after overclocking within the GP2XEngine emulator: returning to the main menu yields a very over-bright, washed out display (reminds me of old busted TV sets). Running the LCD tweaker program also fixes it for me, though.

 

[SatanClaus]

Yep. The LCD Tweak program no longer works under this firmware. I need to over-clock to play some games in MAME and the tweak program does't set the speed that I select, so I'm going back to 1.2.1

Also, when I OC in the PC Engine emu and then exit, the display is SUPER bright, washed out . and strangely, if I go in the LCD tweak, then just exit ... it fixes itself (?????)

.. unles someone found a way to make it work, and I'm just being dim again ...

​

I never used the 1.4 beta, but I heard there is a built in LCD-Tweaker.

 

[TelcoLou]

Yep. The LCD Tweak program no longer works under this firmware. I need to over-clock to play some games in MAME and the tweak program does't set the speed that I select, so I'm going back to 1.2.1

Also, when I OC in the PC Engine emu and then exit, the display is SUPER bright, washed out . and strangely, if I go in the LCD tweak, then just exit ... it fixes itself (?????)

.. unles someone found a way to make it work, and I'm just being dim again ...

​

I never used the 1.4 beta, but I heard there is a built in LCD-Tweaker.

​

Right. And I think what's happening is that the built-in LCD Tweak is over-riding any settings you set in the LCD-Tweak program ...

 

[god_at_hell]

For People who don't read the other fw1.4 thread (TelcoLou read it) ... my posting frome there:

Maybe some of you noticed it, you can not over/underclock by using the cpu_speed.gpe in menu mode. Everytime the gp2xmenu loads the frequency is set to 200mhz. Now you have to make a GPU-scriptfile for every application you want to over/underclock. Just run the cpu_speed.gpe in console-mode right before the actual application and you'll get what you want.

To the overbright PCE-Emu... I think homer doesn't write a static value to the mem-address, but adds a value to the mem-address and subtracts the value when you leave the program. As a result you get a overtimed LCD-display.

 

[Squidge]

What I was told GPH were going to do was reduce the clock frequency to 66Mhz whilst in the menu, and then increase it to 200Mhz when it runs a game or utility, so it will obviously override any configuration by tools overclocking the system.

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

 

[TelcoLou]

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

​

.. or if you're a dim-wit like me, you could just stick with FW 1.2.x

 

[Vimacs]

or you just use a alternative launcher, like zlauncher

 

[Drak]

What I was told GPH were going to do was reduce the clock frequency to 66Mhz whilst in the menu, and then increase it to 200Mhz when it runs a game or utility, so it will obviously override any configuration by tools overclocking the system.

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

​

Say I want to make a simple script to launch SquidgeSnes at 266mhz could you lend a hand?

 

[Shikaku]

What I was told GPH were going to do was reduce the clock frequency to 66Mhz whilst in the menu, and then increase it to 200Mhz when it runs a game or utility, so it will obviously override any configuration by tools overclocking the system.

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

​

Say I want to make a simple script to launch SquidgeSnes at 266mhz could you lend a hand?

​

Check the readme: there's an example.

 

[Hanz™]

What I was told GPH were going to do was reduce the clock frequency to 66Mhz whilst in the menu, and then increase it to 200Mhz when it runs a game or utility, so it will obviously override any configuration by tools overclocking the system.

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

​

Say I want to make a simple script to launch SquidgeSnes at 266mhz could you lend a hand?

​

Check the readme: there's an example.

​

Is it possible to use scripting to tidy up the folder structure a bit in my GP2X.

 

[Drak]

What I was told GPH were going to do was reduce the clock frequency to 66Mhz whilst in the menu, and then increase it to 200Mhz when it runs a game or utility, so it will obviously override any configuration by tools overclocking the system.

The only way around this is what god_at_hell suggests - use a script to launch the emu, or wait for the developer to add in overclocking support.

​

Say I want to make a simple script to launch SquidgeSnes at 266mhz could you lend a hand?

​

Check the readme: there's an example.

​

Which Readme.. damn im dumb

 

[daclassicgamingmaster]

well, I've got the 1.4 FW and I've been running the LCD tweak program and Oc'ing to around 280 or so. I hit 'select' and the screen begins to flutter ever so lightly thus making me think it's running faster and it worked. When I go to return to the program however, the variable is set back at 199....I thought it was working?

 

[TelcoLou]

well, I've got the 1.4 FW and I've been running the LCD tweak program and Oc'ing to around 280 or so. I hit 'select' and the screen begins to flutter ever so lightly thus making me think it's running faster and it worked. When I go to return to the program however, the variable is set back at 199....I thought it was working?

​

Yeah, it doesn't work ... the new FW resets the clock speed to 200mhz everytime you enter the menu.

God_at_hell explained it all ... you need to run it in a script before each emu .... and no, I don't know how to do that :lol:

 

[daclassicgamingmaster]

God_at_hell explained it all ... you need to run it in a script before each emu .... and no, I don't know how to do that :lol:

​

yea I read that and the only thing that came to mind was "WTF?!?!?!?!"

 

[god_at_hell]

I'll explain it on the basis of gngeo.

Gngeo uses the program selector to display a menu, so in this case the gngeo2x.gpe is a script which runs the selector-application with the specific config-file:

#!/bin/sh

./selector ./gngeo2x_config
sync

cd /usr/gp2x/
exec /usr/gp2x/gp2xmenu

the only thing you have to do is adding one line just before the application is executed ... it should look like this

#!/bin/sh

/mnt/sd/cpu_speed.gpe 1 1 280
./selector ./gngeo2x_config
sync

cd /usr/gp2x/
exec /usr/gp2x/gp2xmenu

another example....
say we want to overclock squidgesnes... SSNES has it's own menu and comes without a scriptfile. To overclock SNES you have to create one (use a unix-conform text-editor (NOT MS Notepad/Edit)). I renamed squidgesnes.gpe in squidgesnes because i did not want to get confused with more than one executable. Now create your new file (squidgesnes.gpe on my sd) and edit the content to something like this

#!/bin/sh

/mnt/sd/cpu_speed.gpe 1 1 280
./squidgesnes
sync
cd /usr/gp2x/
exec /usr/gp2x/gp2xmenu

Now, if you run the squidgesnes.gpe, your gp2x clocks at 280mhz.

To understand the cpu_speed parameters take a look in the readmefile.
You better use the LCD/CPU-Tweaker V1.1c than V1.2 for scripts, because V1.2 is way bigger and takes more time to execute (1-3 secs) ... when you only use the commandline 1.1c is as good as 1.2 but is faster .
Get it here, because i don't think there is a mirror left. Inside the zip you can find the noted readme.txt.

NOTE: I have the cpu_speed.gpe in the root-directory of my sd-card ... if you want to use another directory, alter the line to match your path (/mnt/sd/ = sd-root-dir).

 

[TelcoLou]

Holy crap-on-a-cracker!! I think I understand it

I'm gpoing to try one for MAME and see how it works ... I'll post my results.

Thanks so much for your help god_at_hell

Yep ... it's confirmed, I'm very, very dim.

Here's what I made (In programmer's notepad):

#!/bin/sh

/mnt/sd/cpu_speed.gpe 1 2 250

./mnt/sd/mamegp2x/mame_gp2x.gpe

sync

cd /usr/gp2x/

exec /usr/gp2x/gp2xmenu

All I get is a black screen. the line ./mnt/sd/mamegp2x/mame_gp2x.gpe is the path to where the MAME executable is ... I'm lost

 

[god_at_hell]

remove the dot ... thats all

./ means the actual directory, so if you run your script in a folder like /mnt/sd/1234, it's actually /mnt/sd/1234/mnt/sd/mamegp2x/mame_gp2x.gpe

just remove the dot bevore the slash and everything should be allright.

Edit: Which Text-Editor do you use?

 

[TelcoLou]

remove the dot ... thats all

./ means the actual directory, so if you run your script in a folder like /mnt/sd/1234, it's actually /mnt/sd/1234/mnt/sd/mamegp2x/mame_gp2x.gpe

just remove the dot bevore the slash and everything should be allright.

Edit: Which Text-Editor do you use?

​

Programmer's notepad.

I think I finally understand .... I'll be back :lol:

I guess not ... I tried this:

#!/bin/sh

/mnt/sd/cpu_speed.gpe 1 2 250

/mnt/sd/mamegp2x/mnt/sd/mamegp2x/mame_gp2x.gpe

sync

cd /usr/gp2x/

exec /usr/gp2x/gp2xmenu

And this:

#!/bin/sh

/mnt/sd/cpu_speed.gpe 1 2 250

/mnt/sd/mamegp2x/mame_gp2x.gpe

sync

cd /usr/gp2x/

exec /usr/gp2x/gp2xmenu

I have the cpu_speed.gpe in the root of the sd card and I have the MAME executable as shown above (root > mamegp2x > mame_gp2x.gpe)

I really don't get it ...