> Have you tried this on dr3? I know the system works in 2-bit mode in
> general, but there could be something else going on. (For example, does
> the rom you're running on advertise that it works in 2-bit mode? Does that
> same code work on a 3.5 debug rom? I'm not sure what your collection of "20
> other roms" includes... other 4.0 debug roms?)
bobby, you might also want to try running the OS in 2-bit mode, by
installing a utility like "toggle". then, put the OS into 2bit mode
and start your application (without the call to ScrDisplayMode).
http://www.ardiri.com/download/palm/toggle/toggle.zip
since you are not changing the display mode, it will remain in 2bit
mode and you can then see if the ScrDisplayMode() API call is actually
the cause of your problem.
in any event, i tested all the dr1, dr2 and dr3 roms manually -
and i did not find a problem with the device switching into 2bit
grayscale :(
> Where's the crash occurring? A stack trace always helps.
it may be the case that the ScrDisplayMode() API call is not the
cause of the problem - however, you never know :) there could be
a special case that you generate that actually causes a problem
// 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/
