> Yes, I agree with this. Apps that are targetted at a specific market
> other than "general consumer" can break the rules, an make other
> requirements. I always assume here that people are making general use
> apps, unless otherwise stated. Maybe I shouldn't assume that.
even still.. what happens when these "specific" market devices
get outdated and put on ebay or something like that? it is not
exactly an easy task to prevent one of these people installing
a piece of software like FlashPro, which, in effect kills any
little hack that has been made to the Flash RAM area.
maybe another solution is to choose the right device for the
job.. if you want non-volitile storage, why not make the "specific"
market device a TRG pro, and then write directly to the CF cards.
battery dies, CF card stays alive.
or, move onto Handspring devices, using the Flash Springboard module.
there is always an alternative that writing to the Flash RAM area
where the operating systems resides..
you are opening yourself to a nightmare support system when it
may be possible that many users have different versions of the
operating system.. maybe rev 1.0 used 3.0, rev 2.0 used 3.3 etc
how will this affect your "Flash RAM" writing code?
just a few issues to consider, possibly :)
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
