FCC ID: O8FHVP-1H Phone Keypad

 

VisorPhone Module User Guide Copyright Copyright 2000 Handspring, Inc. All rights reserved. Handspring, Springboard, Visor, VisorPhone, the Handspring logo, and the Springboard logo are trademarks of Handspring, Inc., and may be registered in some jurisdictions. Graffiti, HotSync, and Palm OS are registered trademarks of Palm, Inc. or its subsidiaries. All other trademarks are the property of their re-

spective owners. Disclaimer and limitation of liability Handspring, Inc. and its suppliers assume no responsibility for any damage or loss resulting from the use of this guide. Handspring, Inc. and its suppliers assume no responsibility for any loss or claims by third parties which may arise through the use of this software and hardware. Handspring, Inc. and its suppli-

ers assume no responsibility for any damage or loss caused by deletion of data as a result of mal-

function, dead battery, or repairs. Be sure to make backup copies of all important data on other media to protect against data loss. Important: Please read the Handspring End User Software License Agreement in the back of this guide before using the accompanying software program(s). Using any part of the software indicates that you accept the terms of the Handspring End User Software License Agreement. Part #: 50-0227-00 ii Contents Getting Started.................................................................................1 Step 1: Set up your handheld computer.............................................2 Step 2: Get to know your phone ........................................................3 Step 3: Insert your SIM card..............................................................5 Step 4: Connect the phone to your handheld....................................6 Step 5: Charge the battery..................................................................7 Step 6: Turn on your phone...............................................................8 Step 7: Activate your account .............................................................9 Congratulations ................................................................................10 Making Calls..................................................................................11 Calling a speed dial number.............................................................12 Dialing a number with the Dialpad .................................................13 Redialing the last number ................................................................14 Redialing previous numbers.............................................................14 Calling a number in your Address Book..........................................15 Dialing a number from other applications.......................................16 Returning a missed call.....................................................................17 Calling an emergency number .........................................................18 Receiving Calls...............................................................................19 Answering the phone........................................................................20 Responding to call waiting ...............................................................21 Forwarding calls ...............................................................................22 Contents iii Handling Multiple Calls...................................................................23 Placing a call on hold .......................................................................24 Dialing another number while a call is on hold ..............................25 Switching between two calls ............................................................26 Using 3-way calling..........................................................................27 Checking Messages ........................................................................29 Reviewing missed calls .....................................................................30 Checking voicemail ..........................................................................31 Checking text messages....................................................................32 Displaying call history......................................................................33 Purging call history ..........................................................................34 Managing Your Speed Dial List .......................................................35 Defining speed dial buttons .............................................................36 Adding an Address Book entry to your speed dial list.....................37 Changing a speed dial entry.............................................................38 Deleting speed dial entries ...............................................................39 Arranging the speed dial list.............................................................40 Working With SMS Text Messages ..................................................41 Viewing messages .............................................................................42 Replying to messages .......................................................................43 Creating messages ............................................................................44 Creating message greetings and signatures .....................................47 Setting message options ...................................................................48 Saving incoming messages ...............................................................48 Modifying messages .........................................................................49 iv Contents Copying message text .......................................................................49 Forwarding incoming messages .......................................................50 Sorting messages...............................................................................51 Deleting messages ............................................................................52 Enabling SMS Email........................................................................53 Using VisorPhone as a Wireless Modem..........................................55 Establishing a TCP/IP connection with VisorPhone .....................56 Preparing for a direct wireless HotSync operation .........................57 Preparing for a network wireless HotSync operation .....................58 Performing a wireless HotSync operation.......................................59 Customizing Your Phone.................................................................61 Setting dialing prefixes .....................................................................62 Assigning dialing applications ..........................................................63 Changing the phone display.............................................................64 Selecting the ringer settings.............................................................65 Preventing unauthorized use............................................................66 Disabling call waiting .......................................................................67 Blocking your phone number for outgoing calls .............................68 Selecting a service provider network................................................69 Connecting a headset .......................................................................70 Using the Menus ............................................................................71 Phone application Edit menus .........................................................71 Phone application Record menu......................................................71 Phone application Options menu.....................................................72 SMS Message Manager application Message menus.......................73 Contents v SMS Message Manager application Edit menu...............................74 SMS Message Manager application Option menu..........................75 Troubleshooting and Maintenance...................................................77 Caring for your VisorPhone module...............................................82 Caring for the battery ......................................................................83 How do I dispose of the battery? .....................................................84 Warranty and Other Product Information ........................................85 Handspring, Inc. Limited Warranty ...............................................85 Handspring, Inc. End User Software License Agreement..............88 Canadian RFI Statement..................................................................93 Acknowledgments ............................................................................93 Index .............................................................................................95 vi Contents Getting Started Congratulations on the purchase of your new VisorPhone module. Your VisorPhone module integrates the power of a state-of-the-art digital mobile phone with the simplicity of your Handspring handheld computer. Your VisorPhone includes all of the most popular features such as speed dial and call screening. Plus, it handles multiple calls, sends and receives text messages, and fully integrates with your handheld to take advantage of your existing Address Book. To use your VisorPhone, you must first establish an account with a mobile phone service provider. Your account information is located on your SIM (Subscriber Identity Module) card. If a SIM card did not come with your VisorPhone, your service provider will provide one when you subscribe to their service. Your SIM card must be inserted into your VisorPhone before you can use it. Just follow the seven easy steps in this chapter to get up and running quickly. Getting Started 1 Step 1: Set up your handheld computer 1. If you havent already set up your handheld, follow the steps that came with your handheld to set it up.

(Recommended) Synchronize your handheld with your computer. 2. Place your handheld in the cradle and press the HotSync button Tip:

If you need additional information about synchronizing, refer to the Quick Reference guide and Visor Handheld User Guide that came with your handheld. 2 Getting Started Step 2: Get to know your phone Antenna Headset jack Phone button Power button Battery Battery latch SMS Message Manager button Speaker Slider LED Antenna Headset jack Battery Battery latch Power button Receives and sends signals on your VisorPhone. The antenna does not telescope out of the phone. Enables you to connect a headset so you can view your handheld screen while talking on the phone. Powers your VisorPhone. Secures the battery to your VisorPhone. Turns on your VisorPhone and activates the signal. Your phone stays on until you remove it from your handheld or press the power button to turn it off. Getting Started 3 Speaker Phone button SMS Message Manager button Slider LED Functions as the earpiece on your VisorPhone. Tip: To adjust the volume during a call, press the scroll buttons on the front of your handheld. Turns on your handheld and starts the Phone application. If another application is running, press this button to switch to the Phone application. If the phone is ringing, press this button to answer calls. Turns on your handheld and starts the SMS Message Manager application so you can view, send, and receive text messages. Controls the ringer setting. See Selecting the ringer settings on page 65 for details on changing the settings. Provides status information for your VisorPhone. The color of the light and the blink state indicate the status as follows:

No light = Phone off Red/solid = Charger on; battery charging Green/solid = Charger on; battery fully charged Red/slow blink = Phone on; no network service Green/slow blink = Phone on; in service Red/fast blink = Battery low Green/fast blink = Data call active 4 Getting Started If your SIM card is already inserted in your phone, skip to Step 4. Step 3: Insert your SIM card Note:

1. If the battery is attached, press the latch and remove the battery. 2. Insert the SIM card into the slot. Slide the SIM card into the slot 3. Place the battery onto your phone and secure the latch. Tip:

Since calls are billed to your telephone number, you can move your SIM card to any mobile phone that uses a SIM card, and the calls will be billed to your account. Getting Started 5 Step 4: Connect the phone to your handheld 1. Remove the slot protector from your handheld. 2. Insert your VisorPhone module into the Springboard expansion slot until it clicks into position. Slide the slot protector away from your handheld Slide the module into the Springboard expansion slot Tip: To remove your VisorPhone from your handheld, simply slide it out from the Springboard expansion slot. 6 Getting Started Step 5: Charge the battery 1. Plug the travel charger into a wall outlet. 2. Insert the travel charger cable into the connector on your handheld. LED turns solid red when charging and solid green when charged Tip:

Your VisorPhone must be in your handheld while charging. It takes about 1.5 hours to fully charge the battery. Its time to charge the battery when you observe one of the following:

n the battery gauge in the top-right corner of the Phone application appears empty n the LED turns red and blinks quickly n the LED does not turn on when you turn on your phone Getting Started 7 Step 6: Turn on your phone After the battery is charged, you can begin using your phone. 1. Press the Power button on your VisorPhone for two seconds until you hear a beep. 2. If the Unlock Phone dialog appears, enter the default password assigned by your service provider and then tap OK. See your service providers documentation for the default password. Note:

If you are using a SIM card from an established account, enter your existing password. Tap OK unlock your phone Tap numbers to enter password Tap CLR to erase the last number Tip:

See Preventing unauthorized use on page 66 to learn about setting your own password. 8 Getting Started Step 7: Activate your account If you received a new SIM card with your phone, you may need to call your service provider to activate your account. Your service providers phone number is located on the materials that came with your VisorPhone module. Once you receive your phone number, it may take a few hours to become fully active. Some service providers send a special message with your phone number. Follow these steps to check the phone number:

1. Tap the Menu icon 2. Under Options, tap Phone Info. Your VisorPhone number Your equipment ID number 3. Tap OK. Getting Started 9 Congratulations Youre ready to use your VisorPhone module. Keep these things in mind as you use your new phone:

n If you travel outside a coverage area, your phone remains on but you cant make or receive calls. If this occurs, the LED blinks red slowly and the phone periodically tries to register to the network. When you return to a coverage area, the LED blinks green. If you travel outside a coverage area, you cant receive SMS text messages. However, the messages are stored by the network and you will receive them when you return to a coverage area. n n Your account includes a voicemail feature so people can always leave you a message even when your phone is off. n Always use care when operating a mobile phone. If you plan to use your VisorPhone module while driving a car, we recommend using a headset for hands-free operation. See Connecting a headset on page 70 to learn how to connect a headset to your VisorPhone. 10 Getting Started Making Calls There are several ways to make calls with your VisorPhone. This chapter describes how to dial a number by:

n n Entering it on the Dialpad n Selecting it from your speed dial list Selecting it from your Call History list Selecting it from your Address Book n n Dialing from another application n Returning a missed call n Dialing an emergency number After you dial and establish a connection, the Active Call screen appears:

Voicemail notification icon Network name Signal strength icon Battery gauge Tap the Key Pad to enter extra numbers such as a PIN code or an extension Making Calls 11 Calling a speed dial number Speed dialing enables you to quickly place a call without entering the number. This is particularly useful for numbers you call often, such as your home or office. Note: This section assumes youve already created a speed dial list. To learn how to add numbers to your speed dial list see Defining speed dial buttons on page 36. 1. Press the Phone button on your VisorPhone. Tip:

If the screen below doesnt appear, tap the Speed Dial icon

. 2. Select the number you want to call. Tap a button to dial a number Speed Dial, Dialpad, and Call History icons Tap a Page icon to view other speed dial pages Tip:

After you make the connection the Active Call screen appears. If prompted to enter a menu selection, tap Key Pad. If you defined any Extra Digits, such as an extension, tap Extra Digits. 3. Tap Hang Up to end the call. 12 Making Calls Dialing a number with the Dialpad 1. Press the Phone button on your VisorPhone. Tip:

You can also tap the Phone icon Launcher to start the Phone application. in the Applications

. 2. Tap the Dialpad icon 3. Dial the number. If you are dialing an international number, tap the +

key before entering the number to automatically insert the international access code upon dialing. Tip:

To display the last ten numbers dialed, press the scroll buttons on the front of your handheld. Dial box Tap a digit to enter it in the dial box Tap Backspace to erase the last digit Tap CLR to delete the entire entry Tap Send to dial the number in the dial box Tip:

To edit the phone number, tap the Dial box and then use the keypad, Graffiti writing, or the onscreen keyboard. 4. Tap Hang Up to end the call. Making Calls 13 Redialing the last number n Hold down the Phone button for two seconds to redial the last number you called. Redialing previous numbers 1. Press the Phone button 2. Tap the Call History icon outgoing calls. on your VisorPhone. to view a list of previous incoming and 3. Select the number you want to call. Tap the entry you want to dial Tap here to select the call category:

All, Incoming, Out-

going, or Missed Tap Details to view call information Tap Dial to call selected number 4. Tap Dial. Tip: To add a number to your Address Book or Speed Dial list, tap Details, tap Copy Phone #, then in Address Book or the Speed Dial list, select Paste from the Edit menu to insert the number. 14 Making Calls Calling a number in your Address Book 1. Press the Address Book button 2. Select the number you want to call. on the front of your handheld. Tap a name to view or edit contact information Tap a number to select a number to dial Tap a number to select it Tap Dial to call the number Tip:

The Dial button changes to an Email button or an SMS button based on the type of number you select in the Dial dialog. You can assign each of these buttons to launch a different application. See Assigning dialing applications on page 63 for details. 3. Tap Hang Up to end the call. Making Calls 15 Dialing a number from other applications You can also dial numbers from other applications such as Memo Pad or To Do List. 1. Highlight the number you want to dial. 2. Press the Phone button on your VisorPhone. Tap here to add an area code or change the number Select a number to dial Tip: The number automatically appears in the Dial box on the Dialpad screen so you can edit the number if needed. 16 Making Calls Returning a missed call When your VisorPhone is on and you remain in a coverage area, any calls you miss appear in the Call History list and you receive a missed call alert message. When your phone is off or you travel outside a coverage area, your calls are forwarded to voicemail and they do not appear in the Call History list. n If you miss multiple calls, a message appears indicating the number of calls you missed. Follow the steps in Reviewing missed calls" on page 30 to return the calls. If you miss a single call, the following screen appears:

n Tap OK to dismiss the call without calling back Tap Call Back to dial the number Tip:

If the callers phone number is not available, the Call Back button does not appear on the Missed Call screen. Making Calls 17 Calling an emergency number Your VisorPhone provides easy access to the 911 or 112 emergency numbers. You dont need to unlock your phone or even have the SIM card installed to call an emergency number. n Press the Phone button on your VisorPhone. Tap Make Emergency Call Tip:

You can also dial a 911 or 112 emergency number from the Dialpad screen. 18 Making Calls Receiving Calls Whenever your phone is on and you are within a coverage area, you can receive incoming calls. In addition to answering calls, you can also choose several incoming call options. This chapter describes how to:

n Answer the phone (or reject a call) n Respond to a call waiting prompt n Forward your calls Receiving Calls 19 Answering the phone An incoming call turns on your handheld if it is off. Tap Answer to accept the call Callers name and phone number if available Tap Ignore to send the call to voicemail Tip:

You can also answer a call by pressing the Phone button your VisorPhone is ringing. while 20 Receiving Calls Responding to call waiting When you are on the phone and receive a second call, the Phone application updates the Active call screen and emits a Call Waiting beep tone. Tip: Make sure the Disable Call Waiting option on the Call Preferences screen is off. When this option is off the Disable Call Waiting check box is empty. For more information on enabling and disabling call waiting, see Disabling call waiting on page 67. n When the Call Waiting dialog appears, tap the appropriate button. Callers name and phone number if available Tap Ignore to send the call to voicemail Tap Hold & Answer to place 1st call on hold and answer incoming call Tap Drop & Answer to end1st call and answer incoming call Tip:

You can also press the Phone button hold and answer the incoming call. to place the first call on Receiving Calls 21 Forwarding calls If you need to turn off your phone or know you are traveling outside a coverage area, you can forward your calls to another number. Keep in mind that your service provider will still charge you for your forwarded calls. Note: Because call forwarding information is stored by the network, its a good idea to check the current network settings both before and after you change the call forwarding option. 1. Tap the Menu icon 2. Under Options, tap Call Preferences. 3. Select the call forwarding option you want to use. Tap here to forward all calls to the selected number Tip:

You can define up to five forwarding numbers including the voicemail number assigned by your service provider. Select Edit Number from the list to add, change, or delete a number. Tap here to display current network settings 4. Tap OK. 22 Receiving Calls Handling Multiple Calls You can use the Hold button in the Phone application to handle a variety of situations that involve multiple calls. During an active call, you can receive or place another call, switch between two active calls, and create a 3-way conference call. For example, when youre talking to a friend, you can put them on hold, call a restaurant to make dinner reservations, and return to your friend to confirm the time and place. These features also enable you to receive an important incoming call while youre already on the phone, and to facilitate conference calls when youre on the go. This chapter describes how to:

n Place a call on hold n Dial another number while a call is on hold n n Use 3-way calling Switch between two calls Handling Multiple Calls 23 Placing a call on hold 1. Place or answer a call. Call status indicator Tap Hold to put the call on hold Tap Off Hold to return to the call 2. Tap Hang Up to end the call. 24 Handling Multiple Calls Dialing another number while a call is on hold 1. Place or answer a call. 2. Put the call on hold. Tap Hold to put the call on hold 3. Tap 2nd Call. 4. Dial the number. Tap 2nd Call to access dial functions Tip:

to open You can tap the Applications Launcher icon another application that has the number you want to dial. Handling Multiple Calls 25 Switching between two calls 1. Answer or place two calls. See Dialing another number while a call is on hold on page 25. 2. Tap Swap, or tap the call status line to switch between calls. 1st call status 2nd call status Tap KeyPad to access a voice prompt system Tap Swap to change calls Tip:

If you called an automated phone system that prompts you to enter a menu selection or phone extension, tap KeyPad to respond to the voice prompts. 3. Tap Hang Up to end the active call. 26 Handling Multiple Calls Using 3-way calling 1. Answer or place two calls. 2. Join the two calls. Tap 3-way Call to speak with both calls at the same time 1st call status 2nd call status Tap Hold to place both calls on hold Tap Hang Up to end both calls Tap Cancel 3-way to return to the previous active call and to place the other call on hold Handling Multiple Calls 27 28 Handling Multiple Calls Checking Messages Your VisorPhone is capable of receiving voicemail and text messages and generating missed call messages. If you miss a call when your VisorPhone is on and you remain in a coverage area, your missed calls appear in the Call History list and you receive a missed call alert message. When your phone is off or you travel outside a coverage area, your missed calls are forwarded to voicemail and they do not appear in the Call History list. Similarly, when your phone is off or you travel outside a coverage area, your service provider stores your text messages until you turn on your phone or return to a coverage area. Note: You may need to contact your service provider to add the text messaging feature to your rate plan. This feature is sometimes referred to as SMS, or Short Message Service. This chapter describes how to:

n Review missed calls n Check voicemail n Check text messages n Display call history n Purge call history Checking Messages 29 Reviewing missed calls When you dont answer an incoming call, it appears under Missed calls in your Call History list. 1. Tap the Call History icon 2. Tap Missed in the pick list in the upper-right corner. Tap callers name or phone number Tap Dial to return the call 30 Checking Messages Checking voicemail When your phone is off, you travel outside a service area, or you miss or choose to ignore a call, the caller may leave a voicemail message. When you connect to the network, the phone application notifies you that you received voicemail messages. 1. Dial your voicemail service using one of these methods:

n Tap the Voicemail button in the Speed Dial view. n Tap Listen in the Voicemail alert dialog. 2. Tap Key Pad. Tap buttons to dial access codes and review messages 3. Tap Done. Checking Messages 31 Checking text messages When your phone is off or you travel outside a service area, other people can still send you text messages. Your service provider stores the messages for you until you turn on your phone or return to a service area. When you connect to the network, the phone application displays the first message in a screen similar to the following:

Number of new messages Tap Delete to delete the message Tap Done to review messages later Callers name and phone number if available Tap Read all to open the SMS Message Manager Inbox Tap Call to dial the sender Tip:

If you have only one message, the button in the lower-right corner changes to a Reply button. Tap this button to open the SMS Message Manager and send an SMS reply. 32 Checking Messages Displaying call history The Call History view provides quick access to the previous 1,000 incoming and outgoing calls. n Tap the Call History icon

. Outgoing call Missed call Incoming call Tap arrow to select the call category: All, Incoming, Outgoing, or Missed Tap Details to view time and duration Tap Dial to call the selected number Tip:

To temporarily store a number in your handhelds memory, tap Details, tap Copy Phone #, and then tap Done. You can now Paste this number into any application on your handheld. Checking Messages 33 Purging call history Your VisorPhone continues accumulating call history information for up to 1,000 calls until you purge the call history list. To conserve storage space, we recommend that you purge this list periodically. Note: Using the Purge function permanently removes the calls from your handheld. You cannot undo this process to restore the information. 1. From the Call History view, tap the Menu icon 2. Under Record, tap Purge. Tip:

To delete a specific item, select the item from the Call History view and tap Delete Item instead of Purge. 3. Select the purge option you want to use. Tap the pick list to choose which calls to purge 4. Tap OK. 34 Checking Messages Managing Your Speed Dial List You can store up to 50 phone numbers in the speed dial list. There are five pages of numbers that hold ten numbers per page. Tip: Keep your speed dial list organized by storing different types of numbers on different pages. For example, create separate pages for family, business, friends, and emergency numbers. This chapter describes how to:

n Assign phone numbers to speed dial buttons n Add Address Book entries to your speed dial list n Change speed dial entries n Delete speed dial entries n Arrange the speed dial list Managing Your Speed Dial List 35 Defining speed dial buttons 1. Tap the Speed Dial icon

. 2. Tap a blank speed dial button. Note: The first slot on the first Speed Dial page is reserved for your service providers voicemail service number. 3. In the Edit Entry dialog, enter the Name, Number, and any Extra digits. Enter a name for the button Enter digits to dial after placing the call

(such as an extension or access code) Enter the phone number Tap Lookup to find a number in your Address Book Tip:

To insert a pause between Extra digits when dialing, enter a comma (,). Each comma represents a one second pause. 4. Tap OK. 36 Managing Your Speed Dial List Adding an Address Book entry to your speed dial list 1. Tap the Speed Dial icon

. 2. Tap a blank speed dial button. 3. Tap Lookup. 4. In the Phone Number Lookup dialog, use the scroll arrows or begin writing the persons last name to find the number you want. Tap a number to select it Tap Add to insert the number in the speed dial entry 5. Tap Add. Tip:

You can edit the number or name by tapping it in the Edit Entry dialog. 6. From the Edit Entry dialog, tap OK. Managing Your Speed Dial List 37 Changing a speed dial entry 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. 4. Select the entry you want to change. Tap an entry to select it Tap pages to view more entries 5. In the Edit Entry dialog, enter the new information. 6. Tap OK to save the new information. 7. Tap OK again. 38 Managing Your Speed Dial List Deleting speed dial entries 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. 4. Select the entry you want to delete. Tap an entry to select it Tap pages to view more entries 5. In the Edit Entry dialog, tap Delete. 6. Tap OK to confirm deletion. 7. Tap OK. Managing Your Speed Dial List 39 Arranging the speed dial list 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. Drag an entry to another slot or page Tip:

If the new slot is full, the other entries shift down one slot. The right column fills after the left column becomes full. If you drag an entry to a page icon, the entry moves to the first available slot on that page. 4. Tap OK. 40 Managing Your Speed Dial List Working With SMS Text Messages In addition to dialing and receiving calls, you can use your VisorPhone to send and receive short text messages. These text messages, also called SMS

(Short Message Service) messages, are similar to email messages that you send and receive from your computer, but are limited to a few sentences in length. The person receiving your message must also have a mobile phone and a service provider that supports text messages. Some service providers also allow you to use your mobile phone to send text messages to an email address and to receive text messages from a computer. Talk to your service provider for details about their SMS and SMS Email features. This chapter describes how to:

n View messages n Reply to messages n Create messages n Create message greetings and signatures n Set message options Save messages n n Forward messages n Copy message text to the clipboard n Modify outgoing messages n n Delete messages n Enable SMS Email Sort messages Working With SMS Text Messages 41 Viewing messages 1. Open the SMS Message Manager Inbox using one of these methods:

n Press the SMS Message Manager button n From a Message alert dialog, tap Read All. on your VisorPhone. Tap arrow to select the message category:

Inbox, Saved, Pending, or Sent Message read Tap New to create a message Tip: When viewing Saved messages, the arrows indicate whether a message was incoming or outgoing. 2. Tap the message you want to view. 3. Press the scroll buttons on your handheld to scroll through a message. At the start or end of a message, it displays the next message. 4. Tap Done. 42 Working With SMS Text Messages Replying to messages 1. Tap the incoming message to which you want to reply. Tap Reply to respond to the message 2. Tap Reply. 3. Enter the message text. Tip: When you reply to an SMS message, the SMS Message Manager fills in the To field for you. When you reply to an email message, you must enter the email address on the first line of the message. See Creating an SMS Email message on page 46 for more information. 4. Tap Send. Working With SMS Text Messages 43 Creating messages SMS Message Manager enables you to create short text messages and send them to a mobile phone number or an email address. If a message exceeds 160 characters, SMS Message Manager divides the text into multiple messages. As you create a message, the status bar indicates how many messages will be sent and the number of characters in each message. To save time while creating messages, you can insert predefined text from a template. Some templates ask you to enter information such as a meeting time or place. Using a template is similar to filling in the blanks on a form letter instead of writing a letter from scratch. Fortunately, in SMS Message Manager you can easily combine the template text with your own text to personalize your message. You can create a message at any time, but if you send a message when you are outside a coverage area, your VisorPhone places the message in the Pending category and sends it automatically when you return to a coverage area. While a message is in the Pending category, you cannot edit it, but you can delete it before it is sent. 44 Working With SMS Text Messages Creating an SMS text message 1. From any SMS Message Manager list view, tap New. 2. Address the message to a mobile phone number. Tap To to select a number Tap Text to insert text from a template Tap Details to set message options 3. Enter text using Graffiti, the onscreen keyboard, or the pick lists. 4. Tap Send. (The message goes into the Pending category until your phone transmits the message.) Tip:

To store a draft message and send it later, tap Save instead. After your message transmits, your VisorPhone places a copy in the Sent category. If an error occurs while sending the message, an exclamation point

(!) appears next to message in the Sent category. Working With SMS Text Messages 45 Creating an SMS Email message To send a message to an email address, you must first enter your service providers SMS Email Center number. See Enabling SMS Email on page 53. 1. From any SMS Message Manager list view, tap New. 2. Tap the To pick list and select SMS Email Center. Tap To to select SMS Email Center Enter email address followed by a space and # symbol Tap Details to set message options 3. On the first Text line, enter the recipients email address followed by a space and a # symbol. Tip:

You can also select an email address in Address Book and then tap SMS, or select an email address from the Lookup list. 4. Enter the remaining text. 5. Tap Send. (The message goes in the Pending category until it transmits.) Tip:

To store a draft message and send it later, tap Save instead. 46 Working With SMS Text Messages Creating message greetings and signatures When you create a message you can use the greetings pick lists to insert a greeting and signature in your message. You can also add items to these lists or modify the existing items. From any SMS Message Manager list view, tap the Menu icon 1. 2. Under Options, tap Greeting. Tap here to hide the greetings pick lists Tap add Entry to create a new greeting 3. Tap Done. Working With SMS Text Messages 47 Setting message options You can specify whether you want to see a status report for this message, and the time period you want the message to remain in affect. If the recipients phone is off or outside a coverage area, their service provider stores the message until it can be delivered or until it expires, whichever comes first. 1. While creating a new message, tap Details. Tap here for status report Tap here to set expiration 2. Tap OK. Saving incoming messages 1. Open the message you want to save. 2. Tap the Menu icon 3. Under Message, tap Save. Tip:

Saving an incoming message moves the message from your Inbox to the Saved category. 48 Working With SMS Text Messages Modifying messages You can modify any outgoing messages in your Saved or Sent categories. Tip:

You can create your own message template by modifying and resending a Sent message. 1. Open the message you want to change. 2. Tap the message text, or tap Edit. 3. Edit the message. 4. Tap Send. Tip: When modifying a message, you can keep the revised message without sending it by tapping Save instead of Send. Copying message text 1. Open the message you want to copy. 2. Select the text you want to copy. 3. Tap the Menu icon 4. Under Message, tap Put Into Clipboard. Tip:

To create a memo with the text, tap Create New Note instead. 5. Open the message or application where you want to insert the text. 6. Tap the Menu icon 7. Under Edit, tap Paste. Working With SMS Text Messages 49 Forwarding incoming messages 1. From the Inbox or Saved category, open the message you want to forward. 2. Tap the Menu icon 3. Under Message, tap Forward. Tip:

You can edit the forwarded message before sending it. 4. Enter the recipients mobile phone number. Note: The recipients phone must be SMS enabled. 5. Tap Send. 50 Working With SMS Text Messages Sorting messages 1. In the SMS Message Manager Inbox, select the category you want to sort. 2. Tap Show. 3. Select the sort method you want to use. Tap arrow to select sort method 4. Tap OK. Tip:

If you sort the list by name, messages from senders that are not in your Address Book appear at the bottom of the list in numerical order by phone number. Working With SMS Text Messages 51 Deleting messages 1. In the SMS Message Manager Inbox, select the category containing the messages you want to delete. 2. Tap the Menu icon 3. Under Message, tap Purge. 4. Select the deletion method you want to use. Tap arrow to select deletion method 5. Tap OK. 6. Tap Yes to confirm deletion. Tip: To delete a single message, open it and tap the Delete button. 52 Working With SMS Text Messages Enabling SMS Email To use SMS Email you must enter the your service providers SMS Email Center number. The SMS Email Center is where you send any SMS messages that are addressed to an email address instead of a mobile phone number. The SMS Email Center then forwards the message to the recipients email address. Contact your service provider to obtain their SMS Email Center number. 1. From any SMS Message Manager list view, tap the Menu icon 2. Under Options, tap Preferences. Enter SMS Email Center number Tip:

The SMS Message Center number is automatically supplied by your service provider is read from your SIM card. 3. Tap OK. Working With SMS Text Messages 53 54 Working With SMS Text Messages Using VisorPhone as a Wireless Modem In addition to using your VisorPhone as a phone, you can also use it as a modem that operates at 14.4Kbps or 9.6Kbp, depending on the speed of your service provider network. You can use your VisorPhones modem capabilities with third-party communication software that you download from the Internet, such as web browsers or email applications, and to perform wireless HotSync operations when your cradle is not available. Note: To use your VisorPhone as a modem, you must subscribe to the data services feature from your service provider. Contact your service provider for information on the data services feature. This chapter describes how to:

n Establish a TCP/IP connection for use with third-party software n Prepare for a direct wireless HotSync operation n Prepare for a network wireless HotSync operation n Perform a wireless HotSync operation Using VisorPhone as a Wireless Modem 55 Establishing a TCP/IP connection with VisorPhone Before using a third-party communication application, verify with the developer that it is compatible with VisorPhone. 1. Tap the Applications Launcher icon 2. Tap the Prefs icon 3. Tap Network in the pick list in the upper-right corner. 4. Enter the configuration information for your ISP. on the front of your handheld. Select your ISP from the Service pick list Enter your User Name, Password, and your ISPs phone number Note:

If your ISP is not on the Service pick list, tap the Menu icon tap New on the Service menu, and enter the service name.

, 5. Tap Connect and wait for a connection to establish. 6. Start the third-party application you want to use. To learn more about using your handheld with your ISP, see Network Preferences and TCP/IP Software in the Visor Handheld User Guide. 56 Using VisorPhone as a Wireless Modem Preparing for a direct wireless HotSync operation A direct wireless HotSync operation is when you dial a modem attached to your desktop computer to perform a remote HotSync operation. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon 3. Tap Enter Phone #. 4. Enter your computer modem number. Enter the number used to call your computer modem 5. Tap the Menu icon 6. Under Options, tap Modem Sync Prefs. 7. Tap Direct to modem, and then tap OK. 8. On a Windows computer, click the HotSync icon and check Modem on the HotSync Manager menu. On a Macintosh, open HotSync Manager and select Modem Setup on the Serial Port Settings tab. Using VisorPhone as a Wireless Modem 57 Preparing for a network wireless HotSync operation A network wireless HotSync operation is when you dial a modem attached to a network, such as a server on a corporate LAN, to perform a remote HotSync operation. Note: This feature is not available for the Macintosh. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon

. 3. Tap the Menu icon 4. Under Options, tap Modem Sync Prefs. 5. Tap Network, and then tap OK. 6. Tap Select Service and configure the Network Preferences panel. For information on the Network HotSync feature, see Conducting a HotSync operation via a network in Chapter 8 of the Visor Handheld User Guide, and for information on configuring the Network Preferences panel, see Network Preferences and TCP/IP Software in Chapter 9 of the Visor Handheld User Guide. Note:

7. On your desktop computer, click the HotSync icon Network on the HotSync Manager menu. and check 58 Using VisorPhone as a Wireless Modem Performing a wireless HotSync operation Since your VisorPhone operates as a modem at 14.4Kbps or 9.6Kbp, a wireless HotSync operation takes significantly longer than performing a HotSync operation with your cradle. Therefore, we recommend performing a wireless HotSync operation only when your cradle is not available. Tip: To increase the speed of a wireless HotSync operation, select Conduit Setup under Options and reduce the number of applications with which you synchronize. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon

. 3. Tap the Modem Sync icon 4. Wait for your VisorPhone to connect with the modem on the other end

. and for the HotSync operation to finish. Tip:

If necessary, you can cancel the procedure at any time by tapping the Cancel button Using VisorPhone as a Wireless Modem 59 60 Using VisorPhone as a Wireless Modem Customizing Your Phone The Phone application Preference screens enable you to customize many of the VisorPhone features to meet your individual needs. For example, you can choose which view appears when you start the Phone application, and set security options to prevent unauthorized use. Set dialing prefixes Select the ringer setting This chapter describes how to:

n n Reassign the buttons in your Address Book n Change the phone display n n Lock the keypad n Disable call waiting n Block your phone number for outgoing calls n n Connect a headset to your VisorPhone Select a different service provider network Customizing Your Phone 61 Setting dialing prefixes Some service providers require 11-digit dialing. If you already have 7-digit or 10-digit numbers in your Address Book, you can set your VisorPhone to automatically use 11-digit dialing by using a default area code. Using this feature does not change the numbers in your Address Book. 1. Press the Address Book button on the front of your handheld. 2. Tap the Menu icon 3. Under Options, tap Dial Preferences. Tap check box to insert an area code in front of 7-digit numbers before dialing Tap check box to insert a 1 in front of 10-digit numbers before dialing Enter default area code here 4. Tap OK. Note: You may be prompted to enter a default area code the first time you dial a number from your Address Book. 62 Customizing Your Phone Assigning dialing applications When you select a phone number or email address in Address Book, you can tap the Dial, SMS, or Email buttons to direct the selected information to a specific application. The default applications for these buttons are the Phone application and the SMS Message Manager, but you can also assign these buttons to any application that is compatible with the dialing-enabled version of Address Book. 1. Press the Address Book button on the front of your handheld. 2. Tap the Menu icon 3. Under Options, tap Dial Preferences. Tap pick lists to assign an application to that button 4. Tap OK. Customizing Your Phone 63 Changing the phone display 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Phone Preferences. 4. Select the display options you want to use. Tap the view you want to see when you open the Phone application 5. Tap OK. Tap an icon to skip that view when pressing the Phone button repeatedly 64 Customizing Your Phone Selecting the ringer settings 1. Tap the Menu icon 2. Under Options, tap Ringer Preferences. Tip:

The slider on your phone has two positions

. The two Ringer Preferences columns control the behavior of the corresponding slider position. and 3. Select the ringer settings you want to use. Tap Ring pick lists to select ring style Tap Volume pick lists to select volume level Tap Vibrate pick lists to turn vibrate mode on or off Tip:

You can use both a ring tone and vibrate alert or use them separately. For example, you can set one position to ring softly and vibrate, and the other position to vibrate only. To preview a new sound, select Play ring when changed. 4. Tap OK. Customizing Your Phone 65 Preventing unauthorized use You can protect your phone number from unauthorized use by locking your SIM card. 1. Turn on your phone. 2. Press the Phone button on your VisorPhone. 3. Tap the Menu icon 4. Under Options, tap Phone Preferences. 5. Select the Phone Locked check box to lock your SIM card. Tap here to lock and unlock the SIM card Tap here to define a new password 6. Enter your password and tap OK. Note:

If you havent set a password yet, check your service providers documentation for the default password. This is usually 1234. 7. Tap OK. 66 Customizing Your Phone Disabling call waiting If you receive a call while you are talking on the phone, the Phone application notifies you about the second call. If you dont want to be interrupted by other calls, you can disable call waiting. Note: Because call waiting information is stored by the network, its a good idea to check the current network settings both before and after you change the call waiting option. 1. Tap the Menu icon 2. Under Options, tap Call Preferences. 3. Disable the call waiting option. Tap here to disable call waiting Tap here to display current network settings Tap OK. 4. Tip: To reactivate Call Waiting, remove the check from the Disable Call Waiting check box. Customizing Your Phone 67 Blocking your phone number for outgoing calls When you place a call from your VisorPhone, the Phone application reveals your phone number to the person youre calling. If your service provider supports caller ID blocking, you can prevent revealing your phone number to people you call. Note: Because caller ID blocking information is stored by the network, its a good idea to check the current network settings both before and after you change the Block outgoing caller ID option. 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Call Preferences. 4. Enable the Block outgoing caller ID option. Tap here to place anonymous calls 5. Tap OK. 68 Customizing Your Phone Selecting a service provider network If you roam to an area where multiple service providers offer coverage, your VisorPhone automatically selects the provider with the strongest signal. However, if you prefer, you can manually select a service provider network. Note: When you manually select a network, your VisorPhone finds only that network until you either choose another network, or return to Automatic Mode. 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Select Network. 4. Select a network. Tap a network to enter manual mode Tap Automatic Mode to return to automatic search mode Tap OK. 5. Note: Selecting a new network may take 30 seconds or more. Customizing Your Phone 69 Connecting a headset Use the built-in speaker and microphone or connect an optional headset for hands-free operation. For best results, use only headsets from Handspring. Headset jack 70 Customizing Your Phone Using the Menus This section provides an overview of the menu options available in the Phone and SMS Message Manager applications. Some of the menu options vary based on which screen is active. Phone application Edit menus Speed Dial view Dialpad view Edit Speed Dial: Opens a dialog where you can define, change, and delete speed dial buttons. For details, see Changing a speed dial entry on page 38. Paste: Inserts a phone number from the clipboard into the dial box. Phone application Record menu Call History view Purge: Opens a dialog where you can remove selected records from the Call History list. For details, see Purging call history on page 34. Delete Item: Removes the selected record from the Call History list. Using the Menus 71 Phone application Options menu Phone Preferences: Opens a dialog where you can change your phone display and lock the phone. For details, see Changing the phone display on page 64 and see Preventing unauthorized use on page 66. Ringer Preferences: Opens a dialog where you can choose the ringer settings. For details, see Selecting the ringer settings on page 65. Call Preferences: Opens a dialog where you can choose call waiting, call blocking, and call forwarding settings. For details, see Disabling call waiting on page 67, Blocking your phone number for outgoing calls on page 68, and Forwarding calls on page 22. Select Network: Opens a dialog where you can search for and use networks other than your default network. For details, see Selecting a service provider network on page 69. Phone Info: Opens a dialog where you can view information about your phone such as the phone number and the IMEI number that uniquely identifies your phone to the network. About Phone: Opens a dialog where you can view version and copyright information for the Phone application. 72 Using the Menus SMS Message Manager application Message menus Inbox view Message view Delete: Opens a dialog where you can choose which messages you want to remove from the Inbox. For details, see Deleting messages on page 52. Put Into Clipboard: Copies the selected text to the clipboard so you can paste it into another message or application. For details, see Copying message text on page 49. Create New Note: Copies the selected text to a new Memo Pad memo. For details, see Copying message text on page 49. Save: Stores the selected message in the Saved category. Forward: Creates a copy of the selected message so you can send it to someone else. For details, see Forwarding incoming messages on page 50. Call Sender: Dials the person who sent the message. Using the Menus 73 SMS Message Manager application Edit menu Undo: Clears the last action. Cut: Removes the selected text and places it on the clipboard. Copy: Copies the selected text and places it on the clipboard. Paste: Inserts text stored on the clipboard at the current cursor position. Select All: Selects all text in the current record. Keyboard: Opens the onscreen keyboard. Graffiti Help: Opens screens that show you how to form Graffiti characters. 74 Using the Menus SMS Message Manager application Option menu Font: Opens a dialog where you can choose the font you want to use. Greeting: Opens a dialog where you can enter predefined opening and closing phrases to use in your messages. Preferences: Opens a dialog where you can view the SMS Service Center number (if this field is blank, contact your service provider for this information), choose deletion confirmation, and enter your service providers SMS Email Center number. For details, see Enabling SMS Email on page 53. About SMS: Opens a dialog where you can view version and copyright information for the SMS Message Manager application. Using the Menus 75 76 Using the Menus Troubleshooting and Maintenance If you encounter a problem with your VisorPhone module, check this section to see if your problem is listed. If your problem isn't listed here, or the suggestions don't resolve your problem, visit www.handspring.com for the latest troubleshooting and customer support information. My VisorPhone won't turn on n Make sure your VisorPhone is inserted firmly in the Springboard expansion slot. n Make sure your VisorPhone battery isn't drained. n When you turn on your VisorPhone, hold down the power button for at least two seconds, until you hear a beep. n Turn on your handheld to make sure that the handheld batteries aren't drained. Low batteries will prevent your VisorPhone from turning on. I get a message that my SIM card is missing when I turn on my VisorPhone n Make sure your SIM card is properly inserted. The metal contacts must face down (away from the battery), and the side with the corner cut must slide into the SIM slot first. For details, see Step 3: Insert your SIM card on page 5. n Your SIM card may be damaged. Contact your service provider for a new card. Troubleshooting and Maintenance 77 My VisorPhone requires an unlocking code, but I didn't set one I called my service provider to enable my phone service, but it still doesnt work My phone number isn't on the Phone Info screen n Your service provider may have set the locking code before you received your VisorPhone. Enter the default unlocking code: 1234 and then tap OK. If this doesn't work, contact your service provider. Note: It is actually locked your SIM card that is locked, not your VisorPhone. n If you see the Unblock Phone instead of the Unlock Phone screen, you entered the unlocking code incorrectly more than three times, and your VisorPhone is now blocked. Contact your service provider to obtain the unblocking code. Some service providers require 24 hours or more to activate your phone service. If it has been longer than your service providers activation period, report the problem to your service provider. Your service provider may need to install your phone number onto your SIM card. Contact your service provider to see if they can send a message to your VisorPhone that writes your phone number onto your SIM card. 78 Troubleshooting and Maintenance My VisorPhone won't register to the network I tried dialing a phone number, but my VisorPhone just beeps at me n You are probably outside a network coverage area. Try using another GSM phone to verify whether coverage is available in your current location. If coverage is available in your location, try your SIM card in another GSM phone. If it still doesnt, work, your SIM card may be malfunctioning. Contact your service provider for another SIM card. n n Turn off your VisorPhone, and then turn it on again. If a dialog appears asking if you want to search for a network, tap Yes. n Make sure you dialed the correct number. n Wait a few minutes and try again. If the network is very busy, calls cannot connect. n Verify that you are in a network coverage area and then move a few yards away and try the call again. If you are in a weak coverage area (1 bar of signal strength or less), you may not be able to complete calls even though you are registered to the network. I can't dial international numbers Call waiting doesnt work For security purposes, most service providers require you to enable international calling on your account. Call your service provider to enable international calling. Enable call waiting in the Call Preferences dialog box. For details, see Disabling call waiting on page 67. Troubleshooting and Maintenance 79 Call forwarding doesn't work Caller ID blocking for my outgoing calls doesn't work Some peoples names dont appear in Call History I cant send SMS Messages For security purposes, most service providers require you to enable this feature on your account even though there is usually no extra charge. Call your service provider to enable call forwarding. Some service providers require you to enable this feature on your account. Call your service provider to enable blocking your Caller ID. n Call History shows names only if the person's name and the phone number they called from are in your Address Book. n Find out if a caller has blocked their Caller ID. n Check the SMS Preferences dialog box to see if the SMS Message Center number is on this screen. If the number is missing, contact your service provider for the SMS Message Center number and enter it in the SMS Preferences dialog box. n Make sure SMS services are enabled on your account. n Verify that you are in a GSM coverage area. n Make sure the destination number is correct. Some service providers require 11-digit phone numbers for SMS messages. 80 Troubleshooting and Maintenance I get an error message when I send an SMS message to an email address Some phone numbers dont appear in the SMS Lookup The applications I assigned to the Dial, Email, and SMS or Phone buttons in the Dialing Address Book dont launch You need to enter the SMS Email Center number in the SMS Preferences dialog box. This number is different from the SMS Message Center number you use to send messages to other mobile phone numbers. For more information, see Enabling SMS Email on page 53. Make sure the number you want is identified as a mobile number in your Address Book. Only mobile phone numbers appear when you use the SMS Message Manager Lookup button. n Check the Dial Preferences dialog box in the Address Book to confirm the application is assigned to the Dial, Email, or SMS button. For details, see Assigning dialing applications on page 63. n Contact the software developer for the application you want to use when you tap the button, and verify that the software is compatible with the new Dialing Address Book and the version of Palm OS your VisorPhone uses. To take advantage of these buttons, an application must contain special code that registers its capabilities to the Address Book. I can't make data calls n Verify that data calls are enabled on your account. n Verify that you are in a coverage area. Troubleshooting and Maintenance 81 I can't synchronize when my VisorPhone is connected to my handheld Make sure that there are no active calls on your VisorPhone before you begin a HotSync operation. You cannot synchronize while you have an active call, and you cannot make or receive calls during a HotSync operation. Caring for your VisorPhone module n Keep your VisorPhone and its accessories out of the reach of small children. n Keep you VisorPhone dry. n Use your VisorPhone at normal temperatures (between -4 degrees and 130 degrees Fahrenheit). Temperatures outside of this range may cause damage to your VisorPhone. n Keep your VisorPhone away from dusty or dirty areas. n Do not disassemble your VisorPhone. n Do not use harsh detergents to clean your VisorPhone. n Use only genuine Handspring accessories. Third party accessories are not guaranteed to function properly with your VisorPhone. n Do not let the Springboard contacts on your VisorPhone come in direct contact with conductive or electronic objects. n Do not short any contacts on your VisorPhone module or the Springboard connectors. 82 Troubleshooting and Maintenance Caring for the battery Your VisorPhone uses a 680mAh Lithium Ion battery. A fully-charged battery provides approximately 3 hours of talk time and more than 70 hours of standby time. Follow these guidelines to get the most from your battery:

n Do not disassemble the battery pack. n If you are not using your VisorPhone for an extended period of time, disconnect the battery pack from the phone and store it in a cool, dry place; charge the battery at least once every six months when not in use. n Use your VisorPhone at normal temperatures (between -4 degrees and 130 degrees Fahrenheit). Using your VisorPhone outside of the normal temperature range can severely decrease the battery performance. n Never throw the battery pack into fire or expose it to extreme heat. n If the battery pack ever becomes hot or smells odd, stop using it. If the battery pack becomes damaged and leaks liquid, stop using it and avoid skin contact with the leaking liquid. n n Use only a genuine Handspring battery pack. Third party battery packs are not guaranteed to function properly with your VisorPhone. n Always replace the battery pack with the same type of pack. Using another type of battery pack may cause an explosion. n Do not short any battery contacts or let the contacts come in direct contact with conductive or electronic objects. n Be sure to properly dispose of the battery. For more information, see How do I dispose of the battery? on page 84. Troubleshooting and Maintenance 83 How do I dispose of the battery?

When your battery fails to hold a charge, you need to replace it. Caution:

It is illegal in many areas to dispose of Lithium Ion batteries in household or business trash. Call your local recycling center for instructions on battery recycling, or contact Handspring for safe disposal options. Do not handle a damaged or leaking battery. 84 Troubleshooting and Maintenance Warranty and Other Product Information Handspring, Inc. Limited Warranty HARDWARE: Handspring, Inc. (Handspring), warrants to the original end user (Customer) that this product will be free from defects in workmanship and materials, under normal intended use, for one year from the date of original purchase from Handspring. Handspring's sole obligation under this express war-

ranty shall be, at Handspring's option and expense, to replace the product or part with a comparable product or part, repair the product or part, or if neither repair nor replacement is reasonably available, Handspring may, in its sole discretion, refund to Customer the purchase price paid for the product or part. Replacement products or parts may be new or reconditioned. Handspring warrants any replaced or repaired product or part, and any hardware upgrade to which Customer is entitled under an agreement between Customer and Handspring, for a period of ninety (90) days from shipment, or through the end of the original warranty, whichever is longer. All products or parts that are replaced become the property of Handspring. Accessory products, as listed in the applicable Handspring catalogue, are not covered under this Limited Warranty. Handspring shall not be responsible for Customer's software, firmware, information, or memory data contained in, stored on, or integrated with any products returned to Handspring for repair, whether under warranty or not. SOFTWARE: Handspring warrants to Customer that the Desktop organizer software licensed from it will perform in substantial conformance to their program specifications, for a period of ninety (90) days from the date of original purchase from Handspring. Handspring warrants the media containing software against fail-

ure during the warranty period. No updates are provided. Handspring does not provide any warranty for any third party applications software that is licensed to Customer by the third party. Handspring's sole obliga-

tion with respect to this express warranty shall be (at Handspring's discretion) to refund the purchase price paid by Customer for any defective software product, or to replace any defective media with software which substantially conforms to applicable Handspring published specifications. Handspring makes no warranty or representation that its software products will meet Customer's requirements or will work in combination with any hardware or applications software products provided by third parties, that the operation of the soft-

ware products will be uninterrupted or error free, or that all defects in the software products will be correct-

ed. OBTAINING WARRANTY SERVICE: Customer must contact Handspring within the applicable war-

ranty period to obtain warranty service authorization. Dated proof of original purchase from Handspring will be required. Handspring is not responsible for Customer products or parts received without a warranty service authorization. In the United States, Handspring may ship a replacement product or part prior to re-

Warranty and Other Product Information 85 ceiving the original product or part (advance exchange). If advance exchange is not available, then the re-

paired product or part will be shipped as soon as reasonably possible, which will be no later than thirty (30) days after Handspring receives the original product or part. Repaired or replacement products will be shipped to Customer at Handspring's expense. The repair and replacement process for products or parts in locations outside of the United States will vary depending on Customer's location. Products or parts shipped by Customer to Handspring must be sent prepaid and packaged appropriately for safe shipment, and it is recommended that they be insured or sent by a method that provides for tracking of the package. When an advance exchange is provided and Customer fails to return the original product or part to Handspring within thirty (30) days from the date the warranty service authorization is issued, Handspring will charge Customer the then current published catalogue price of such product or part. WARRANTIES EXCLUSIVE: IF THIS PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER'S SOLE REMEDY FOR BREACH OF THAT WARRANTY SHALL BE RE-

PLACEMENT OR REPAIR OF THE PRODUCT OR PART OR REFUND OF THE PURCHASE PRICE PAID, AT HANDSPRING'S OPTION. TO THE FULL EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PUR-

POSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, AND NON IN-

FRINGEMENT, ALL OF WHICH ARE EXPRESSLY DISCLAIMED BY HANDSPRING and ITS SUPPLIERS. HANDSPRING NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTAL-

LATION, MAINTENANCE OR USE OF ITS PRODUCTS. HANDSPRING AND ITS SUPPLIERS SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT OR MAL-

FUNCTION IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER'S OR ANY THIRD PERSON'S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UN-

AUTHORIZED ATTEMPTS TO OPEN, REPAIR, OR MODIFY THE PRODUCT, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHT-

NING, OTHER HAZARDS, OR ACTS OF GOD. THIS WARRANTY DOES NOT COVER PHYSI-

CAL DAMAGE TO THE SURFACE OF THE PRODUCT, INCLUDING CRACKS OR SCRATCHES ON THE LCD TOUCHSCREEN OR OUTSIDE CASING. THIS WARRANTY DOES NOT APPLY WHEN THE MALFUNCTION RESULTS FROM THE USE OF THIS PRODUCT IN CONJUNCTION WITH ACCESSORIES, OTHER PRODUCTS, OR ANCILLARY OR PERIPHER-

AL EQUIPMENT AND HANDSPRING DETERMINES THAT THERE IS NO FAULT WITH THE PRODUCT ITSELF. THIS WARRANTY DOES NOT APPLY TO ANY MALFUNCTION OR FAIL-

86 Warranty and Other Product Information URE OF THE PRODUCT OR PART DUE TO ANY COMMUNICATION SERVICE CUSTOMER MAY SUBSCRIBE TO OR USE WITH THE PRODUCT. LIMITATION OF LIABILITY: TO THE FULL EXTENT ALLOWED BY LAW, HANDSPRING ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUEN-

TIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REV-

ENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF INFORMATION OR DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLA-

TION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF THIS PRODUCT, EVEN IF HANDSPRING HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND LIMITS ITS LIABILITY TO REPLACEMENT, REPAIR, OR REFUND OF THE PURCHASE PRICE PAID, AT HANDSPRING'S OPTION. THIS DISCLAIMER OF LIABILITY FOR DAMAGES WILL NOT BE AFFECTED IF ANY REMEDY PROVIDED HEREIN SHALL FAIL OF ITS ESSENTIAL PURPOSE. NOTICE TO CONSUMERS: Some countries, states, or provinces do not allow the exclusion or limita-

tion of implied warranties or the limitation of incidental or consequential damages for certain products sup-

plied to consumers, or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in their application to you. When the implied warranties are not allowed to be excluded in their entirety, they will be limited to the duration of the applicable written warranty. This warranty gives you specific legal rights which may vary depending on local law. GOVERNING LAW: This Limited Warranty shall be governed by the laws of the State of California, U.S.A. as such laws are applied to agreements entered into and to be performed entirely within California between California residents and by the laws of the United States, excluding its conflicts of laws principles and excluding the United Nations Convention on Contracts for the International Sale of Goods. Warranty and Other Product Information 87 Handspring, Inc. End User Software License Agreement THIS PRODUCT CONTAINS SOFTWARE, THE USE OF WHICH IS LICENSED BY HAND-

SPRING, INC. AND ITS SUPPLIERS (COLLECTIVELY, HANDSPRING), TO ITS CUSTOMERS FOR THEIR USE ONLY AS SET FORTH BELOW. SOFTWARE LICENSE: Handspring grants you a nonexclusive license to use the accompanying software program(s) (the Software) subject to the terms and restrictions set forth in this End User Software License Agreement (License Agreement). You are not permitted to lease or rent, distribute or sublicense the Soft-

ware or to use the Software in a time-sharing arrangement or in any other unauthorized manner. Further, no license is granted to you in the human readable code of the Software (source code). Except as provided below, this License Agreement does not grant you any rights to patents, copyrights, trade secrets, trademarks, or any other rights in respect to the Software. The Software is licensed to be used solely on or in connection with Handspring products. With respect to the Desktop Software, you may reproduce and provide one (1) copy of such Software for each personal computer on which such Software is used as permitted hereunder. With respect to the Device Software, you may use such Software only on one (1) Handspring product. Otherwise, the Software and supporting documentation may be copied only as essential for backup or archive purposes in support of your use of the Software as per-

mitted hereunder. You must reproduce and include all copyright notices and any other proprietary rights no-

tices appearing on the Software on any copies that you make. Notwithstanding any other provision of this License Agreement, this License Agreement shall not be deemed to apply to any applications software licensed to you by third parties that is included on the same media as Handspring's Software (Other Software) if the Other Software provides that the use of the Other Software is subject to the terms and conditions of the third party's license agreement. Portions of the Software are licensed to Handspring, and from Handspring to you, pursuant to the GNU Li-

brary General Public License (GNU Software), a copy of which is supplied herewith and incorporated herein in its entirety by this reference. Notwithstanding any other provision of this License Agreement, this License Agreement shall not be deemed to apply to the GNU Software. Source code versions of the GNU Software are available at Handspring's web site, currently located at www.handspring.com. PAYMENT OF FEES: The effectiveness of the licenses granted hereunder is conditioned on the receipt by Handspring of any applicable fees. 88 Warranty and Other Product Information NO ASSIGNMENT; NO REVERSE ENGINEERING: You may transfer the Software and this License Agreement to another party in connection with a transfer of the Handspring product upon which the Soft-

ware is used, if the other party agrees in writing to accept the terms and conditions of this License Agree-

ment. If you transfer the Software, you must at the same time either transfer all copies of the Software as well as the supporting documentation to the same party or destroy any such materials not transferred. Except as set forth above, you may not transfer or assign the Software or your rights under this License Agreement. Modification, reverse engineering, reverse compiling, or disassembly of the Software is expressly prohibited. However, if you are a European Union (EU) resident, information necessary to achieve interoperability of the Software with other programs within the meaning of the EU Directive on the Legal Protection of Computer Programs is available to you from Handspring upon written request. EXPORT RESTRICTIONS: You agree that you will not export or re-export the Software or accompa-

nying documentation (or any copies thereof) or any products utilizing the Software or such documentation in violation of any applicable laws or regulations of the United States or the country in which you obtained them. The software covered by this License Agreement may contain strong data encryption code which can-

not be exported outside of the U.S. or Canada. You agree that you will not export/reexport, either physically or electronically, the encryption software or accompanying documentation without obtaining written autho-

rization from the U.S. Department of Commerce. UNITED STATES GOVERNMENT LEGEND: If you are acquiring the Software on behalf of any unit or agency of the United States Government, the following provisions apply. The Software constitutes a commercial item, as that term is defined at Federal Acquisition Regulation (FAR) 2.101 (Oct. 1995), con-

sisting of commercial computer software and commercial computer software documentation, as such terms are used in FAR 12.212 (Sept. 1995), and is provided to the U.S. Government only as commercial soft-

ware (with Restricted Rights, if applicable). Use, duplication, or disclosure by the U.S. Government is sub-

ject to restrictions set forth in this License Agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. TERM AND TERMINATION: This License Agreement is effective until terminated. You may termi-

nate it at any time by destroying the Software and documentation together with all copies and merged por-

tions in any form. It will also terminate immediately if you fail to comply with any term or condition of this License Agreement. Upon such termination you agree to destroy the Software and documentation, together with all copies and merged portions in any form. Warranty and Other Product Information 89 GOVERNING LAW: This License Agreement shall be governed by the laws of the State of California as such laws are applied to agreements entered into and to be performed entirely within California between Cal-

ifornia residents and by the laws of the United States. You agree that the conflicts of laws principles of such laws and the United Nations Convention on Contracts for the International Sale of Goods (1980) are hereby excluded in its entirety from application to this License Agreement. LIMITED WARRANTY; LIMITATION OF LIABILITY: All warranties and limitations of liability ap-

plicable to the Software are as stated on the Limited Warranty or in the product manual accompanying the Software. Such warranties and limitations of liability are incorporated herein in their entirety by this refer-

ence. SEVERABILITY: In the event any provision of this License Agreement is found to be invalid, illegal or un-

enforceable, the validity, legality and enforceability of any of the remaining provisions shall not in any way be affected or impaired and a valid, legal and enforceable provision of similar intent and economic impact shall be substituted therefor. ENTIRE AGREEMENT: This License Agreement sets forth the entire understanding and agreement be-

tween you and Handspring, supersedes all prior agreements, whether written or oral, with respect to the Soft-

ware, and may be amended only in a writing signed by both parties. Safety And General Information IMPORTANT INFORMATION ON SAFE AND EFFFICIENT OPERATION. Read this information before using your integrated multi-service portable radio. For the Safe and Efficient Operation of Your Radio, Observe These Guidelines:

Your radio product contains a transmitter and a receiver. When it is ON, it receives and transmits radio fre-

quency (RF) energy. The radio operates in the frequency range of 800 MHz to 1990 MHz and employs digital modulation techniques. When you use your radio, the system handling your call controls the power level at which your radio transmits. The output power level typically may vary over a range from .001 Watts to 2 Watts. 90 Warranty and Other Product Information Exposure To Radio Frequency Energy Your VisorPhone Radio Product is designed to comply with the following national and international stan-

dards and guidelines regarding exposure of human beings to radio frequency electromagnetic energy:

n United States Federal Communications Commission, Code of Federal Regulations; 47 CFR part 2 sub-part J American National Standards Institute (ANSI) IEEE. C95. 1-1992 National Council on Radiation Protection and Measurements (NCRP). Report 86 International Commission on Non-Ionizing Radiation Protection (ICNIRP) 1998 National Radiological Protection Board of the United Kingdom, GS 11, 1988 Verband Deutscher Elektrotechniker (VDE) DIN-0848 Department of Health and Welfare Canada. Safety Code 6 n n n n n n To assure optimal radio performance and make sure human exposure to radio frequency electromagnetic energy is within the guidelines set forth in the above standards, always adhere to the following procedure:

When placing or receiving a phone call hold the radio as you would a telephone. Speak directly into the mi-

crophone and position the antenna up over your shoulder. For body-worn operation, the antenna should be kept at least one inch from the body when transmitting. A carry holder with a belt clip is available from handspring.com for body-worn use. When using any data feature of the radio, with or without an accessory cable, position the antenna of the radio product at least one inch (2.5 cm) away from the body. DO NOT hold the antenna when the radio is IN USE. Holding the antenna affects call quality and may cause the radio to operate at a higher power level than needed. Interference to Medical and Personal Electronic Devices Most electronic equipment is shielded from RF energy. However, certain equipment may not be shielded against the RF signals from your wireless phone. Warranty and Other Product Information 91 Pacemakers The Health Industry Manufacturers Association recommends that a minimum separation of six inches (6") be maintained between a handheld wireless phone and a pacemaker to avoid potential interference with the pacemaker. These recommendations are consistent with the independent research by the recommendations of Wireless Technology Research. Persons with pacemakers should:

n ALWAYS keep the phone more than six inches from their pacemaker when the phone is turned ON. not carry the phone in a breast pocket. use the ear opposite the pacemaker to minimize the potential for interference. turn the phone OFF immediately if you have any reason to suspect that interference is taking place. n n n Hearing Aids Some digital wireless phones may interfere with some hearing aids. In the event of such interference, you may want to consult your hearing aid manufacturer to discuss alternatives. Other Medical Devices If you use any other personal medical device, consult the manufacturer of your device to determine if it is ad-

equately shielded from external RF energy. Your physician may be able to assist you in obtaining this infor-

mation. Turn your phone OFF in health care facilities when any regulations posted in these areas instruct you to do so. Hospitals or health care facilities may be using equipment that could be sensitive to external RF energy. Interference to Other Electronic Devices RF energy may affect improperly installed or inadequately shielded electronic operating and entertainment systems in motor vehicles. Check with the manufacturer or representative to determine if these systems are adequately shielded from external RF energy. Also check with the manufacturer of any equipment that has been added to the vehicle. Turn your radio OFF before boarding any aircraft to prevent possible interference to aircraft systems. Reg-

ulations of the United states Federal Aviation Administration prohibit use when the aircraft is in the air and require you have permission from a crew member to use your radio while the aircraft is one the ground. 92 Warranty and Other Product Information Safety and General Use While Driving Check the laws and regulations on the use of telephones in the area where you drive. Always obey them. When using the phone while driving, please:

n Give full attention to driving and to the road Use hands-free operation, if available Pull off the road and park before making or answering a call if driving conditions so require. n n Canadian RFI Statement This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numrique de la classe B respecte toutes les exigences du Rglement sur le matriel brouilleur du Canada. Acknowledgments We would like to thank the following developers whose contributions were an integral part of the Hand-

spring product:

n n Rindel & Partner GmbH OPTION International Group www.rindle.de OPTION International Group www.option.com Warranty and Other Product Information 93 94 Warranty and Other Product Information adding from Call History 14 adding to Speed Dial 37 dialing from 15 Dialing Preferences 63 Index Numerics 3-way calling 27 A Active call 11, 23 Address Book Adjusting volume 4 Answering calls 1921 Antenna 3 B Battery care 83 charging 7 disposal 84 gauge 11 indicators 7 location 3 specifications 83 Beep tone 21 Buttons Phone 4 power 3 ringer 4 scroll 4, 13, 42 slider 4 SMS Message Manager 4 C Call Preferences 21, 22, 67, 68, 72 status 24, 26, 27 waiting 21, 67 Call History 17 adding to Address Book 14 adding to Speed Dial list 14 deleting items 34 dialing from 14 displaying 33 icon 14 incoming calls 33 missed calls 17, 29, 30, 33 outgoing calls 33 purging 34 Caller ID 17, 20, 21, 32, 68 Index 95 Calls 3-way 27 active 11, 23 answering 1921 answering call waiting 21 conference 27 forwarding 22 ignoring 20 incoming 1922, 33 missed 17, 30, 33 outgoing 1118, 33, 68 placing a second 25 placing on hold 24 switching 26 Conference calls 27 Coverage area 10, 17, 19, 22, 29, 44, 48 D Deleting Dialing Call History 34 SMS messages 32, 44, 52 Speed Dial entries 39 applications 63 emergency numbers 18 from Address Book 15 from Call History 14, 30, 33 from Memo Pad 16 from To Do List 16 last number 14 prefixes 62 previous numbers 13, 14, 33 with Dialpad 13 with Speed Dial 12 Dialpad dialing numbers 13 icon 13 E Edit call forwarding number 22 menu 71, 74 phone number 13, 15, 16, 37 SMS messages 49, 50 Speed Dial 38, 40 Email messages 41, 43, 46, 53 Emergency numbers 18 F Forwarding calls 22 SMS Email 53 SMS messages 50, 73 96 Index Frequently asked questions 7782 G Greetings 47 H Headset connecting 70 jack 3 Hold button 24 HotSync operations 5559, 82 I Icons battery 11 Call History 14, 30 Dialpad 13 signal strength 11 Speed Dial 12 Voicemail 11 Ignoring calls 20 Incoming calls 1922, 33 Indicators battery 4, 7, 11 Call History 33 call status 24, 26, 27 call waiting 21 missed call 17 network service 4, 10, 11 signal strength 11 voicemail 11 K Key Pad 11, 12, 31 L LED 3, 4, 7, 10 License agreement 88 Light, see LED 4 Limited warranty 85 Locking phone 66 M Memo Pad 16 Menus Message Manager, see SMS menus 73 status 48 Messages checking 2933 expiration 48 Phone application 7172 SMS Message Manager 7375 Index 97 missed call 17 purging SMS 52 replying 43 sorting SMS 51 text 10, 29, 32, 42 voicemail 10, 31 Missed calls 17, 30, 33 Modem 5559 Module inserting 6 removing 6 N Network coverage area 10 HotSync operation 58 name 11 selecting 69, 72 status 4, 68 voicemail number 36 Network status 22, 67 O Options Call Preferences 67, 68 call waiting 67 menu 72, 75 Phone Preferences 64 Ringer Preferences 65 Outgoing calls 1118, 33, 68 P Password 8, 66 Phone application starting 13 Phone button 4 Phone number checking 9 editing 13 Power button 3 Preferences Call 68 call waiting 67 dialing 63 Phone 64 ringer 65 Prefixes 62 Purging Call History 34 SMS messages 52 R Record menu 71 Redialing a number 14 98 Index Ringer button 4 settings 65 S Safety 10, 83, 9093 Scroll buttons 4, 13, 42 Security 66 Setup 29 Signal strength 11, 69 Signatures 47 SIM card defined 1, 5 IMEI 9 inserting 5 locking 66 phone number 9 SMS Message Center number 53 Slider 3, 4, 65 SMS changing messages 49 copying text 49 creating messages 44 email messages 46, 53 forwarding messages 50 greetings 47 Inbox 42 menus 7375 message expiration 48 Message Manager button 4 messages 29, 32 Preferences 53 purging messages 52 replying to messages 43 saving messages 48 signatures 47 sorting messages 51 Software license 88 Sorting messages 51 Speaker 3, 4, 70 Speed Dial adding Address Book entries 37 adding Call History entries 14 changing entries 38 defining buttons 36 deleting entries 39 dialing numbers 12 icon 12 list 3540 organizing 35, 40 voicemail 31, 36 Index 99 Support 77 Switching calls 26 T Text messages, see SMS To Do List 16 Troubleshooting 7782 V Vibrate 65 VisorPhone inserting 6 parts of 3 removing 6 turning on 8 icon 11 Volume 4 W Warranty 85 Wireless HotSync operations Voicemail 10, 17, 20, 29, 31, 36 synchronization, see 100 Index

 

 

Applicant: Handspring, Inc. Correspondence Reference Number: 17208 731 Confirmation Number: EA98852 Answer to question #4 This is the RF Exposure warning that will appear in the VisorPhone manual. Exposure To Radio Frequency Energy Your VisorPhone Radio Product is designed to comply with the following national and international standards and guidelines regarding exposure of human beings to radio frequency electromagnetic energy:

United States Federal Communications Commission, Code of Federal Regulations; 47 CFR part 2 sub-part J American National Standards Institute (ANSI) IEEE. C95. 1-1992 National Council on Radiation Protection and Measurements (NCRP). Report 86 International Commission on Non-Ionizing Radiation Protection (ICNIRP) 1998 National Radiological Protection Board of the United Kingdom, GS 11, 1988 Verband Deutscher Elektrotechniker (VDE) DIN-0848 Department of Health and Welfare Canada. Safety Code 6 To comply with the above FCC Regulations governing human exposure to radio frequency energy, users MUST adhere to the following procedure:

To comply with FCC RF exposure guidelines during body-worn operation, use the Handspring Belt Clip or the Handspring Holster. Use of other body worn accessories that have not been tested with the VisorPhone for RF exposure compliance may not comply. 1

 

 

Exposure To Radio Frequency Energy Your VisorPhone Radio Product is designed to comply with the following national and international standards and guidelines regarding exposure of human beings to radio frequency electromagnetic energy:

United States Federal Communications Commission, Code of Federal Regulations; 47 CFR part 2 sub-part J American National Standards Institute (ANSI) IEEE. C95. 1-1992 National Council on Radiation Protection and Measurements (NCRP). Report 86 International Commission on Non-Ionizing Radiation Protection (ICNIRP) 1998 National Radiological Protection Board of the United Kingdom, GS 11, 1988 Verband Deutscher Elektrotechniker (VDE) DIN-0848 Department of Health and Welfare Canada. Safety Code 6 To comply with the above FCC Regulations governing human exposure to radio frequency energy, users MUST adhere to the following procedures:

For body-worn operation, the antenna should be kept at least one inch from the body when transmitting. A carry holder with a belt clip is available from handspring.com for body-worn use. When using any data feature of the radio, with or without an accessory headset cable, position the radio product at least one inch (2.5 cm) away from the body. When placing or receiving a phone call hold the radio as you would a telephone. To assure optimal radio performance, always adhere to the following procedures:

Speak directly into the microphone and position the antenna up over your shoulder. DO NOT hold the antenna when the radio is IN USE. Holding the antenna affects call quality and may cause the radio to operate at a higher power level than needed. Interference to Medical and Personal Electronic Devices Most electronic equipment is shielded from RF energy. However, certain equipment may not be shielded against the RF signals from your wireless phone.

 

 

Development Kit for Handspring Handheld Computers Release 1.0 9/13/99 Version 0.9 Information herein is preliminary and subject to change without notice. Copyright 1999 by Handspring, Inc. All rights reserved. TRADEMARK ACKNOWLEDGMENT Handspring, Visor, and Springboard are trademarks of Handspring, Inc. All other trademarks are the properties of their respective owners. Document number: 80-0004-00 Handspring, Inc. 189 Bernardo Ave. Mountain View, CA 94043-5203 TEL: (650) 230-5000 FAX: (650) 230-2100 www.handspring.com ii Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 9/13/99 Table of contents Section I Introduction Chapter 1 Application Development for a Handspring Handheld Computer Chapter 2 Application development for a Handspring Springboard module 2.1 2.2 Springboard memory-based module software development Specialized Springboard module hardware and software design I-3 I-4 I-4 I-5 Section II Springboard expansion slot Chapter 1 Application development to support plug & play 1.1 1.2 Generic Applications Special-Purpose Applications Chapter 2 Module design details 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Memory Space Module access time and wait state Interrupts Interrupt Latency Reset Power Management Power Management Options for Interrupt Handlers Module Insertion Notification Catching Module Removals Chapter 3 Springboard Software Integration 3.1 3.2 3.3 3.4 Module setup application Overriding Module Software Module welcome application Interrupt Handler Interaction Chapter 4 Software API Extension 4.1 4.2 4.3 4.4 4.5 Checking Presence and Version of Handspring Extensions Utility Calls Generic Module Support in PalmOS Copy Protecting Module Applications API Calls 4.5.1 HsAppEventHandlerSet 4.5.2 HsAppEventPost 4.5.3 HsCardAttrGet 4.5.4 HsCardAttrSet 4.5.5 HsCardErrTry/HsCardErrCatch 4.5.6 HsCardEventPost 4.5.7 HsCardPatchInstall 4.5.8 HsCardPatchPrevProc 4.5.9 HsCardPatchRemove 4.5.10 HsDatabaseCopy 4.5.11 HsEvtResetAutoOffTimer II-2 II-3 II-3 II-5 II-5 II-6 II-6 II-7 II-7 II-7 II-8 II-9 II-10 II-12 II-12 II-15 II-16 II-16 II-18 II-18 II-19 II-19 II-20 II-21 II-22 II-23 II-24 II-26 II-27 II-29 II-30 II-32 II-33 II-34 II-36 Copyright 1999 by Handspring, Inc. All rights reserved. 1 9/13/99 Version 1.0 Chapter 5 External Interface 5.1 5.2 Pinout Signal Descriptions Chapter 6 Electrical and mechanical specifications 6.1 6.2 6.3 6.4 6.5 Absolute electrical maximum ratings DC electrical characteristics AC Characteristics Springboard connector insertion/extraction force ratings Springboard module base color Chapter 7 HsExt.h Header File Section III Cradle connector Chapter 1 Functional Description Chapter 2 Signal Descriptions Chapter 3 Keyboard Support via Remote UI 3.1 3.2 3.3 3.4 3.5 Remote UI Packet Description Remote UI Packet Header Remote UI Packet Body CRC Computation Remote UI Packet Example Section IV Development Tools Section V Mechanical Information Chapter 1 Visor handheld Chapter 2 Springboard module with battery Chapter 3 Springboard standard module Chapter 4 Cradle base Chapter 5 Cable connectors Section VI Compatibility Testing Chapter 1 PalmOS Software Applications Chapter 2 Springboard-Specific Software Applications Chapter 3 Springboard-Specific Hardware/Software Applications Section VII Handspring Licensing Section VIII Approved Vendor List Section IX Trademarks and Logos Chapter 1 Overview Chapter 2 Logos II-37 II-39 II-40 II-43 II-43 II-43 II-44 II-45 II-46 II-47 III-2 III-4 III-6 III-6 III-7 III-9 III-9 III-11 V-2 V-3 V-4 V-5 V-6 VI-2 VI-3 VI-4 IX-1 IX-4 Copyright 1999 by Handspring, Inc. All rights reserved. 2 Version 1.0 Section I Introduction The Visor handheld computer is Handsprings first generation of PalmOS-compatible products. It is 100% compatible with existing software applications currently available for PalmOS 3.1-compatible platforms. In addition, it has a key enhancement that provides unparalleled flexibility for application and peripheral developers: the Springboard expansion slot. The Springboard expansion slot supports true hot plug & play capability of removable plug-in modules for the Visor handheld. This developers kit contains all the necessary information required by developers to manufacture Springboard-compatible modules. This document includes the following information on the Springboard expansion slot:

Electrical design specifications Software design integration information Handsprings PalmOS API extension definition Mechanical design Licensing information For developers designing products that communicate with the Visor handheld via the Handspring cradle connector, this kit also contains the cradle connectors electrical and mechanical design specifications, as well as information on applicable Handsprings API extensions. Copyright 1999 by Handspring, Inc. All rights reserved. Section I - 1 Section I: Introduction Version 1.0 Mechanical information included in this kit is in DXF, IGES, and Pro-E formats. Design files for a standard Springboard module, the Visor cradle assembly and the exterior dimensions of the Visor handheld are included. How to Contact Handspring Handsprings on-line developer support web site is currently under construction, therefore we are currently offering support to our developers via e-mail. If you have any technical questions regarding the contents of this package, or if you require further technical support, please contact DevSupport@handspring.com. If you have any business questions regarding this package, please go to the Developer Program section of Handsprings web site. Section I - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Application Development for a Handspring Handheld Computer Chapter 1 Application Development for a Handspring Handheld Computer As previously mentioned, the Visor handheld is Handsprings first implementation of a handheld computer. It has been certified as 100% compatible with the PalmOS version 3.1. Thus any application designed for the Palm Computing Platform and running on a PalmOS 3.1-based device will run on Visors internal memory without modification. Developers should already be familiar with PalmOS application design before beginning development of applications for Handsprings handheld computer. This development kit does not contain information regarding the design and implementation of standard PalmOS applications. For this information, please refer to the PalmOS SDK documentation provided by 3Com at http://www.palm.com/devzone/. Tools for developing PalmOS applications can be purchased from Metrowerks (http://

www.metrowerks.com). CodeWarrior for PalmOS is the name of Metrowerks integrated PalmOS development package; it includes a compiler, linker, assembly-level debugger, and Palm emulator. Note that the Palm emulator in CodeWarrior does not currently support Handsprings PalmOS API extensions that support Springboard module described in this development kit. Also provided with this kit is a complete GNU tool kit that can be used to develop applications for the Visor handheld and your Springboard or cradle module in lieu of CodeWarrior. Documentation on how to use the GNU tool kit is included when you install it on your PC. Note that the Visor handheld ROM cannot be used with the current version of POSE (PalmOS Emulator) because of minor modifications to the hardware design such as button configuration. However, Handsprings future goal is to provide a version of POSE that will supports Visor hardware. Also included in this developer kit is a new Desktop software that supports the Visors USB interface. You must install this software to communicate with and download your application to the handheld. The Visor handheld supports USB for higher rates of data synchronization with a personal computer. Note that the Visor handheld cradle can be purchased in two configurations:

serial or USB. USB is the standard configuration and can be used with PCs running Windows 98 or 2000, and Apple computers that have a USB connector. Serial is recommended for PCs running Windows 95 and NT, as these operating systems do not have reliable built-in USB support. Whatever cradle you use, you must install the Desktop software provided by Handspring. Copyright 1999 by Handspring, Inc. All rights reserved. Section I - 3 Section I: Introduction Version 1.0 Chapter 2 Application development for a Handspring Springboard module As mentioned in the previous chapter, software for the Visor handheld can be developed in the same way as any PalmOS-based application. When you want to transfer your application to a Springboard-compatible memory module or build a specialized module (a module with special hardware in it), you must use Handsprings new development tools. 2.1 Springboard memory-based module software development If you are an application developer who simply wants to transfer your application to a non-volatile Springboard memory module, Handspring has set up a supplier to program multiple cards with your software. You simply need the Palm-makeROM tool as described in Section IV, Development Tools, on page IV-1 to build a ROM image and send it to this supplier. You can also use Handsprings available 8MB Flash Module. This module, available on our web site, is a run-time read-only memory-based module that can be re-programed using the included GNU debugger, as described in the GNU tool kit documentation. Handspring includes an application with the module that enables users to transfer any application resident in internal memory to the module memory. Handspring is also developing an OTP (One-Time Programmable) memory module kit. You will be able to buy blank OTP memory modules from an approved vendor and program these modules yourself with your application. Since the Springboard memory modules described above (ROM, flash & OTP) are based on read only memory (at least during run-time) and that they can be removed at any time during execution, there are some considerations to take into account when designing your application. Refer to Chapter 1, Application development to support plug & play, on page II-2 for a more detailed description. For information on Handsprings approved third-party suppliers, refer to Section VIII, Approved Vendor List, on page VIII-1. This information will also be updated regularly on our developer support web site. In addition to the application that you want to transfer to a Springboard module, you should consider adding a welcome application that is automatically launched when a Springboard module is inserted in a handheld. Refer to section 3.3, Module welcome application, on page II-16 for a description of the welcome application. Section I - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Application development for a Handspring Springboard module 2.2 Specialized Springboard module hardware and software design If you are building a Springboard module with special hardware, you must be familiar with the PalmOS application developement as described in the previous sections. However, you will have to use the new Handspring API standard. This API and all other necessary information to built Springboard compatible modules are explained in the next sections. This kit also contains source code examples for Springboard module applications. They have been developed using the GNU tool kit. These examples show how to develop more sophisticated applications that install interrupt handlers or OS patches when the associated module is plugged into the Springboard expansion slot. These examples have been fully tested at Handspring and can be used as a baseline for application development. Copyright 1999 by Handspring, Inc. All rights reserved. Section I - 5 Section I: Introduction Version 1.0 Section I - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section II Springboard expansion slot The Springboard expansion slot allows different functional modules to be inserted and removed from a handheld computer at any time. To support this functionality, Handspring has made extensions to the standard PalmOS in order to enable new, specialized hardware and software that can detect the insertion of a module, load applications stored on the module, and cleanly remove them when the module is removed. This operation correctly implements plug & play for the handheld computer. Application software that resides in a modules memory is executed in place just like applications in the devices internal ROM or RAM. It launches and executes just as fast as built-in applications. The design allows for removing a module while running an application on it. The user is automatically switched out of the module application and back to the application launcher, as necessary. Because the Springboard expansion slot is a direct extension of the CPUs parallel bus, modules can also be designed that contain specialized hardware to address new markets not being touched by the handheld computer today (communication, entertainment, professional, etc.). This section describes the Springboard expansion slot. It provides you with the information necessary to:

Implement application-only products on a Springboard compatible memory module Design Springboard compatible modules and the applications to support them. If you need information to develop application running on the handheld internal memory, please refer to Chapter 1, Application Development for a Handspring Handheld Computer, on page I-3 of this document. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 1 Section II: Springboard expansion slot Version 1.0 Chapter 1 Application development to support plug

& play The Handspring expansion slot supports true hot plug & play of removable modules. You can insert or remove a module at any time, regardless of the current state of the machine and regardless of which applications are currently running. When a module is inserted, any software resident on the module is immediately available to you, and, in some cases, is automatically executed as well. A modules ROM can contain any number of applications. To enable this automatically, all modules must have code that contains module identification information. This information is in the module header; it must be generated by the Palm-makeROM utility described in Section IV, Development Tools.. Modules can also be built with custom hardware and applications that use Handsprings API. For this custom purpose, a module driver or control application is needed on the module itself so that the driver or application is loaded into the handhelds internal memory and is used to control the custom hardware. Typically the custom design includes a setup application, which is responsible for installing and removing the system extensions required to use the module. To install system extensions or shared libraries (presumably needed by some special hardware on the module), Handspring provides a mechanism for specifying a Module setup application. If it is present when the module is inserted, the setup application is executed. When the module is removed, the setup application is re-executed to handle removal of the modules software; the utility is then deleted from the handhelds internal memory. If desired, the module manufacturer can also designate one of the applications in the ROM as a Module welcome application, which is automatically launched whenever the module is inserted. Hot plug & play support works with most pre-existing PalmOS applications without any modification to them. We call these Generic Applications. In general, these applications do not patch any system trap calls, install shared libraries or interrupt handlers, or create background threads. The vast majority of existing PalmOS applications fall into this category. If a generic application is running on or using a module when it is removed, the system transparently and cleanly switches the user back to the applications launcher. Non-generic applications and system extensions are those that either enhance or change system functionality, or interface with special hardware. We will define these applications as Special-

Purpose Applications. These applications cannot support true hot plug & play unless the module contains a Module setup application. Without a setup application, the system is forced to soft-

reset the device when the module is removed. The Special-Purpose Applications section below describes how to design these types of applications and modules so that they are fully compatible with hot insertion and removal. Section II - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Application development to support plug & play 1.1 Generic Applications Generic PalmOS applications that are placed onto a memory module, such as the 8MB Flash Module, are supported by hot plug & play without modifications. Depending on the application, there are some rare instances where the application might get confused when it is relaunched after a module is pulled out and re-inserted. Designing an application to avoid this possible problem is straightforward. The following precautions are good design practices and ensure that an application can be successfully relaunched after any soft reset (which can occur any time a user presses the soft reset button). There are two problem areas to consider when designing your application:

1. When the current application is executing out of module memory, or 2. When the current application is using the module memory when it is removed. In these instances, the operating system is forced to abort the application and clean up any resources in use by the application. It does that by closing all databases that are still open. Normally a problem is not presented unless the application was in the middle of writing out changes to a database it owns. If the module is pulled out during this time, the application's database could be left in a partially updated state, which might cause the application to be confused or even crash the next time it executes and re-uses that database again. This window of vulnerability is very small in most applications; it typically occurs only after dismissing a dialog or choosing a menu item (to create or delete a new record, for example). It is unlikely, although possible, that a user would pull a module out during this period of time. For an application to protect itself from this potential problem, it must perform some simple checks whenever it re-opens a database it owns. For example, the application could set a valid bit in a record as the last step in updating the record. If the valid bit is not set when re-reading the record, the record can be automatically fixed or simply deleted. This process also ensures that the application can survive any soft reset as well. 1.2 Special-Purpose Applications As mentioned above, products that extend system functionality by installing system patches or shared libraries that hook into interrupt handlers or create background threads should not be placed on a removable module unless it includes a Module setup application. If there is no setup application, the system is forced into a soft reset when the module is removed. Typically software of this nature is placed on a module in order to provide access to special hardware on it. To support hot insertion and removal, the modules ROM must provide a Module setup application. The system looks for this utility when the module is installed and automatically copies it into the built-in RAM of the device. The system calls the utility with an install message. The setup application can then install interrupt handlers, system patches, shared libraries, background threads, or whatever else is required in order to support the module and its hardware. All of the code to support these system extensions must either be present in the setup application or initially copied into built-in RAM by the setup application before being installed into the system. When a module is removed, the system calls the setup application again with a remove message, giving the setup application the opportunity to remove all hooks it had previously placed into the system. Note that this function call happens after the module is removed, because it is the actual removal that interrupts the OS, which in turn calls the setup Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 3 Section II: Springboard expansion slot Version 1.0 function. The module has tipically been removed when the setup application is called, so it must not be used to set the modules hardware in a certain mode. If this operation is needed, the module must do this operation itself. After the setup application completes the remove operation, the system deletes the utility from the handheld built-in memory. The system patches, extensions, interrupt handlers, libraries, etc. that are installed by a setup application often need to access special hardware devices on the module itself, install and process interrupts, handle power management, etc. To support these functions, Handspring provides API calls (described in API Calls on page II-21) for querying and changing various attributes of the module hardware and its interface to the Springboard expansion slot. In addition to these configuration API calls, Handspring provides other calls that ensure that system extension code can gracefully detect and recover from a module removal at any time. These calls are more fully described in Catching Module Removals on page II-10. Section II - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Module design details Chapter 2 Module design details This chapter describes hardware aspects regarding memory space, interrupts, reset, power management, and insertion and removal of the modules. It also references the various Module Support API calls provided for interfacing to the module hardware; these calls are described in API Calls on page II-21. 2.1 Memory Space Figure II.1 shows the memory map for the modules. In Handpsrings first product, the Visors handheld, 32 MB of address space is reserved for the Springboard expansion slot. The base address and size may change in future releases, you should use the hsCardAttrCsBase attribute of the HsAppEventHandlerSet() call to obtain this information dynamically at run-time in order to ensure that your module software remains compatible with future revisions of the base unit and/

or system software. The beginning of the module ROM is expected to be at this base address. Two chip select lines, called CS0* and CS1* (* means an active low signal), are output to the Springboard module. By default, when a new module is inserted, the system assigns 16 MB of address space to each chip select. The address space for CS0* is referred to as csSlot0; the address space for CS1* is referred to as csSlot1; so csSlot1 starts at csSlot0 + 16 MB. Figure II.1: Module Memory Map 32 MB Maximum CsSlot1 Memory Space

(signal name is CS1*) CsSlot0 Memory Space

(signal name is CS0*) Basic Internal Memory Space used by Handheld Programmable size using hsCardAttrCsSize hsCardAttrCsBase Each chip select is configured to address 16-bit wide memory devices. The ROM in the module must reside at the beginning of csSlot0 and must be 16 bits wide in order for the system to recognize the module. The system makes no assumptions about what resides at csSlot1. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 5 Section II: Springboard expansion slot Version 1.0 You can use the HsAppEventHandlerSet() and HsCardAttrSet() calls to query or change the csSlot0 and csSlot1 address ranges via the hsCardAttrCsSize attribute. The ranges can be set to any power of two between 128 KB and 16 MB, but both ranges must be set to the same size. csSlot1 always starts immediately after the csSlot0 range. If, for example, csSlot0 start at address 0x2800 0000 and you change the size of the chip select address ranges to 1 megabytes, then csSlot1 starts at address 0x2810 0000 and continues up to address 0x281F FFFF. 2.2 Module access time and wait state When a module is first inserted, the system accesses the ROM at csSlot0 with the maximum number of wait states allowed by the base unit hardware. On the Visor handheld, this value is six wait states of the Dragonball EZ processor running at ~16.58 MHz, requiring a ROM with a maximum access time of 430 ns (setup time + 6 wait state = 70 + (6 * 60)). Once the system validates the ROM header, it reads a value out of the ROM header that indicates the actual required access time of the module in nanoseconds and re-programs the number of wait states accordingly. The Palm-MakeROM tool places this value into the ROM header (see -tokStr <id>

<value> on page IV-2). Both csSlot0 and csSlot1 must have the same number of wait states (a limitation imposed by the processor itself), so you must set this value to the worst case access time of your ROM and whatever other hardware is present on your module. The hsCardAttrAccessTime attribute of the HsCardAttrSet() call can also be used to change the number of wait states dynamically while the module is inserted. This method might be useful, for example, when temporarily accessing a slow device on your module. Once the ROM has been validated, the system updates itself so that all applications and databases present on the ROM are available for access or execution by the system or by other applications. All applications in the ROM appear in the applications launcher. If there is a setup application on the module, it is copied in the handheld internal memory and is sent an install message. Then if the module has a Module welcome application, this application is automatically launched as well. 2.3 Interrupts IRQ* is a dedicated interrupt line that hardware on a module can assert to interrupt the CPU. This interrupt is level sensitive and active low. The software for the module can install an interrupt handler for this interrupt using the hsCardAttrIntHandler attribute of HsCardAttrSet(). The module interrupt handler can be written in C or assembly language. It is passed a 32-bit reference parameter that you specify in the hsCardAttrCardParam attribute of HsCardAttrSet() and a boolean flag named *sysAwakeP that is passed by reference. Typically the 32-bit reference parameter is a pointer to the interrupt handler globals. The *sysAwakeP parameter usage is described below in Interrupt Handler Interaction on page II-16. In general, the interrupt handler must observe a number of restrictions that all interrupt PalmOS handlers observe. It cannot allocate, free, or move memory chunks, or allocate any system resources (semaphores, timers, tasks, etc.). If asserted when the handheld is in sleep mode, this interrupt wakes it up. The hsCardAttrIntEnable attribute can be used at any time to enable or disable module interrupts to the processor. It must be called after installing the interrupt handler for the first time. Section II - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Module design details When the module is removed, the system immediately disables further module interrupts (using the hsCardAttrIntEnable attribute), and sends the remove message to the module's setup application. The setup application should then clear the hsCardAttrIntHandler attribute to zero to remove the interrupt handler. 2.4 Interrupt Latency This section describes the interrupt latency times for the Visor handheld computer, which uses a DragonBall EZ processor running at 16.58 MHz. Latencies are likely to change in future products, so it is recommended that you design your module hardware and software to be tolerant of latencies that are at least three times the numbers published here. Table II.1 shows three examples of interrupt latency times. The latency times were measured on an actual unit and include all exception processing and function call overhead to get to the first instruction of the module interrupt handler. The three cases include: 1) when the device is already awake, 2) the first time the interrupt handler is called after coming out of sleep mode but before the rest of the system is awake (the *sysAwakeP parameter is false), and 3) the second time the interrupt handler is called after coming out of sleep mode, which is after the rest of the system has awakened (the *sysAwakeP parameter is true). Table II.1: Interrupt Latency Examples Condition Device already awake Device asleep (*sysAwakeP == false) Device asleep (*sysAwakeP == true)1 Latency 0.047 ms 1.17 ms 3.14 ms Recommended Design time 0.15 ms 4 ms 10 ms 1. Designer should add 20 ms to the recommend design time to allow for opening the USB port as described below. In the third case, the designer must take into account an additional 20 milliseconds if the OS needs to open the USB library. Note that this case only happens if the USB library was open when the device went to sleep. This situation is rare because most application will close the USB library before the device goes to sleep. 2.5 Reset When a module is first inserted, an interrupt is generated to the handheld and power is slowly applied to the module. In the Visor handheld computer, the OS ensures that the reset signal

(RESET*) remains asserted for at least 30 ms before releasing it. Because the Springboard module power is guaranteed to ramp up within 5 ms, there is at least 25 ms of power-on reset time for the module. If required, the module software can manually assert and release RESET* after the module has been inserted by setting the hsCardAttrReset attribute of HsCardAttrSet(). 2.6 Power Management A module can provide software and hardware support for power management. A routine for taking the module into and out of low power mode can be installed through the hsCardAttrPwrHandler attribute. The operating system calls this routine whenever the handheld Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 7 Section II: Springboard expansion slot Version 1.0 is turned on or off (that is, taken into or out of sleep mode). Parameters to the routine tell it whether to power up or down. If powering down, a second parameter indicates the reason. The reason code is either hsCardPwrDownNormal (a normal power down) or hsCardPwrDownLowVoltage

(indicates that this is an emergency shut down due to low or no battery voltage). Refer to the HsExt.h Header File for more information on hsCardPwrDownNormal and hsCardPwrDownLowVoltage. The power handler routine must observe the same restrictions as an interrupt handler because it might be called from the context of an interrupt routine, particularly when the system performs an emergency shutdown due to low battery voltage. In addition, a power handler must execute very quickly. When the batteries are removed, the power handler is executed using only the energy stored in the battery backup capacitor; thus it should do the minimal amount of work necessary to put the hardware into low power mode before returning. Ideally this process simply involves setting or clearing a bit in one or two hardware registers. The base unit asserts the LOWBAT* signal on the module when the batteries fall below a certain critical threshold voltage level (approximately 1.6 V). In the Visor handheld, power to the module is removed a few milliseconds after the batteries fall below this critical threshold . When the batteries are replaced, the module is re-powered and a new initialization sequence occurs. The handler routine is called first and puts the module into its low power state through software. However, LOWBAT* must be used to prevent the module from asserting its interrupt, IRQ*, so that the module does not attempt to wake up the device when the batteries are too low for operation. 2.7 Power Management Options for Interrupt Handlers Various power-saving options are available to module interrupt handlers. Through return parameters and system calls that it makes, the interrupt handler can tell the system how much of the hardware to power up as a result of the interrupt and how long to stay awake before going back into sleep mode. The *sysAwakeP parameter to the module interrupt handler is a boolean flag passed by reference that tells the interrupt handler how much of the system is currently awake. If the device is asleep

(off from a user's perspective) when the module interrupt the handheld, the system calls the module interrupt handler first before it wakes up any of the remaining hardware (sound, timers, keypad, etc.) and passes false to *sysAwakeP. Because the rest of the system is not awake yet, the interrupt handler cannot make any system calls at this stage except for HsCardErrTry/

HsCardErrCatch. If the handler can process the interrupt at this stage, then it needs to clear the interrupt source and return. The system then immediately puts the system back into sleep mode. This procedure is the most power-efficient means of processing the interrupt because no other extra hardware is powered up, but it does limit the interrupt handler to simple memory manipulations. If the interrupt handler is called with *sysAwakeP set to false but needs to make one or more system calls (such as HsCardEventPost(), SysSemaphoreSet(), etc.), then it should set

*sysAwakeP and return without clearing the source of the interrupt. When the system sees

*sysAwakeP set upon return of the module interrupt handler, it continues the wake-up sequence and wakes the rest of the system (except for the LCD). Once the system wake-up is completed, it Section II - 8 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Module design details calls the module interrupt handler again with *sysAwakeP set true. At this stage, the interrupt handler is free to make any system calls that are normally valid from interrupt handlers. Before the interrupt handler returns from being called with *sysAwakeP set true, it has the additional option of telling the system whether or not to turn on the LCD and how long to stay awake before returning to sleep mode. To do this, the handler calls HsEvtResetAutoOffTimer(). If the handler does not call HsEvtResetAutoOffTimer() before exiting, the default behavior of the system is to return to sleep mode on the next call to EvtGetEvent() by the current application. Typically, this occurrence is on the order of tens or hundreds of milliseconds, depending on the current application's event loop. The HsEvtResetAutoOffTimer() call takes two parameters: a stayAwakeTicks value and a userOn boolean for controlling the LCD. The stayAwakeTicks tells the system the minimum amount of time to stay awake before going back to sleep mode. This value is specified in system ticks;

however, keep in mind that the system checks the timer approximately every five seconds to verify if it needs to put itself in sleep mode. Passing (-1) tells the system to stay awake for the current auto-off setting indicated in the General Preferences panel. If the interrupt handler wants the LCD to turn on, then it sets the userOn boolean. The interrupt handler will sets the userOn boolean if it has just posted an event through HsCardEventPost() that results in an alert being displayed or other user interface activity. 2.8 Module Insertion Notification If a module is already plugged in during a device reset, all applications and panels on the module are sent the standard PalmOS reset action code (sysAppLaunchCmdSystemReset), as are all normal built-in applications and panels. When a module is hot-inserted at run time, the system also broadcasts the reset action code, but only to applications (not panels) on the module that have the dmHdrAttrResetAfterInstall bit set in their database header. This behavior ensures that applications that require the reset notification are notified, but does not unnecessarily slow down the module insertion process by having to call every application and panel on a module when it is inserted. Note that this is a slight modification of the original purpose of the dmHdrAttrResetAfterInstall bit in the database header. Its original purpose was to tell HotSync to soft reset the device after one or more of these reset-after-install applications are installed onto the device. During the reset sequence, all applications (and thus the one(s) just installed) are sent the reset action code. However, when present on a module application this bit now means that the application wants to receive the reset action code after the module is inserted. Thus the application gets the reset action code sent to it even though the system has not really gone through a soft reset. This particular behavior was chosen for maximum compatibility with most existing applications, but unfortunately a small subset of applications might be confused by it. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 9 Section II: Springboard expansion slot Version 1.0 Figure II.2: Operational Flowchart when Inserting a Module Start Was a module detect interrupt generated ?

no yes Is there a setup app

no Power is slowly applied to the module by the handheld hardware and the OS resets the module The OS reads the module header information and updates the globals for the applications launcher 2.9 Catching Module Removals Is there a welcome app

no All visible applications appear in the applications launcher yes yes Copy setup app in internal memory and execute it Execute welcome app directly from Module Memory For normal application code, the operating system simply aborts an application that is running on a module or using a module when it is removed. However, if non-application code such as an interrupt routine is accessing the module when it is removed, a bus error occurs and, by default, the system will not know how to auto-correct the erroneous access. Other possible problem areas are shared libraries or patches to system calls that the module has installed. To handle these situations, Handspring provides the HsCardErrTry/HsCardErrCatch macros. These macro calls should be wrapped around any code in your interrupt routines, shared libraries, or system extensions that access memory or other hardware devices out on the module. If a module is removed when one of these sections of code is executing and a bus error occurs, the system automatically passes control to the HsCardErrCatch section. You can then look at various local variables that you have set up to determine the best course of action to take in dealing with the module removal. In most cases, you can simply set a flag that says the module has been removed and wait for your setup application to be called with the remove message. Your setup application should then uninstall all module-dependent hooks that you have placed into the system. Section II - 10 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Module design details Figure II.3: Operational Flowchart when Removing a Module Start Was a module detect interrupt generated ?

no yes Is there a setup app

no yes The OS deletes the setup app and updates globals to reflect the removal of the module and its applications The OS calls the setup app

(already in the Handhelds internal memory) Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 11 Section II: Springboard expansion slot Version 1.0 Chapter 3 Springboard Software Integration Modules that provide just additional user applications in ROM are straightforward to design and construct; modules that provide additional hardware functionality often involve interrupt handlers, shared libraries, and/or system extensions to enable other applications or system software to use the new hardware. Probably the most critical portion of the software design for a module is the operation and interaction of these various pieces with each other and the rest of the system. For example, a pager module might have an interrupt routine that fires off whenever a page comes in. That interrupt routine might have to store the contents of the incoming page and then decide whether or not to inform the user that a message came in. If it wanted to inform the user of the message, it might simply display an alert on the screen (similar to a Datebook alarm going off) and/or cause a switch to a Pager application where the user can view and manage the incoming pages. This chapter provides an overview of how interrupt routines and other system extensions can interact with the module hardware, application code, and the rest of the system. It also references some of the API calls provided for these purposes. The most important thing to remember about interrupt handlers, shared libraries, and system extensions is that their code must be copied into main memory before they are installed into the system. If not, the system cannot recover from a module removal situation without forcing a soft reset. They can, however, access memory or other devices on the module as long as they follow the guidelines described in Catching Module Removals on page II-10. The Module setup application mechanism provides a convenient method for copying these types of code into the handheld internal memory before installation. 3.1 Module setup application Any module that provides custom hardware and software that access the hardware usually requires a module setup application. The setup application installs any system extensions, interrupt handlers, shared libraries, system trap patches, etc. that are necessary for using the new hardware. It is also responsible for undoing these installations when the module is removed. Because the setup application is copied into the main memory before being executed, complete installation and removal of the module software is guaranteed even if the module is removed prior to or during installation. Note that the module is already removed when the setup application is called to uninstall. When a module is inserted or when the device is reset, the operating system automatically queries the module ROM to determine if there is a setup application for the module. If a setup application exists, the operating system copies it into main memory and then executes the setup application by sending it an install message. Likewise, when the module is removed, the system calls the same setup application, sends it a remove message, then deletes the setup application itself. Section II - 12 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Springboard Software Integration A setup application is built just like any other PalmOS application, however, it must be given a special database creator and type to indicate that it is a module setup application and not a normal PalmOS application. See the CardSetup Sample for an example (under the

<installDir>\PalmDev\info\Tools\Sample directory after you install the PalmTools included with this kit). A module setup application is called with one of two action codes sent to its PilotMain(): hsSysAppLaunchCmdInstall or hsSysAppLaunchCmdRemove. In both cases, the cmdPBP parameter block passed to the utility is a structure pointer containing the card number that has been inserted or removed. In this context, card number is the standard PalmOS cardNo parameter used by function like DmCreateDatabase(UInt cardNo, ...). Usually the setup application saves this card number in its globals that it allocates during the install. Refer to the HsExt.h Header File for more information on hsSysAppLaunchCmdInstall and hsSysAppLaunchCmdRemove. The parameter block passed during the hsSysAppLaunchCmdInstall action code also contains an isReset field. This value is true (non-zero) only if the install action code is being sent as a result of the device going through a soft or hard reset. Most setup applications can safely ignore this field because their actions are independent of whether or not the module was inserted before the reset. If the module was inserted before the reset, any shared library or other databases that the setup application normally copies to built-in RAM are already present in built-in RAM. There is no harm in copying them from the module again. During installation and removal processing, a setup application is not allowed to use application global or static variables; all variables must be normal stack- or register-based local. This restriction is the same one that is placed on other PalmOS applications when processing other system actions codes such as find or goto. However, most module software requires globals of some kind. These globals are most likely shared by the module's interrupt handler, applications, and other extensions. The hsCardAttrCardParam attribute of the module is provided for this purpose. Use this attribute to store a 32-bit pointer to the module's globals; it can be set using HsCardAttrSet() and retrieved using HsAppEventHandlerSet(). In addition, this attribute is automatically passed to the module's interrupt handler as a parameter on the stack. If the module setup application needs to install a shared library that is in a separate database out on the module, it must first copy the shared library database from the removable module into main memory before installing the library. Likewise it should delete the library from main memory during removal processing. The library database can be easily copied into memory using the HsDatabaseCopy() routine. If a module setup application needs to patch any system traps, it must use the HsCardPatchInstall() routine to install them. It should not use SysSetTrapAddress(). Using HsCardPatchInstall() ensures that the patch can safely be removed using HsCardPatchRemove() during removal processing without interfering with other third-party extensions that may have been activated or de-activated (using an application like HackMaster) in the meantime. If a module setup application installs an interrupt handler, event handler, or system patch from its own code segment (a subroutine linked in with the setup application itself), it must be sure to lock down its code segment before returning from the install action code. This precaution ensures that its code segment is not inadvertently moved by the PalmOS memory manager while the module is installed. The following portion of code does this operation:

Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 13 Section II: Springboard expansion slot Version 1.0

// Because we installed a patch from this code resource, make sure

// this code resource remains locked down after we exit. VoidHand codeResH = DmGet1Resource ('code', 1);

if (codeResH) MemHandleLock (codeResH);

codeResH;

Similarly, during the remove action code, the module setup application should restore the lock count of the code resource as follows:

// Restore lock count of code resource VoidHand codeResH = DmGet1Resource ('code', 1);

if (codeResH) MemHandleUnock (codeResH);

codeResH;

A typical module setup application allocates a memory chunk for the module's globals using MemPtrNew(), resets the owner of this chunk to 0 using MemPtrSetOwner(), and then stores the returned pointer in the hsCardAttrCardParam attribute of the module. A code example follows:

DWord PilotMain (Word cmd, Ptr cmdPBP, Word launchFlags)

void*

Err err;

VoidHand codeResH;

globalsP;

if (cmd == hsSysAppLaunchCmdInstall)

HsSysAppLaunchCmdInstallType* installP;

installP = (HsSysAppLaunchCmdInstallType*)cmdPBP globalsP = MemPtrNew (sizeof (MyGlobalsType));

if (globalsP)

MemPtrSetOwner (globalsP, 0);

globalsP->cardNo = installP->cardNo;

HsCardAttrSet (globalsP->cardNo, hsCardAttrCardParam,

&globalsP);

// Install shared libraries using SysLibInstall()

// Patch system traps using HsCardPatchInstall()

// Install interrupt handler using

// HsCardAttrSet(globalsP->cardNo, hsCardAttrIntHandler, ...)

// Enable module interrupts using

// HsCardAttrSet (globalsP->cardNo, hsCardAttrIntEnable, ...)

// Because we installed a patch from this code resource, make sure

// this code resource remains locked down after we exit. codeResH = DmGet1Resource ('code', 1);

if (codeResH) MemHandleLock (codeResH);

else if (cmd == hsSysAppLaunchCmdRemove)

HsSysAppLaunchCmdRemoveType* removeP;

removeP = (HsSysAppLaunchCmdRemoveType*)cmdPBP err = HsCardAttrGet (removeP->cardNo, hsCardAttrCardParam,

&globalsP);

if (!err && globalsP) MemPtrFree (globalsP);

// Remove shared libraries using SysLibRemove()

// Restore system traps using HsCardPatchRemove() Section II - 14 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Springboard Software Integration

// Restore lock count of our code resource codeResH = DmGet1Resource ('code', 1);

if (codeResH) MemHandleUnlock (codeResH);

return 0;

Another restriction placed on a module setup application is when it is called with the remove message. When this happens, it cannot display any alerts (using FrmAlert() or similar mechanism) or make system calls that might display UI elements or process user interface events. The remove action code can be sent to the setup application after the current application has aborted and before a new application is launched; therefore the system might not be in a state to process user interface events. The install action code, however, does not have these restrictions. It can display alerts or progress dialogs if it wishes to because it is always called from the context of the current application's main event loop. By the time the setup application is called with the remove message, it can assume that the system has already done the following:

1. Disabled module interrupts by resetting the hsCardAttrIntEnable attribute to 0. 2. Removed the module interrupt handler by resetting the hsCardAttrIntHandler attribute to 0. 3. Removed the module event handler by resetting the hsCardAttrEvtHandler attribute to 0. 4. Removed the module's power handler by resetting the hsCardAttrPwrHandler attribute to 0. 3.2 Overriding Module Software The basic principle behind Handsprings removable modules is that all of the module software and hardware resides on the module itself. In this way, a module that is inserted in any handheld is immediately functional without requiring any manual software installation or configuration. Also, most modules will be built with masked ROM in order to keep costs to a minimum. In the unfortunate event that a bug is discovered after a masked ROM module has been released, however, you might need to provide a software patch for users of your module. By taking special precautions in the design of your setup application, you can minimize the need to design and implement a software patch for your module. For example, suppose your module copies a shared library from the module ROM to internal memory. Instead of blindly copying the shared library from the module to internal memory, your setup application should first check internal memory for a newer version of that library. If a newer version already exists in internal memory, you can skip copying the version from the module. Use the DmGetNextDatabaseByTypeCreator() call in these situations; it automatically searches for the latest version of a database by type and/or creator. If you find the newer version in internal memory (card number 0), then you can skip copying the database from the module. Note: Always register all your database creator IDs with 3Com developer support to ensure that they are unique. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 15 Section II: Springboard expansion slot Version 1.0 3.3 Module welcome application Whenever a module is inserted and after copying and executing the Module setup application (if present), the system looks for a welcome application on the module. This application is a normal PalmOS application with a database name of CardWelcome. If this application is found, the OS automatically switches to it. For example, this application could be a module-specific launcher application or an application that lets you set preferences for the module. Because it is a normal PalmOS application, it appears in the PalmOS applications launcher and can be accessed through the launcher anytime after the module has been inserted. The name that appears in the PalmOS application launcher for this welcome application can be set up in the tAIN resource of the welcome appthe same as for other PalmOS applications. This launchers visible name in the tAIN resource is independent of the actual database name of CardWelcome. If a module is inserted during a soft or hard reset, the system does not automatically switch to the welcome application. You can, however, override this behavior and have the welcome application launched automatically during a reset. To do this, include the HsWR token in the module's ROM. To include this token, specify it on the command line to the Palm-MakeROM tool

(-tokStr <id> <value>) as described in Section IV, Development Tools, on page IV-1. 3.4 Interrupt Handler Interaction All interrupt handlers in the PalmOS must observe a number of restrictions. They cannot allocate, free, or move memory in any memory heap; create, modify, or delete databases; create, delete, or block system resources such timers, tasks, semaphores, etc.; or display any user interface. About the only thing an interrupt handler can safely do is change the contents of pre-allocated, locked memory blocks, queue keyboard events, or trigger system semaphores. In addition, interrupt handlers must execute as quickly as possible in order to maximize user-responsiveness of the device and minimize the chances of adversely interfering with other interrupt response times. One of the first tasks of any module interrupt handler is to remove the source of the interrupt. This step usually involves reading a register on the module that effectively deasserts the interrupt line. Module interrupts are level-sensitive and unless the module interrupt handler removes the source of the interrupt by the time it exits, the interrupt handler is immediately re-executed. Next the module interrupt handler usually processes and/or stores some data regarding the interrupt. For this purpose, it usually needs a pointer to some global data containing one or more buffers and/or counters. This pointer must have been allocated in advance by application or setup code. Usually this type of buffer is allocated during initialization time using MemPtrNew() and is set to have an owner ID of 0 (using MemPtrSetOwner) to prevent the system from freeing it when the current application quits. Module interrupt handlers are passed a 32-bit parameter on the stack, which is set up through the hsCardAttrCardParam attribute of the HsCardAttrSet() call. Usually this parameter is the globals pointer for the interrupt handler. Finally the interrupt handler may have to notify the system or an application that an event of particular interest has occurred. In particular, if an alert or similar message needs to be displayed, the interrupt handler must rely on application or system code to display it after the interrupt handler returns, because interrupt handlers themselves are not allowed to have any Section II - 16 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Springboard Software Integration user interface. Typically the interrupt handler uses the HsAppEventPost() system routine to trigger the user interface. Note: Refer to Power Management Options for Interrupt Handlers on page II-8 for important information about when it is safe to make system calls from a module interrupt handler. System calls cannot be made from a module interrupt handler if the *sysAwakeP parameter passed to it is false. The interrupt handler can use the HsCardEventPost() call to post a module event. This call accepts an event number between 0 and hsMaxCardEvent and a 16-bit event parameter. After the interrupt handler exits and control is returned to the main event loop, the system calls the module's CardEvtHandler() with the given event number and 16-bit event parameter. CardEvtHandler() is installed through the hsCardAttrEvtHandler attribute of HsCardAttrSet(). For convenience, the CardEvtHandler() is also passed a copy of the same 32-bit parameter that the interrupt handler gets (the interrupt handler globals). Because CardEvtHandler() executes from the context of the main event loop, it has no restrictions as far as allocating memory or making other system calls. It can put up an alert, call SysUIAppSwitch() to cause a switch to another application, or do anything else it desires. It is important to note that the CardEvtHandler() function executes in the context of (or is effectively called from) the current UI application. For this reason, the module event handler function should keep its stack usage (local variables, nested function calls, etc.) down to a minimum. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 17 Section II: Springboard expansion slot Version 1.0 Chapter 4 Software API Extension This chapter describes in detail the calling conventions and parameters for each of the Handspring API calls. For a description of how and where to use most of these calls, refer to Chapter 2, Module design details, on page II-5 and Chapter 3, Springboard Software Integration, on page II-12. The use of the remaining generic utility calls provided by Handspring are described in Utility Calls on page II-19. The header file HsExt.h provided with this kit contains all the public equates referenced in this chapter including all constants, structure definitions, function prototypes, etc. 4.1 Checking Presence and Version of Handspring Extensions For application code or other types of code that might be installed onto both non-Handspring PalmOS devices and Handspring devices, you must first ensure that you are on a Handspring device before making Handspring-specific API calls. Use the FtrGet() call of PalmOS and check for the presence of the Handspring extensions feature. The hsFtrCreator and hsFtrIDVersion constants that are passed to FtrGet() are defined in the Handspring header file HsExt.h. For example:

value;

DWord err = FtrGet (hsFtrCreator, hsFtrIDVersion, &value);

if (!err)

// Since FtrGet() did not return an error, we can

// safely make Handspring specific API calls like

// HsCardAttrGet(), HsCardAttrSet(), etc.

If FtrGet() returns no error, then the Handspring extensions are present and it is safe to call any Handspring API call that is described in this chapter. The current version level of the Handspring extensions is returned in the value parameter. It is encoded as 0xMMmfsbbb, where MM is the major version number, m is the minor version number, f is the bug fix level, s is the stage (3-

release, 2-beta 1-alpha, 0-development) and bbb is the build number for non-releases. For example, Version 2.00a2 would be encoded as 0x02001002, where the major version number is 02, the minor version number is 0, the bug fix level is 0, the stage is alpha, and the build number is 0x2. Because the format used for the version number of the Handspring extensions is the same as that used for the PalmOS ROM version number, your code can use version macros such as sysGetROMVerMajor and sysGetROMVerMinor (defined in SystemMgr.h of the Palm Computing Platform SDK) for decoding the version number of the Handspring extensions. Another Handspring feature provides the modification date of the Handspring extensions. This feature has an ID of hsFtrIDModDate (replaces hsFtrIDVersion in the above example). The value Section II - 18 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension of this feature changes with every release of the Handspring extensions, regardless of whether or not new features were added. Thus you should use it for informative purposes only. If your software makes decisions based on a certain version or feature of the Handspring extensions in order to run, it should use the hsFtrIDVersion feature instead. 4.2 Utility Calls Besides the API calls that are provided specifically for dealing with removable modules, the Handspring utility functions described in this section are not necessarily module related. The HsDatabaseCopy() call can be used to copy a database from a module to built-in memory, vice-versa, or to duplicate an existing database within the same module. This function can be useful in module setup applications if they need to copy any databases from the module to built-

in memory as part of the setup process. The HsAppEventHandlerSet() and HsAppEventPost() calls can be used to provide more flexible event-handling mechanisms for an application. Normally when applications have their own custom event types, they must specifically look for these events in their main event loop after calling EvtGetEvent(). This process is not a problem in the main event loop of the application, but it can be a problem if a system event loop (such as the system Find dialog or Category Edit dialog event loops) is executing at the time the event is posted. Because the system event loop is not aware of any application-specific event types, it simply ignores them. If the application registers its own custom event handler procedure using HsAppEventHandlerSet(), then this procedure is called automatically by the system during SysHandleEvent() in response to any event posted by HsAppEventPost(). This way, the application's event handler is called even if the event is posted, while the system is in one of its own custom dialog event loops. Keep in mind that your application's event handler might be called from the context of another application's action code processing. Even though your application is the current application visible to the user at the time, the global CPU registers are not your application's globals due to the action code processing. Thus your application event handler routine must never rely on global variables. Instead it should use the evtRefCon parameter that is passed to it as a pointer to any variables it needs to access or update. This evtRefCon parameter value is set up by the HsAppEventHandlerSet() call. 4.3 Generic Module Support in PalmOS Besides the calls mentioned in this chapter, the standard PalmOS memory and data manager calls for dealing with modules and memory on modules are always available. For example, MemNumCards() returns the number of modules that are present. It returns 2 if there is a removable module inserted and 1 otherwise. The built-in memory of the handheld base unit is accessed by passing a module number of 0 to the appropriate memory and data manager calls, whereas the removable module memory is accessed using a module number of 1. Calls such as MemCardInfo() can be used to get the module name, manufacturer name, etc. for any module by passing the appropriate module number. Remember that even if MemNumCards() returns a 2, indicating that the removable module is currently installed, the user may pull the module out at any timeeven immediately after this call Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 19 Section II: Springboard expansion slot Version 1.0 returns. When a module is removed, the system automatically aborts any application code that is currently in the process of trying to access memory on the removable module and returns control to the application launcher. In general, application code can simply call MemNumCards() during its start-up and assume that the information will remain current until the application exits. If the module is pulled out while the application is using it, the system automatically and immediately aborts the application. If the application is not referencing the module when the module is pulled out, then the system sends it an exit event and waits for the application to exit normally. When a module is inserted, the current application is sent a normal exit event as well. It might or might not be re-launched after it exits, depending on the contents of the module (for example, it might have a welcome application on it that is launched instead). 4.4 Copy Protecting Module Applications If desired, module applications easily can be designed so that they will not run if copied off the module to another device's internal RAM. A simple mechanism is for the application to check for the presence of the removable module and compare the module's name when it starts up. If the module is not present or the module's name is not correct, it can display an appropriate error message and refuse to run. All removable modules will have unique module names that the module manufacturer must register with Handspring. This name is an ASCII string of up to 31 characters. To get the name of a module, use the MemCardInfo() call and pass in the module number of the removable module. For example:

char cardName[32];

err;

Err err = MemCardInfo (1 /*cardNo*/, cardName, 0 /*manufName*/, 0 /*versionP*/, 0 /*crDateP*/, 0 /*romSizeP*/, 0 /*ramSizeP*/, 0 /*freeBytesP*/);

if (err || StrCompare (cardName, "MyCardName"))

DisplayCopyProtectError();

Section II - 20 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 4.5 API Calls Software API Extension This section lists the Handspring API calls in alphabetical order. The calls are summarized in the table below. Table II.1: API Call Summary Call Description HsAppEventHandlerSet Register event handler procedure Page #

page II-22 Enable event posting by application event handler page II-23 HsCardErrTry/HsCardErrCatch Enable safe recovery for module removals HsAppEventPost HsCardAttrGet HsCardAttrSet HsCardEventPost HsCardPatchInstall HsCardPatchPrevProc HsCardPatchRemove HsDatabaseCopy Retrieve attribute Set attribute Queue an event Enable patch installs Get address of previous system trap implementation page II-32 Remove setup application patch Copy PalmOS database HsEvtResetAutoOffTimer Reset auto-off timer The use of the generic utility calls is described in 4.2, Utility Calls. page II-24 page II-26 page II-27 page II-29 page II-30 page II-33 page II-34 page II-36 Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 21 Section II: Springboard expansion slot Version 1.0 4.5.1 HsAppEventHandlerSet Summary Prototype Description Parameters Returns Provided for applications so they can register their own event handler procedure that can be triggered using HsAppEventPost(). Err HsAppEventHandlerSet (HsAppEventHandlerPtr procP, DWord evtRefCon) Sets up an application's event handler procedure. The system calls this handler procedure from the main event loop in response to an event posted by the HsAppEventPost() routine. The event handler has this prototype:

Boolean AppEvtHandler (DWord evtRefCon, Word evtNum, Word evtParam) It returns true if the event was successfully handled and false if not. The evtRefCon parameter is a copy of the evtRefCon value passed to HsAppEventHandlerSet(). The evtNum and evtParam parameters are copies of values passed in to HsAppEventPost(). Note that this event handler can be called while the system is in the middle of sending an action code, like find, to another application. Even though your application is the current application visible to the user at the time, the global CPU registers will not be your application's globals due to the action code processing. Thus the AppEvtHandler routine must never use global variables. Instead it should use the evtRefCon parameter as a pointer to a structure containing any variables it needs to reference or update. The system automatically removes your AppEvtHandler() for you when your application quits. procP evtRefCon IN IN Pointer to event handler procedure, or NIL to remove the cur-

rent one. This 32-bit reference constant gets passed to the event handler when it is called by the system. 0 if no error Section II - 22 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension 4.5.2 HsAppEventPost Summary Provided for applications so that they can post an event to be processed by their own application event handler procedure installed using the HsAppEventHandlerSet() call. Prototype Description Err HsAppEventPost (Word evtNum, Word evtParam) Queues an event for the application's own event handler procedure. The system calls the event handler procedure from the main event loop. The event handler can be installed using the HsAppEventHandlerSet() call. The event handler has this prototype:

Boolean AppEvtHandler (DWord evtRefCon, Word evtNum, Word evtParam) It returns true if the event was successfully handled and false if not. The evtRefCon parameter is a copy of the evtRefCon value passed to HsAppEventHandlerSet(). Parameters Returns evtNum evtParam IN IN The event number to post. Can be any value between 0 and hsMaxAppEvent. A 16-bit parameter that is passed to CardEvtHandler. 0 if no error Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 23 Section II: Springboard expansion slot Version 1.0 4.5.3 HsCardAttrGet Summary Retrieves any one of the attributes of a module or its software/hardware interface. Err HsCardAttrGet (Word cardNo, HsCardAttrEnum attr, void* valueP) Returns the current value of a particular module attribute designated by the attr parameter. The return value is placed in the buffer pointed to by valueP. Prototype Description Parameters attr cardNo

*valueP IN IN OUT which attribute to retrieve which module number to query about value of attribute is returned in this buffer The possible values of attr and the corresponding return types are shown below. The R/W column indicates if settings are read-only (R) or read-write

(RW). The read-write attributes can be configured through the HsCardAttrSet() call. Setting Value R/W Description hsCardAttrRemovable Byte R hsCardAttrHwInstalled Byte R hsCardAttrSwInstalled Byte R hsCardAttrCsBase DWord R True if this module is a removable module. False if the module is not removable (built-in module: cardNo = 0). Returns hsErrIn-

validCard if slot cardNo does not exist. True if a module is physically installed at cardNo and has fin-

ished its power-on reset cycle. False if not. Returns hsErrInvalid-

Card if slot cardNo does not exist. Note that this attribute is true before hsCardAttrSwInstalled is true. True if the PalmOS Memory, Data, and other managers have been updated to access the given module. False otherwise. Note that this attribute is not true until some period of time after the module is physically installed and hsCardAttrHwInstalled is true. Base address of first slot chip select. The second chip select always starts at hsCardAttrCsBase + hsCardAttrCsSize. hsCardAttrCsSize DWord RW Address range of each of the chip selects. hsCardAttrAccessTime DWord RW hsCardAttrReset Byte RW Minimum access time of slot chip selects in nanoseconds. Note that when set, the value passed in is rounded up to the next available access time setting available in hardware. If value is non-zero, the module reset signal going to the module is asserted. If zero, the module reset signal is deasserted. Section II - 24 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension Setting Value R/W Description hsCardAttrIntEnable Byte RW hsCardAttrCardParam DWord RW hsCardAttrIntHandler void*

RW hsCardAttrPwrHandler void*

RW hsCardAttrEvtHandler void*

RW hsCardAttrLogicalBase void*

R hsCardAttrLogicalSize DWord R hsCardAttrHdrOffset DWord R Returns If value is non-zero, module interrupts are enabled. If value is zero, the module interrupts are disabled. Contains the 32-bit parameter that is passed to the module's interrupt handler, power handler, and event handler. This attribute is a pointer to the module interrupt handler which must have this calling convention:

void CardIntHandler (DWord cardParam, Boolean*

sysAwakeP);

The cardParam that is passed to this interrupt handler can be set up through the hsCardAttrCardParam attribute. This attribute is a pointer to the module's power handler routine, which must have this calling convention:

void CardPwrHandler (DWord cardParam, Boolean sleep, HsCardPwrDownEnum reason) The cardParam is a convenience copy of the hsCardAttrCard-

Param module attribute. This attribute is a pointer to a Module Event Handler procedure. A module interrupt handler can trigger the system to call this event handler using HsCardEventPost(). This mechanism is described in Interrupt Handler Interaction on page II-16 Contains the logical base address reserved for the given module slot. This value, added to the module's header offset, gives the address of the module's ROM header. Most applications do not need to use this value. It is provided mainly for advanced appli-

cations like flash programming applications that need to format their own module headers. Contains the logical address space reserved for the given mod-

ule. This value is greater than or equal to the actual addressable memory on the module. Contains the offset from the module base address to the mod-

ule's ROM header. Most applications do not need to use this value. It is provided mainly for advanced applications like flash programming applications that need to format their own module headers. 0 hsErrNotSupported hsErrInvalidCard if no error this setting is not supported invalid module number Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 25 Section II: Springboard expansion slot Version 1.0 4.5.4 HsCardAttrSet Summary Prototype Description Parameters Returns Sets an attribute of a module's interface. Err HsCardAttrSet (Word cardNo, HsCardAttrEnum attr, void* valueP) Sets the new value of a particular module attribute designated by the attr parameter. attr cardNo

*valueP IN IN IN which attribute to set which module number to set attribute on new value of attribute is passed in this buffer The possible values of setting and the corresponding data type of

*valueP are documented in the HsCardAttrGet() call. Only those indicated as being read/write (RW) attributes can be changed through this call. 0 hsErrNotSupported hsErrInvalidCard hsErrReadOnly if no error this setting is not supported invalid module number this attribute is read-only and cannot be changed. Section II - 26 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension 4.5.5 HsCardErrTry/HsCardErrCatch Summary Prototype Description Limitations These macros are provided for interrupt handlers, system extensions, and shared libraries that need to access memory or devices out on a removable module. These calls enable safe recovery if the module is removed while in critical sections of code. HsCardErrTry

// Do something that accesses the removable module

HsCardErrCatch

// Recover or cleanup after a failure in the above Try block.

// The code in this Catch block does not execute if

// the above Try block completes without a module removal

} HsCardErrEnd

// You must structure your code exactly as above. You cannot have a

// HsCardErrTry { } without a HsCardErrCatch { } HsCardErrEnd,

// or vice versa. The HsCardErrTry/HsCardErrCatch macros should be wrapped around any section of code within an interrupt handler, system extension, shared library, or other system code that needs to access memory or hardware on a removable module. If the module is removed while the critical section of code is executing, control is passed to the HsCardErrCatch() section. These macros can be nested. For example, you can call a subroutine from within your HsCardErrTry block that has its own try/catch block. Every routine that has an HsCardErrTry clause, however, must have an HsCardErrCatch. HsCardErrTry and HsCardErrCatch are based on setjmp/longjmp. At the beginning of a Try block, setjmp saves the machine registers. A module removal triggers longjmp, which restores the registers and jumps to the beginning of the Catch block. Therefore, any changes in the Try block to variables stored in registers are not retained when entering the Catch block. The solution is to declare variables that you want to use in both the Try and Catch blocks as volatile. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 27 Section II: Springboard expansion slot Version 1.0 For example:

volatile long x = 1; // Declare volatile local variable HsErrErrTry

... x = 100; // Set local variable in Try

HsCardErrCatch

if (x > 1) // Use local variable in Catch HsCardErrEnd SysBeep(1);

Parameters Returns none N/A Section II - 28 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension 4.5.6 HsCardEventPost Summary Prototype Description Parameters Returns Provided for interrupt handlers so that they can queue an event for processing later by a CardEvtHandler() procedure. Err HsCardEventPost (Word cardNo, Word evtNum, Word evtParam) Queues an event for a CardEvtHandler() procedure. The system calls the CardEvtHandler procedure from the main event loop of the current application after the interrupt handler returns. The CardEvtHandler can be installed using the hsCardAttrEvtHandler attribute of HsCardAttrSet(). The CardEvtHandler has this prototype:

Boolean CardEvtHandler (DWord cardParam, Word evtNum, Word evtParam) It should return true if it successfully handled the event and false if it did not. The cardParam value passed to CardEvtHandler is a convenience copy of the hsCardAttrCardParam module attribute. evtNum cardNo evtParam IN IN IN The event number to post. Can be any value between 0 and hsMaxCardEvent. Module number for which to post event. A 16-bit parameter that is passed to CardEvtHandler. 0 hsErrInvalidCard if no error invalid module number Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 29 Section II: Springboard expansion slot Version 1.0 4.5.7 HsCardPatchInstall Summary Prototype Description Enables Module Setup utilities to install patches to PalmOS system calls. Err HsCardPatchInstall (Word trapNum, void* procP) Patches a PalmOS system trap call. Setup utilities should always use this call to patch traps rather than the PalmOS SysSetTrapAddress() call because this call ensures compatibility with other third party extensions that may have been installed by the user (through HackMaster or equivalent). The implementation of the patch must use the HsCardPatchPrevProc() routine to obtain the address of the old trap call in order to pass control over to it. When the module Setup application is called to remove the module software, it must use HsCardPatchRemove() to remove every patch installed by HsCardPatchInstall(). Important: module setup applications are only allowed to install one patch per system trap number. If HsCardPatchInstall() is called twice for the same trap without an intervening HsCardPatchRemove(), it returns the error code hsErrCardPatchAlreadyInstalled. Here is an example of a patch implementation that does some work then passes control over to the previous implementation:

static Boolean PrvCardSysHandleEvent (EventPtr eventP)

Boolean handled;

Boolean (*oldProcP) (EventPtr eventP) = 0;

// Do some stuff

// Call old routine HsCardPatchPrevProc (sysTrapSysHandleEvent,

(DWord*)&oldProcP);

handled = (*oldProcP) (eventP);

return handled;

Parameters trapNum procP IN IN The trap number of the call to patch. This value is a SysTrap-

Number PalmOS enum value as found in the PalmOS header file <SysTraps.h>. Pointer to procedure to plug into the system trap. Section II - 30 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Returns 0 hsErrInvalidCard if no error invalid module number Software API Extension Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 31 Section II: Springboard expansion slot Version 1.0 4.5.8 HsCardPatchPrevProc Summary Prototype Description Parameters Returns Used by system patches installed using HsCardPatchInstall() to get the address of the previous implementation of the system trap. Err HsCardPatchPrevProc (Word trapNum, void** prevProcPP) Use this call inside the implementation of a system patch for a module in order to get the address of the previous implementation of the call. In most cases, patches do their own work before calling the previous implementation. See HsCardPatchInstall() for an example of a patch implementation. trapNum IN

*prevProcPP OUT The trap number of the call that was patched. This value is a SysTrapNumber PalmOS enum value as found in the PalmOS header file <SysTraps.h>

The address of the previous implementation is returned in this pointer. 0 ftrErrNoSuchFeature if no error trap was not patched by HsCardPatchInstall Section II - 32 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension 4.5.9 HsCardPatchRemove Summary Prototype Description Parameters Returns Removes a module setup application patch installed by HsCardPatchInstall(). Err HsCardPatchInstall (Word trapNum, void* procP) When the module setup application gets called to remove the module software, it must use this call to remove every patch installed by HsCardPatchInstall(). trapNum IN The trap number of the call that was patched. This value is a SysTrapNumber PalmOS enum value as found in the PalmOS header file <SysTraps.h>

0 hsErrCardPatchNotInstalled if no error trap was not patched by HsCardPatchInstall Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 33 Section II: Springboard expansion slot Version 1.0 4.5.10 HsDatabaseCopy Summary Prototype Description Parameters Copies an entire PalmOS database. Err HsDatabaseCopy (Word srcCardNo, LocalID srcDbID, Word dstCardNo, char* dstNameP, DWord hsDbCopyFlags, char* tmpNameP, LocalID* dstDbIDP) Copies an entire PalmOS database. The source and destination can be the same module or different modules, and the source database can be copied from ROM or RAM. The hsDbCopyFlags parameter can be used to control the copy operation. The caller has the option of preserving the creation date, modification date, backup date, and/or modification number of the source database, as well as whether or not an existing database with the same name should be automatically overwritten or not. srcCardNo srcDbID dstCardNo dstNameP hsDbCopyFlags tmpNameP IN IN IN IN IN IN

*dstDbIDP OUT Module number of source database. Database ID of source database. Module number of destination database. Name of new database. If a nil pointer is passed, then the name of the source database is used. One or more of hsDbCopyFlagXXX flags as described below in Table II.2. Temporary name to use while copying, or nil pointer to use default temporary name. The database ID of the created destination database is returned here unless dstDbIDP is a nil pointer. Section II - 34 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Software API Extension Table II.2 lists the possible flags for the hsDbCopyFlags parameter. Table II.2: hsDbCopyFlags Flags Flag Description hsDbCopyFlagPreserveCrDate Preserve the creation date of the source database. If not set, then the desti-

nation database gets the current date and time as its creation date. hsDbCopyFlagPreserveModDate Preserve the modification date of the source database. If not set, then the destination database gets the current date and time as its modification date. hsDbCopyFlagPreserveModNum Preserve the modification number of the source database. If not set, then the destination database gets a new modification number unrelated to the source databases. hsDbCopyFlagPreserveBckUpDate Preserve the backup date of the source database. If not set, then the desti-

nation database gets a backup date of 0. hsDbCopyFlagOKToOverwrite Preserve the creation date of the source database. If not set, then the desti-

nation database gets the current date and time as its creation date. Delete existing destination database first, if it exists. Normally any pre-exist-

ing destination database with the same name is left intact until the source has been copied over as a temporary database. This guarantees that any pre-existing database is not lost if the copy operation fails. If space is limited on the destination module, however, there may not be room for two tempo-

rary copies of the destination database, so this flag can be set to override the default behavior. hsDbCopyFlagDeleteFirst Returns 0 non-zero if no error if a Data, Memory, or other type of error occurs during the copy operation Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 35 Section II: Springboard expansion slot Version 1.0 4.5.11 HsEvtResetAutoOffTimer Summary Prototype Description Parameters Returns Provided for interrupt handlers so that they can reset the auto-off timer of the system and turn on the LCD if it is not already on. Err HsEvtResetAutoOffTimer (SDWord stayAwakeTicks, Boolean userOn) By default, if a module interrupt wakes the device and the handler returns without calling HsEvtResetAutoOffTimer(), the system puts the device back to sleep on the next round through the event loop (see Power Management Options for Interrupt Handlers on page II-8 for a complete description). However, by calling HsEvtResetAutoOffTimer(), the interrupt handler can tell the system to turn on the LCD if it is not already turned on and tell the system to stay awake for at least a certain number of system ticks. If this call is made when the LCD is already on, it has no effect other than to possibly extend the auto-off timer. The stayAwakeTicks parameter is specified in system ticks, but the current granularity of the system in this respect is only approximately five seconds. Consequently if you pass a value like sysTicksPerSecond*1, the system might not shut off for five seconds. Passing (-1) for stayAwakeTicks makes the system stay awake for at least the current auto-off time as specified in the General Preferences panel. stayAwakeTicks userOn IN IN The minimum amount of time, in system ticks, to keep the sys-

tem awake. Even though this parameter is specified in ticks, the minimum granularity of the system in this respect is about five seconds. Passing (-1) means to stay awake for the current Auto-off time as specified in the General Preference panel. If true, turn on the LCD if it is not already on. 0 if no error Section II - 36 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 External Interface Chapter 5 External Interface The Springboard expansion slot allows for hardware and software expansion of Handsprings family of PalmOS-compatible handheld computers and for seamless hot Plug & Play capability. Figure II.1 shows the block diagram of the slot interface. Figure II.1: Springboard Expansion Slot Connector Block Diagram Address 24 Control Data 16 Buffers Transceivers Host CPU Slot Connector IRQ*

VCC VDOCK MIC+

MIC LOWBAT*

RESET*

GND CD1*

CD2*

The Springboard expansion slot provides a slave-only interface for expanding the capabilities of the main handheld unit. The slot supports hot swapping via buffers and transceivers; it otherwise functions as if it is directly connected to the host CPU bus. Physically, the Springboard expansion slot connector is identical to a PCMCIA connector. However, the electrical specifications differ between these two connectors. Modules can be inserted into or removed from the base unit at any time, even when the device is on. When a module is inserted, the software and hardware automatically configure the module, making its features instantly available. A module can be a simple ROM-only module with a set of Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 37 Section II: Springboard expansion slot Version 1.0 additional applications, or it can provide additional powerful hardware functionality, such as network connectivity, sound support, and communications options. A variety of functions, such as pagers, radios, or backup flash memory, can be interfaced with Handsprings handheld computers in this way. Figure II.2 shows the Springboard 68-pin expansion slot. Figure II.2: Springboard expansion slot 3-D view Pin 2 Pin 1

... Pin 35 Section II - 38 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 5.1 Pinout External Interface Table II.1 summarizes the signal names with their respective pin numbers on the 68-pin expansion slot connector. Note that the signal direction (I/O/P/PU1) is viewed from the module to the handheld. Table II.1: Springboard Expansion Slot Connector Pin Summary Pin Name I/O/P/PU1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 GND D3 D4 D5 D6 D7 CS0*2 A10 OE*

A11 A9 A8 A13 A14 WE*

IRQ*

VCC VDOCK A16 A15 A12 A7 A6 A5 A4 A3 A2 A1 A0 D0 D1 D2 N.C. GND P I/O I/O I/O I/O I/O I I I I I I I I I O/PU P P I I I I I I I I I I I I/O I/O I/O P Function Ground Data Bit 3 Data Bit 4 Data Bit 5 Data Bit 6 Data Bit 7 Chip Select 0 Address Bit 10 Output Enable Address Bit 11 Address Bit 9 Address Bit 8 Address Bit 13 Address Bit 14 Write Enable Interrupt Request Module VCC, 3.3V Dock VCC Address Bit 16 Address Bit 15 Address Bit 12 Address Bit 7 Address Bit 6 Address Bit 5 Address Bit 4 Address Bit 3 Address Bit 2 Address Bit 1 Address Bit 0 Data Bit 0 Data Bit 1 Data Bit 2 No Connect Ground Pin Name I/O/P/PU 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 GND CD1*

D11 D12 D13 D14 D15 CS1*

N.C. N.C. N.C. A17 A18 A19 A20 A21 VCC VDOCK A22 A23 N.C. N.C. N.C. RESET*

N.C. MIC+

MIC-

N.C. LOWBAT*

D8 D9 D10 CD2*

GND P O/PU I/O I/O I/O I/O I/O I I I I I I P P I I I I I I I/O I/O I/O O/PU P Function Ground Card detect 1 Data Bit 11 Data Bit 12 Data Bit 13 Data Bit 14 Data Bit 15 Chip Select 1 No Connect No Connect No Connect Address Bit 17 Address Bit 18 Address Bit 19 Address Bit 20 Address Bit 21 Module VCC, 3.3V Docking Voltage Address Bit 22 Address Bit 23 No Connect No Connect No Connect Reset No Connect Microphone +

Microphone -

No Connect Low Battery Data Bit 8 Data Bit 9 Data Bit 10 Card detect 2 Ground 1. 2. I = input, O = output, and P = power, with respect to the module. PU indicates the signal is internally pulled up within the the handheld.

* indicates an active-low signal. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 39 Section II: Springboard expansion slot Version 1.0 5.2 Signal Descriptions The signals are described below in alphabetical order. Active-low signals have an asterisk * at the end of their names. A[23:0]

Address Bus The 24-bit address bus provides addressing for up to 32 MB. Each of the two chip selects (CS0 and CS1) has direct access of up to 16 MB. Address line A23 is the most significant address bit, and A0 is the least significant address bit. The default size of each region is 16 MB and is software programmable. This bus is an input to the expansion slot; it is always driven during normal and sleep mode. The address bus is valid throughout the entire bus cycle. I Note: In Visor, Handsprings first generation of handheld computer, A0 is not used. So in this implementation of the Springboard expansion slot, the bus is 16-bit only. CD1*, CD2* Module Detects O CD1* and CD2* are active-low module detect signals that indicate to the handheld when the expansion module has been firmly seated into the Springboard expansion slot. The two Module Detect pins are physically shorter than all other pins on the expansion connector. On the host side, the signals perform two functions: 1) they interrupt the handheld to alert the CPU that a module has been inserted or removed, and 2) they begin turning on the VCC power supply. Depending on the electrical load on the module, VCC is valid within 5 ms. Both signals should be tied directly to GND on the expansion module. CS0*, CS1* Chip Selects I These two active-low chip select signals control access to the two addressable regions on the module. The address space for CS0* is referred to as csSlot0; the address space for CS1* is referred to as csSlot1. In order for the PalmOS to recognize the module and its contents, use CS0* to access ROM or FLASH. CS1* is optional and can be used to interface with additional ROM, FLASH, UARTs, or other peripheral devices. Both chip select signals are asserted for the duration of the memory cycle. Only one of the two chip selects is valid for each module access. The address bus is guaranteed to be valid before and during the assertion of the chip select signal. Refer to Section 2.1, Memory Space, for more information on the chip selects and their corresponding address spaces. D[15:0]

Data Bus I/O The data bus consists of 16 data lines, D[15:0]. D15 is the most significant data bit, and D0 is the least significant data bit. Only 16-bit operations are performed on the data bus. Section II - 40 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 GND IRQ*

LOWBAT*

External Interface Module Ground GND is the ground connection to the module. All GND signals must be connected to the modules ground reference or plane. I O Interrupt Request The active low interrupt request is level sensitive. This signal is output from the Springboard module whenever interrupt service is required from the handheld computer. There is no default interrupt service routine for the module, so the application resident on the expansion module must install the interrupt service routine (ISR) during initialization (see Interrupts on page II-6 for more information on interrupt handling). Interrupt acknowledgment is user-defined and must be accommodated by the expansion module application as well. The internal Visor interface has a pull-up resistor, so the module does not require one. I Low Battery Warning The low battery warning signal indicates that the handhelds batteries are below 1.6 V or are being swapped out. When this signal is asserted, the expansion module is electrically removed to prevent data loss in the handheld. When the batteries are replaced, the module is re-inserted. MIC+, MIC- Microphone I OE*

RESET*

These two signals interface to the microphone on the handheld unit. The signals are a differential pair and are directly connected to an electret condenser microphone. Appropriate bias must be supplied by the module on the MIC+ signal. The Visor handheld uses a microphone with a 2.2K ohm impedance, a standby operating voltage of 2.0 V, and a maximum current consumption of 0.5 ma. Output Enable I OE* is the active-low output enable, or read signal, for the module. When qualified with a low on either CS0* or CS1*, a low on OE* indicates a read cycle from the module. The address bus is valid before the assertion of OE*. The module can drive the data bus as soon as a chip select and OE*

are asserted. Data must be driven for the entire cycle, as determined by the levels on the chip select and OE*. WE* is deasserted during read cycles. Note: The chip selects are not guaranteed to be asserted prior to the assertion of OE*. Also the cycle is ended when either a chip select or OE*

is deasserted. Module Reset RESET* is an active low reset signal for the expansion module. During module insertion, RESET* is asserted while VCC is rising; it is held asserted for 30 ms minimum after the module is inserted to allow circuitry on the module sufficient time to stabilize. Because module power is guaranteed to be applied within 5 ms, the module will have a minimum I Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 41 Section II: Springboard expansion slot Version 1.0 VCC VDOCK WE*

valid reset signal of 25 ms. Application software can also assert this signal at any time to reset the module. Module Power I VCC is the 3.3V power supply, which can be used to power the expansion module (some expansion modules can supply their own power). Power is not provided on these pins until the module is firmly seated in the slot and both module detects, CD1* and CD2*, are asserted. The power supply ramps up to 3.3V 5% within 5 ms of insertion. The maximum current that can be supplied by the slot is 100 mA. Expansion module designs that use this power source must take into account what the users will see when LOWBAT* is asserted and the Springboard expansion slot power is removed. Docking voltage I This pin could provide a charging supply to the module when the handheld is placed into a special charging dock. The handheld passes this charging supply from a pin on its cradle connector through to pins on the Springboard expansion module connector. For developers who want to use this pin, note that future Handspring products might make use of it and that the preliminary specification is 5V

@ 1A max. Write Enable WE* is the active-low write enable signal for the module. When qualified with a low on either CS0* or CS1*, a low on WE* indicates a write cycle to the module. The address bus is valid before the assertion of WE*. The data bus, driven by the host interface, is valid before the assertion of WE*. In addition, WE* is deasserted prior to the deassertion of the chip select. OE* is deasserted during write cycles. I Note: Because there is not a separate write enable for each byte, all 16 bits of the data bus are written at the same time. Thus there is no support for byte writes to the expansion module. Section II - 42 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Electrical and mechanical specifications Chapter 6 Electrical and mechanical specifications This chapter provides the electrical and timing characteristics of the Visor handheld and Springboard module. It also provides electrical and mechanical guidelines for your Springboard design. 6.1 Absolute electrical maximum ratings Table II.1 lists the maximum electrical ratings for the Visor handheld. Table II.1: Absolute electrical maximum ratings for the Visor handheld Rating Symbol Value Storage Temperature Range Operating Temperature Range Tstg TA

-20 to 85 0 to 50 Unit

C

C 6.2 DC electrical characteristics Table II.2 lists the DC electrical characteristics for Springboard modules. Unless otherwise specified, all parameters are specified at VCC = 3.3V, 25 C. Table II.2: DC electrical characteristics Symbol Parameter Vcc Supply Voltage1 Icc Is1 Is2 VIH VIL VOH VOL IIL IOZ 3 VDOCK Operating Current Standby Current, LOWBAT* = H Standby Current, LOWBAT* = L2 Input High Voltage Input Low Voltage Output High Voltage (IOH = 2.0 mA) Output Low Voltage (IOL = -2.5 mA) Input Leakage Current (0V <= VIN <= Vcc) 3-state Leakage Current (0V <= VOUT <= Vcc) Docking Voltage Min 3.0 2.0 0.0 2.4 0.0 Max 3.6 100 100 10 Vcc + 0.5 0.8 Vcc + 0.5 0.4 5 5 5 Unit V mA m A m A V V V V m A m A V In Visor, Handspring first generation of handheld computer, the minimum supply voltage could actually be zero if LOWBAT* is asserted. 1. 2. Since the Visor handheld (see note 1) actually removes power from the Springboard expansion slot, this specification is for future product compatibility. 3. Prelimnary. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 43 Section II: Springboard expansion slot Version 1.0 6.3 AC Characteristics This section lists the AC timing parameters for Springboard modules. Unless otherwise specified, all parameters are specified at VCC = 3.3V, 25 C. Table II.3: Read Cycle Timing Parameters Num Parameter 1 2 3 4 5 6 7 Address valid to CSx* asserted WE* negated before address valid CSx* asserted to OE* asserted1 Data valid from CSx* asserted CSx* pulse width Data in hold after CSx* negated OE* negated after CSx* negated Min 55

-5 125 + nT 5 3 Max Unit 5 95 + nT2 425 26 ns ns ns ns ns ns ns 1. 2. The chip selects are not guaranteed to be asserted prior to the assertion of OE*. Also the cycle is ended when either a chip select or OE* is deasserted. n is the number of wait states. T is the system clock period. Figure II.1: Read Cycle Timing A[23:0]

CSx*

OE*

WE*

D[15:0]

2 1 5 3 4 7 6 Section II - 44 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Electrical and mechanical specifications Table II.4: Write Cycle Timing Num Parameter 1 2 3 4 5 6 7 Address valid to CSx* asserted CSx* asserted to WE* asserted CSx* asserted to data valid CSx* pulse width WE* negated before CSx* negated Data hold after CSx* negated CSx* negated to data in, Hi-Z 1. n is the number of wait states. T is the system clock period. Figure II.2: Write Cycle Timing Min 55

-5 125 + nT1 25 35 Max Unit 13 45 425 40 55 ns ns ns ns ns ns ns A[23:0]

CSx*

OE*

WE*

D[15:0]

1 4 2 5 7 3 6 6.4 Springboard connector insertion/extraction force ratings Table II.5 lists the mechanical insertion/extraction force ratings for the Springboard expansion slot connector. Table II.5: Insertion/extraction force for the Springboard expansion slot connector Rating Insertion force1 (PRELIMINARY) Extraction force (PRELIMINARY) Value 1.5 - 6 1.5 - 5 Unit pounds pounds 1. These rating were verified up to 3000 insertion/extraction of the module. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 45 Section II: Springboard expansion slot Version 1.0 6.5 Springboard module base color The Visor handheld basic graphite color is also used for the module. The specification for this color is:

Material Color Texture GE C2800 PC/ABS BK-1455 11010 Section II - 46 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 HsExt.h Header File Chapter 7 HsExt.h Header File This chapter lists the HsExt.h header file, which contains the equates for all the constants referenced in this manual. After the tools have been installed, the file can be found in the

<installDir>\PalmTools\m68k-palmos-coff\include\PalmOS\Handspring folder. Handspring Common Includes Copyright 1998 Handspring, Inc. All Rights Reserved.

* Project:

* Copyright info:

* FileName:

* Description:

* ToDo:

* History:

13-Jan-1999 RM - Created by Ron Marianetti Public header file for the Handspring extensions to PalmOS HsExt.h

#ifndef __HSEXT_H__

#define __HSEXT_H__

// Include Common equates

#include <Common.h>

// Handspring Database creator IDs

#include <HsCreators.h>

// Handspring API Equates

// This is the Handspring feature id. Apps can tell if they're on

// a handspring device if they get 0 err back from:

#define hsFtrCreator err = FtrGet (hsFtrCreator, hsFtrIDVersion, &value)

'hsEx'

// 0xMMmfsbbb, where MM is major version, m is minor version

// f is bug fix, s is stage: 3-release,2-beta,1-alpha,0-development,

// bbb is build number for non-releases

// V1.12b3 would be: 0x01122003

// V2.00a2 would be: 0x02001002

// V1.01 would be: 0x01013000

#define hsFtrIDVersion 0

// Modification date of Handspring extensions

#define hsFtrIDModDate 1 Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 47 Section II: Springboard expansion slot Version 1.0

// Feature number indicating that the Launcher Database Mgr library is loaded.

// The value of the feature is the refNum of the loaded library.

// Call FtrGet (hsFtrCreator, hsFtrIDLdbMgrLibRefNum, ...) to get this feature.

#define hsFtrIDLdbMgrLibRefNum 2

// Error codes

#define hsErrorClass

#define hsErrNotSupported

#define hsErrInvalidCardNum

#define hsErrReadOnly

#define hsErrInvalidParam

#define hsErrBufferTooSmall

#define hsErrInvalidCardHdr

#define hsErrCardPatchAlreadyInstalled (hsErrorClass | 7)

#define hsErrCardPatchNotInstalled (hsErrorClass | 8)

(hsErrorClass | 4)

(hsErrorClass | 5)

(hsErrorClass | 6)

(hsErrorClass | 1)

(hsErrorClass | 2)

(appErrorClass+0x0100)

(hsErrorClass | 3)

// Key codes and events

// Max card user event number that can be passed to HsCardEventPost()

#define hsMaxCardEvent 0x07

// Max app user event number that can be passed to HsAppEventPost()

#define hsMaxAppEvent 0x03

// Keycode range assigned to us from 3Com: vchrSlinkyMin to vchrSlinkyMax

#define hsChrRangeMin

#define hsChrRangeMax 0x1600 0x16FF

// New key codes we generate for the "dot" soft icons

#define hsChrMidLeftDot

#define hsChrMidRightDot (hsChrRangeMin+1)

#define hsChrBotLeftDot

#define hsChrBotRightDot (hsChrRangeMin+3)

(hsChrRangeMin+2) hsChrRangeMin

// The virtual cradle 2 character i

#define hsChrCradle2OnChr

#define hsChrCradle2OffChr

(hsChrRangeMin+4) // dock input level asserted

(hsChrRangeMin+5) // dock input level de-asserted

// card removed or inserted

#define hsChrCardStatusChg

(hsChrRangeMin+6)

// Range of key events available to the HsCardEventPost() call

#define hsChrCardUserFirst

#define hsChrCardUserLast

(hsChrRangeMin+0x80)

(hsChrCardUserFirst+hsMaxCardEvent)

// Range of key events available to the HsAppEventPost() call

#define hsChrAppUserFirst

#define hsChrAppUserLast

(hsChrCardUserLast+1)

(hsChrAppUserFirst+hsMaxAppEvent)

// Special Databases that can be present on a card

// Handspring defined selector codes for the "CardSetup" application on

// a card

#define hsSysAppLaunchCmdInstall (sysAppLaunchCmdCustomBase+0)

#define hsSysAppLaunchCmdRemove (sysAppLaunchCmdCustomBase+1) Section II - 48 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 HsExt.h Header File

// The cmdPBP parmeter to the setup app's PilotMain() will point to

// this structure when the hsSysAppLaunchCmdInstall action code is sent typedef struct

Word Byte cardNo;

isReset;

// card # of removable card

// true if being called due to a soft or app must be "tolerant"

install action code it was already reset. Byte reserved;

// hard reset. The setup

// of being sent an

// during reset even if

// installed before the

// Database info of the launched setup app, sent for convenience Word

// card # of setup app LocalID setupCardNo;

setupDbID;

// database ID of setup app

} HsSysAppLaunchCmdInstallType;

// The cmdPBP parmeter to the setup app's PilotMain() will point to

// this structure when the hsSysAppLaunchCmdRemove action code is sent typedef struct

cardNo;

} HsSysAppLaunchCmdRemoveType;

Word

// card # of removable card

// If a card has a database with this type and creator, it will be automatically

// copied to card 0 when inserted and sent an action code of

// hsSysAppLaunchCodeInstall. Likewise, when the card is removed,

// this app will be sent an action code of hsSysAppLaunchCodeRemove and

// then it will be deleted.

// hsFileCCardSetup

// hsFileTCardSetup

<= defined in HsCreators.h

<= defined in HsCreators.h

// If a card has an application database with this name, it will be

// automatically launched when the card is inserted

#define hsWelcomeAppName

"CardWelcome"

// Library alias names that SysLibFind maps to a real library name

// according to the appropriate hsPrefSerialLibXXX setting.

// By Convention, library alias names start with a '*'. The exception

// is the "Serial Library" name which is mapped in order to

// be compatible with pre-existing applications that already use it.

#define hsLibAliasDefault

#define hsLibAliasHotSyncLocal "*HsLoc SerLib" //hsPrefSerialLibHotSyncLocal

#define hsLibAliasHotSyncModem "*HsMdm SerLib" //hsPrefSerialLibHotSyncModem

#define hsLibAliasIrda

#define hsLibAliasConsole

"*Cons SerLib" //hsPrefSerialLibConsole

"*Irda SerLib" //hsPrefSerialLibIrda

"Serial Library" //hsPrefSerialLibDef

// Actual library name of the Dragonball's built-in serial library.

// This is the default value of the hsPrefDefSerialLib pref setting which

// SysLibFind uses to map an incoming library name to an actual library

// name.

#define hsLibNameBuiltInSerial "BuiltIn SerLib"

// Flags for the HsDatabaseCopy routine

Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 49 Section II: Springboard expansion slot Version 1.0

#define hsDbCopyFlagPreserveCrDate 0x0001 // preserve creation date

#define hsDbCopyFlagPreserveModDate 0x0002 // preserve modification date

#define hsDbCopyFlagPreserveModNum 0x0004 // preserve modification number

#define hsDbCopyFlagPreserveBckUpDate 0x0008 // preserve backup date

#define hsDbCopyFlagOKToOverwrite 0x0010 // if true, it's OK to overwrite existing database.

#define hsDbCopyFlagDeleteFirst 0x0020 // delete dest DB first, if it exists. Use this if space limited on dest card. Implies hsDbCopyFlagOKToOverwrite

#define hsDbCopyFlagPreserveUniqueIDSeed 0x0040 // preserve database unique ID seed

// is

// Flags for the HsDmGetNextDBByTypeCreator() call

#define hsDmGetNextDBFlagOneCard 0x00001 // Only search 1 card

// Reason codes for the card power handler

typedef enum

hsCardPwrDownNormal = 0, hsCardPwrDownLowVoltage = 1

// normal power down

// low voltage

} HsCardPwrDownEnum;

// Equates for the HsCardAttrGet/Set calls

// Prototypes for the various handlers that can be installed for a card typedef void(*HsCardIntHandlerPtr) (DWord cardParam, Boolean* sysAwakeP);

typedef void(*HsCardPwrHandlerPtr) (DWord cardParam, Boolean sleep,

*HsCardPwrDownEnum*/ reason);

typedef Boolean (*HsCardEvtHandlerPtr) (DWord cardParam, Word evtNum, Word /

Word evtParam);

// The attributes typedef enum

// Type : RW : Description

hsCardAttrRemovable,// Byte : R : true if card is removable hsCardAttrHwInstalled,// Byte : R : true if card hardware is installed hsCardAttrSwInstalled,// Byte : R : true if card software is installed hsCardAttrCsBase, hsCardAttrCsSize, hsCardAttrAccessTime,// DWord : RW : required access time

// DWord : R : address of first chip select

// DWord : RW : size of chip selects hsCardAttrReset, hsCardAttrIntEnable,// Byte : RW : if true, enable card interrupt

// Byte : RW : if true, assert reset to card hsCardAttrCardParam,// DWord : RW : parameter passed to int handler, handler hsCardAttrIntHandler,// HsCardIntHandlerPtr hsCardAttrPwrHandler,// HsCardPwrHandlerPtr

// power handler, and event

// : RW : card interrupt handler

// : RW : card power handler Section II - 50 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 HsExt.h Header File hsCardAttrEvtHandler,// HsCardEvtHandlerPtr

// : RW : card event handler hsCardAttrLogicalBase,// DWord : R : logical base address of card hsCardAttrLogicalSize,// DWord : R : total reserved address space for card hsCardAttrHdrOffset,// DWord : R : offset from halCardAttrLogicalBase to

// card header

// Leave this one at end!!!

hsCardAttrLast

} HsCardAttrEnum;

// Equates for the HsPrefGet/Set calls

// The prefs typedef enum

// Type : Description

// The following are used by SysLibFind() to resolve a virtual library

// name to an actual one. hsPrefSerialLibDef,

// Char[] : Name of serial library

// to substitute for hsLibAliasDefault hsPrefSerialLibHotSyncLocal, // Char[] : Name of serial library

// to substitute for hsLibAliasHotSyncLocal hsPrefSerialLibHotSyncModem, // Char[] : Name of serial library

// to substitute for hsLibAliasHotSyncModem hsPrefSerialLibIrda, // Char[] : Name of serial library hsPrefSerialLibConsole, // Char[] : Name of serial library

// to substitute for

// to substitute for hsLibAliasIrda hsLibAliasConsole

// Leave this one at end!!!

hsPrefLast

} HsPrefEnum;

// Prototype of the App Event Handler that can be setup using

// HsAppEventHandlerSet() and triggered using HsAppEventPost(). The

// evtRefCon is a copy of evtRefCon passed to HsAppEventHandlerSet()

// This routine should not rely on globals since it may be called

// while in the context of another app's action code.

typedef Boolean (*HsAppEvtHandlerPtr) (DWord evtRefcon, Word evtNum, Word evtParam);

// Handspring selectors for the Handspring system trap

// NOTE: If you add traps here, you must:

2.) Modify the PrvHsSelector routine in HsExtensions.c to recognize 1.) Add a prototype to the Prototypes section of this header or to the prototype section of HsExtPrv.h if it's private call Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 51 Section II: Springboard expansion slot Version 1.0 and dispatch to the new call

// IMPORTANT: If you change any of these trap numbers, be sure to

// update any *Patches.txt patch files that use the trap number to patch

// the object code.

// This is the trap number we use for the Hs trap calls

// IMPORTANT: If this changes, you must manually update the any object code

// patches files. PalmVSystemboot10001Patches.txt is at least one that

// patches this trap in .

#define sysTrapHsSelector sysTrapSysReserved4

#define hsSelectorBase 0 typedef enum

hsSelInfo = hsSelectorBase, // 0 hsSelPrvInit, hsSelPrvCallSafely, hsSelPrvCallSafelyNewStack, // 3 hsSelDatabaseCopy, hsSelExtKeyboardEnable, hsSelCardAttrGet, hsSelCardAttrSet, hsSelCardEventPost, hsSelPrvErrCatchListP, hsSelPrefGet, hsSelPrefSet,

// 5

// 9

// 2

// 4

// 6

// 7

// 8

// 1

// A

// B hsSelDmGetNextDBByTypeCreator, // C hsSelDmGetNextDBInit,

// D hsSelCardHdrUpdate, hsSelAppEventHandlerSet, // F hsSelAppEventPost,

// E

// 10 hsSelUsbCommStatePtr, hsSelCardPatchInstall, hsSelCardPatchRemove,

// 11

// 12

// 13 hsSelEvtResetAutoOffTimer, // 14 hsSelDmDatabaseUniqueIDSeed, // 15 hsSelAboutHandspringApp, // 16 hsSelDmDatabaseIsOpen, hsSelDmDatabaseIsProtected, // 18

// 17

// Leave this one at the end!!!

hsSelLast

} HsSelEnum;

#define hsNumSels (hsSelLast - hsSelBase)

// <chg 11-6-98 RM>

#if (defined __GNUC__) && (EMULATION_LEVEL == EMULATION_NONE)

#define SYS_SEL_TRAP(trapNum, selector) \

__attribute__ ((inline (0x3f3c, selector, m68kTrapInstr+sysDispatchTrapNum,trapNum)))

#else

#define SYS_SEL_TRAP(trapNum, selector) \

Section II - 52 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0

#endif FOURWORD_INLINE(0x3f3c, selector, m68kTrapInstr+sysDispatchTrapNum,trapNum) HsExt.h Header File x = 1;

HsCardErrTry

// HsCardErrTry / Catch / support

// Typical Use:

// x = 0;

// // access card in some manner that may fail

// value = cardBaseP[0]

// // do other stuff too

// // access card again

// value = cardBaseP[1]

// // Recover or cleanup after a failure in above Try block

// // The code in this block does NOT execute if the above

// // try block completes without a card removal

if (x > 1) SysBeep(1);

} HsCardErrEnd HsCardErrCatch

// Set local variable in Try

// Try & Catch macros

#define HsCardErrTry

ErrExceptionType_tryObject;

Ptr*

_listP;

_listP = HsPrvErrCatchListP();

_tryObject.err = 0;

_tryObject.nextP = (ErrExceptionPtr)*_listP;\

*_listP = (Ptr)&_tryObject;

if (ErrSetJump(_tryObject.state) == 0) \

volatile Word ShlDBHdrTablePtr volatile hdrTabP = nil;

// NOTE: All variables referenced in and after the ErrCatch must

// be declared volatile. Here's how for variables and pointers:

// If you have many local variables after the ErrCatch you may

// opt to put the ErrTry and ErrCatch in a separate enclosing function.

#define HsCardErrCatch oldMode;

*_listP = (Ptr)_tryObject.nextP;

else

*_listP = (Ptr)_tryObject.nextP;

Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 53 Section II: Springboard expansion slot

#define HsCardErrEnd

Version 1.0

// Prototypes

DWord HsInfo (Word item, Word paramSize, void* paramP) SYS_SEL_TRAP (sysTrapHsSelector, hsSelInfo);

Err tmpNameP, Err Err Err Err HsDatabaseCopy (Word srcCardNo, LocalID srcDbID, Word dstCardNo, char* dstNameP, DWord hsDbCopyFlags, char*

SYS_SEL_TRAP (sysTrapHsSelector, hsSelDatabaseCopy);

LocalID* dstDbIDP) HsExtKeyboardEnable (Boolean enable) SYS_SEL_TRAP (sysTrapHsSelector, hsSelExtKeyboardEnable);

HsCardAttrGet (Word cardNo, Word /*HsCardAttrEnum*/ attr, SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardAttrGet);

void* valueP) HsCardAttrSet (Word cardNo, Word /*HsCardAttrEnum*/ attr, SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardAttrSet);

void* valueP) HsCardEventPost (Word cardNo, Word evtNum, Word evtParam) SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardEventPost);

Ptr*

HsPrvErrCatchListP (void) SYS_SEL_TRAP (sysTrapHsSelector, hsSelPrvErrCatchListP);

Err Err Err Err Err HsPrefGet (Word /*HsPrefEnum*/ pref, void* bufP, DWord* prefSizeP) SYS_SEL_TRAP (sysTrapHsSelector, hsSelPrefGet);

HsPrefSet (Word /*HsPrefEnum*/ pref, void* bufP, DWord prefSize) SYS_SEL_TRAP (sysTrapHsSelector, hsSelPrefSet);

// This call behaves the same as the PalmOS DmGetNextDatabaseByTypeCreator

// but can also be used in conjunction with the HsGetNextDBInit()

// call to start the search at a particular card number or limit

// the search to one card. HsDmGetNextDBByTypeCreator (Boolean newSearch, DmSearchStatePtr stateInfoP, ULongtype, ULong creator, Boolean onlyLatestVers, UIntPtr cardNoP, LocalID* dbIDP) SYS_SEL_TRAP (sysTrapHsSelector, hsSelDmGetNextDBByTypeCreator);

// Can be used to init the stateInfo for HsDmGetNextDBByTypeCreator()

// so that it starts at a particular card number or limits the

// search to one card. The flags are 1 or more of hsDmGetNextDBFlagXXX HsDmGetNextDBInit (DmSearchStatePtr stateInfoP, DWord flags, Word cardNo) SYS_SEL_TRAP (sysTrapHsSelector, hsSelDmGetNextDBInit);

// This is an advanced call for use by card flash utilities that

// change which card header to use AFTER the card is installed. HsCardHdrUpdate (Word cardNo, void* newCardHdrP) Section II - 54 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 HsExt.h Header File SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardHdrUpdate);

// Register an app event handler that can be triggered using

// HsAppEventPost(). The evtRefCon will be passed to the

// event handler when it is called.

// The event Handler should not rely on global variables since it may

// be called while in the context of another app's action code.

// Instead, pass in a pointer in evtRefCon to globals. HsAppEventHandlerSet (HsAppEvtHandlerPtr procP, DWord evtRefCon) SYS_SEL_TRAP (sysTrapHsSelector, hsSelAppEventHandlerSet);

// Post an event to be processed by the AppEventHandler procedure

// registered with HsAppEventHandlerSet(). The evtNum param

// can be from 0 to hsMaxAppEvent. HsAppEventPost (Word evtNum, Word evtParam) SYS_SEL_TRAP (sysTrapHsSelector, hsSelAppEventPost);

Err Err memory that can be shared between the debugger stub's communication support and run-time communication support.

// Returns a pointer to a 4 byte area of global

// This can be used by USB for example to store the enumeration state.

// This is an exported stub into the HAL layer routine which actually

// does the real work. DWord*

HsUsbCommStatePtr (void) SYS_SEL_TRAP (sysTrapHsSelector, hsSelUsbCommStatePtr);

// Patch a system trap for a card. This call should be used instead of

// SysSetTrapAddress() by card setup utilities because it will

// insure compatibility with HackMaster and any HackMaster

// hacks that are installed.

// The implementation of the patch should use HsCardPatchPrevProc()

// to get the address of the old routine to chain to:

// IMPORTANT: Setup utilities are only allowed to install *ONE*

// patch for each trapNum!

HsCardPatchInstall (Word trapNum, void* procP) HsCardPatchPrevProc (&oldProcP);

(*oldProcP)();

SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardPatchInstall);

// Remove a patch of a system trap installed using HsSysPatchInstall().

// The 'creator' and 'id' must the same as passed to HsSysPatchInstall(). HsCardPatchRemove (Word trapNum) SYS_SEL_TRAP (sysTrapHsSelector, hsSelCardPatchRemove);

Err Err

// Macro to get the old routine address of a trap patched using

// HsCardPatchInstall()

#define HsCardPatchPrevProc(trapNum,oldProcPP)

FtrGet (hsFileCCardSetup, trapNum, (DWord*)oldProcPP) Err Err

// Called from interrupt routines to reset the auto-off timer

// and tell the system whether or not the user hardware (i.e. LCD)

// needs to be woken up or not. Note: The granularity of the

// stayAwakeTicks is only about 5*sysTicksPerSecond. HsEvtResetAutoOffTimer (SDWord stayAwakeTicks, Boolean userOn) SYS_SEL_TRAP (sysTrapHsSelector, hsSelEvtResetAutoOffTimer);

// Call to get or set the Unique ID seed field of a database HsDmDatabaseUniqueIDSeed (Word cardNo, LocalID dbID, Boolean set, DWord* uniqueIDSeed) SYS_SEL_TRAP (sysTrapHsSelector, hsSelDmDatabaseUniqueIDSeed);

void HsAboutHandspringApp (UInt16 appCardNo, LocalID appDbId,

// <chg 29-Jun-99 dia> Added extra credits string parameter. Copyright 1999 by Handspring, Inc. All rights reserved. Section II - 55 Section II: Springboard expansion slot Version 1.0 Char* copyrightYearStrP, Char* extraCreditsStrP) SYS_SEL_TRAP (sysTrapHsSelector, hsSelAboutHandspringApp);

// <chg 30-Jun-99 dia> Defined macros to make about box easier to call.

#define HsAboutHandspringAppWithYearId(yearId)

do

UInt16 appCardNo;

LocalID appDbId;

VoidHandyearStrH;

Char* yearStrP;

yearStrH = DmGetResource (strRsc, yearId);

yearStrP = MemHandleLock (yearStrH);

SysCurAppDatabase(&appCardNo, &appDbId);

HsAboutHandspringApp (appCardNo, appDbId, yearStrP, NULL);\

MemPtrUnlock (yearStrP);

DmReleaseResource (yearStrH);

while (0)

#define HsAboutHandspringAppWithYearCredId(yearId, creditsId)\

do

UInt16 appCardNo;

LocalID appDbId;

VoidHandyearStrH, extraStrH;

Char* yearStrP;

Char*

extraStrP;

yearStrH = DmGetResource (strRsc, yearId);

yearStrP = MemHandleLock (yearStrH);

extraStrH = DmGetResource (strRsc, creditsId);

extraStrP = MemHandleLock (extraStrH);

SysCurAppDatabase(&appCardNo, &appDbId);

HsAboutHandspringApp (appCardNo, appDbId, yearStrP, extraStrP);\

MemPtrUnlock (extraStrP);

DmReleaseResource (extraStrH);

MemPtrUnlock (yearStrP);

DmReleaseResource (yearStrH);

while (0)

Byte Byte

#endif Section II - 56 HsDmDatabaseIsOpen (UInt16 cardNo, LocalID dbID) SYS_SEL_TRAP (sysTrapHsSelector, hsSelDmDatabaseIsOpen);

HsDmDatabaseIsProtected (UInt16 cardNo, LocalID dbID) SYS_SEL_TRAP (sysTrapHsSelector, hsSelDmDatabaseIsProtected);

Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section III Cradle connector The cradle connector provides serial communication with Handsprings family of handheld computers. The cradle connector, shown in Figure III.1) is located at the bottom of the handheld device. It is typically used for communicating with a PC or Mac for data synchronization;

however, a variety of peripherals such as a keyboard, pager, or modem can also be interfaced to the handheld unit through this port. Figure III.1: Cradle view Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 1 Section III: Cradle connector Version 1.0 Chapter 1 Functional Description The Cradle Connector contains two serial buses that communicate with external devices: a USB bus and a simple serial bus. The high-speed USB interface is a slave-only interface, providing a payload bandwidth of up to 400 Kbps between a host PC or Mac and the handheld device. The serial port provides asynchronous capability to low-speed devices (9600 Kbps or less). Figure III.1 shows how the Cradle Connector interfaces with the handheld. Figure III.1: Cradle Connector Interface Handheld USB Interface Cradle Connector USB_D+

USB_D-

VDOCK GND TXD RXD HS1*

KBD*

TXD RXD HotSync IRQ*

IRQ2*

Section III - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Functional Description Figure III.2: 3D View of Visor handheld bottom or cradle connector Pin 1 Figure III.3: 3D View of Eight-Pin cradle connector Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 3 Section III: Cradle connector Version 1.0 Chapter 2 Signal Descriptions This section defines the functions of the signals on the eight-pin Cradle Connector. Figure III.1 is a three-dimensional view of the Visor base, showing the eight pins. Table III.1 lists the signals with their respective pin assignments. The signals are described in alphabetical order following the table. Active-low signals have a * at the end of their names. Table III.1: Cradle Connector Pin Summary Pin Name I/O/P1 Function 1 2 3 4 5 6 7 8 RXD KBD*

HS1*

GND USB_D-

USB_D+

VDOCK TXD I I I P I/O I/O P O UART Receive Data, TTL level HotSync 2, ground for keyboard HotSync interrupt Ground USB Data- differential signal USB Data+ differential signal Expansion module charging voltage UART Transmit Data, TTL level, or Power 1. I = input, O = output, and P = power, with respect to the connector. GND HS1*

KBD*

Ground GND is the ground connection to the handheld. This signal must be connected to the ground reference in the cradle or peripheral. P HotSync Interrupt This active-low interrupt pin is asserted low in order to initiate a HotSync with the handheld. In a cradle application, a push button would momentarily short this signal to GND to begin a HotSync. I Keyboard Detect This active-low pin is held low in order to indicate the presence of a keyboard. While KBD* is held low, the handheld expects keyboard data to be sent on the RXD pin. Refer to Chapter 3, Keyboard Support via Remote UI, on page III-6 for information on the keyboard data packet structure supported by the handheld. I Section III - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 RXD TXD USB_D+

USB_D-

VDOCK Signal Descriptions Receive Data RXD connects directly to the Visors CPU UART. Note that RXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. RXD is an input to the handheld and an output from a cradle or peripheral. O Transmit Data TXD connects directly to the CPUs UART. Note that TXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. TXD is an output from the handheld and an input to a cradle or peripheral. This pin provides up to 3 mA maximum at 3.0 V when KBD* is asserted for low-

power peripherals, such as keyboards. I USB Data+

I/O USB_D+ is the positive signal in the USB differential pair. This signal and USB_D- implement the USB signaling protocol for communicating with a USB host, such as a PC or a Mac. USB Data-

This signal is the negative signal in the USB differential pair. This signal and USB_D+ implement the USB signaling protocol for communicating with a USB host, such as a PC or a Mac. I/O Cradle Power P This pin provides a high-voltage charging supply to the module when the handheld is placed into a special charging dock. The handheld passes this charging supply from a pin on its cradle connector through to pins on the Springboard Expansion module connector. Typically this supply is used to recharge batteries integrated into the expansion module. For developers who want to use this pin, please contact Developer Support at DevSupport@handspring.com to verify its availability on future products. Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 5 Section III: Cradle connector Version 1.0 Chapter 3 Keyboard Support via Remote UI The handheld platform supports character input from an external keyboard or pen-based device through the Cradle Connector located at the bottom of the handheld device. Pin 2 of the eight-pin Cradle Connector is the keyboard detect pin (KBD*). Grounding this pin indicates to the handheld processor that:

1. A keyboard or other remote UI device is present on the Cradle Connector, and 2. Incoming serial data packets on RXD (pin 1 on the Cradle Connector) should be interpreted as described by this document. Note that the Cradle Connector does not include hardware signaling for buffer overflow conditions within the handheld device. Therefore the maximum recommended serial transfer speed to the handheld device is limited to 9600 kbps. Remote UI is supported in all existing versions of PalmOS; for more information please see the PalmOS Programmers Companion at http://www.palm.com/devzone/docs.html. 3.1 Remote UI Packet Description As long as pin 2, KBD*, on the Cradle Connector is held low, the handheld will receive incoming data packets on RXD and interpret them as Remote UI Packets. Remote UI Packets have three sections: a header, a body, and a CRC as shown in Figure III.1. Figure III.1: Remote UI Packet Header 10 Body 16 CRC 2

# of bytes The Remote UI Packet structure is flexible enough to support remote input from a variety of devices, but for software simplification, most of these fields can be hardcoded for keyboard-

specific input. Section III - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Keyboard Support via Remote UI Table III.1 describes in detail the fields in the header, body, and CRC sections. Table III.1: Remote UI Packet Fields Field Data Length

(in Bytes) Parameter Name Value Comment 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 2 1 1 1 1 2 1 1 1 1 1 1 2 2 1 1 2 2 2 2 signature1 signature2 dest src type Header Fields 0xBEEF Indicates serial link packet. 0xED 0x02 0x02 0x00 Indicates serial link packet. Indicates remote UI serial link packet. Indicates remote UI serial link packet. Typically used as return address for response messages. Not required for keyboard input. Indicates system packet type to the handheld. bodySize calculated Size of body in bytes. transactionID calculated Increment by one for each new message. Not required for keyboard input (will not be checked). checksum calculated 8-bit sum of header fields NOT including this field. Data Fields command 0x0D Indicates that input is a remote event. filler dont care For word alignment. penDown 0 or 1 Indicates pen event. Reset to 0 for keyboard input. filler penX penY filler keyPress keyModifier keyAscii keyCode dont care For word alignment. 0 0 Pen X coordinate. Reset to 0 for keyboard input. Pen Y coordinate. Reset to 0 for keyboard input. dont care For word alignment. 0x01 lookup lookup 0x00 Indicates a key has been pressed. Modifier bits (shift, control, etc.) Bitmapped to this 16-bit field. PalmOS keycodes see chars.h. Reserved - Always set to 0. CRC Field CRC calculated Computed using table method; see Section 3.4, CRC Computation, for more information. Uses big-endian byte ordering. The following subsections provide more details on the contents of the header, body, and CRC. 3.2 Remote UI Packet Header The Remote UI Packet header consists of eight fields as shown in Figure III.2. Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 7 Section III: Cradle connector Version 1.0 Figure III.2: Remote UI Packet Header signature1 signature2 2 1 dest 1 src 1 type 1 bodySize transactionID checksum 2 1 1 The first two fields (signature1 and signature2) contain a predefined code that indicates to the handheld that the incoming packet is a serial link packet. The dest and src fields refer to the logical socket used for communication for remote UI. For keyboard applications, these fields are both set to 0x02. The type field indicates that this packet is a system packet. It is hardcoded to 0x00. The 16-bit bodySize field must contain the size of the body portion of the packet (in bytes). Do not include the size of the header or CRC bytes in this calculation. The transactionID field is a running message counter, and is typically used for two-way communications over the serial port. Reply messages are tagged with the transactionID of the original message. Because the handheld does not send responses to keyboard packets, this field is not used and can be set to any value. However, other types of remote UI devices should increment transactionID by one for each packet sent. The checksum value is a simple eight-bit addition of the bytes in the header. If a checksum mismatch occurs, the handheld searches all incoming data bytes for signature1 in order to resynchronize to the sender. Sample code to generate a checksum is shown below. PrvCalcHdrChecksum(Checksum SlkChecksum, BytePtr bufP, Long count);

* SlkChecksum

* Computes the 16-bit checksum of bytes in a buffer.

* Arguments:

* Returns:

static SlkPktHeaderChecksum PrvCalcHdrChecksum(SlkPktHeaderChecksum start, BytePtr bufP, Long count)

SlkChecksum start BytePtr bufP Long count 8-bit checksum of the data

-- starting checksum value

-- ptr to the data buffer

-- number of bytes in buffer

// The compiler produces the fastest code with a while(--count) loop... do {

start += *bufP++;

} while(--count);

return( start );

Section III - 8 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Keyboard Support via Remote UI 3.3 Remote UI Packet Body Figure III.3 shows the Remote UI Packet body. Figure III.3: Remote UI Packet Body com-

mand filler pen Down filler penX penY filler key Press 1 1 1 1 2 2 1 1 key Modi-

fier 2 keyAsc ii 2 key Code 2 The command field is always set to 0x0D, indicating that the packet contains remote event data. The penDown, penX, and penY fields define pen events; they are all reset to 0 for keyboard input. The keyPress field contains a flag that indicates a keypress has occurred on the remote UI device. The keyModifier and keyAscii fields define the keypress. The keyCode field is reserved for future purposes and should always be set to 0x0. The keyAscii values supported by PalmOS are defined in the chars.h include file within the PalmOS source code. The keyModifier values are defined in the PalmOS source file event.h;

they are also listed in Table III.2 below. Table III.2: Key Modifiers for PalmOS Key KeyModifier Field Values shiftKey capsLock numLock commandKey optionKey controlKey autoRepeatKey doubleTapKey poweredOnKey appEvtHookKey libEvtHookKey 0x0001 0x0002 0x0004 0x0008 0x0010 0x0020 0x0040 0x0080 0x0100 0x0200 0x0400 3.4 CRC Computation The 16-bit cyclic redundancy check (CRC) value is calculated using the contents of both the header and the body. Note that the handheld device uses big-endian byte ordering for computing a CRC, so keyboards must generate CRCs using big-endian byte ordering. CRCs are computed using the table look-up method. Source code to generate CRCs is shown in the example below. If the handheld detects a bad CRC, the packet is ignored, but no error response is sent back to the keyboard. Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 9 Section III: Cradle connector Version 1.0

* FUNCTION: Crc16CalcBlock

* DESCRIPTION: Calculate the 16-bit CRC of a data block using the table lookup method.

* PARAMETERS:

* RETURNS:

Word Crc16Calc (VoidPtr bufP, Word count, Word crc)

A 16-bit CRC for the data buffer. bufP count crc

-- pointer to the data buffer;

-- the number of bytes in the buffer;

-- the seed crc value; pass 0 the first time function is called, pass in new crc result as more data is added to packet and crc is updated. registerBytePtr byteP = (BytePtr)bufP;

WordPtr crctt

= (WordPtr)crctt_16;

// CRC translation table

// Calculate the 16 bit CRC using the table lookup method.

if ( count ) {

do {

crc = (crc << 8) ^ crctt[ (Byte)((crc >> 8) ^ *byteP++) ];

} while ( --count );

return( crc & 0xffff );

// This is the lookup table used when performing the 16-bit CRC calculation. //

static Word crctt_16[ 256 ] =

0x0000, 0x1021, 0x2042, 0x3063, 0x4084, 0x50A5, 0x60C6, 0x70E7, 0x8108, 0x9129, 0xA14A, 0xB16B, 0xC18C, 0xD1AD, 0xE1CE, 0xF1EF, 0x1231, 0x0210, 0x3273, 0x2252, 0x52B5, 0x4294, 0x72F7, 0x62D6, 0x9339, 0x8318, 0xB37B, 0xA35A, 0xD3BD, 0xC39C, 0xF3FF, 0xE3DE, 0x2462, 0x3443, 0x0420, 0x1401, 0x64E6, 0x74C7, 0x44A4, 0x5485, 0xA56A, 0xB54B, 0x8528, 0x9509, 0xE5EE, 0xF5CF, 0xC5AC, 0xD58D, 0x3653, 0x2672, 0x1611, 0x0630, 0x76D7, 0x66F6, 0x5695, 0x46B4, 0xB75B, 0xA77A, 0x9719, 0x8738, 0xF7DF, 0xE7FE, 0xD79D, 0xC7BC, 0x48C4, 0x58E5, 0x6886, 0x78A7, 0x0840, 0x1861, 0x2802, 0x3823, 0xC9CC, 0xD9ED, 0xE98E, 0xF9AF, 0x8948, 0x9969, 0xA90A, 0xB92B, 0x5AF5, 0x4AD4, 0x7AB7, 0x6A96, 0x1A71, 0x0A50, 0x3A33, 0x2A12, 0xDBFD, 0xCBDC, 0xFBBF, 0xEB9E, 0x9B79, 0x8B58, 0xBB3B, 0xAB1A, 0x6CA6, 0x7C87, 0x4CE4, 0x5CC5, 0x2C22, 0x3C03, 0x0C60, 0x1C41, 0xEDAE, 0xFD8F, 0xCDEC, 0xDDCD, 0xAD2A, 0xBD0B, 0x8D68, 0x9D49, 0x7E97, 0x6EB6, 0x5ED5, 0x4EF4, 0x3E13, 0x2E32, 0x1E51, 0x0E70, 0xFF9F, 0xEFBE, 0xDFDD, 0xCFFC, 0xBF1B, 0xAF3A, 0x9F59, 0x8F78, 0x9188, 0x81A9, 0xB1CA, 0xA1EB, 0xD10C, 0xC12D, 0xF14E, 0xE16F, 0x1080, 0x00A1, 0x30C2, 0x20E3, 0x5004, 0x4025, 0x7046, 0x6067, 0x83B9, 0x9398, 0xA3FB, 0xB3DA, 0xC33D, 0xD31C, 0xE37F, 0xF35E, 0x02B1, 0x1290, 0x22F3, 0x32D2, 0x4235, 0x5214, 0x6277, 0x7256, 0xB5EA, 0xA5CB, 0x95A8, 0x8589, 0xF56E, 0xE54F, 0xD52C, 0xC50D, 0x34E2, 0x24C3, 0x14A0, 0x0481, 0x7466, 0x6447, 0x5424, 0x4405, 0xA7DB, 0xB7FA, 0x8799, 0x97B8, 0xE75F, 0xF77E, 0xC71D, 0xD73C, 0x26D3, 0x36F2, 0x0691, 0x16B0, 0x6657, 0x7676, 0x4615, 0x5634, 0xD94C, 0xC96D, 0xF90E, 0xE92F, 0x99C8, 0x89E9, 0xB98A, 0xA9AB, 0x5844, 0x4865, 0x7806, 0x6827, 0x18C0, 0x08E1, 0x3882, 0x28A3, 0xCB7D, 0xDB5C, 0xEB3F, 0xFB1E, 0x8BF9, 0x9BD8, 0xABBB, 0xBB9A, 0x4A75, 0x5A54, 0x6A37, 0x7A16, 0x0AF1, 0x1AD0, 0x2AB3, 0x3A92, 0xFD2E, 0xED0F, 0xDD6C, 0xCD4D, 0xBDAA, 0xAD8B, 0x9DE8, 0x8DC9, 0x7C26, 0x6C07, 0x5C64, 0x4C45, 0x3CA2, 0x2C83, 0x1CE0, 0x0CC1, 0xEF1F, 0xFF3E, 0xCF5D, 0xDF7C, 0xAF9B, 0xBFBA, 0x8FD9, 0x9FF8, 0x6E17, 0x7E36, 0x4E55, 0x5E74, 0x2E93, 0x3EB2, 0x0ED1, 0x1EF0

Section III - 10 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Keyboard Support via Remote UI 3.5 Remote UI Packet Example The following example shows a hex dump of a packet representing the keystroke a (lowercase a):

BE 02 00 00 EF B0 00 00 ED 0D 01 2C 02 CC CC D8 02 00 00 00 CC 00 00 00 00 10 00 61 Table III.3 categorizes the above data into the respective packet fields. Table III.3: Packet Example Breakdown BE EF ED 02 02 00 0010 02 B0 0D CC 00 CC 00 00 00 00 01 CC 00 00 00 61 00 00 Header signature1 signature2 dest src type bodySize transactionID checksum Body command filler penDown filler penX penY keyPress filler keyModifier keyAscii keyCode 2C D8 CRC Checksum For more information, refer to the Serial Link Protocol section in the PalmOS Programmers Companion, available at the Palm developers website at http://www.palm.com/devzone/. Copyright 1999 by Handspring, Inc. All rights reserved. Section III - 11 Section III: Cradle connector Version 1.0 Section III - 12 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section IV Development Tools All modules must have a ROM on them that identifies the module and includes the software for it. Handspring provides the Palm-MakeROM tool for creating a file with the modules ROM image. This file can then be used to create a ROM for the module. The beginning of a module ROM has a header structure that contains the name of the module, the manufacturer's name, the version number of the module, the total size of the ROM, etc. Besides the module header, the ROM contains one or more PalmOS applications or other types of databases. Modules that include special hardware usually include a setup utility; some modules may also include a welcome application. The PalmOS applications that are passed to Palm-MakeROM are standard PalmOS .PRC files that can be built using any of the standard PalmOS development tools including those from Metrowerks or the Handspring PalmOS GNU tools. The Palm-MakeROM utility is a command-line based tool that accepts parameters identifying the information to store in the module header, as well as a list of files that are PalmOS databases to include in the ROM image. This tool is quite powerful and has many options, but most developers will only need to know about the options described here. For a full list of options, enter the

-help option of the tool. Below is an example command line to build a module ROM with two applications on it. For a sample makefile that builds a module ROM, see <InstallDir>/PalmTools/../../Tools/

Samples/CardROM/Build/Makefile. Palm-MakeROM -op create

-hdr 0x08000000

-chName "SampleROMCard"

-chManuf "Handspring, Inc."

-chVersion 0x0100

-romName "ROM Store"

-romBlock 0x08000000 0x00010000

-chRomTokens 0x0800FF00 0x0100

-tokStr HsAT 200

-romDB "WelcomeApp.prc"

-romDB "MyApp.prc"

-o CardROM.bin

This command line builds a ROM image file called CardROM.bin with a module header and two applications in it: WelcomeApp.prc and MyApp.prc. Copyright 1999 by Handspring, Inc. All rights reserved. Section IV - 1 Section IV: Development Tools Version 1.0 Table IV.1 describes each of the command line parameters. Table IV.1: Command Line Parameters Parameter Description

-hdr <hdrOffset>

-chName <cardName>

-chManuf <manufName>

-chVersion <version>

-chRomTokens <offset> <size>

The offset from the base of the module to the module header. Must be 0x08000000 for all Handspring removable modules. This offset, added to the removable module's assigned logical base address in PalmOS of 0x20000000, yields the address of the module's ROM at 0x28000000. The ASCII name of the module. Can be up to 31 characters in length. This name must be registered with Handspring via the developer support web site. The name of the manufacturer of the module. Can be up to 31 characters in length. This name must also be registered with Handspring. The 16-bit version number of the module. This value is for your purposes only and can be any format. You should always increase the value with subsequent versions of the module. A typical use is to store the major version in the high byte and the minor version in the low byte. The offset and size of the ROM token area on the module. This area is used to store data specified in the '-tokStr' parameter. The <offset> should be set to the end of the ROM minus space for the tokens themselves. In the above exam-

ple, the ROM offset is at 0x08000000 and its size is 0x10000 (64K), so the ROM tokens are put at 0x08000FF00 with a size of 0x100.

-romName <romName>

The name of the ROM to be stored on the module. This parameter is for descrip-

tive purposes only and can be any name up to 31 characters long.

-romBlock <offset> <size>

The offset and size of the ROM area on the module relative to the module base address. The <offset> must be 0x08000000 for all Handspring modules. The size is the total size of the formatted ROM area used by the Palm-MakeROM tool, which can be less than or equal to the size of the ROM chip itself.

-romDB <prcName>

The name of a PalmOS .PRC file to include in the ROM image. This option can be repeated for every .PRC file included in the ROM image. The ID and value of a ROM token to be placed in the ROM token area specified by the -chRomTokens option. This option can be repeated for every ROM token that needs to be included. The ID must be a string of four characters. The value can be any number of characters long. All Handspring removable modules contain an 'HsAT' token with a value specify-

ing the required access time of the chip selects in nanoseconds. For modules without this value, the chip select access time will be set to the slowest possible value allowed by the base unit hardware. For example:

-tokStr HsAT 200 Optionally, you can also include an 'HsWR' ROM token. The presence of this token (the value is ignored) tells the system to launch the module welcome appli-

cation on the module if the module is inserted during a soft or hard reset. Nor-

mally, the module welcome application is not launched after a reset. For example:

-tokStr HsWR 1 The name of the ROM output image file. This file is a binary output file image of the ROM with bytes in Motorola order (big-endian). Thus the first byte of the file corresponds to address 0 in the ROM (the high-order eight bits of the first word), the second byte corresponds to address 1 (the low-order eight bits of the first word), the third byte corresponds to address 2, etc.

-tokStr <id> <value>

-o <outputName>

-help List all options to Palm-MakeROM. Section IV - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section V Mechanical Information This section provides mechanical information on the following:

Visor handheld Springboard module with battery Springboard standard module Cradle base Cable connectors Each chapter of this section includes a simple view and the associated file name of the mechanical drawings or model included in this kit. The format used are DWG, DXF, PRO-E or IGES. Developers Note: One of Handsprings goals is to provide future products that allow backward-

compatibility with earlier Springboard module designs. However, take care when designing your Springboard modules. To maintain compatibility with existing Springboard modules, the Springboard expansion slot depth and width will remain constant; however, the surrounding molding may change in thickness or size. Please refer to the mechanical drawings included with this kit for the recommended non-encroachement areas. Also be aware that future Handpsring handheld designs may incorporate faster processors, so you must ensure that your module designs do not have any dependencies, such as wait states, that may be impacted by processor speed. Copyright 1999 by Handspring, Inc. All rights reserved. Section V - 1 Section V: Mechanical Information Version 1.0 Chapter 1 Visor handheld The files for the mechanicals for the Visor handheld is: Visor.zip. Section V - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Chapter: Springboard module with battery Chapter 2 Springboard module with battery The files for the mechanicals for the Springboard Modules with batteries is:

BatterySpringboardModule.zip. Copyright 1999 by Handspring, Inc. All rights reserved. Section V - 3 Section V: Mechanical Information Version 1.0 Chapter 3 Springboard standard module The files for the mechanicals for the Springboard memory module is: SpringboardStandard.zip. Section V - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Chapter: Cradle base Chapter 4 Cradle base The files for Visor handheld cradle is: Cradle.zip. Note that the cradle connector mechanical definition is part of this design file. Copyright 1999 by Handspring, Inc. All rights reserved. Section V - 5 Section V: Mechanical Information Version 1.0 Chapter 5 Cable connectors The mechanical file for the different HotSync cable connectors (cradle, USB and 68 pin Springboard connector) is: connector.zip. Section V - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section VI Compatibility Testing Developers of Springboard expansion modules are responsible for self-testing their products for compatibility with the following:

The PalmOS Springboard-specific modifications to the PalmOS Visor hardware All developers who wish to use the Springboard-compatible logo must ensure that their products conform to the software, electrical, and mechanical specifications outlined below. The compatibility testing required varies depending on the type of Springboard expansion module you develop. There are three types of design that can be done for Handspring handheld computer and/or a Springboard expansion modules:

PalmOS software applications Springboard-specific software applications Springboard hardware/software products These three types are described in more detail in the following three chapters. Copyright 1999 by Handspring, Inc. All rights reserved. Section VI - 1 Section VI: Compatibility Testing Version 1.0 Chapter 1 PalmOS Software Applications PalmOS software applications are software-only applications. Handspring does not require any special testing or certification for such applications that are executed from internal memory. However, if the software is hosted in non-volatile memory on a Springboard module, the module itself must be tested for Springboard compatibility. Section VI - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Chapter 2 Springboard-Specific Software Applications Springboard-Specific Software Applications Springboard-specific software applications are software-only applications. These products run on a Springboard expansion module and use Handsprings proprietary software APIs to extend the PalmOS. Software that runs on a Springboard expansion module and uses calls to Handsprings APIs must undergo Springboard software compatibility testing, even if a pre-approved expansion module is used to host the software. The items that need to be verified are include the following:

The header file is a valid Springboard header The software meets Palms requirements for PalmOS compatibility All databases, preferences, or other variable data are written to Module 0 All auto-loading software (welcome apps) runs correctly upon insertion of the module Any patches or other system extensions loaded by the module are properly executed, do not interfere with the proper operation of the Visor handheld, and are properly removed from the handheld internal memory when the module is removed The hsCardAttrCsbase attribute of the HsCardAttrGet() function is used properly Software interrupts do not interfere with the proper functioning of the Visor unit All module identification information is correct and available The software conforms to all other specifications described elsewhere in this DK Copyright 1999 by Handspring, Inc. All rights reserved. Section VI - 3 Section VI: Compatibility Testing Version 1.0 Chapter 3 Springboard-Specific Hardware/Software Applications The Springboard-specific hardware/software applications plug into the Springboard expansion slot. The software included in these products must undergo all of the compatibility testing described in the previous chapter. In addition, the hardware modules must undergo mechanical and electrical self-certification to ensure that they conform to the specifications described in Electrical and mechanical specifications on page II-43. These products must also be tested for conformity with the following mechanical requirements:

The module must not intrude physically on the cradle, battery-door, IR port, or stylus holder The force required to insert or remove the card conforms to the requirements specified in Electrical and mechanical specifications on page II-43 Electrically, the module must be tested for conformity with the following requirements:

The maximum operating current must not exceed 100 mA The standby current when LOWBAT* is asserted must be as low as possible, preferably below 100 m A. The module must not assert IRQ when LOWBAT* is asserted Under no circumstances should the module drain the Visor batteries and/or backup capacitor to such a degree that the handheld computer cannot maintain the integrity of its internal RAM. Section VI - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section VII Handspring Licensing HANDSPRING, INC. Developer Agreement PLEASE READ THE TERMS OF THE FOLLOWING AGREEMENT CAREFULLY. BY USING THE MATERIALS DISTRIBUTED WITH THIS AGREEMENT (THE DEVELOPMENT KIT), YOU ARE AGREEING TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, PLEASE DO NOT USE THE DEVELOPMENT KIT. INSTEAD, PLEASE DESTROY ALL COPIES OF THE DEVELOPMENT KIT WHICH YOU MAY HAVE. DEFINITION. Springboard contain an external slot (the Springboard software products can be inserted. Enabled Products are Handspring handheld computers that slot) into which compatible third party hardware or LICENSE GRANT. Subject to the terms and conditions of this Agreement, Handspring hereby grants to Developer a non-exclusive, non-transferable license under Handsprings intellectual property rights in the Development Kit (a) to use, reproduce and create derivative works of the materials provided by Handspring under this Agreement, solely internally in connection with Developers development and manufacture of i) products which plug into the Springboard and meet Handsprings Springboard accessory products (such as keyboards or reference manuals) for use with Springboard Enabled Products (such plug-in products and accessory products, collectively, Licensed Products); (b) to make, have made, use, distribute and sell Licensed Products directly or indirectly to end users for use with Springboard unmodified Development Kit in its entirety (including this Agreement) to third parties who agree to be bound by the terms and conditions of this Agreement. compatibility requirements (Licensed Plug-Ins) or ii) Enabled Products; and (c) to distribute the slot LICENSE RESTRICTIONS. Except as otherwise expressly provided under this Agreement, Handspring grants and Developer obtains no rights, express, implied, or by estoppel, in any Handspring intellectual property, and Developer shall have no right, and specifically agrees not to

(a) transfer or sublicense its license rights to any other person; (b) decompile, decrypt, reverse engineer, disassemble or otherwise reduce the software contained in the Development Kit to human-readable form to gain access to trade secrets or confidential information in such software, except and only to the extent such activity is expressly permitted by applicable law notwithstanding such limitation; (c) use or allow others to use the Development Kit, in whole or part, to develop, manufacture or distribute any products other than Licensed Products; (d) use or allow others to use the Development Kit, in whole or part, to develop, manufacture or distribute products (including Licensed Products) for use as a plug-in or accessory to any product other than Springboard Enabled Products; (e) use or allow others to use the Development Kit, in whole or part, to develop, manufacture or distribute any products incorporating an external or internal slot design; or (f) modify or create derivative works of any portion of the Development Kit. Copyright 1999 by Handspring, Inc. All rights reserved. Section VII - 5 Section VII: Handspring Licensing Version 1.0 OWNERSHIP. Handspring is the sole and exclusive owner of all rights, title and interest in and to the Development Kit, including, without limitation, all intellectual property rights therein. Developers rights in the Development Kit are limited to those expressly granted hereunder. Handspring reserves all other rights and licenses in and to the Development Kit not expressly granted to Developer under this Agreement. Subject to Handsprings rights in the Development Kit and the Springboard Products developed by Developer in accordance with this Agreement. Enabled Products, Developer shall retain all rights in the Licensed compatibility trademark (the Mark) in connection with a Licensed Plug-In, compatibility requirements (the Compatibility Criteria). Developer agrees that it COMPATIBILITY TESTING AND BRANDING. Prior to Developers use of Handsprings Springboard Developer shall conduct reasonable testing in accordance with Handsprings compatibility testing guidelines to ensure that the Licensed Plug-In conforms in all respects to Handsprings Springboard will not use the Mark or make any statements claiming or implying compatibility with the Springboard compatibility testing and that, if Handspring determines that any Licensed Plug-In is not compliant with the Compatibility Criteria, Developer shall immediately cease use of the Mark in connection with that Licensed Plug-In. All goodwill generated by Developers use of the Mark shall inure to Handsprings benefit. slot in connection with any Licensed Plug-Ins which have not passed such Subject to the terms and conditions of this Agreement, Handspring hereby grants to Developer a non-exclusive, non-transferable license to use, subject to the guidelines set forth in Handsprings trademark policy and other applicable guidelines, (i) Handsprings Springboard compatibility trademark solely in connection with the marketing and sale of Licensed Plug-ins which comply with the Compatibility Criteria; and (ii) artwork, icons, logos, color schemes, and other industrial designs and designations of source provided by Handspring to Developer hereunder solely in connection with the marketing and sale of Licensed Products DEVELOPER INDEMNIFICATION. Developer will defend at its expense any action brought against Handspring to the extent that it arises from or relates to Developers development, manufacturing, marketing or distribution of Licensed Products, and Developer will pay any settlements and any costs, damages and attorneys' fees finally awarded against Handspring in such action which are attributable to such claim; provided, the foregoing obligation shall be subject to notifying Developer promptly in writing of the claim, giving it the exclusive control of the defense and settlement thereof, and providing all reasonable assistance in connection therewith. Notwithstanding the foregoing, Developer shall have no liability for any claim of infringement to the extent required by compliance with the Compatibility Criteria. WARRANTY DISCLAIMER. HANDSPRING MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, AS TO ANY MATTER WHATSOEVER, AND SPECIFICALLY DISCLAIMS ALL WARRANTIES OR CONDITIONS OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE. LIMITATION OF LIABILITY. EXCEPT FOR BREACHES OF THE SECTIONS ENTITLED LICENSE GRANT, OR LICENSE RESTRICTIONS, IN NO EVENT WILL EITHER PARTY BE LIABLE TO THE OTHER FOR LOST PROFITS, LOST BUSINESS, OR ANY CONSEQUENTIAL, EXEMPLARY OR INCIDENTAL DAMAGES ARISING OUT OF OR RELATING TO THIS AGREEMENT, REGARDLESS OF WHETHER BASED IN CONTRACT OR TORT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Section VII - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 TERM AND TERMINATION. This Agreement shall remain in effect for the partial calendar year ending on the first March 31 following the effective date, and shall automatically renew for additional one (1) year terms ending on each subsequent March 31, except that the Agreement shall automatically terminate if either party materially breaches or is in default of any obligation hereunder or if either party provides notice of non-renewal by January 1. The parties agree that Handspring may provide notice by making the notice available in a manner similar to the manner in which the Development Kit was made available. GENERAL. This Agreement will be governed by and construed and interpreted in accordance with the internal laws of the State of California, excluding that body of law applicable to conflict of laws. No waiver, amendment or modification of any provision hereof or of any right or remedy hereunder will be effective unless made in writing and signed by the party against whom such waiver, amendment or modification is sought to be enforced. No failure by any party to exercise, and no delay by any party in exercising, any right, power or remedy with respect to the obligations secured hereby will operate as a waiver of any such right, power or remedy. Neither this Agreement nor any right or obligation hereunder may be assigned or delegated by Developer

(including by operation of law) without Handsprings express prior written consent, which consent will not be unreasonably withheld, and any assignment or delegation without such consent will be void. This Agreement will be binding upon and inure to the benefit of the successors and the permitted assigns of the respective parties hereto. If any provision of this Agreement is declared by a court of competent jurisdiction to be invalid, void, or unenforceable, the parties will modify such provision to the extent possible to most nearly effect its intent. In the event the parties cannot agree, then either party may terminate this Agreement on sixty (60) days notice. This Agreement constitutes the entire understanding and agreement of the parties hereto with respect to the subject matter hereof and supersedes all prior agreements or understandings, written or oral, between the parties hereto with respect to the subject matter hereof. Copyright 1999 by Handspring, Inc. All rights reserved. Section VII - 7 Section VII: Handspring Licensing Version 1.0 Section VII - 8 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section VIII Approved Vendor List Handspring desires to make it easy for all developers to implement their ideas on our Visor handheld platform. Thus we are providing a list of Handspring-approved components for developers to use in their designs, if so chosen. Table VIII.1: Approved Vendor List Name Contact e-mail Phone#

Web site ATL Tony Sass tonys@atllink.com 801-434-0974 http://www.atllink.com/

Smart Modular Dave Floriani dave.floriani@smartm.com 510-624-8137 http://www.smartmodular.com/

Table VIII.2: Approved Components Part Number Description Supplier Specification 13-0006-00 Springboards slot 68-pin female connector 31-0021-00 USB cable connector/overmold 13-0003-00 Cradle connector (also called dock connector) ATL ATL ATL 13000600.pdf (.dwg) 31002100.pdf (.dwg) 13000300.pdf (.dwg) TBD 2MB OTP- or Masked -ROM Springboard module Smart Modular N/A Copyright 1999 by Handspring, Inc. All rights reserved. Section VIII - 1 Section VIII: Approved Vendor List Version 1.0 Section VIII - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Section IX Trademarks and Logos Chapter 1 Overview Section IX defines the specifications for the Springboard symbol and colors. It also provides a view of all available Springboard logos and Icons on the Visor handheld that are included in this kit. The source files for these logos and icons are in Logo_Icons.zip. Here is a description of each files per folder. Under the Logos Developers folder:

Color.springboard = color symbol with word springboard in GIF format color.tag.springboard = color symbol with words springboard compatible in GIF format SB.symbol = Springboard 's' in EPS format SB.color = Springboard logo in color with word Springboard in EPS format SBcom.color = Springboard logo in color with words Springboard compatible in EPS format Under the Logos Developers\B&W folder:

SB Symbol.rev = Springboard 's' in reverse white in EPS format SB.B&W = Springboard logo with word springboard all in black in EPS format SBcom.B&W = Springboard logo with words springboard compatible all in black in EPS format BW.springboard = Springboard logo with word springboard all in black in GIF format BW.tag.springboard = Springboard logo with words springboard compatible all in black in GIF format Under the Icon folder:

lcd.area.eps Copyright 1999 by Handspring, Inc. All rights reserved. Section IX - 1 Section IX: Trademarks and Logos Version 1.0

. S P R I N G B O A R D S Y M B O L & C O L O R The Springboard symbol was designed to capture the modularity and exi-

bility of our Springboard technology. Shown here are the color and black-

and-white versions of the symbol. As with our corporate symbol, never alter or reproportion the Springboard symbol in any way. A B D C E A B C C O L O R : H S Y E L L O W ( S I M I L A R T O P M S 1 3 0 ) C O L O R : H S B L U E ( S I M I L A R T O P M S 2 8 8 ) C O L O R : H S G R E E N ( S I M I L A R T O P M S 3 4 1 5 ) D B & W: 1 0 0 % B L A C K E M I N . S I Z E : 1 P I C A 9 . 5 P T S Section IX - 2 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Overview S P R I N G B O A R D S I G N AT U R E S The Springboard signature includes the symbol and the Springboard logotype used together in a specic orien-

tation, as shown. A variation on this signature, the Springboard Compatible signature, also is featured. As with our corporate signature, consistent use of the elements that comprise the Springboard and Springboard Compatible signatures, helps strengthen and reinforce our brand. B D A B C A C S P R I N G B O A R D S I G N A T U R E B M I N I M U M S I Z E : 2 P I C A S 6 P T S S B C O M P A T I B L E S I G N A T U R E D M I N I M U M S I Z E : 3 P I C A S Copyright 1999 by Handspring, Inc. All rights reserved. Section IX - 3 Section IX: Trademarks and Logos Version 1.0 Chapter 2 Logos Figure IX.1: Color.springboard.gif Figure IX.2: Color.tag.springboard.gif Section IX - 4 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Logos Figure IX.3: SB.symbol.eps Figure IX.4: SB.color.eps Copyright 1999 by Handspring, Inc. All rights reserved. Section IX - 5 Section IX: Trademarks and Logos Version 1.0 Figure IX.5: SBcom.color.eps Figure IX.6: SB Symbol.rev.eps Section IX - 6 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Figure IX.7: SB.B&W.eps Logos Figure IX.8: SBcom.B&W.eps Copyright 1999 by Handspring, Inc. All rights reserved. Section IX - 7 Section IX: Trademarks and Logos Version 1.0 Figure IX.9: BW.springboard.gif Figure IX.10: BW.tag.springboard.gif Section IX - 8 Copyright 1999 by Handspring, Inc. All rights reserved. Version 1.0 Figure IX.11: lcd.area.eps Logos Copyright 1999 by Handspring, Inc. All rights reserved. Section IX - 9 Section IX: Trademarks and Logos Version 1.0 Section IX - 10 Copyright 1999 by Handspring, Inc. All rights reserved.

 

 

VisorPhone Module User Guide Copyright Copyright 2000 - 2001 Handspring, Inc. All rights reserved. Handspring, Springboard, Visor, VisorPhone, the Handspring logo, and the Springboard logo are trademarks of Hand-

spring, Inc., and may be registered in some jurisdictions. Graffiti, HotSync, and Palm OS are registered trademarks of Palm, Inc. or its subsidiaries. All other trademarks are the property of their respective owners. Disclaimer and limitation of liability Handspring, Inc. and its suppliers assume no responsibility for any damage or loss resulting from the use of this guide. Handspring, Inc. and its suppliers assume no responsibility for any loss or claims by third parties which may arise through the use of this software and hardware. Handspring, Inc. and its suppli-

ers assume no responsibility for any damage or loss caused by deletion of data as a result of mal-

function, dead battery, or repairs. Be sure to make backup copies of all important data on other media to protect against data loss. Important: Please read the Handspring End User Software License Agreement in the back of this guide before using the accompanying software program(s). Using any part of the software indicates that you accept the terms of the Handspring End User Software License Agreement. Part #: 50-0227-01 ii Contents Getting Started.................................................................................1 Step 1: Set up your handheld computer.............................................2 Step 2: Insert your SIM card into your VisorPhone .........................3 Step 3: Insert your battery into your VisorPhone .............................4 Step 4: Get to know your phone ........................................................5 Step 5: Connect the phone to your handheld....................................7 Step 6: Charge the battery..................................................................8 Step 7: Turn on your phone...............................................................9 Step 8: Activate your account ...........................................................10 Congratulations ................................................................................11 Making Voice Calls ........................................................................13 Calling a speed dial number.............................................................14 Dialing a number with the Dialpad .................................................15 Redialing the last number ................................................................16 Redialing previous numbers.............................................................16 Calling a number in your Address Book..........................................17 Dialing a number from other applications.......................................18 Returning a missed call.....................................................................19 Calling an emergency number .........................................................20 Receiving Calls...............................................................................21 Answering the phone........................................................................22 Responding to call waiting ...............................................................23 Forwarding calls ...............................................................................24 Contents iii Handling Multiple Calls...................................................................25 Placing a call on hold .......................................................................26 Dialing another number while a call is on hold ..............................27 Switching between two calls ............................................................28 Using 3-way calling..........................................................................29 Checking Messages ........................................................................31 Reviewing missed calls .....................................................................32 Checking voicemail ..........................................................................33 Checking text messages....................................................................34 Displaying call history......................................................................35 Purging call history ..........................................................................36 Managing Your Speed Dial List .......................................................37 Defining speed dial buttons .............................................................38 Adding an Address Book entry to your speed dial list.....................39 Changing a speed dial entry.............................................................40 Deleting speed dial entries ...............................................................41 Arranging the speed dial list.............................................................42 Using Your SIM Phonebook ............................................................43 Copying entries from your speed dial list to your SIM card...........44 Copying entries from your SIM card to your speed dial list...........45 Deleting entries from your SIM card ..............................................46 Dialing entries on your SIM card ....................................................47 iv Contents Working With SMS Text Messages..................................................49 Enabling SMS and SMS Email ........................................................50 Viewing messages .............................................................................51 Replying to messages........................................................................52 Creating messages ............................................................................53 Creating message greetings and signatures .....................................56 Saving incoming messages................................................................57 Copying incoming messages ............................................................57 Forwarding incoming messages .......................................................58 Modifying messages..........................................................................58 Sorting messages...............................................................................59 Deleting messages ............................................................................60 Using VisorPhone as a Wireless Modem..........................................61 Setting up VisorPhone as a wireless modem ...................................62 Using third-party data applications with VisorPhone.....................63 Preparing for a direct wireless HotSync operation .........................64 Preparing for a network wireless HotSync operation .....................65 Performing a wireless HotSync operation.......................................66 Customizing Your Phone.................................................................67 Setting dialing prefixes for use in North America...........................68 Assigning dialing applications ..........................................................69 Changing the phone display.............................................................70 Selecting the ringer settings.............................................................71 Preventing unauthorized use of your phone....................................72 Unlocking your phone......................................................................73 Contents v Disabling call waiting .......................................................................74 Blocking your phone number for outgoing calls.............................75 Selecting a service provider network ...............................................76 Connecting a headset .......................................................................77 Using the Menus.............................................................................79 Phone application Edit menus .........................................................79 Phone application Record menu......................................................79 Phone application Options menus...................................................80 SIM Phonebook application Edit menu ..........................................81 SIM Phonebook application Options menu....................................81 SMS Message Manager application Message menus ......................82 SMS Message Manager application Edit menu...............................83 SMS Message Manager application Options menu ........................84 Troubleshooting and Maintenance...................................................85 Caring for your VisorPhone module...............................................91 Caring for the battery ......................................................................92 How do I dispose of the battery? .....................................................93 Warranty and Other Product Information ........................................95 Index ...........................................................................................115 vi Contents Getting Started Congratulations on the purchase of your new VisorPhone module. Your VisorPhone module integrates the power of a state-of-the-art digital mobile phone with the simplicity of your Handspring handheld computer. To use your VisorPhone, you must first activate your account with your mobile phone service provider. Your account information is located on your SIM (Subscriber Identity Module) card. If a SIM card did not come with your VisorPhone, your service provider will provide one when you subscribe to their service. Your SIM card must be inserted into your VisorPhone before you can use it. Just follow the eight easy steps in this chapter to get up and running quickly. Getting Started 1 Step 1: Set up your handheld computer 1. If you havent already set up your handheld, follow the steps that came with your handheld to set it up.

(Recommended) Synchronize your handheld with your computer. 2. Place your handheld in the cradle and press the HotSync button Tip:

If you need additional information about synchronizing, refer to the Quick Reference Guide and Visor Handheld User Guide that came with your handheld. 2 Getting Started Step 2: Insert your SIM card into your VisorPhone The SIM (Subscriber Identity Module) card is a small rectangular plastic piece. The SIM card is included with your service providers documentation and is often referred to as a smartcard. If your SIM card is already inserted in your phone, skip to Step 3. Note:

n Insert the SIM card into the slot. Slide the SIM card into the slot Tip:

Since calls are billed to your telephone number, you can move your SIM card to any mobile phone that uses a SIM card, and the calls will be billed to your account. Getting Started 3 Step 3: Insert your battery into your VisorPhone n Insert the battery into your VisorPhone and secure the latch. SIM card 4 Getting Started Step 4: Get to know your phone Antenna Headset jack Phone button Power button Battery Battery latch SMS Message Manager button Speaker Slider LED Antenna Headset jack Battery Battery latch Power button Receives and sends signals on your VisorPhone. The antenna does not telescope out of the phone. Enables you to connect a headset so you can view your handheld screen while talking on the phone. Powers your VisorPhone. Secures the battery to your VisorPhone. Turns on your VisorPhone and activates the signal. Your phone stays on until you remove it from your handheld or press the power button to turn it off. Getting Started 5 Speaker Phone button SMS Message Manager button Slider LED Functions as the earpiece on your VisorPhone. Tip: To adjust the volume during a call, press the scroll buttons on the front of your handheld. Turns on your handheld and starts the Phone application. If another application is running, press this button to switch to the Phone application. If the phone is ringing, press this button to answer calls. Turns on your handheld and starts the SMS Message Manager application so you can view, send, and receive text messages. Controls the ringer setting. See Selecting the ringer settings on page 71 for details on changing the settings. Provides status information for your VisorPhone. The color of the light and the blink state indicate the status as follows:

No light = Phone off Red/solid = Charger on; battery charging Green/solid = Charger on; battery fully charged Red/slow blink = Phone on; no network service Green/slow blink = Phone on; in service Red/fast blink = Battery low Green/fast blink = Data call active 6 Getting Started Step 5: Connect the phone to your handheld 1. Remove the slot protector from your handheld. 2. Insert your VisorPhone module into the Springboard expansion slot. Slide the slot protector away from your handheld Slide the module into the Springboard expansion slot Tip: To remove your VisorPhone from your handheld, simply slide it out from the Springboard expansion slot. Getting Started 7 Step 6: Charge the battery 1. Plug the travel charger into a wall outlet. 2. Insert the travel charger cable into the connector on your handheld. LED turns solid red when charging and solid green when charged Tip: When your phone is on, the charge icon appears in the Phone application while your VisorPhone charges. Note that your VisorPhone must be in your handheld while charging, and that it takes about 1.5 hours to fully charge the battery. Its time to recharge the battery when you observe one of the following:

n the LED turns red and blinks quickly n the LED does not turn on when you turn on your phone n the battery gauge in the top-right corner of the Phone application appears empty when your VisorPhone is on and the Phone application is on the screen 8 Getting Started Step 7: Turn on your phone After the battery is charged, you can begin using your phone. 1. Press the Power button on your VisorPhone for two seconds until you hear a beep. Note:

If the Unlock Phone dialog appears, see Unlocking your phone on page 73 for instructions. 2. Wait up to two minutes for your VisorPhone to locate your service providers network. Do not tap OK. Tip: When your VisorPhone locates the network, the Network Search dialog displays a Welcome message and your service providers name appears in the upper-left corner of the Phone application. If you are in an area without coverage, the Network Search dialog displays an Unable to register to the network message and No Service appears in the upper-left corner of the Phone application. Getting Started 9 Step 8: Activate your account If you received a new SIM card with your phone, you need to call your service provider to activate your account (unless it was activated upon purchase at a retail location). Your service providers phone number is located on the materials that came with your VisorPhone module. Once you receive your phone number, it may take a few hours to become fully active. Some service providers send a special message with your phone number. Follow these steps to check the phone number:

1. Make sure your phone is on for at least 30 seconds. 2. Press the Phone button application. on your VisorPhone to access the Phone 3. Tap the Menu icon 4. Under Options, tap Phone Info. 5. Tap OK. 10 Your VisorPhone number (if available) Your equipment ID number Getting Started Congratulations Youre ready to use your VisorPhone module. Keep these things in mind as you use your new phone:

n If you travel outside a coverage area, your phone remains on but you cant make or receive calls. If this occurs, the LED blinks red slowly and the phone periodically tries to register to the network. When you return to a coverage area, the LED blinks green. n Although VisorPhone supports many calling features, such as call waiting, call hold, call forwarding, 3-way calling, voicemail, SMS, and SMS Email, check with your service provider to confirm that these services are available and active on your mobile calling plan. If you travel outside a coverage area, you cant receive SMS text messages. However, the messages are stored by the network and you will receive them when you return to a coverage area. n n Your account includes a voicemail feature so people can always leave you a message even when your phone is off. n Always use care when operating a mobile phone. If you plan to use your VisorPhone module while driving a car, we recommend that you become familiar with local laws concerning use of a mobile phone while driving, and that you use a headset for hands-free operation. See Connecting a headset on page 77 to learn how to connect a headset to your VisorPhone. Getting Started 11 12 Getting Started Making Voice Calls There are several ways to make voice calls with your VisorPhone. This chapter describes how to dial a number by:

n n Entering it on the Dialpad n Selecting it from your speed dial list Selecting it from your Call History list Selecting it from your Address Book n n Dialing from another application n Returning a missed call n Dialing an emergency number After you dial and establish a connection, the Active Call screen appears:

Voicemail notification icon

(not used by all networks) Network name Making Voice Calls Signal strength icon Battery gauge Tap Key Pad to enter extra numbers such as a PIN code or an extension 13 Calling a speed dial number Speed dialing enables you to quickly place a call without entering the number. This is particularly useful for numbers you call often, such as your home or office. Note: This section assumes youve already created a speed dial list. To learn how to add numbers to your speed dial list see Defining speed dial buttons on page 38. 1. Press the Phone button on your VisorPhone. Tip:

If the screen below doesnt appear, tap the Speed Dial icon

. 2. Select the number you want to call. Tap a button to dial a number Speed Dial, Dialpad, and Call History icons Tap a Page icon to view other speed dial pages Tip:

After you make the connection the Active Call screen appears. If prompted to enter a menu selection, tap Key Pad. If you defined any Extra Digits, such as an extension, tap Extra Digits. 3. Tap Hang Up to end the call. 14 Making Voice Calls Dialing a number with the Dialpad 1. Press the Phone button on your VisorPhone. Tip:

You can also tap the Phone icon Launcher to start the Phone application. in the Applications

. 2. Tap the Dialpad icon 3. Dial the number. If you are dialing an international number, tap the +

key before entering the number to automatically insert the international access code upon dialing. Tip:

To display the last ten numbers dialed, press the scroll buttons on the front of your handheld. Dial box Tap a digit to enter it in the dial box Tap Backspace to erase the last digit Tap CLR to delete the entire entry Tap Send to dial the number in the dial box Tip:

To edit the phone number, tap the Dial box and then use the keypad, Graffiti writing, or the onscreen keyboard. 4. Tap Hang Up to end the call. Making Voice Calls 15 Redialing the last number n Hold down the Phone button for two seconds to redial the last number you called. Redialing previous numbers 1. Press the Phone button 2. Tap the Call History icon outgoing calls. on your VisorPhone. to view a list of previous incoming and 3. Select the number you want to call. Tap the entry you want to dial Tap Dial to call selected number Tap here to select the call category:

All, Incoming, Out-

going, or Missed Tap Details to view call information 4. Tap Dial. Tip: To add a number to your Address Book or Speed Dial list, tap Details, tap Copy Phone #, then in Address Book or Speed Dial Edit view, tap the line where you want to add the number, and select Paste from the Edit menu to insert the number. 16 Making Voice Calls Calling a number in your Address Book 1. Press the Address Book button 2. Select the number you want to call. on the front of your handheld. Tap a name to view or edit contact information Tap a number to select a number to dial Tap a number to select it Tap Dial to call the number Tip:

If you install a third-party email or SMS application, the Dial button changes to an Email button when you select an email address, or to an SMS button when you select a mobile phone number. See Assigning dialing applications on page 69 for details on assigning compatible third-party SMS and Email applications to these buttons. 3. Tap Hang Up to end the call. Making Voice Calls 17 Dialing a number from other applications You can also dial numbers from other applications such as Memo Pad or To Do List. 1. Highlight the number you want to dial. 2. Press the Phone button on your VisorPhone. Tap here to add an area code or change the number Select a number to dial Tip: The number automatically appears in the Dial box on the Dialpad screen so you can edit the number if needed. 18 Making Voice Calls Returning a missed call When your VisorPhone is on and you remain in a coverage area, any calls you miss appear in the Call History list and you receive a missed call alert message. When your phone is off or you travel outside a coverage area, your calls are forwarded to voicemail and they do not appear in the Call History list. n If you miss multiple calls, a message appears indicating the number of calls you missed. Follow the steps in Reviewing missed calls" on page 32 to return the calls. If you miss a single call, the following screen appears:

n Tap OK to dismiss the call without calling back Tap Call Back to dial the number Tip:

If the callers phone number is not available, the Call Back button does not appear on the Missed Call screen. Making Voice Calls 19 Calling an emergency number Your VisorPhone provides easy access to emergency numbers such as 112 or 911. 1. Press the Phone button 2. Do one of the following:

on your VisorPhone. n If your phone is unlocked, dial 112 or 911 from the Dialpad screen. n If your phone is locked or your SIM card is missing, tap Make Emergency Call from the Unlock Phone or SIM Card Not Found screen. Tap Make Emergency Call You dont need to unlock your phone or even have the SIM card installed to call an emergency number. Making Voice Calls Tip:

20 Receiving Calls Whenever your phone is on and you are within a coverage area, you can receive incoming calls. In addition to answering calls, you can also choose several incoming call options. This chapter describes how to:

n Answer the phone (or reject a call) n Respond to a call waiting prompt n Forward your calls Receiving Calls 21 Answering the phone An incoming call turns on your handheld if it is off. Tap Answer to accept the call Callers name and phone number if available Tap Ignore to send the call to voicemail Tip:

You can also answer a call by pressing the Phone button your VisorPhone is ringing. while 22 Receiving Calls Responding to call waiting When you are on the phone and receive a second call, the Phone application updates the Active call screen and emits a Call Waiting beep tone. Tip: Make sure the Disable Call Waiting option on the Call Preferences screen is off. When this option is off the Disable Call Waiting check box is empty. For more information on enabling and disabling call waiting, see Disabling call waiting on page 74. n When the Call Waiting dialog appears, tap the appropriate button. Tap Hold & Answer to place 1st call on hold and answer incoming call Tap Drop & Answer to end1st call and answer incoming call Callers name and phone number if available Tap Ignore to send the call to voicemail Tip:

You can also press the Phone button hold and answer the incoming call. to place the first call on Receiving Calls 23 Forwarding calls If you need to turn off your phone or know you will be traveling outside a coverage area, you can forward your calls to another number. Keep in mind that your service provider will still charge you for your forwarded calls. Note: Because call forwarding information is stored by the network, its a good idea to check the current network settings both before and after you change the call forwarding option. 1. Tap the Menu icon 2. Under Options, tap Call Preferences. 3. Select the call forwarding option you want to use. Tap here to forward all calls to the selected number Tip:

You can define multiple forwarding numbers. Select Edit numbers from the list to add, change, or delete a number. Tap here to display current network settings 4. Tap OK. 24 Receiving Calls Handling Multiple Calls You can use the Hold button in the Phone application to handle a variety of situations that involve multiple calls. During an active call, you can receive or place another call, switch between two active calls, and create a 3-way conference call. For example, when youre talking to a friend, you can put them on hold, call a restaurant to make dinner reservations, and return to your friend to confirm the time and place. These features also enable you to receive an important incoming call while youre already on the phone, and to facilitate conference calls when youre on the go. This chapter describes how to:

n Place a call on hold n Dial another number while a call is on hold n n Use 3-way calling Switch between two calls Handling Multiple Calls 25 Placing a call on hold 1. Place or answer a call. Call status indicator Tap Hold to put the call on hold Tap Off Hold to return to the call 2. Tap Hang Up to end the call. 26 Handling Multiple Calls Dialing another number while a call is on hold 1. Place or answer a call. 2. Put the call on hold. Tap Hold to put the call on hold 3. Tap 2nd Call. 4. Dial the number. Tap 2nd Call to access dial functions Tip:

to open You can tap the Applications Launcher icon another application that has the number you want to dial. Handling Multiple Calls 27 Switching between two calls 1. Answer or place two calls. See Dialing another number while a call is on hold on page 27. 2. Tap Swap, or tap the call status line to switch between calls. 1st call status 2nd call status Tap KeyPad to access a voice prompt system Tap Swap to change calls Tip:

If you called an automated phone system that prompts you to enter a menu selection or phone extension, tap KeyPad to respond to the voice prompts. 3. Tap Hang Up to end the active call. 28 Handling Multiple Calls Using 3-way calling 1. Answer or place two calls. 2. Join the two calls. Tap 3-way Call to speak with both calls at the same time 1st call status 2nd call status Tap Hold to place both calls on hold Tap Hang Up to end both calls Tap Cancel 3-way to return to the previous active call and to place the other call on hold Handling Multiple Calls 29 30 Handling Multiple Calls Checking Messages Your VisorPhone is capable of receiving voicemail and text messages and generating missed call messages. If you miss a call when your VisorPhone is on and you remain in a coverage area, your missed calls appear in the Call History list and you receive a missed call alert message. When your phone is off or you travel outside a coverage area, your missed calls are forwarded to voicemail and they do not appear in the Call History list. Similarly, when your phone is off or you travel outside a coverage area, your service provider stores your text messages until you turn on your phone or return to a coverage area. Note: You may need to contact your service provider to add the text messaging feature to your rate plan. This feature is sometimes referred to as SMS, or Short Message Service. This chapter describes how to:

n Review missed calls n Check voicemail n Check text messages n Display call history n Purge call history Checking Messages 31 Reviewing missed calls When you dont answer an incoming call, it appears under Missed calls in your Call History list. 1. Tap the Call History icon 2. Tap Missed in the pick list in the upper-right corner. Tap callers name or phone number Tap Dial to return the call 32 Checking Messages Checking voicemail When your phone is off, you travel outside a service area, or you miss or choose to ignore a call, the caller may leave a voicemail message. When you connect to the network, the phone application notifies you that you received voicemail messages. 1. Dial your voicemail service using one of these methods:

n Tap the Voicemail button in the Speed Dial view. n Tap Listen in the Voicemail alert dialog. n Tap the Voicemail icon in the upper-right part of the Speed Dial view or the Dialpad view. Tip:

Some service providers do not support the Listen button and the Voicemail icon

. 2. Tap Key Pad on the Active Call screen. Tap buttons to dial access codes and review messages 3. Tap Done. Checking Messages 33 Checking text messages When your phone is off or you travel outside a service area, other people can still send you text messages. Your service provider stores the messages for you until you turn on your phone or return to a service area. When you connect to the network, the SMS Message Manager displays the first message in a screen similar to the following:

Number of new messages Tap OK to review messages later Tap Delete to delete the message Callers name and phone number if available Tap Call Back to dial the sender 34 Checking Messages Displaying call history The Call History view provides quick access to the previous 1,000 incoming and outgoing calls. n Tap the Call History icon

. Missed call Incoming call Outgoing call Tap arrow to select the call category: All, Incoming, Outgoing, or Missed Tap Details to view time and duration Tap Dial to call the selected number Tip:

To temporarily store a number in your handhelds memory, tap Details, tap Copy Phone #, and then tap Done. You can now Paste this number into any application on your handheld. Checking Messages 35 Purging call history Your VisorPhone continues accumulating call history information for up to 1,000 calls until you purge the call history list. To conserve storage space, we recommend that you purge this list periodically. Note: Using the Purge function permanently removes the calls from your handheld. You cannot undo this process to restore the information. 1. From the Call History view, tap the Menu icon 2. Under Record, tap Purge. Tip:

To delete a specific item, select the item from the Call History view and tap Delete Item instead of Purge. 3. Select the purge option you want to use. Tap the pick list to choose which calls to purge 4. Tap OK. 36 Checking Messages Managing Your Speed Dial List You can store up to 50 phone numbers in the speed dial list. There are five pages of numbers that hold ten numbers per page. Tip: Keep your speed dial list organized by storing different types of numbers on different pages. For example, create separate pages for family, business, friends, and emergency numbers. This chapter describes how to:

n Assign phone numbers to speed dial buttons n Add Address Book entries to your speed dial list n Change speed dial entries n Delete speed dial entries n Arrange the speed dial list Managing Your Speed Dial List 37 Defining speed dial buttons 1. Tap the Speed Dial icon

. 2. Tap a blank speed dial button. Note: The first slot on the first Speed Dial page is reserved for your service providers voicemail service number. 3. In the Edit Entry dialog, enter the Name, Number, and any Extra digits. Enter a name for the button Enter digits to dial after placing the call

(such as an extension or access code) Enter the phone number Tap Lookup to find a number in your Address Book Tip:

To insert a pause between Extra digits when dialing, enter a comma (,). Each comma represents a one second pause. 4. Tap OK. 38 Managing Your Speed Dial List Adding an Address Book entry to your speed dial list 1. Tap the Speed Dial icon

. 2. Tap a blank speed dial button. 3. Tap Lookup. 4. In the Phone Number Lookup dialog, use the scroll arrows or begin writing the persons last name to find the number you want. Tap a number to select it Tap Add to insert the number in the speed dial entry 5. Tap Add. Tip:

You can edit the number or name by tapping it in the Edit Entry dialog. 6. From the Edit Entry dialog, tap OK. Managing Your Speed Dial List 39 Changing a speed dial entry 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. 4. Select the entry you want to change. Tap an entry to select it Tap pages to view more entries 5. In the Edit Entry dialog, enter the new information. 6. Tap OK to save the new information. 7. Tap Done. 40 Managing Your Speed Dial List Deleting speed dial entries 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. 4. Select the entry you want to delete. Tap an entry to select it 5. In the Edit Entry dialog, tap Delete. 6. Tap OK to confirm deletion. 7. Tap Done. Tap pages to view more entries Managing Your Speed Dial List 41 Arranging the speed dial list 1. Tap the Speed Dial icon

. 2. Tap the Menu icon 3. Under Edit, tap Edit Speed Dial. Drag an entry to another slot or page Tip:

If the new slot is full, the other entries move over one slot as the rows fill from top to bottom. If you drag an entry to a page icon, the entry moves to the first available slot on that page. 4. Tap Done. 42 Managing Your Speed Dial List Using Your SIM Phonebook In addition to storing your phone number and billing information, your SIM card also contains a phone list that is separate from your Address Book and speed dial list. Most SIM cards enable you to store more than 50 names and numbers. By storing a phone list on your SIM card, you have immediate access to your phone list when you move your SIM card to another phone. The SIM Phonebook application is a utility that enables you to view and manage the phone list on your SIM card. This chapter describes how to:

n Copy entries from your speed dial list to your SIM card n Copy entries from your SIM card to your speed dial list n Delete entries from your SIM card n Dial entries on your SIM card Using Your SIM Phonebook 43 Copying entries from your speed dial list to your SIM card 1. Tap the Applications Launcher icon 2. Tap the SIM Phonebook icon 3. Tap Speed Dial in the pick list in the upper-right corner. 4. Tap the entry you want to copy. on the front of your handheld. Tip:

To copy all the numbers in your speed dial list, select Copy All from the Edit menu. Tap Speed Dial Tap a name or number to select it Tap Copy to add the entry to your SIM card Tip:

A check mark indicates that the entry is already on both your speed dial list and your SIM list. 5. Tap Copy. 44 Using Your SIM Phonebook Copying entries from your SIM card to your speed dial list 1. Tap the Applications Launcher icon 2. Tap the SIM Phonebook icon

. 3. Tap SIM in the pick list in the upper-right corner. 4. Tap the entry you want to copy. on the front of your handheld. Tip:

To copy all the numbers in your speed dial list, select Copy All from the Edit menu. Tap SIM Tap a name or number to select it Tap Copy to add the entry to your speed dial list Tip:

A check mark indicates that the entry is already on both your speed dial list and your SIM list. 5. Tap Copy. Using Your SIM Phonebook 45 Deleting entries from your SIM card 1. Tap the Applications Launcher icon 2. Tap the SIM Phonebook icon 3. Tap SIM in the pick list in the upper-right corner. on the front of your handheld. Tip:

To delete entries from your speed dial list, tap Speed Dial instead. 4. Select the entry you want to delete. 5. Tap Delete. 6. Tap OK to confirm deletion. Tap to select SIM or Speed Dial Tap a name or number to select it Tap Delete to remove the entry 46 Using Your SIM Phonebook Dialing entries on your SIM card 1. Tap the Applications Launcher icon 2. Tap the SIM Phonebook icon

. 3. Tap SIM in the pick list in the upper-right corner. on the front of your handheld. Tip:

You can also dial entries from your speed dial list by tapping Speed Dial instead. 4. Select the entry you want to dial. Tip:

You can also send a text message to an SMS-enabled mobile phone by tapping a mobile phone number and then tapping SMS instead of Dial. Tap to select SIM or Speed Dial Tap a name or number to select it Tap Dial to call the number Tap SMS to send a text message 5. Tap Dial. Using Your SIM Phonebook 47 48 Using Your SIM Phonebook Working With SMS Text Messages In addition to dialing and receiving calls, you can use your VisorPhone to send and receive short text messages. These text messages, also called SMS

(Short Message Service) messages, are similar to email messages that you send and receive from your computer, but are limited to a few sentences in length. The person receiving your message must also have a GSM mobile phone and a service provider that supports text messages. Some service providers also allow you to use your mobile phone to send text messages to an email address and to receive text messages from a computer. Talk to your service provider for details about their SMS and SMS Email features. This chapter describes how to:

n Enable SMS and SMS Email n View messages n Reply to messages n Create messages n Create message greetings and signatures n Set message options Save messages n n Forward messages n Copy message text to the clipboard n Modify outgoing messages n n Delete messages Sort messages Working With SMS Text Messages 49 Enabling SMS and SMS Email To send and reply to SMS messages, you must subscribe to your service providers SMS service. If you subscribe to this service, your service provider supplies an SMS Message Center number which appears in the SMS Preferences dialog. To use SMS Email, you must subscribe to your service providers SMS Email service and enter their SMS Email Center number in the SMS Preferences dialog. The SMS Email Center forwards the SMS messages to the recipients email address. Contact your service provider to obtain their SMS Email Center number. 1. Press the SMS Message Manager button on your VisorPhone. 2. From any SMS Message Manager list view, tap the Menu icon 3. Under Options, tap Preferences. Confirm SMS Message Center number Enter SMS Email Center number 4. Tap OK. 50 Working With SMS Text Messages Viewing messages You can view SMS messages even if you dont subscribe to your service providers SMS service. 1. Press the SMS Message Manager button open the SMS Message Manager Inbox. on your VisorPhone to Tap arrow to select the message category:

Inbox, Saved, Pending, or Sent Message read Tap New to create a message Tip: When viewing Saved messages, the arrows indicate whether a message was incoming or outgoing. 2. Tap the message you want to view. 3. Press the scroll buttons on your handheld to scroll through a message. At the start or end of a message, it displays the next message. 4. Tap Done. Working With SMS Text Messages 51 Replying to messages To reply to SMS messages, you must subscribe to your service providers SMS service. See Enabling SMS and SMS Email on page 50 to determine if you subscribed to your service providers SMS service. 1. Tap the incoming message to which you want to reply. Tap Reply to respond to the message 2. Tap Reply. 3. Enter the message text. Tip: When you reply to an SMS message, the SMS Message Manager fills in the To field for you. When you reply to an email message, you must enter the email address on the first line of the message. See Creating an SMS Email message on page 55 for more information. 4. Tap Send. 52 Working With SMS Text Messages Creating messages SMS Message Manager enables you to create short text messages and send them to a GSM mobile phone number or an email address. If a message exceeds 160 characters, SMS Message Manager divides the text into multiple messages. As you create a message, the status bar indicates how many messages will be sent and the total number of characters in all the messages. To save time while creating messages, you can insert predefined text from a template. Some templates ask you to enter information such as a meeting time or place. Using a template is similar to filling in the blanks on a form letter instead of writing a letter from scratch. Fortunately, in SMS Message Manager you can easily combine the template text with your own text to personalize your message. You can create a message at any time, but if you send a message when you are outside a coverage area, your VisorPhone places the message in the Pending category and sends it automatically when you return to a coverage area. While a message is in the Pending category, you cannot edit it, but you can delete it before it is sent. Working With SMS Text Messages 53 Creating an SMS text message 1. From any SMS Message Manager list view, tap New. 2. Address the message to a mobile phone number. Tap To to select a number Tap Text to insert text from a template 3. Enter text using Graffiti, the onscreen keyboard, or the Text and Greetings pick lists. 4. Tap Send. (The message goes into the Pending category until your phone transmits the message.) Tip:

To store a draft message and send it later, tap Save instead. After your message transmits, your VisorPhone places a copy in the Sent category. If an error occurs while sending the message, an exclamation point

(!) appears next to the message in the Sent category. Note: Some service providers may restrict you from sending SMS messages to recipients outside your service network. 54 Working With SMS Text Messages Creating an SMS Email message To send a message to an email address, you must first enter your service providers SMS Email Center number. See Enabling SMS and SMS Email on page 50. 1. From any SMS Message Manager list view, tap New. 2. Tap the To pick list and select SMS Email Center. Tap To to select SMS Email Center Enter email address followed by a space and # symbol 3. On the first Text line, enter the recipients email address followed by a space and a # symbol. 4. Enter the remaining text. 5. Tap Send. (The message goes in the Pending category until it transmits.) Tip:

To store a draft message and send it later, tap Save instead. Working With SMS Text Messages 55 Creating message greetings and signatures When you create a message you can use the greetings pick lists to insert a greeting and signature in your message. You can also add items to these lists or modify the existing items. From any SMS Message Manager list view, tap the Menu icon 1. 2. Under Options, tap Greetings. Tap here to hide the greetings pick lists Tap Add entry to create a new greeting Tap Add entry to create a new signature 3. Tap Done. 56 Working With SMS Text Messages Saving incoming messages 1. Open the message you want to save. 2. Tap the Menu icon 3. Under Message, tap Save. Tip:

Saving an incoming message moves the message from your Inbox to the Saved category. Copying incoming messages 1. Open the message you want to copy. 2. Tap the Menu icon 3. Under Message, tap Put Into Clipboard. Tip:

To create a memo with the text, tap Copy to Memo Pad instead. 4. Open the message or application where you want to insert the message. 5. Tap the Menu icon 6. Under Edit, tap Paste. Working With SMS Text Messages 57 Forwarding incoming messages 1. From the Inbox or Saved category, open the incoming message you want to forward. 2. Tap the Menu icon 3. Under Message, tap Forward. Tip:

You can edit the forwarded message before sending it. 4. Enter the recipients mobile phone number. Note: The recipients phone must be SMS enabled. 5. Tap Send. Modifying messages You can modify any outgoing messages in your Saved or Sent categories. Tip:

You can create your own message template by modifying and resending a Sent message. 1. Open the message you want to change. 2. Tap the message text, or tap Edit. 3. Edit the message. 4. Tap Send. Tip: When modifying a message, you can keep the revised message without sending it by tapping Save instead of Send. 58 Working With SMS Text Messages Sorting messages 1. In the SMS Message Manager, tap Show. 2. Select the sort method you want to use. Tap arrow to select sort method 3. Tap OK. Tip:

If you sort the list by name, messages from senders that are not in your Address Book appear at the bottom of the list in numerical order by phone number. Working With SMS Text Messages 59 Deleting messages 1. In the SMS Message Manager, tap the pick list in the upper-right corner to select the category containing the messages you want to delete. 2. Tap the Menu icon 3. Under Message, tap Purge. 4. Select the deletion method you want to use. Tap arrow to select deletion method 5. Tap OK. 6. If prompted, tap Yes to confirm deletion. Tip: To delete a single message, open it and tap the Delete button. 60 Working With SMS Text Messages Using VisorPhone as a Wireless Modem In addition to using your VisorPhone as a phone, you can also use it as a modem that operates at 14.4Kbps or 9.6Kbps, depending on the speed of your service provider network. You can use your VisorPhones modem capabilities with third-party communication software that you download from the Internet, such as web browsers or email applications, and to perform wireless HotSync operations when your cradle is not available. Set up your VisorPhone as a wireless modem This chapter describes how to:

n n Use third-party data applications with VisorPhone n Prepare for a direct wireless HotSync operation n Prepare for a network wireless HotSync operation n Perform a wireless HotSync operation Using VisorPhone as a Wireless Modem 61 Setting up VisorPhone as a wireless modem To use your VisorPhone as a modem, you must subscribe to the data services feature from your service provider and establish an ISP account or corporate dial-up account. 1. Tap the Applications Launcher icon 2. Tap the Prefs icon 3. Tap Network in the pick list in the upper-right corner. 4. Enter the configuration information for your ISP. on the front of your handheld. Select your ISP from the Service pick list Tap here to enter advanced DNS and IP Address settings Enter your User Name, Password, and your ISPs phone number Note:

If your ISP is not on the Service pick list, tap the Menu icon tap New on the Service menu, and enter the service name. 5. Check your settings by tapping Connect. When your settings work properly, the Connect button changes to a Disconnect button.

, To learn more about using your handheld with your ISP, see Network Preferences and TCP/IP Software in the Visor Handheld User Guide. 62 Using VisorPhone as a Wireless Modem Using third-party data applications with VisorPhone Before using a third-party communication application, verify with the developer that the application you installed is compatible with VisorPhone. 1. Install the third-party application on your handheld. See Installing third-party applications in the Visor Handheld User Guide for details. 2. Start the third-party application you installed. Note: Most third-party applications automatically connect you to your ISP when you start the application. If the application doesnt connect you to your ISP, follow these steps to establish a connection:

a.Tap the Applications Launcher icon handheld. on the front of your

. b.Tap the Prefs icon c.Tap Network in the pick list in the upper-right corner. d.Tap Connect and wait for a connection to establish. 3. Disconnect after you finish using the third-party application. Using VisorPhone as a Wireless Modem 63 Preparing for a direct wireless HotSync operation A direct wireless HotSync operation is when you dial a modem attached to your desktop computer to perform a remote HotSync operation. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon 3. Tap Enter Phone #. 4. Enter your computer modem number, and then tap OK. Enter the number used to call your computer modem

. 5. Tap the Menu icon 6. Under Options, tap Modem Sync Prefs. 7. Tap Direct to modem, and then tap OK. 8. On a Windows computer, click the HotSync icon on the HotSync Manager menu. On a Macintosh, open HotSync Manager and select Modem Setup on the Serial Port Settings tab. and check Modem 64 Using VisorPhone as a Wireless Modem Preparing for a network wireless HotSync operation A network wireless HotSync operation is when you dial a modem attached to a network, such as a server on a corporate LAN, to perform a remote HotSync operation. Note: This feature is not available for the Macintosh. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon

. 3. Tap the Menu icon 4. Under Options, tap Modem Sync Prefs. 5. Tap Network, and then tap OK. 6. Tap Select Service and configure the Network Preferences panel. For information on the Network HotSync feature and configuring the Network Preferences panel, see the Visor Handheld User Guide. Note:

7. On your desktop computer, click the HotSync icon Network on the HotSync Manager menu. and check 8. Click the HotSync icon again, select Setup, click the Network tab, and then select your user name. 9. Perform a HotSync operation. Using VisorPhone as a Wireless Modem 65 Performing a wireless HotSync operation Since your VisorPhone operates as a modem at 14.4Kbps or 9.6Kbps, a wireless HotSync operation takes significantly longer than performing a HotSync operation with your cradle. Therefore, we recommend performing a wireless HotSync operation only when your cradle is not available. Tip: To increase the speed of a wireless HotSync operation, select Conduit Setup under Options and reduce the number of applications with which you synchronize. 1. Tap the Applications Launcher icon on the front of your handheld. 2. Tap the HotSync icon

. 3. Tap the Modem Sync icon 4. Wait for your VisorPhone to connect with the modem on the other end

. and for the HotSync operation to finish. Tip:

If necessary, you can cancel the procedure at any time by tapping the Cancel button. 66 Using VisorPhone as a Wireless Modem Customizing Your Phone The Phone application Preference screens enable you to customize many of the VisorPhone features to meet your individual needs. For example, you can choose which view appears when you start the Phone application, and set security options to prevent unauthorized use. Set dialing prefixes Select the ringer setting This chapter describes how to:

n n Reassign the buttons in your Address Book n Change the phone display n n Prevent unauthorized use of your phone n Unlock your phone n Disable call waiting n Block your phone number for outgoing calls n n Connect a headset to your VisorPhone Select a different service provider network Customizing Your Phone 67 Setting dialing prefixes for use in North America Some North American service providers require 11-digit dialing. If you already have 7-digit or 10-digit numbers in your Address Book, you can set your VisorPhone to automatically use 11-digit dialing by using a default area code. Using this feature does not change the numbers in your Address Book. 1. Press the Address Book button on the front of your handheld. 2. Tap the Menu icon 3. Under Options, tap Dial Preferences. Tap check box to insert an area code in front of 7-digit numbers before dialing Tap check box to insert a 1 in front of 10-digit numbers before dialing Enter default area code here 4. Tap OK. Note: You may be prompted to enter a default area code the first time you dial a number from your Address Book. 68 Customizing Your Phone Assigning dialing applications When you select a phone number or email address in Address Book, you can tap the Dial, SMS, or Email buttons to direct the selected information to a specific application. The default applications for these buttons are the Phone application and the SMS Message Manager. However, if you have third-party SMS or Email applications installed on your handheld, you can assign these buttons to any application that is compatible with the dialing-

enabled version of Address Book. 1. Press the Address Book button on the front of your handheld. 2. Tap the Menu icon 3. Under Options, tap Dial Preferences. Tap pick lists to assign an application to that button Tip:

If no other applications appear in the pick lists, then you dont have compatible SMS or Email applications on your handheld. 4. Tap OK. Customizing Your Phone 69 Changing the phone display 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Phone Preferences. 4. Select the display options you want to use. Tap the view you want to see when you open the Phone application 5. Tap OK. Tap an icon to skip that view when pressing the Phone button repeatedly 70 Customizing Your Phone Selecting the ringer settings 1. Tap the Menu icon 2. Under Options, tap Ringer Preferences. Tip:

The slider on your phone has two positions

. The two Ringer Preferences columns control the behavior of the corresponding slider position. and 3. Select the ringer settings you want to use. Tap Ring pick lists to select ring style Tap Volume pick lists to select volume level Tap Vibrate pick lists to turn vibrate mode on or off Tip:

You can use both a ring tone and vibrate alert or use them separately. For example, you can set one position to ring softly and vibrate, and the other position to vibrate only. To preview a new sound, select Play ring when changed. 4. Tap OK. Customizing Your Phone 71 Preventing unauthorized use of your phone You can protect your phone number from unauthorized use by locking your SIM card. 1. Turn on your phone. 2. Press the Phone button on your VisorPhone. 3. Tap the Menu icon 4. Under Options, tap Phone Preferences. 5. Select the Phone Locked check box to lock your SIM card. Tap here to lock and unlock the SIM card Tap here to define a new password (PIN) 6. Enter your password (PIN) and tap OK. Note:

If you havent set a password yet, check your service providers documentation for the default password. In North America, this is usually 1234 or 1111. 7. Tap OK. 72 Customizing Your Phone Unlocking your phone 1. Turn on your phone. 2. Press the Phone button 3. Enter your password (PIN). on your VisorPhone. Note:

If you havent set your own password, enter the password listed in your service provider documentation. In North America, this is usually 1234 or 1111. If you are using a SIM card from an established account, enter your existing password. Tap OK to unlock your phone Tap numbers to enter password Tap CLR to erase the entire entry 4. Tap OK. Tip:

See Preventing unauthorized use of your phone on the previous page to learn about setting your own password. Customizing Your Phone 73 Disabling call waiting If you receive a call while you are talking on the phone, the Phone application notifies you about the second call. If you dont want to be interrupted by other calls, you can disable call waiting. Note: Because call waiting information is stored by the network, its a good idea to check the current network settings both before and after you change the call waiting option. 1. Tap the Menu icon 2. Under Options, tap Call Preferences. 3. Disable the call waiting option. Tap here to disable call waiting Tap here to display current network settings Tap OK. 4. Tip: To reactivate Call Waiting, remove the check from the Disable Call Waiting check box. 74 Customizing Your Phone Blocking your phone number for outgoing calls When you place a call from your VisorPhone, the Phone application reveals your phone number to the person youre calling. If your service provider supports caller ID blocking, you can prevent revealing your phone number to people you call. Note: Because caller ID blocking information is stored by the network, its a good idea to check the current network settings both before and after you change the Block outgoing caller ID option. 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Call Preferences. 4. Enable the Block outgoing caller ID option. Tap here to place anonymous calls 5. Tap OK. Customizing Your Phone 75 Selecting a service provider network If you roam to an area where multiple service providers offer coverage, your VisorPhone automatically selects the provider with the strongest signal. However, if you prefer, you can manually select a service provider network. Note: When you manually select a network, your VisorPhone finds only that network until you either choose another network, or return to Automatic Mode. 1. Press the Phone button on your VisorPhone. 2. Tap the Menu icon 3. Under Options, tap Select Network. 4. Select a network. Tap a network to enter manual mode Tap Automatic Mode to return to automatic search mode Tap OK. 5. Note: Selecting a new network may take 30 seconds or more. 76 Customizing Your Phone Connecting a headset Use the built-in speaker and microphone or connect an optional headset for hands-free operation. For best results, use only headsets from Handspring. Headset jack Customizing Your Phone 77 78 Customizing Your Phone Using the Menus This section provides an overview of the menu options available in the Phone, SIM Phonebook, and SMS Message Manager applications. Some of the menu options vary based on which screen is active. Phone application Edit menus Speed Dial view Dialpad view Edit Speed Dial: Opens a dialog where you can define, change, and delete speed dial buttons. For details, see Changing a speed dial entry on page 40. Paste: Inserts a phone number from the clipboard into the dial box. Phone application Record menu Call History view Purge: Opens a dialog where you can remove selected records from the Call History list. For details, see Purging call history on page 36. Delete Item: Removes the selected record from the Call History list. Using the Menus 79 Phone application Options menus Speed Dial and Dialpad views Call History view Phone Preferences: Opens a dialog where you can change your phone display and lock the phone. For details, see Changing the phone display on page 70 and see Preventing unauthorized use of your phone on page 72. Ringer Preferences: Opens a dialog where you can choose the ringer settings. For details, see Selecting the ringer settings on page 71. Call Preferences: Opens a dialog where you can choose call waiting, call blocking, and call forwarding settings. For details, see Disabling call waiting on page 74, Blocking your phone number for outgoing calls on page 75, and Forwarding calls on page 24. Select Network: Opens a dialog where you can search for and use networks other than your default network. For details, see Selecting a service provider network on page 76. Phone Info: Opens a dialog where you can view information about your phone such as the phone number and the IMEI number that uniquely identifies your phone to the network. Font Preference: Opens a dialog where you can choose the font you want. About Phone: Opens a dialog where you can view version and copyright information for the Phone application. 80 Using the Menus SIM Phonebook application Edit menu Speed Dial and SIM views Copy All: Copies all entries that exist in one phone list to the other phone list. If you are viewing the speed dial list, it copies all new entries to your SIM card. If you are viewing the SIM card list, it copies all new entries to the speed dial list. SIM Phonebook application Options menu Speed Dial and SIM views Help: Opens a dialog where you can view tips about using the SIM Phonebook application. About: Opens a dialog where you can view version and copyright information for the SIM Phonebook application. Using the Menus 81 SMS Message Manager application Message menus Inbox view Message view Purge: Opens a dialog where you can choose which messages you want to remove from the Inbox. For details, see Deleting messages on page 60. Put Into Clipboard: Copies the selected message to the clipboard so you can paste it into another message or application. For details, see Copying incoming messages on page 57. Copy to Memo Pad: Copies the selected message to a new Memo Pad memo. For details, see Copying incoming messages on page 57. Save: Stores the selected message in the Saved category. Forward: Creates a copy of the selected message so you can send it to someone else. For details, see Forwarding incoming messages on page 58. Call Sender: Dials the person who sent the message. 82 Using the Menus SMS Message Manager application Edit menu Undo: Clears the last action. Cut: Removes the selected text and places it on the clipboard. Copy: Copies the selected text and places it on the clipboard. Paste: Inserts text stored on the clipboard at the current cursor position. Select All: Selects all text in the current field. Keyboard: Opens the onscreen keyboard. Graffiti Help: Opens screens that show you how to form Graffiti characters. Using the Menus 83 SMS Message Manager application Options menu Font: Opens a dialog where you can choose the font you want to use. Greetings: Opens a dialog where you can enter predefined opening and closing phrases to use in your messages. For details, see Creating message greetings and signatures on page 56. Preferences: Opens a dialog where you can view the SMS Service Center number (if this field is blank, contact your service provider for this information), choose deletion confirmation, and enter your service providers SMS Email Center number. For details, see Enabling SMS and SMS Email on page 50. About SMS: Opens a dialog where you can view version and copyright information for the SMS Message Manager application. 84 Using the Menus Troubleshooting and Maintenance If you encounter a problem with your VisorPhone module, check this section to see if your problem is listed. If your problem isn't listed here, or the suggestions don't resolve your problem, visit us at www.handspring.com for technical support contact information. My VisorPhone won't turn on I get a message that my SIM card is missing when I turn on my VisorPhone n Make sure your VisorPhone is inserted firmly in the Springboard expansion slot. n Make sure your VisorPhone battery isn't drained. n When you turn on your VisorPhone, hold down the power button for at least two seconds, until you hear a beep. n Turn on your handheld to make sure that the handheld batteries aren't drained. Low batteries will prevent your VisorPhone from turning on. n Make sure your SIM card is properly inserted. The metal contacts must face down (away from the battery), and the side with the corner cut must slide into the SIM slot first. For details, see Step 2: Insert your SIM card into your VisorPhone on page 3. n Your SIM card may be damaged. Contact your service provider for a new card. Troubleshooting and Maintenance 85 My VisorPhone requires an unlocking code

(PIN), but I didn't set one I called my service provider to enable my phone service, but it still doesnt work n Your service provider may have set the locking code before you received your VisorPhone. Enter the default unlocking code (PIN) and then tap OK. In North America, the default unlocking code is usually 1234 or 1111. If this doesn't work, contact your service provider. Note: It is actually your SIM card that is locked, not your VisorPhone. n If you see the Unblock Phone screen instead of the Unlock Phone screen, you entered the unlock code

(PIN) incorrectly three times, and your VisorPhone is now blocked. Contact your service provider to obtain the unblock code. If you enter the unblock code

(PUK) incorrectly ten times, your SIM is permanently disabled. Some service providers require 24 hours or more to activate your phone service. If it has been longer than your service providers activation period, report the problem to your service provider. 86 Troubleshooting and Maintenance My phone number isn't on the Phone Info screen Your service provider may need to install your phone number onto your SIM card. Contact your service provider to see if they can send a message to your VisorPhone that writes your phone number onto your SIM card. My VisorPhone won't register to the network I tried dialing a phone number, but my VisorPhone just beeps at me n You are probably outside a network coverage area. n Try using another GSM phone to verify whether coverage is available in your current location. If coverage is available in your location, try your SIM card in another GSM phone. If it still doesnt, work, your SIM card may be malfunctioning. Contact your service provider for another SIM card. n Turn off your VisorPhone, and then turn it on again. If a dialog appears asking if you want to search for a network, tap Yes. n Make sure you dialed the correct number. n Wait a few minutes and try again. If the network is very busy, calls cannot connect. n Verify that you are in a network coverage area and then move a few yards away and try the call again. If you are in a weak coverage area (1 bar of signal strength or less), you may not be able to complete calls even though you are registered to the network. Troubleshooting and Maintenance 87 I can't dial international numbers Call waiting doesnt work Call forwarding doesn't work Caller ID blocking for my outgoing calls doesn't work Some incoming callers names dont appear in Call History The SIM Phonebook application won't open For security purposes, most service providers require you to enable international calling on your account. Call your service provider to enable international calling. Enable call waiting in the Call Preferences dialog. For details, see Disabling call waiting on page 74. For security purposes, most service providers require you to enable this feature on your account even though there is usually no extra charge. Call your service provider to enable call forwarding. Some service providers require you to enable this feature on your account. Call your service provider to enable blocking your Caller ID. n Find out if a caller has blocked their Caller ID. n Call History does not show names for records you marked hidden in your Address Book. Make sure your SIM card is inserted in your VisorPhone and that your phone has been on for at least 30 seconds. 88 Troubleshooting and Maintenance My SIM Phonebook doesnt display the full name and number Some phone numbers dont appear in the SMS Lookup I cant send SMS Messages When a name or number is longer than will fit in the SIM Phonebook display, three dots appear to indicate that the entry contains additional information. SIM Phonebook does not truncate the actual entry, it just does not appear on the screen. Make sure the number you want is identified as a mobile number in your Address Book. Only mobile phone numbers appear when you use the SMS Message Manager Lookup button. n Make sure SMS services are enabled on your account by checking the SMS Preferences dialog to see if the SMS Message Center number is on this screen. If the number is missing, contact your service provider for the SMS Message Center number and enter it in the SMS Preferences dialog. Note: Receiving SMS messages does not indicate that you have a subscription to your service providers SMS service. You must subscribe to this service to send or reply to messages. n Verify that you are in a GSM coverage area. n Make sure the destination number is correct. Some service providers require 11-digit phone numbers for SMS messages. Troubleshooting and Maintenance 89 I get an error message when I send an SMS message to an email address The applications I assigned to the Dial, Email, and SMS buttons in the Dialing Address Book dont launch I get a No Carrier error when making data calls Make sure you have subscribed to and enabled the SMS email feature. You need to get the SMS Email Center number from your service provider and enter it in the SMS Preferences dialog. This number is different from the SMS Message Center number you use to send messages to other mobile phone numbers. For more information, see Enabling SMS and SMS Email on page 50. n Check the Dial Preferences dialog in the Address Book to confirm the application is assigned to the Dial, Email, or SMS button. For details, see Assigning dialing applications on page 69. n Contact the software developer for the application you want to use when you tap the button, and verify that the software is compatible with the new Dialing Address Book and the version of Palm OS your VisorPhone uses. To take advantage of these buttons, an application must contain special code that registers its capabilities to the Dialing Address Book. n Verify that data calls are enabled on your account. n Verify that you are in a coverage area. 90 Troubleshooting and Maintenance I can't synchronize when my VisorPhone is connected to my handheld Make sure that there are no active calls on your VisorPhone before you begin a HotSync operation. You cannot synchronize while you have an active call, and you cannot make or receive calls during a HotSync operation. Caring for your VisorPhone module n Keep your VisorPhone and its accessories out of the reach of small children. n Keep your VisorPhone dry. n Use your VisorPhone at normal temperatures between -20 degrees and 54.4 degrees Celsius (-4 degrees and 130 degrees Fahrenheit). Temperatures outside of this range may cause damage to your VisorPhone. n Keep your VisorPhone away from dusty or dirty areas. n Do not disassemble your VisorPhone. n Do not use harsh detergents to clean your VisorPhone. n Use only genuine Handspring accessories. Third party accessories are not guaranteed to function properly with your VisorPhone. n Do not let the Springboard contacts on your VisorPhone come in direct contact with conductive or electronic objects. n Do not short any contacts on your VisorPhone module or the Springboard connectors. Troubleshooting and Maintenance 91 Caring for the battery Your VisorPhone uses a 680mAh Lithium Ion battery. A fully-charged battery provides approximately 3 hours of talk time and more than 70 hours of standby time. Follow these guidelines to get the most from your battery:

n Do not disassemble the battery pack. n If you are not using your VisorPhone for an extended period of time, disconnect the battery pack from the phone and store it in a cool, dry place; charge the battery at least once every six months when not in use. n Never throw the battery pack into fire or expose it to extreme heat. n If the battery pack ever becomes hot or smells odd, stop using it. If the battery pack becomes damaged and leaks liquid, stop using it and avoid skin contact with the leaking liquid. n n Use only a genuine Handspring battery pack. Third party battery packs are not guaranteed to function properly with your VisorPhone. n Always replace the battery pack with the same type of pack. Using another type of battery pack may cause an explosion. n Do not short any battery contacts or let the contacts come in direct contact with conductive or electronic objects. n Be sure to properly dispose of the battery. For more information, see How do I dispose of the battery? on page 93. 92 Troubleshooting and Maintenance How do I dispose of the battery?

When your battery fails to hold a charge, you need to replace it. Caution:

It is illegal in many areas to dispose of Lithium Ion batteries in household or business trash. Call your local recycling center for instructions on battery recycling, or contact Handspring for safe disposal options. Do not handle a damaged or leaking battery. Troubleshooting and Maintenance 93 94 Troubleshooting and Maintenance Warranty and Other Product Information Handspring, Inc. Springboard Module End User Software License Agreement THIS PRODUCT CONTAINS PRE-LOADED SOFTWARE, THE USE OF WHICH IS LI-

CENSED BY HANDSPRING, INC. AND ITS SUPPLIERS (COLLECTIVELY, "HAND-

SPRING"), TO ITS CUSTOMERS FOR THEIR USE ONLY AS SET FORTH BELOW. SOFTWARE LICENSE: Handspring grants you a nonexclusive license to use the software program(s) (the

"Software") pre-loaded on this Product subject to the terms and restrictions set forth in this VisorPhone End User Software License Agreement ("License Agreement"). You are not permitted to lease or rent, distribute or sublicense the Software or to use the Software in a time-sharing arrangement or in any other unautho-

rized manner. Further, no license is granted to you in the human readable code of the Software (source code). Except as provided below, this License Agreement does not grant you any rights to patents, copy-

rights, trade secrets, trademarks, or any other rights in respect to the Software. The Software is licensed to be used solely as pre-loaded on the Product and solely in connection with Handspring products. Otherwise, the Software and supporting documentation may be copied only as essential for backup or archive purposes in support of your use of the Software as permitted hereunder. You must reproduce and include all copyright notices and any other proprietary rights notices appearing on the Software on any copies that you make. PAYMENT OF FEES: The effectiveness of the licenses granted hereunder is conditioned on the receipt by Handspring of any applicable fees. NO ASSIGNMENT; NO REVERSE ENGINEERING: You may transfer the Software and this License Agreement to another party in connection with a transfer of the Product on which the Software is pre-load-

ed, if the other party agrees in writing to accept the terms and conditions of this License Agreement If you transfer the Software, you must at the same time either transfer all copies of the Software as well as the sup-

porting documentation to the same party or destroy any such materials not transferred. Except as set forth above, you may not transfer or assign the Software or your rights under this License Agreement. Modifica-

tion, reverse engineering, reverse compiling, disassembly, or removal of the Software from the Product on which it is pre-loaded is expressly prohibited. However, if you are a European Union ("EU") resident, in-

formation necessary to achieve interoperability of the Software with other programs within the meaning of the EU Directive on the Legal Protection of Computer Programs is available to you from Handspring upon written request. EXPORT RESTRICTIONS: You agree that you will not export or re-export the Software or accompa-

nying documentation (or any copies thereof) or any products utilizing the Software or such documentation Warranty and Other Product Information 95 in violation of any applicable laws or regulations of the United States or the country in which you obtained them. The software covered by this License Agreement may contain strong data encryption code which can-

not be exported outside of the U.S. or Canada. You agree that you will not export/re-export, either physically or electronically, the encryption software or accompanying documentation without obtaining written autho-

rization from the U.S. Department of Commerce. UNITED STATES GOVERNMENT LEGEND: If you are acquiring the Software on be-half of any unit or agency of the United States Government, the following provisions apply. The Software constitutes a "com-

mercial item", as that term is defined at Federal Acquisition Regulation (FAR) 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation", as such terms are used in FAR 12.212 (Sept. 1995), and is provided to the U.S. Government only as commercial software (with

"Restricted Rights", if applicable). Use, duplication, or disclosure by the U.S. Government is subject to re-

strictions set forth in this License Agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a)

(1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-

14 (ALT III), as applicable. TERM AND TERMINATION: This License Agreement is effective until terminated. You may terminate it at any time by destroying the Software and documentation together with all copies and merged portions in any form. It will also terminate immediately if you fail to comply with any term or condition of this License Agreement. Upon such termination you agree to destroy the Software and documentation, together with all copies and merged portions in any form. GOVERNING LAW: This License Agreement shall be governed by the laws of the State of California as such laws are applied to agreements entered into and to be performed entirely within California between Cal-

ifornia residents and by the laws of the United States. You agree that the conflicts of laws principles of such laws and the United Nations Convention on Contracts for the International Sale of Goods (1980) are hereby excluded in its entirety from application to this License Agreement. LIMITED WARRANTY; LIMITATION OF LIABILITY: All warranties and limitations of liability ap-

plicable to the Software are as stated on the Limited Warranty or in the product manual accompanying the Software. Such warranties and limitations of liability are incorporated herein in their entirety by this refer-

ence. SEVERABILITY: In the event any provision of this License Agreement is found to be invalid, illegal or un-

enforceable, the validity, legality and enforceability of any of the remaining provisions shall not in any way be affected or impaired and a valid, legal and enforceable provision of similar intent and economic impact shall be substituted therefor. ENTIRE AGREEMENT: This License Agreement sets forth the entire understanding and agreement be-

tween you and Handspring, supersedes all prior agreements, whether written or oral, with respect to the Soft-

ware, and may be amended only in a writing signed by both parties. 96 Warranty and Other Product Information Handspring, Inc. Limited Warranty for Accessories LIMITED WARRANTY: Handspring, Inc. ("Handspring"), warrants to the original end user ("Custom-

er") that under normal intended use (i) Handspring hardware accessories will be free from defects in work-

manship and materials for one year from the date of purchase, and (ii) Handspring software accessories will substantially conform to their specifications and the media containing the software will be free from defects in workmanship and materials, for ninety (90) days from the date of purchase. Handspring does not provide any warranty for any third party software. During the warranty period, Handspring shall either repair, re-

place or refund the purchase price of defective accessories. Handspring and its suppliers shall not be liable for any losses or damages of any kind resulting from the use of this accessory or for any of Customer's software or data stored on accessories returned to Handspring for service. WARRANTY SERVICE: Customer must obtain warranty service authorization from Handspring within the applicable warranty period before returning defective accessories to Handspring. Returned accessories must be shipped prepaid and packaged appropriately, and it is recommended that they be insured or sent by a method that provides for tracking of the package. If Handspring ships a replacement accessory to Custom-

er before receiving the original accessory and Customer fails to return the original accessory to Handspring within thirty (30) days from the date the warranty service authorization is issued, Handspring will charge Customer the then current published catalogue price of such accessory. LIMITATIONS: THIS LIMITED WARRANTY IS IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS; INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, AND NON INFRINGEMENT, ALL OF WHICH ARE EXPRESSLY DISCLAIMED BY HANDSPRING AND ITS SUPPLIERS. IN NO EVENT WILL HANDSPRING OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, CONSE-

QUENTIAL, OR INDIRECT DAMAGES RESULTING FROM THE POSSESSION, USE, OR FAILURE OF THIS ACCESSORY. Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the lim-

itation of incidental or consequential damages or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in their application to you. When the implied warranties are not allowed to be excluded in their entirety, they will be limited to the duration of the applicable written war-

ranty. This warranty gives you specific legal rights which may vary depending on local law. Warranty and Other Product Information 97 Handspring, Inc. Springboard-modul Endnutzer-softwarelizenzvereinbarung DIESES PRODUKT ENTHLT VORINSTALLIERTE SOFTWARE, DEREN VERWENDUNG VON HANDSPRING, INC. UND SEINEN LIEFERANTEN (IM FOLGENDEN HAND-

SPRING" GENANNT) AN SEINE KUNDEN FR DEREN PERSNLICHEN GEBRAUCH -

AUSSCHLIESSLICH WIE UNTEN AUSGEFHRT - LIZENZIERT IST. SOFTWARELIZENZ: Handspring gewhrt Ihnen eine einfache Lizenz fr die Verwendung des/der Soft-

wareprogramms/Softwareprogramme (im nachfolgenden Software" genannt), das/die auf diesem Produkt vorinstalliert ist/sind, gem den Bestimmungen und Beschrnkungen dieses VisorPhone Endnutzer-Soft-

warelizenzvertrags (im nachfolgenden Lizenzvertrag" genannt). Sie sind nicht befugt, die Software zu ver-

leasen oder zu vermieten, zu vertreiben oder Unterlizenzen zu vergeben. Zudem ist es Ihnen nicht gestattet, die Software im Rahmen einer Timesharing Vereinbarung oder in sonstiger nicht autorisierter Weise zu (be-

)nutzen. Darber hinaus erhalten Sie keine Lizenz fr den Quellcode der Software. Abgesehen von den unten ausgefhrten Bestimmungen werden Ihnen keine Rechte an Patenten, Urheberrechten, Geschftsgeheimnis-

sen, Warenzeichen oder anderen Rechten bezglich der Software eingerumt. Die Software darf nur so wie auf diesem Produkt vorinstalliert und nur in Verbindung mit Handspring-Produkten verwendet werden. Die Software und das Begleitmaterial drfen nur kopiert werden, soweit dies aus Datensicherungs- oder Ar-

chivierungsgrnden zur Nutzung der Software gem den hier dargelegten Bestimmungen zwingend er-

forderlich in der Software enthaltenen Urheberrechtshinweise und alle Markenrechtshinweise in die von Ihnen erstellten Kopien aufnehmen und die Hinweise auf den Kopien wie-

dergeben. ist. Sie mssen alle GEBHREN: Die hiermit gewhrte Lizenz wird mit Erhalt der Zahlung aller anwendbaren Gebhren durch Handspring wirksam. KEINE ABTRETUNG, KEINE RCKENTWICKLUNG: Sie drfen die Software und diesen Lizenz-

vertrag im Rahmen einer bertragung des Produkts, auf dem die Software vorinstalliert ist, an Dritte ber-

tragen, wenn diese sich schriftlich mit den Bestimmungen dieses Lizenzvertrags einverstanden erklren. Wenn Sie die Software bertragen, mssen Sie gleichzeitig auch entweder alle Kopien sowie das Begleitma-

terial an dieselbe Partei bertragen oder aber das nicht bertragene Material vernichten. Abgesehen von der obengenannten Regelung drfen Sie die Software oder Ihre Rechte im Rahmen dieses Lizenzvertrags nicht abtreten oder bertragen. Jede Vernderung, Rckentwicklung, Dekompilierung, Disassemblierung oder Entfernung der Software von dem Produkt, auf dem die Software vorinstalliert ist, ist ausdrcklich verboten. Wenn sich jedoch Ihr Wohnsitz im Gebiet der Europischen Union (EU") befindet, knnen Sie Informa-

tionen, die zur Herstellung der Interoperabilitt der Software mit anderen Programmen im Sinne der EU-

Richtlinie zum rechtlichen Schutz von Computerprogrammen bentigt werden, auf schriftliche Anfrage von Handspring erhalten. 98 Warranty and Other Product Information EXPORTBESCHRNKUNGEN: Sie erklren sich damit einverstanden, die Software und das Begleit-

material (oder jegliche Kopien davon) bzw. Produkte, die die Software nutzen, nicht unter Verletzung gel-

tender Gesetze und Bestimmungen der USA oder des Landes, in dem Sie sie erhalten haben, zu exportieren oder zu reexportieren. Die von diesem Lizenzvertrag betroffene Software enthlt eventuell Datenverschls-

selungscode, der nicht aus den U.S.A. oder Kanada ausgefhrt werden darf. Sie erklren sich damit einver-

standen, die Verschlsselungssoftware oder das Begleitmaterial ohne schriftliche Genehmigung das U.S. Department of Commerce weder gegenstndlich noch elektronisch zu exportieren oder zu reexportieren. RECHTLICHE BESCHRNKUNGEN FR REGIERUNGSBEHRDEN DER USA: Wenn Sie die Software im Auftrag einer Abteilung oder Dienststelle der Regierungsbehrden der USA beschaffen, gelten die folgenden Bestimmungen. Die Software stellt eine kommerzielle Ware" gem FAR 2.101 (Okt. 1995) dar, bestehend aus kommerzieller Computer-Software" und Dokumentation fr kommerzielle Computer-Software" entsprechend FAR 12.212 (Sept. 1995), und wird den Regierungsbehrden der USA nur als kommerzielle Software (ggf. mit Eingeschrnkten Rechten") zur Verfgung gestellt. Die Verwen-

dung, Vervielfltigung oder Offenlegung durch die Regierungsbehrden der USA unterliegt den Bestim-

mungen dieser Lizenzvereinbarung und den rechtlichen Beschrnkungen von DFARS 227.7202-1(a) und 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Okt. 1988), FAR 12.212(a) (1995), FAR 52.227-19 oder FAR 52.227-14 (ALT III), je nachdem, welche Bestimmungen anwendbar sind.}

GELTUNGSDAUER UND KNDIGUNG: Dieser Lizenzvertrag bleibt bis zu seiner Kndigung in Kraft. Sie knnen ihn jederzeit kndigen, indem Sie die Software und das Begleitmaterial zusammen mit allen Kopien und anhngenden Teilen, gleich welcher Form, zerstren. Darber hinaus endet der Vertrag umgehend bei Versto gegen eine der Bestimmungen dieses Lizenzvertrags. Sie stimmen zu, bei einer solchen Beendigung die Software und das Begleitmaterial zusammen mit allen Kopien und anhngenden Teilen, gleich welcher Form, zu zerstren. GELTENDES RECHT: Dieser Lizenzvertrag unterliegt dem Sachrecht des US-Bundesstaates Kaliforn-

ien und dem Bundesrecht der U.S.A. unter Ausschlu der Regelungen des Interlokalen und Internationalen Privatrechts sowie des Wiener UN-Kaufrechtsbereinkommens von 1980. BESCHRNKTE GEWHRLEISTUNG; HAFTUNGSBESCHRNKUNG: Auf die Software sind die Garantiebestimmungen und Haftungsbeschrnkungen, wie sie im Benutzerhandbuch aufgefhrt sind, anwendbar. Diese Garantiebestimmungen und Haftungsbeschrnkungen werden hiermit in ihrer Gesa-

mtheit Bestandteil dieses Lizenzvertrags. UNWIRKSAMKEIT EINZELNER BESTIMMUNGEN: Falls eine Bestimmung dieses Lizenzvertrags fr unwirksam, illegal oder undurchsetzbar befunden wird, ist die Gltigkeit, rechtliche Zulssigkeit und Durchsetzbarkeit der brigen Bestimmungen in keiner Weise betroffen oder beeintrchtigt. GESAMTE VEREINBARUNG: Dieser Lizenzvertrag stellt die gesamte Vereinbarung und den gesamten Vertrag zwischen Ihnen und Handspring dar und ersetzt alle frheren schriftlichen oder mndlichen Ver-

Warranty and Other Product Information 99 trge, die fr diese Software gelten, und kann nur in schriftlicher Form und nach Unterzeichnung durch beide Parteien abgendert werden. Handspring, Inc. Haftungsbeschrnkung Und Beschrnkte Gewhrleistung Fr Zubehr HAFTUNGSBESCHRNKUNG: Handspring Inc. (Handspring") ist gegenber dem ursprnglichen Endnutzer (Kunden") zur Einhaltung der zwingenden Bestimmungen des deutschen Gewhrleistungsrechts verpflichtet. Die deutschen Gewhrleistungsbestimmungen gelten mit folgenden Abweichungen:

Im Falle der Mangelhaftigkeit des Produkts oder eines Teils im Sinne des Gesetzes ist Handspring nach sein-

er Wahl dazu berechtigt, das Produkt oder Teil zu ersetzen oder zu reparieren. Bei Fehlschlagen der Ersat-

zlieferung oder Nachbesserung stehen dem Kunden weiterhin alle ihm gesetzlich zwingend zukommenden Rechte zu. Jegliche Haftung fr einen schuldhaft durch Handspring verursachten Schaden wird hiermit ausgeschlossen, soweit ein solcher Schaden nicht durch Handspring zuzurechnende grobe Fahrlssigkeit oder Vorsatz verursacht worden ist und soweit es sich bei einem solchen Schaden nicht um Tod oder Krperschaden han-

delt, welcher durch eine Handspring zuzurechnende Handlung oder Unterlassung verursacht wurde. BESCHRNKTE GEWHRLEISTUNG FR ZUBEHR: Zustzlich zu den zwingenden Bestimmu-

ngen des deutschen Gewhrleistungsrechts, die unter den oben aufgefhrten Einschrnkungen anwendbar sind, gewhrt Handspring die im folgenden dargestellte Garantie:

Handspring bernimmt gegenber dem Kunden die Garantie, da bei gewhnlichem, zweckbezogenen Ge-

brauch (i) Handspring-Hardwarezubehr fr den Zeitraum von einem Jahr ab Kaufdatum frei von Verarbe-

itungs- und Materialfehlern ist und da (ii) Handspring-Softwarezubehr im wesentlichen seiner Beschreibung entspricht und die Datentrger, auf denen die Software enthalten ist, fr einen Zeitraum von neunzig (90) Tagen ab Kaufdatum frei von Verarbeitungs- und Materialfehlern sind. Handspring bernimmt keine Garantie fr Software von Drittanbietern. Whrend der Garantiezeit wird defektes Zubehr von Handspring entweder repariert, ersetzt oder aber der Kaufpreis dafr rckerstattet. HANDSPRING UND SEINE LIEFERANTEN HAFTEN WEDER FR VERLUSTE ODER SCHDEN, GLEICH WELCHER ART, DIE AUS DEM GEBRAUCH DIESES ZUBEHRS ENTSTEHEN, NOCH FR KUNDENSOFTWARE ODER -DATEN, DIE AUF ZUBEHR EN-

THALTEN SIND, DAS FR REPARATUREN AN HANDSPRING GESCHICKT WIRD, SOWEIT EIN SOLCHER VERLUST ODER SCHADEN NICHT DURCH HANDSPRING ZUZURECH-

NENDE GROBE FAHRLSSIGKEIT ODER VORSATZ VERURSACHT WORDEN IST UND SO-

WEIT ES SICH BEI EINEM SOLCHEN SCHADEN NICHT UM TOD ODER KRPERSCHADEN HANDELT, WELCHER DURCH EINE HANDSPRING ZUZURECHNENDE HANDLUNG ODER UNTERLASSUNG VERURSACHT WURDE. 100 Warranty and Other Product Information WAHRNEHMUNG VON GARANTIELEISTUNGEN, RCKGABE FEHLERHAFTEN ZUBE-

HRS UND VERSPTETE RCKGABE FEHLERHAFTEN ZUBEHRS: Der Kunde mu in-

nerhalb der geltenden Garantiezeit eine Garantiezusage von Handspring einholen, bevor defektes Zubehr an Handspring zurckgeschickt wird. Das eingesandte Material mu mit Rckporto versehen und angemes-

sen verpackt sein. Es wird auerdem empfohlen, das Zubehr zu versichern oder eine Versandart zu whlen, die die Rckverfolgung des Pakets ermglicht. Wenn Handspring Ersatzzubehr an den Kunden liefern lt, bevor Handspring das Originalzubehr erhalten hat, und der Kunde das Originalzubehr nicht inner-

halb von dreiig (30) Tagen nach Erteilung der Garantiezusage an Handspring zurcksendet, berechnet Handspring dem Kunden den zu diesem Zeitpunkt gltigen Katalogpreis des entsprechenden Zubehrs. VERBRAUCHERINFORMATION: In einigen Staaten, Lndern, oder Provinzen ist der Ausschlu oder die Beschrnkung der gesetzlichen Gewhrleistungsbestimmungen bzw. die Haftungsbeschrnkung hin-

sichtlich zuflliger Schden oder hinsichtlich Folgeschden oder hinsichtlich Krperverletzungen nicht zu-

lssig, so da die oben vorgenommene Haftungs- und Gewhrleistungsbeschrnkung auf Sie mglicherweise keine Anwendung findet. Diese Gewhrleistungserklrung verleiht Ihnen bestimmte Re-

chte, die je nach anwendbarem Recht verschieden sein knnen Handspring, Inc. Contrat De Licence Utilisateur Final Du Module Springboard CE PRODUIT CONTIENT UN LOGICIEL PRECHARGE, DONT L'UTILISATION EST REGIE PAR UNE LICENCE ACCORDEE PAR HANDSPRING, INC. ET SES FOURNISSEURS

(COLLECTIVEMENT, HANDSPRING ) A SES CLIENTS POUR LEUR SEULE UTILISA-

TION , DANS LES CONDITIONS ENONCEES CI-APRES. LICENCE DE LOGICIEL : Handspring vous accorde une licence non exclusive d'utilisation du ou des programme(s) (le Logiciel ) prcharg(s) sur ce Produit conformment aux termes et restrictions du prsent Contrat de licence de logiciel pour Utilisateur Final de la VisorPhone (le Contrat de licence ). Vous n'tes pas autoris donner en location, ni louer, distribuer ou accorder de sous-licences du Logiciel, ni l'utiliser en temps partag ou de quelque autre faon non autorise. En outre, aucune licence ne vous est accorde sur le code source du Logiciel. Sous rserve des droits qui vous sont concds ci-dessous, le prsent Contrat de Licence ne vous confre aucun droit sur les brevets, droits d'auteur, secrets de fabrique, marques commerciales, ou autres droits affrents au Logiciel. Vous devez utiliser le Logiciel uniquement avec le Pro-

duit dans lequel il est prcharg et seulement en connexion avec les produits Handspring. D'autre part, le Logiciel et la documentation qui l'accompagne ne peuvent tre copis qu' des fins de sauvegarde ou d'ar-

chivage dans le cadre d'une utilisation conforme aux termes du prsent Contrat. Vous devez reproduire et inclure sur toutes les copies que vous effectuez toutes les mentions de droits d'auteur et de droits de proprit figurant sur le Logiciel. REDEVANCE DE LICENCE : La prise d'effet des licences accordes en vertu du prsent Contrat est soumise au versement Handspring des redevances applicables. Warranty and Other Product Information 101 INTERDICTION DE CESSION ET D'INGENIERIE INVERSE : Vous tes autoris transfrer le Logiciel et le prsent Contrat de licence un tiers avec le Produit sur lequel il est prcharg, condition que ledit tiers s'engage par crit respecter les termes et conditions du prsent Contrat de Licence. Si vous proc-

dez un tel transfert, vous devez fournir toutes les copies du Logiciel et de la documentation qui l'accompa-

gne au tiers qui vous transfrez le Logiciel ou dtruire tout lment non transfr. Sous rserve des disposition qui prcdent, le prsent Contrat ne vous autorise pas transfrer ou cder le Logiciel ou vos droits rsultant du prsent Contrat Il vous est expressment interdit de modifier, d'effectuer de l'ingnierie inverse, de dcompiler, de dsassembler, ou retirer le Logiciel du Produit sur lequel il est prcharg. Toute-

fois, si vous tes un rsident de l'Union europenne ( UE ), vous pouvez demander par crit Handspring les informations ncessaires l'interoprabilit du Logiciel avec d'autres programmes au sens de la directive europenne sur la protection lgale des programmes d'ordinateur. RESTRICTIONS A L'EXPORTATION : Vous vous engagez ne pas exporter ou rexporter le Logiciel, ni la documentation qui l'accompagne (ou les copies de ces documents), ni les produits utilisant le Logiciel ou sa documentation en violation des lois ou rglementations applicables aux Etats-Unis ou dans le pays dans lequel vous les avez acquis. Le Logiciel rgi par le prsent Contrat peut contenir de fortes cls de chiffrement des donnes ne pouvant pas tre exportes des Etats-Unis ou du Canada. Vous vous engagez ne pas export-

er/rexporter, physiquement ou lectroniquement, le logiciel de chiffrement ou la documentation qui l'ac-

compagne sans l'autorisation crite pralable du U.S. Department of Commerce. DISPOSITIONS RELATIVES AU GOUVERNEMENT DES ETATS-UNIS : Si vous faites l'acquisi-

tion du Logiciel pour le compte d'une entit du gouvernement des Etats-Unis, les dispositions suivantes s'ap-

pliquent. Le Logiciel est un article commercial , tel que dfini par l'article 2.101 (Oct. 1995) du FAR

(Federal Acquisition Regulation) et se compose du Logiciel informatique commercial et de la Docu-

mentation pour logiciel informatique commercial , telles que ces expressions sont utilises dans les articles 12.212 (Sept. 1995) du FAR, et est fourni au gouvernement des Etats-Unis uniquement en tant qu'article commercial (avec des Droits restreints , le cas chant). L'utilisation, la reproduction, ou la divulgation par le gouvernement des Etats-Unis est soumise aux restrictions prvues dans le prsent Contrat de licence et les articles DFARS 227.7202-1 (a) et 227.7202-3 (a) (1995), DFARS 252.227-7013 (c)(1)(ii) (OCT 1988), FAR 12.212 (a) (1995), FAR 52.227-19, ou l'article FAR 52.227-14 (ALT III), selon le cas. DISPOSITIONS ET RESILIATION : Le prsent Contrat de licence demeurera en vigueur jusqu' sa r-

siliation. Vous pouvez le rsilier tout moment en dtruisant le Logiciel et sa documentation ainsi que toutes les copies et les lments qui y sont intgrs. Ce Contrat sera rsili de plein droit si vous ne respectez pas un de ses termes ou conditions. En cas de rsiliation vous vous engagez dtruire le Logiciel et sa documentation ainsi que toutes les copies et les lments qui y sont intgrs. LOI APPLICABLE : Le prsent contrat est rgi par les lois en vigueur dans l'Etat de Californie. Vous re-

connaissez que sont expressment exclus l'application des rgles de conflit de lois mentionnes ci-dessus ainsi que celle de la Convention des Nations Unies relative aux contrats de vente internationale de marchandises

(1980). 102 Warranty and Other Product Information LIMITATION DE GARANTIE ; LIMITATION DE RESPONSABILITE : Toutes les garanties et limitations de responsabilit applicables au Logiciel sont mentionnes dans la Limitation de Garantie ou le manuel accompagnant le Logiciel. Lesdites garanties et limitations sont incorpores par rfrence au prsent Contrat. Ces limitations ne s'appliqueront que dans les limites de la loi applicable. En tout tat de cause la garantie lgale s'appliquera si le client est un consommateur au sens dfini par le code franais de la consom-

mation. NULLITE PARTIELLE : Si une disposition du prsent Contrat est juge non valable, illgale ou inop-

posable, les autres dispositions ne seront pas affectes, et ladite disposition sera remplace par une disposi-

tion lgale et opposable ayant une porte et un impact conomique similaires. INTEGRALITE DU CONTRAT : Le prsent Contrat de licence constitue l'intgralit du Contrat vous liant Handspring. Il annule et remplace tout accord antrieur, crit ou oral, relatif au Logiciel, et ne peut tre modifi que par un document crit sign par les deux parties. Handspring, Inc. Limitation De Garantie Concernant Les Accessoires GARANTIE LIMITEE : Handspring, Inc. ( Handspring ), garantit l'utilisateur final initial (le Client

) que, dans des conditions d'utilisation normale, (i) les accessoires des matriels Handspring seront exempts de dfauts matriels et de fabrication pendant une priode d'un an compter de la date d'acquisition, et que

(ii) les accessoires des logiciels Handspring seront pour l'essentiel conformes aux spcifications et que les supports du Logiciel seront exempts de dfauts matriels ou de fabrication, pendant une priode de quatre-

vingt-dix (90) jours compter de la date d'acquisition. Handspring n'accorde aucune garantie en ce qui con-

cerne des logiciels tiers. Pendant la priode de garantie, Handspring pourra son choix rparer, remplacer ou rembourser le prix d'achat des accessoires dfectueux. Handspring et ses fournisseurs ne pourront tre tenus pour responsables des pertes ou dommages d'aucune sorte rsultant de l'utilisation de cet accessoire ou subis par tout logiciel ou donnes du Client stocks sur des accessoires retourns Handspring pour des prestations de service. GARANTIE DE SERVICES : Le Client doit obtenir pendant la priode de garantie applicable une au-

torisation de fourniture de service auprs de Handspring pralablement au retour des accessoires dfectueux. Lesdits accessoires doivent tre expdis port pay et correctement emballs. Il est recommand de les as-

surer ou de les expdier via un mode de transport permettant le suivi du colis. Si Handspring expdie un ac-

cessoire de remplacement au Client avant de recevoir l'accessoire original et que le Client ne renvoie pas celui-ci dans les trente (30) jours compter de la date d'autorisation de fourniture de service dans le cadre de la garantie, Handspring facturera au Client le prix de l'accessoire mentionn dans le catalogue en vigueur. LIMITATIONS : LA PRESENTE GARANTIE LIMITEE REMPLACE LES AUTRES GARANTIES, TERMES OU CONDITIONS ; Y COMPRIS LES GARANTIES, TERMES OU CONDITIONS DE QUALITE, DE CONVENANCE A UN USAGE PARTICULIER, DE QUALITE SATISFAISANTE, Warranty and Other Product Information 103 DE CONFORMITE A LA DESCRIPTION ET DE NON CONTREFACON, LESQUELLES SONT EXPRESSEMENT EXCLUES PAR. HANDSPRING ET SES FOURNISSEURS. HANDSPRING OU SES FOURNISSEURS NE SAURAIENT EN AUCUN CAS ETRE TENUS POUR RESPONSABLES DES DOMMAGES SPECIAUX, INCIDENTS, CONSECUTIFS OU INDIRECTS RESULTANT DE LA POSSESSION, DE L'UTILISATION DE L'ACCESSOIRE, OU D'UNE DEFAILLANCE DE CE-

LUI-CI. Certains pays, Etats ou provinces ne permettent pas l'exclusion ou la limitation de garanties implicites ou re-

sponsabilit pour dommages conscutifs ou prjudice corporel. Les limitations et exclusions mentionnes ci-

dessus ne vous sont donc peut-tre pas applicables. Lorsque les garanties implicites ne peuvent pas tre ex-

clues dans leur intgralit, elles ne sont valables que pendant la dure de la garantie crite applicable. Cette garantie vous confre des droits lgaux spcifiques qui peuvent varier en fonction du droit local applicable. Handspring, Inc. Contrato De Licencia Para El Usuario Final Del Software Del Mdulo Springboard ESTE PRODUCTO CONTIENE SOFTWARE PREINSTALADO CUYO USO SE OTORGA BAJO LICENCIA DE HANDSPRING, INC. Y SUS PROVEEDORES (COLECTIVAMENTE DE-

NOMINADO "HANDSPRING") AL CLIENTE, SEGN LAS CONDICIONES QUE SE ES-

TABLECEN A CONTINUACIN. LICENCIA DEL SOFTWARE: Handspring le otorga una licencia no exclusiva para utilizar los programas de software (el "Software") preinstalados en este producto, sujeta a las condiciones y restricciones establecidas en este Contrato de licencia para el usuario final de la VisorPhone ("Contrato de licencia"). No se permite el arrendamiento, subarrendamiento, alquiler, distribucin o transferencia de la licencia del Software a terceros, ni su uso en tiempo compartido o de cualquier modo no autorizado. Adems, no se otorga ninguna licencia sobre el cdigo legible del Software (cdigo fuente). Salvo en las situaciones establecidas a continuacin, este Contrato de licencia no le otorga ningn derecho sobre patentes, derechos de autor, secretos comerciales, marcas comerciales o cualquier otro tipo de derechos relativos al Software. La licencia del Software se con-

cede slo para su uso como programa preinstalado en el Producto y en conexin con otros productos de Handspring. El Software y la documentacin adjunta slo se podrn reproducir como copias de seguridad o para archivarlos durante las operaciones inherentes al uso del Software segn lo establecido en este documen-

to. Cada copia que haga deber reproducir e incluir todas las notas de derechos de autor, as como cualquier otra nota de propiedad de derechos que aparezca en el Software. PAGO DE DERECHOS: La efectividad de la licencia que se otorga por el presente documento est condi-

cionada al pago de los derechos correspondientes a Handspring. LIMITACIONES DE TRANSFERENCIA E INGENIERA INVERSA: Slo se podr transferir el Software y este Contrato de licencia a terceros si transfiere el Producto en el que se encuentre preinstalado el Software, siempre que la otra parte acepte por escrito los trminos y condiciones de este Contrato de licencia. 104 Warranty and Other Product Information Al transferirse el Software, debern transferirse al mismo tiempo todas las copias del Software y la documen-

tacin adjunta al mismo destinatario o destruir cualquier material no transferido. Salvo en los casos estable-

cidos anteriormente, no se podr transferir o ceder el Software ni los derechos que otorga este Contrato de licencia. Estn expresamente prohibidas la modificacin, utilizacin de tcnicas de ingeniera inversa, de-

compilacin, desensamblaje o eliminacin del Software del Producto en el que se encuentre preinstalado. No obstante, si usted es residente en la Unin Europea ("UE"), puede solicitar a Handspring por escrito la informacin necesaria para asegurar la interoperabilidad del Software con otros programas segn lo descrito en la Directiva de la UE sobre proteccin legal de programas informticos. LIMITACIONES DE EXPORTACIN: Usted se compromete a no exportar o reexportar el Software y la documentacin adjunta (o copias de los mismos) u otros productos que utilicen dicho Software y docu-

mentacin si ello va contra las leyes y regulaciones correspondientes de los Estados Unidos o el pas en que los adquiri. El Software cubierto por este Contrato de licencia puede contener cdigos de cifrado de datos de alto nivel, que no se puede exportar fuera de los Estados Unidos o Canad. Usted se compromete a no exportar o reexportar, ya sea por medios fsicos o electrnicos, el software de cifrado o la documentacin ad-

junta sin la autorizacin expresa y por escrito del Departamento de Comercio de los Estados Unidos (U.S. Department of Commerce). DISPOSICIONES RELATIVAS AL GOBIERNO DE LOS ESTADOS UNIDOS: Si adquiere el Software en nombre de alguna entidad o agencia del gobierno de los Estados Unidos, se aplicarn las dis-

posiciones siguientes. El Software constituye un "artculo comercial" (commercial item), segn la definicin del trmino descrita en la Regulacin federal sobre adquisiciones (Federal Acquisition Regulation - FAR) 2.101 (Octubre de 1995), que consta de "programas informticos comerciales" y "documentacin de progra-

mas informticos comerciales", segn el uso de dichos trminos en la FAR 12.212 (Septiembre de 1995), y se le proporciona al gobierno de los Estados Unidos slo como software comercial (con "derechos limitados"

si as se establece). Su uso, duplicacin o divulgacin por parte del gobierno de los Estados Unidos est sujeto a las limitaciones establecidas en este Contrato de licencia, de acuerdo con lo dispuesto en DFARS 227.7202-

1(a) y 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19 o FAR 52.227-14 (ALT III), segn corresponda. DURACIN Y FINALIZACIN: Este contrato de Licencia estar vigente hasta su finalizacin. Si se deseara terminarlo en un momento dado, deber destruirse el Software y la documentacin junto con todas las copias y partes combinadas por cualquier medio. El Contrato de licencia tambin finalizar en caso de incumplimiento de cualquier trmino o condicin del mismo. En tal caso, usted se compromete a destruir el Software y la documentacin, junto con todas las copias y partes combinadas por cualquier medio. LEGISLACIN APLICABLE: Este Contrato de licencia se rige por las leyes del Estado de California tal como esas leyes se aplican a los contratos celebrados y ejecutados completamente en California por resident-

es de California segn la legislacin de los Estados Unidos. Usted acepta que queda excluida en su totalidad la aplicacin de las normas sobre conflicto entre dichas leyes, as como la Convencin de las Naciones Unidas sobre Contratos de Compra-Venta Internacional de Mercancas (1980) al presente Contrato de Licencia. Warranty and Other Product Information 105 GARANTA LIMITADA Y LIMITACIONES DE RESPONSABILIDAD: Todas las garantas y limit-

aciones de responsabilidad correspondientes al Software se aplicarn segn lo establecido en la Garanta Lim-

itada o en el manual del producto que acompaa al Software. Dichas garantas y limitaciones de responsabilidad quedan incorporadas en su totalidad al presente Contrato por la referencia que aqu se hace a ellas. VALIDEZ DE LAS CLUSULAS: : En caso de que alguna disposicin de este Contrato de licencia resulte ser no vlida, ilegal o no exigible, ello no afectar a la validez, legalidad y exigibilidad de ninguna de las dis-

posiciones restantes. En tal caso, la disposicin afectada se sustituir por otra disposicin vlida, legal y exigi-

ble cuyos efectos e impactos econmicos sean similares. INTEGRIDAD DEL CONTRATO: Este Contrato de Licencia constituye el compromiso y acuerdo nte-

gro entre usted y Handspring, y sustituye y reemplaza cualesquiera acuerdos previos, ya sea oral o escrito, rel-

ativo al Software. Este contrato slo se podr modificar mediante un documento escrito firmado por ambas partes. Handspring, Inc. Garanta Limitada Para Accesorios GARANTA LIMITADA: Handspring, Inc. ("Handspring"), garantiza al usuario final ("Cliente") que, en condiciones de uso normales, (i) los accesorios de hardware de Handspring estarn libres de defectos en cuan-

to a materiales y mano de obra durante un ao desde la fecha de compra y (ii) los accesorios de software de Handspring cumplirn sustancialmente las especificaciones indicadas y los soportes fsicos del software es-

tarn libres de defectos en cuanto a materiales y fabricacin durante noventa (90) das a partir de la fecha de compra. Handspring no ofrece ninguna garanta para software de terceros. Durante el periodo de garanta, Handspring reparar, reemplazar o devolver el importe de la compra de accesorios defectuosos. Handspring y sus proveedores no son responsables de prdidas o daos de cualquier tipo causados por el uso de este accesorio ni de software o datos del Cliente almacenados en los accesorios devueltos a Handspring. SERVICIO DE GARANTA: Antes de devolver accesorios defectuosos a Handspring, el Cliente deber obtener autorizacin del servicio de garanta de Handspring dentro del periodo de garanta correspondiente. Los accesorios devueltos debern empaquetarse adecuadamente y su envo ser a cargo del Cliente. Se re-

comienda asegurarlos o enviarlos mediante un mtodo que permita su seguimiento. Si Handspring enva un accesorio de repuesto al Cliente antes de recibir el accesorio original y el Cliente no entrega dicho accesorio original a Handspring en treinta (30) das desde la fecha en que emiti la autorizacin de servicio de garanta, Handspring aplicar al Cliente el precio de dicho accesorio segn se indique en el ltimo catlogo publicado. LIMITACIONES: ESTA GARANTA LIMITADA SUSTITUYE A TODAS LAS DEMS GA-

RANTAS, TRMINOS Y CONDICIONES; INCLUYENDO GARANTAS, TRMINOS Y CONDI-

CIONES DE COMERCIABILIDAD, IDONEIDAD PARA UN PROPSITO DETERMINADO, CALIDAD SATISFACTORIA, CORRESPONDENCIA CON LA DESCRIPCIN (EXCEPTO EN LA MEDIDA EN QUE AS LO PREVEA LA LEGISLACIN LOCAL) E IMCUMPLIMIENTOS, RE-

106 Warranty and Other Product Information NUNCIANDO EXPRESAMENTE HANDSPRING Y SUS PROVEEDORES A OTORGAR NINGU-

NA DE LAS ANTERIORES GARANTAS, TRMINOS O CONDICIONES. HANDSPRING O SUS PROVEEDORES NO SERN RESPONSABLES EN NINGN CASO DE DAOS ESPECIALES, FORTUITOS, EMERGENTES O INDIRECTOS CAUSADOS POR LA POSESIN, USO O FAL-

LOS DE ESTE ACCESORIO. Algunos pases, estados o provincias no permiten la exclusin o limitacin de las garantas implcitas, la lim-

itacin de daos fortuitos y perjuicios derivados o la limitacin de responsabilidad por daos personales y, por lo tanto, la aplicacin de algunas de las limitaciones y exclusiones anteriores puede estar restringida. Si no est permitido excluir limitaciones implcitas en su totalidad, stas se limitarn a la duracin de la garanta escrita correspondiente. Esta garanta le otorga derechos legales especficos que pueden variar segn las leyes locales. Handspring, Inc. Springboard Module Contratto Di Licenza Software Per L'utente Finale QUESTO PRODOTTO CONTIENE SOFTWARE PRE-CARICATO, L'USO DEL QUALE CONSENTITO IN BASE ALLA LICENZA DELLA HANDSPRING ED I SUOI FORNITORI

(COMPLESSIVAMENTE,, "HANDSPRING"), AI SUOI CLIENTI ESCLUSIVAMENTE PER LORO USO ED COME DI SEGUITO PREVISTO LICENZA SOFTWARE: Handspring concede all'utente una licenza non esclusiva per usare il/i program-

ma/i software [il "Software") pre-caricato in questo Prodotto in base ai termini e alle limitazioni previste nel presente Contratto di Licenza Software VisorPhone per l'Utente Finale ("Contratto di Licenza"). All'utente non consentito concedere in noleggio, distribuire o concedere in sublicenza il Software o usare il Software in condivisione o in qualsiasi altro modo non autorizzato. Inoltre, all'utente non viene concessa alcuna licen-

za sul codice del Software leggibile da un operatore (codice sorgente). Salvo quanto di seguito previsto, il presente Contratto di Licenza non concede all'utente alcun diritto su brevetti, diritti d'autore, segreti com-

merciali, marchi commerciali o alcun altro diritto sul Software. Il Software viene concesso in licenza affinch venga usato esclusivamente come pre-caricato nel Prodotto ed esclusivamente in connessione con prodotti Handspring. Inoltre, il Software e la documentazione di supporto potranno essere copiati solo in quanto nec-

essario per fini di backup o archivio, a supporto dell'uso del Software da parte dell'utente secondo quanto previsto. L'utente deve riprodurre e includere tutti gli avvisi sul diritto d'autore e qualsiasi altro diritto di propriet che appaiono sul Software su qualsiasi copia che l'utente effettuer. PAGAMENTO DI CORRISPETTIVI: L'efficacia della licenza concessa subordinata alla ricezione da parte della Handspring di ogni corrispettivo dovuto. DIVIETO DI CESSIONE; DIVIETO DI REVERSE ENGINEERING: L'utente potr cedere il Soft-

ware e il presente Contratto di Licenza a terzi in connessione ad un trasferimento del Prodotto sul quale il Software pre-caricato, a patto che i terzi si obblighino per iscritto ad accettare i termini e le condizioni del Warranty and Other Product Information 107 presente Contratto di Licenza. Qualora l'utente trasferisca il Software, dovr allo stesso tempo trasferire tutte le copie del Software cos come la documentazione di supporto al cessionario o distruggere tale materiale che non venga trasferito. Salvo quanto sopra previsto, l'utente non potr trasferire o cedere il Software o i suoi diritti derivanti dal presente Contratto di Licenza. Sono espressamente proibite la modifica, il reverse engi-

neering, la decompilazione, il disassemblamento, o la rimozione del Software dal Prodotto sul quale lo stesso pre-caricato. Tuttavia, qualora l'utente sia residente nell'Unione Europea ("EU"), le informazioni neces-

sarie per ottenere l'interoperabilit del Software con altri programmi, secondo le previsioni della Direttiva EU sulla Tutela Legale dei Programmi per Computer, saranno rese disponibili all'utente dalla Handspring in base ad una richiesta scritta. LIMITI ALL'ESPORTAZIONE: L'utente si obbliga a non esportare o ri-esportare il Software o la doc-

umentazione di accompagnamento (o qualsiasi copia degli stessi) o qualsiasi Prodotto che utilizzi il Software o tale dumentazione, in violazione di qualsiasi legge o regolamento degli Stati Uniti o della nazione nella quale l'utente ha ottenuto gli stessi. Il software oggetto del presente Contratto di Licenza pu contenere un particolare codice di crittografia di dati che non pu essere esportato al di fuori degli Stati Uniti o del Canada. L'utente si obbliga a non esportare/ri-esportare, sia materialmente che informaticamente, il software di crit-

tografia o la documentazione di accompagnamento senza aver ottenuto un autorizzazione scritta del Diparti-

mento di Commercio degli Stati Uniti. AVVISO PER IL GOVERNO DEGLI STATI UNITI: Qualora l'utente stia ottenendo il Software per conto di qualsiasi ente o istituzione del Governo degli Stati Uniti, si applicheranno le seguenti previsioni. Il Software costituisce "bene commerciale", come questo termine definito dal Federal Acquisition Regulation

(FAR) 2.101 (Oct. 1995), ed costituito dal "software commerciale" e "documentazione su software commer-

ciale", come questi termini vengono definiti nel FAR 12.212 (Sept. 1995), e viene fornito al Governo degli Stati Uniti solo come software commerciale (con "Limitazione di Diritti", qualora applicabili). L'uso, la du-

plicazione, o la rivelazione da parte del Governo degli Stati uniti subordinato alle limitazioni stabilite nel presente Contratto di Licenza e cos come previsto nel DFARS 227.7202-1(a) e 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, o FAR 52.227-14 (ALT III), in quanto applicabili. DURATA, RECESSO E RISOLUZIONE: Il presente Contratto di Licenza a tempo indeterminato. L'utente potr recedere dallo stesso in qualsiasi momento, distruggendo il Software e la documentazione in-

sieme a tutte le copie e le parti unificate delle stesse in qualsiasi forma. Il presente Contratto di Licenza sar automaticamente risolto "di diritto e senza necessit di una pronuncia giudiziale" qualora l'utente sia inadem-

piente ai seguenti termini o condizione del presente Contratto di Licenza: In caso di risoluzione, l'utente si obbliga a distruggere il Software e la documentazione, insieme a tutte le copie le parti unificate delle stesse in qualsiasi forma. LEGGE APPLICABILE: Al presente Contratto di Licenza si applicher la legge dello Stato della Califor-

nia L'utente accetta che i principi sui conflitti di leggi applicabili contenuti in tale legge e la Convenzione 108 Warranty and Other Product Information delle Nazioni Unite sulla Vendita Internazionale di Beni (1980) sono espressamente ed integralmente es-

cluse dall'applicazione al presente Contratto di Licenza. LIMITAZIONE DI GARANZIE; LIMITAZIONE DI RESPONSABILITA': Tutte le faranzie e le limitazioni di responsabilit applicabili al Software sono quelle indicate nella Limitazione di Garanzia o nel manuale del prodotto che accompagna il Software. Tali garanzie e limitazioni di responsabilit sono inte-

gralmente incorporate nel presente per riferimento. Tale limitazione si applicher secondo quanto consen-

tito dalla legge. In ogni caso, le garanzie di legge si applicheranno se l'utente un consumatore, secondo la definizione del Codice dei Consumatori Francese. NULLITA' PARZIALE: Nel caso in cui qualsiasi previsione del presente Contratto di Licenza sia ritenuta non valida, illegale o inefficace, la validit, legalit ed efficacia di ogni altra previsione non sar in alcun modo pregiudicata o diminuita e un previsione valida, legale ed efficace con scopo ed impatto economico analogo dovr essere inserita al suo posto. INTERO ACCORDO: Il presente Contratto di Licenza stabilisce l'intero accordo tra l'utente e Hand-

spring, sostituisce tutti i precedenti accordi, sia scritti che orali, relativi al Software, e potr essere modificato solo per iscritto con sottoscrizione di entrambe le parti. Handspring, Inc. Limitazione Di Garanzia Per Gli AccessorI LIMITAZIONE DI GARANZIE: Handspring garantisce all'originario utente ("Cliente") che in caso di uso normale e previsto (i) gli accessori hardware Handspring saranno privi di difetti di produzione e nei ma-

teriali per un anno dalla data di acquisto, e (ii) gli accessori software Handspring saranno sostanzialmente conformi alle loro caratteristiche e che i supporti che contengono il software saranno privi di difetti di produzione e nei materiali, per novanta (90) giorni dalla data di acquisto. Handspring non fornisce alcuna garanzia per il software di terzi. Durante il periodo di garanzia, Handspring riparer, sostituir o rimborser il prezzo di acquisto degli accessori difettosi. Salvo il caso di dolo o colpa grave, Handspring e i suoi fornitori non saranno responsabili per qualsiasi per-

dita o danni di alcun tipo derivanti dall'uso di questo accessorio o per qualsiasi software del Cliente o dati registrati su accessori restituiti a Handspring per il servizio di garanzia. SERVIZIO DI GARANZIA: Il Cliente deve ottenere l'autorizzazione per il servizio di garanzia da Hand-

sping entro il relativo servizio di garanzia prima di restituire gli accessori difettosi ad Handspring. Gli acces-

sori restituiti devono essere inviati con spese di trasporto pre-pagate e opportunamente impacchettati, e si raccomanda che gli stessi siano assicurati o inviati con un metodo che consenta di rintracciare i pacchi. Qua-

lora Handspring invii un accessorio in sostituzione al Cliente prima di aver ricevuto l'accessorio originale ed il Cliente non restituisca l'accessorio originale a Handspring entro trenta (30) giorni dalla data in cui l'au-

torizzazione al servizio di garanzia stata emessa, Handspring addebiter al Cliente il prezzo di listino in vigore a tale data per tale accessorio. Warranty and Other Product Information 109 LIMITAZIONI: LA PRESENTE LIMITAZIONE DI GARANZIA SOSTITUISCE TUTTE LE AL-

TRE GARANZIE, TERMINI, O CONDIZIONI, COMPRESE LE GARANZIE, TERMINI O CON-

DIZIONI DI IDONEITA' AL COMMERCIO, IDONEITA' AD UNO SCOPO PARTICOLARE, QUALITA', CORRISPONDENZA ALLA DESCRIZIONE, E NON VIOLAZIONE DI DIRITTI AL-

TRUI, LE QUALI VENGONO ESPRESSAMENTE ESCLUSE DA HANDSPRING ED I SUOI FOR-

NITORI. SALVA L'IPOTESI DI DOLO O COLPA GRAVE, IN NESSUN CASO HANDSPRING O I SUOI FORNITORI SARANNO RESPONSABILI PER QUALSIASI DANNO SPECIALE, INCIDEN-

TALE CONSEGUENZIALE O DIRETTO DERIVANTE DAL POSSESSO, USO, O MANCATO FUNZIONAMENTO DI QUESTO ACCESSORIO. Alcuni paesi, stati o province non consentono l'esclusione o la limitazione di garanzie implicite o la limitazi-

one di danni incidentali o conseguenziali o la limitazione di responsabilit per lesioni personali, pertanto le limitazioni ed esclusioni di cui sopra potranno essere limitate nella loro applicazione all'utente. Nel caso in cui non sia consentita l'esclusione integrale delle garanzie implicite, le stesse saranno limitate alla durata della relativa garanzia scritta. La presente garanzia concede all'utente specifici diritti che possono variare in base alla normativa locale applicabile. 110 Warranty and Other Product Information Safety and General Information IMPORTANT INFORMATION ON SAFE AND EFFFICIENT OPERATION. Read this information before using your integrated multi-service portable radio. For the Safe and Efficient Operation of Your Radio, Observe These Guidelines:

Your radio product contains a transmitter and a receiver. When it is ON, it receives and transmits radio fre-

quency (RF) energy. The radio operates in the frequency range of 800 MHz to 1990 MHz and employs dig-

ital modulation techniques. When you use your radio, the system handling your call controls the power level at which your radio transmits. The output power level typically may vary over a range from .001 Watts to 2 Watts. Exposure to Radio Frequency Energy Your VisorPhone Radio Product is designed to comply with the following national and international stan-

dards and guidelines regarding exposure of human beings to radio frequency electromagnetic energy:

n United States Federal Communications Commission, Code of Federal Regulations;

47 CFR part 2 sub-part J American National Standards Institute (ANSI) IEEE. C95. 1-1992 National Council on Radiation Protection and Measurements (NCRP). Report 86 International Commission on Non-Ionizing Radiation Protection (ICNIRP) 1998 National Radiological Protection Board of the United Kingdom, GS 11, 1988 Verband Deutscher Elektrotechniker (VDE) DIN-0848 Department of Health and Welfare Canada. Safety Code 6 n n n n n n To comply with the above FCC Regulations governing human exposure to radio frequency energy, users MUST adhere to the following procedure:

n To comply with FCC RF exposure guidelines during body-worn operation, use the Handspring Belt Clip or the Handspring Holster. Use of other body worn accessories that have not been tested with the VisorPhone for RF exposure compliance may not comply. To assure optimal radio performance, always adhere to the following procedures:

n When placing or receiving a phone call hold the radio as you would a telephone. n Speak directly into the microphone and position the antenna up over your shoulder. DO NOT hold the antenna when the radio is IN USE. Holding the antenna affects call quality and may cause the radio to operate at a higher power level than needed. n Warranty and Other Product Information 111 Interference to Medical and Personal Electronic Devices Most electronic equipment is shielded from RF energy. However, certain equipment may not be shielded against the RF signals from your wireless phone. Pacemakers The Health Industry Manufacturers Association recommends that a minimum separation of six inches (6") be maintained between a handheld wireless phone and a pacemaker to avoid potential interference with the pacemaker. These recommendations are consistent with the independent research by the recommendations of Wireless Technology Research. Persons with pacemakers should:

n ALWAYS keep the phone more than six inches from their pacemaker when the phone is turned ON. not carry the phone in a breast pocket. use the ear opposite the pacemaker to minimize the potential for interference. turn the phone OFF immediately if you have any reason to suspect that interference is taking place. n n n Hearing Aids Some digital wireless phones may interfere with some hearing aids. In the event of such interference, you may want to consult your hearing aid manufacturer to discuss alternatives. Other Medical Devices If you use any other personal medical device, consult the manufacturer of your device to determine if it is ad-

equately shielded from external RF energy. Your physician may be able to assist you in obtaining this infor-

mation. Turn your phone OFF in health care facilities when any regulations posted in these areas instruct you to do so. Hospitals or health care facilities may be using equipment that could be sensitive to external RF energy. Interference to Other Electronic Devices RF energy may affect improperly installed or inadequately shielded electronic operating and entertainment systems in motor vehicles. Check with the manufacturer or representative to determine if these systems are adequately shielded from external RF energy. Also check with the manufacturer of any equipment that has been added to the vehicle. Turn your radio OFF before boarding any aircraft to prevent possible interference to aircraft systems. Reg-

ulations of the United states Federal Aviation Administration prohibit use when the aircraft is in the air and require you have permission from a crew member to use your radio while the aircraft is one the ground. 112 Warranty and Other Product Information Safety and General Use While Driving Check the laws and regulations on the use of telephones in the area where you drive. Always obey them. When using the phone while driving, please:

n Give full attention to driving and to the road Use hands-free operation, if available Pull off the road and park before making or answering a call if driving conditions so require. n n International Safety Statements Aircraft Safety Switch off your cellular telephone when in an aircraft. The use of cellular telephones in an aircraft may be dangerous to the operation of the aircraft, disrupt the cellular network and is illegal. Failure to observe this instruction may lead to suspension or denial of cellular services to the offender, or legal action or both. Non-ionising Radiation As with other mobile radio transmitting equipment, users are advised that for satisfactory operation of the equipment and for the safety of the personnel. it is recommended that no part of the human body be allowed to come to close to the antenna during operation of the equipment. FCC Statement This device complies with part 15 of the FCC rules. Operation is subject to the following two conditions:

(1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio fre-

quency energy and, if not installed and used in accordance with the instructions, may cause harmful inter-

ference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

n Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. n n n Warranty and Other Product Information 113 The use of shielded I/O cables is required when connecting this equipment to any and all optional peripheral or host devices. Failure to do so may violate FCC rules. Caution: Changes or modifications not covered in this manual must be approved in writing by the manufac-

turer's Regulatory Engineering Department. Changes or modifications made without written approval may void the user's authority to operate this equipment. Responsible Party:

Handspring, Inc. 189 Bernardo Avenue Mountain View, California 94043-5203 United States of America

(650) 230-5000 Canadian RFI Statement This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Reg-

ulations. Cet appareil numrique de la classe B respecte toutes les exigences du Rglement sur le matriel brouilleur du Canada. Acknowledgments We would like to thank the following developers whose contributions were an integral part of the Handspring product:

n OPTION International NV Kolonel Begaultlaan 45 3012 Leuven BELGIUM Tel: +32 16 317 411 info@option.com www.option.com 114 Warranty and Other Product Information adding from Call History 16 adding to Speed Dial 39 dialing from 17 Dialing Preferences 69 C Call Index Numerics 3-way calling 29 A Active call 13, 25 Address Book Adjusting volume 6 Answering calls 2123 Antenna 5 B Battery care 92 charging 8 disposal 93 gauge 13 indicators 8 inserting 4 location 5 specifications 92 Beep tone 23 Buttons Phone 6 power 5 ringer 6 scroll 6, 15, 51 slider 6 SMS Message Manager 6 Preferences 23, 24, 74, 75, 80 status 26, 28, 29 waiting 23, 74 Call History 19 adding to Address Book 16 adding to Speed Dial list 16 deleting items 36 dialing from 16 displaying 35 icon 16 incoming calls 35 missed calls 19, 31, 32, 35 outgoing calls 35 purging 36 Caller ID 19, 22, 23, 34, 75 Index 115 Calls Dialing 3-way 29 active 13, 25 answering 2123 answering call waiting 23 conference 29 forwarding 24 ignoring 22 incoming 2124, 35 missed 19, 32, 35 outgoing 1320, 35, 75 placing a second 27 placing from SIM Phonebook 47 placing on hold 26 switching 28 Conference calls 29 Coverage area 11, 19, 21, 24, 31, 53 D Deleting Call History 36 SIM card entries 46 SMS messages 34, 53, 60 Speed Dial entries 41 applications 69 emergency numbers 20 from Address Book 17 from Call History 16, 32, 35 from Memo Pad 18 from SIM Phonebook 47 from To Do List 18 last number 16 prefixes 68 previous numbers 15, 16, 35 with Dialpad 15 with Speed Dial 14 Dialpad dialing numbers 15 icon 15 E Edit call forwarding number 24 menu 79, 81, 83 phone number 15, 17, 18, 39 SMS messages 58 Speed Dial 40, 42 Email messages 49, 50, 52, 55 Emergency numbers 20 116 Index F Forwarding calls 24 SMS Email 50 SMS messages 58, 82 Frequently asked questions 8591 G Greetings 56 H Headset connecting 77 jack 5 Hold button 26 HotSync operations 6166, 91 I Icons battery 13 Call History 16, 32 Dialpad 15 Phonebook 44, 45 signal strength 13 Speed Dial 14 Voicemail 13 Ignoring calls 22 Incoming calls 2124, 35 Indicators battery 6, 8, 13 Call History 35 call status 26, 28, 29 call waiting 23 missed call 19 network service 6, 11, 13 signal strength 13 voicemail 13 K Key Pad 13, 14, 33 L LED 5, 6, 8, 11 Light, see LED 6 Limited warranty 95 Locking phone 72 M Memo Pad 18 Menus Phone application 7980 Phonebook 81 SMS Message Manager 8284 Index 117 Message Messages Manager, see SMS menus 82 checking 3135 missed call 19 purging SMS 60 replying 52 sorting SMS 59 text 11, 31, 34, 51 voicemail 11, 33 Missed calls 19, 32, 35 Modem 6166 Module inserting 7 removing 7 N Network coverage area 11 HotSync operation 65 name 13 selecting 76, 80 status 6, 75 voicemail number 38 Network status 24, 74 O Options Call Preferences 74, 75 call waiting 74 menu 80, 81, 84 Phone Preferences 70 Ringer Preferences 71 Outgoing calls 1320, 35, 47, 75 P Password 72, 73 Phone application menus 7980 starting 15 Phone button 6 Phone number checking 10 editing 15 Phonebook menus 81 PIN 72, 73, 86 Power button 5 Preferences Call 75 call waiting 74 dialing 69 118 Index Phone 70 ringer 71 Prefixes 68 PUK 86 Purging Call History 36 SMS messages 60 R Record menu 79 Redialing a number 16 Ringer button 6 settings 71 S Safety 11, 92, 110112 Scroll buttons 6, 15, 51 Security 72 Setup 210 Signal strength 13, 76 Signatures 56 SIM card defined 1, 3 IMEI 10 inserting 3 locking 72 Index phone number 10 Phonebook 4347 SMS Message Center number 50 SIM Phonebook 4347 Slider 5, 6, 71 SMS changing messages 58 copying text 57 creating messages 53 email messages 50, 55 forwarding messages 58 greetings 56 Inbox 51 menus 8284 Message Manager button 6 messages 31, 34 Preferences 50 purging messages 60 replying to messages 52 saving messages 57 signatures 56 sorting messages 59 Sorting messages 59 Speaker 5, 6, 77 119 V Vibrate 71 VisorPhone inserting 7 parts of 5 removing 7 turning on 9 icon 13 Volume 6 W Warranty 95 Wireless HotSync operations Voicemail 11, 19, 22, 31, 33, 38 synchronization, see Speed Dial adding Address Book entries 39 adding Call History entries 16 changing entries 40 copying entries from SIM card 44, 45 defining buttons 38 deleting entries 41 dialing numbers 14 icon 14 list 3742 organizing 37, 42 voicemail 33, 38 Support 85 Switching calls 28 T Text messages, see SMS To Do List 18 Troubleshooting 8591 U Unblock code 86 Unlock code 86 120 Index