|
|
Post by samphex on Jan 21, 2008 21:46:44 GMT 1
This situatation has never happened to me before. After installing a bunch of files(utitlities and other freeware), none of my snes games seem to work anymore(even chrono trigger  ). it shows "stack use 10%" "failed to alloc" "6144kb ftrMem for ROM" in the launcher it shows "RAM: 7760/5315KB DB:14979/5402KB" I am using a four gig memory card. I am using centro RC9(one that has 0-4(or 5?) for snes and nes) I have 35.6M free of 68.8M in phone and 2.7 gig of 3.7 gig of ram in card. I am not sing UDMH(whatever that is) I hope I provided enough info and did not leave anything out. Oh and did I mention im am doing this on garnet OS?  |
|
|
|
Post by Tinnus on Jan 21, 2008 21:57:57 GMT 1
It says it couldn't alloc Feature Memory, and that's regular DBCache so UDMH won't help here. You might try a warm reset (reset while holding "up") which will not pre-load background stuff (should work), or MemUnfragment, or DBCacheTool or something like that. What happens is that some of the apps you instaled are probably doing something when your device is restarted and are fragmenting the DBCache (temporary area where stuff is copied to when it's ran, and used by LJP to store the ROMs at runtime). Fragmentation means that the free space is all separete into small blocks, and it seems LJP needs 6MB in one chunk, which is quite a bit  (mental note: implement ROM paging) |
|
|
|
Post by metaview on Jan 21, 2008 22:10:12 GMT 1
Did you try a normal Reset? installing a lot of stuff leads to a fragmented DBCache (what you have). It might be better after a Reset, or it might be not. UnCache will prevent the fragmentation, as it blocks the Reset-message to most of your apps. Tinnus: if you ROM paging, you will find the next with a weaker device who complains  |
|
|
|
Post by Tinnus on Jan 21, 2008 22:45:52 GMT 1
Well, always good to have that extra 2MB or some ;D
Not as much as something like extra 16MB for GBA, but... of course we'd need a buffer for the loaded pages, so anyway it can't be helped to much more than that. But usually it's that tiny part that gives SNES and stuff their problems.
Not to mention paging would load the ROM in separate (fragmentable) blocks.
|
|
|
|
Post by samphex on Jan 21, 2008 22:56:38 GMT 1
A soft reset did it.(gawd...it took me like 15 minutes to find and enter all those crap numbers...FOR NOTHIN!) And tinnus..it's a system rest, not a warm reset. Theres, soft, system, and hard reset. (There is also the dumb reset where you take your phone to the phone company with a problem and they replace it. -__- Hence the dumb reset.)
|
|
|
|
Post by Tinnus on Jan 21, 2008 23:21:40 GMT 1
It was called a warm reset as far as I was reading manuals Palm just likes to change the names of things all the time, but I'm pretty sure that was called warm reset since it was created (and until the LifeDrive). |
|
|
|
Post by _Em on Jan 21, 2008 23:31:59 GMT 1
Yup... then they realized that they had to rename a "soft" reset and "hard" reset to "hot" reset and "cold" reset... and decided instead to rename "warm".
There are also other resets, such as the zero-out-reset, the debug reset, and a few others. Samphex, these resets generally pre-date Palm's foray into smartphones; the Palm user culture tends to stick with the original names.
|
|
|
|
Post by samphex on Jan 21, 2008 23:50:24 GMT 1
Over my head. Over my head. I will stick with the current ones. I know someday in the future they will switch the names of hard and soft, and a few days later, all the people who take advice from others while debugging their palm will scream their heads off unless they used a good backup program. *sigh...
|
|
). 
