Endless Paradigm

@ afiser: Yes, I know how to use Google. Only the problem was not solved. I tried like 15 different gzip.exe files and none worked. So this is why I asked.

s_king Wrote:My application is checking the first 4 bytes of the selected file and allows you to use if it's:
~PSP in the header prx
_ELF in the data prx
So you can't use a compressed prx as data and/or a decompressed prx as header.

Adding the 'patch 0xE7E8 part in the vshmain.prx' ability to my program is really easy. But is this necessary only in vshmain or every other prx?

Edit: 0x18 - 0x1A is the module identifyer part in the decompressed prx?

compressed prx 0x30 = elf 0x18
compressed prx 0x34 = elf 0x40
compressed prx 0x54 = elf 0x48

compressed prx 0x48 = elf 0x5C « only vsh modules
compressed prx 0x58 = elf 0x68 « only vsh modules

edit:
regarding your vshmain.prx patch question. only vshmain.prx...
by the way its interesting to see how many prx's M33 are physically patching. DAX did it as far as I know completly by patching the memory

can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

vodkkaa {who took my name} Wrote:can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

that's a question only M33 could answer really, you would have to know how the header works and how to remake it, take a look HERE for more infomation. another thing you could do is compare all of the M33 modules with ~PSP headers.

vodkkaa {who took my name} Wrote:can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

bstronga Wrote:cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.

only tried with custom firmware extender though ;p

bstronga Wrote:

vodkkaa {who took my name} Wrote:can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

bstronga Wrote:cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.

only tried with custom firmware extender though ;p

so are you saying its possible and if so how??

vodkkaa {who took my name} Wrote:

bstronga Wrote:

vodkkaa {who took my name} Wrote:can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

bstronga Wrote:cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.

only tried with custom firmware extender though ;p

so are you saying its possible and if so how??

just attach your plugin ...

bstronga Wrote:

vodkkaa {who took my name} Wrote:

bstronga Wrote:

vodkkaa {who took my name} Wrote:can user made prx's be compressed.  for example i have made a prx that is 120kb but it interferes with the webbrowser.  anyway to compress it?

bstronga Wrote:cool.
however it does always use 0xC37AED69 which is fine for vsh modules
but not for modules like vshctrl.prx or third party plugins you may want to compress. which would need 0x33D63A71.

only tried with custom firmware extender though ;p

so are you saying its possible and if so how??

just attach your plugin ...

Here it is (I'm wokring with vodkaa on this)
HERE

i actually had to treat it as a vsh module ;o

bstronga Wrote:i actually had to treat it as a vsh module ;o

It doesn't appear to be showing up in the xmb? Ahhh... 3.52 only?