MIDP for Palm 1.0 App memory size

right now the max app memory size for MIDP for Palm 1.0 is 64Kb. Is there any way to increase it? and how to do it . why its limit is 64Kbthanks in advance!!
[178 byte] By [wzy8555] at [2007-9-26 12:19:01]
# 1

[wzy8555],

64kb is the maximum application memory size for an 8Mb Palm OS device that you can set in the MIDP for Palm 1.0 Java Application Manager software.

HTH.

Allen Lai

Developer Technical Support

SUN Microsystems

http://www.sun.com/developers/support/

allenlai at 2007-7-2 2:55:20 > top of Java-index,Java Mobility Forums,Java ME Technologies...
# 2

I am currently trying to write a graphically intensive program that should be well within the capabilities of my Palm m505 (it's based on a Commodore 64 program, after all).

Until the 64k heap limit is raised, I cannot implement this in Java. Why is this limit so far below (1/80th) the free memory for the device?

In the mean time, can anyone recommend a good C compiler?

.

madeye at 2007-7-2 2:55:20 > top of Java-index,Java Mobility Forums,Java ME Technologies...
# 3

[madeye],

The application memory made available by the MIDP for Palm OS to MIDlets is imposed by the Palm OS itself. The maximum memory made available by MIDP for Palm OS 1.0 for an 8MB Palm OS device is 64kb.

HTH.

Allen Lai

Developer Technical Support

SUN Microsystems

http://www.sun.com/developers/support/

allenlai at 2007-7-2 2:55:20 > top of Java-index,Java Mobility Forums,Java ME Technologies...
# 4

From the recent chat session, Todd Kennedy replied:

todd_kennedy: I'll talk about the heap size for MIDP-4-Palm. There is no way to change the heap size due to some technical limitations. Without going into too much detail, the Palm's memory is physically partitioned into 64K segments. And, in the MIDP-4-Palm implementation, we provide a compacting garbage collector. Without sacrificing performance, it becomes difficult to compact Java objects across multiple segments. However, the compacting garbage collector is usually efficient enough to allow MIDlets to run better than a non-compacting collector with a larger heap size. The only real limitation is that no single object may be larger than about 60K.

see http://developer.java.sun.com/developer/community/chat/JavaLive/2001/jl1127.html for more details.

Allen: I am confused, is the max object size 64k or the max application size 64k?

d1camero at 2007-7-2 2:55:20 > top of Java-index,Java Mobility Forums,Java ME Technologies...
# 5

> From the recent chat session, Todd Kennedy replied:

>

> todd_kennedy: I'll talk about the heap size for

> MIDP-4-Palm. There is no way to change the heap size

> due to some technical limitations. Without going into

> too much detail, the Palm's memory is physically

> partitioned into 64K segments. And, in the MIDP-4-Palm

> implementation, we provide a compacting garbage

> collector. Without sacrificing performance, it becomes

> difficult to compact Java objects across multiple

> segments. However, the compacting garbage collector is

> usually efficient enough to allow MIDlets to run

> better than a non-compacting collector with a larger

> heap size. The only real limitation is that no single

> object may be larger than about 60K.

>

> see

> http://developer.java.sun.com/developer/community/chat/

> avaLive/2001/jl1127.html for more details.

>

> Allen: I am confused, is the max object size 64k or

> the max application size 64k?

It is the amount of memory used to run a MIDlet java application during runtime. It is not the file size of the MIDlet .class file i.e. not the max application size.

allenlai at 2007-7-2 2:55:20 > top of Java-index,Java Mobility Forums,Java ME Technologies...