hey i don't know what the hell is going on i ripped through this forum in search of info, and have yet to find anything this shits been killing me for days, i compile this piece of code the most basic form of EBOOT and when i fire it up my PSP shuts off, this didn't USED to happen it used to work perfectly fine on other firmwares. has there been a change I'm unaware of ?
Also I've noticed theres problems with buttons callbacks and other unusual shit, perhaps its the SDK or tool chain I've installed it on fedora core 8 shouldn't be a problem but who knows, its been known to do weirder things. They are the latest versions by the way.
Here is the sample i used the same old sample i been using as a template forever: main.c
If you still cant read the text and shut down cleanly, it's either the compiler or the PSP firmware. Related question - why are you on 3.90? 4.01 has been out for weeks now.
is not prx shit, if you want to code for slim and fat with firmware > 3.xx without 1.5 support (I mean for all PSP that haven't 1.5K support) it is mandatory, and it produces still an Eboot.
If you don't do that you will have an error code like 800200d2 (I think) when launching it on those PSP.
Concerning the heap, the size of your Eboot has nothing to do with it, the heap is linked to the memory you dynamically allocate.
A very small hb may need lots of memory and a very big one may need a small amount of dynamic mem.
It is wise to define the Heap and Stack even if there are default values (which I don't know).
is not prx shit, if you want to code for slim and fat with firmware > 3.xx without 1.5 support (I mean for all PSP that haven't 1.5K support) it is mandatory, and it produces still an Eboot.
If you don't do that you will have an error code like 800200d2 (I think) when launching it on those PSP.
Concerning the heap, the size of your Eboot has nothing to do with it, the heap is linked to the memory you dynamically allocate.
A very small hb may need lots of memory and a very big one may need a small amount of dynamic mem.
It is wise to define the Heap and Stack even if there are default values (which I don't know).
lol well what i ment to say was my program isnt taking more then a measly half a mb of ram its features are to move a file which is 44kb but the above shit about coding for 3.xx WITH OUT 1.50 i didnt know this should help me i appreciate the details! now i have a better understanding of what NOT to do in the future thanks again!
It depends on what you want to do, but if you set PSP_HEAP_SIZE_MAX(), it means your hb takes all the heap space and that it remains nothing for other PRXes you may have to load.
Not just other prxs - other THREADS. Most PSP apps create threads to do things (like install the exit callback in virtually every app). Memory for the thread's stack is NOT taken from the space of the app that spawns the thread - it's taken from the memory left over after the heap is allocated. Allocate too much memory (MAX) for the heap and nothing is left for threads. When you try to create the threads, they fail. Depending on the app, this causes the app to fail or act funny. Some programs will work without their helper threads, but at reduced functionality. For example, SNES9xTYL creates threads for the sound. If you set the heap too big and those threads fail to be created, SNES keeps running, but you don't get any sound.
Insert_witty_name wrote:Because your original post (before you edited it) was as far wrong as you could get :)
yes i realized that after i read it back sometimes i type with out thinking hence why i came back n fixed it. its the worst with programming cuz its intangible so i get a little confused or mixed up and then i come back and I'm like WHAT THE HELL WAS I THINKING. but yo if im wrong TELL ME WHY cuz sometimes i need a reminder hey dummy thats wRONG DARRR! lmao i'm not the kinda guy to take offence to correction. but i do if people tell me im a dummy and dont tell me WHY lol then i wonder