Ok, From what I have been reading everyone has been trying to figure out how to set caps lock on the pearl 8100. After a lot of research I couldn't find anything.. one guy even said that RIM forgot to include this feature. I'm not sure if this is the correct way but it's a work around that I figured out. When typing a message hold down the right shift key (the one that you press for a cap letter) then while holding that down press the green phone key (key you use to make a call) this will open up the dialer/phone log but Caps WILL BE locked!! only thing is to get back to your message you have to escape from the phone dialer.. once you get back to your message it will be in all caps.. is this the only way?? or has anyone found the right way to do this?

Great find. It works for me, however I have to hold the shift key and press the green phone button twice. And then hit shift twice again to get rid of the caps lock.

Wirelessly posted (8100: BlackBerry8100/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Nice, i've been looking for this too. Thanks. i'd also like to stop my BB from making the first letter of a word after a period capital.

To get it to turn off hold down the right shift key and just move the trackball it will turn caps lock off

Wirelessly posted (8700c: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) BlackBerry8100/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/102)

AWESOME FIND GraffixNyc!

nice.

tested in Memo Pad and it worked as written, albeit with the doubletap John Clark described. was also able to initiate in Calendar, but could not do so from within the Address Book. however, once the CAPS LOCK is initiated it does appear to remain indefinitely, even moving from app to app, but will be disabled by pressing CAPS again.

whammy: the keypad punctuation characters cannot be typed while CAPS LOCK is enabled, as pressing the ALT key will switch to NUM mode.

excellent find, and despite the punctuation issue (a manageable quirk), quite usable. mebbe we oughta keep this kinda hush-hush though, as RIM might decide to fix this "bug".

thanks for the heads up, Graf!