For details about the differences between version 2 and version 3, see the file Version3.TXT in the distribution.
You have to define a special SmartClip for Buddy to use. The clip's name can be anything, but it must start with a greater-than sign. For example, the SmartClip could be named ">Buddy". In that clip, you define which fields are clipped, and those fields become your appointment description. If Buddy does not see that SmartClip, it stops and does nothing. (Note: if you are in a full-screen note or a Memo file, then Buddy uses the line under the cursor instead of a SmartClip.)
Whew! That's a complicated question with a simple answer. Just set the "(Int'l) Normal Fn-A, Fn-I..." checkbox or use the "(Int'l) Require MENU before Buddy..." feature. (EXM screen image)
Those function keys are only used in "formatted" Memo files. If you push one of those keys, even by accident, your unformatted (ASCII) file will become formatted. You may not want that to happen. So, unless you are editing a formatted file, Buddy disables those Memo functions and uses those function keys (plus F6) for other things. (Screen image.) To get access to those keys for the first time in an unformatted file, just push MENU first. Once your file becomes formatted, Buddy restores those keys to their built-in functions. (To access the original F6 function in an unformatted file, use MENU Edit Insert.)
Fill out and mail the registration form (REGISTER.TXT), or use CompuServe's GO SWREG (look for program ID #2101). If you have already registered your copy of 100Buddy version 1 or 2, then you do not need to register again for version 3. Sorry, there is no upgrade from 95Buddy.
No, previously registered users can upgrade at no charge. When you move Buddy to a new machine, however, you have to re-enter your serial number using the confidential instructions I mailed to you. If you have lost those instructions, please contact me.
Yes, if your machine is an English version, or an international version that has English-language displays, then Buddy will be happy. But, Buddy only understands English, just like me. On machines with non-English displays, many Buddy features don't work. I do not have a list of those features; you'll have to try it yourself (there is no danger) or ask other people on a BBS.
No, it would be too much work. For starters, there are hundreds of places in the program where Buddy (1) makes decisions based on particular pixels, letters, or words that appear on the display and (2) outputs certain characters to the application. Sorry.
This can happen if you have manually changed your APNAME.LST file. For example, if you changed it to assign a blue key to "acCIS." To test this, rename your APNAME.LST file and then try MENU-dot in DOS. The proper way to assign a blue-key to an application such as acCIS is to use Buddy to re-assign the blue-key to the hotkey you have assigned to the application.
This is easy to do yourself just by looking at the map overlay. If the moon is near the sun, then it is a new moon. If the moon is near the center of the night region, then it is a full moon. If the moon is near the terminator, then the moon is at first or third quarter. See? You learn something every day!
Nothing. Check your calendar: it's either March 21 or September 21, right? Think about it.
You need to tell Buddy the location of your "local city." This is set on the WorldTime Overlay settings screen in the Buddy EXM. Be sure the "Time zone," "east," and "DST" controls are set correctly according to the instructions and examples on that screen.
Some of my ZIP files have a "header" on them, courtesy of my Mac software. Unzippers are supposed to simply skip over anything before the ZIP signature, but some older unzippers don't do that. You need PKUNZIP version 2.04g or newer. On the CompuServe HPHAND forum, that would be PK204G.EXE in library 1.
To unload Buddy, be sure you have checked "Unload Buddy when terminating sysmgr" in the Buddy EXM. Then, terminate sysmgr by pressing &More MENU A T ENTER. If Buddy says it is still loaded, then you should check your AUTOEXEC.BAT and be sure you did not load another TSR after Buddy. TSRs must be unloaded in reverse order, and Buddy will not unload if it determines that a later-loaded TSR is still running.
You can also unload Buddy from DOS by pushing SHIFT-MENU-DEL, or by typing BUDDY -U.
There are two ways for d-letter to be inhibited. One is "inhibit after a lower case letter," and that will inhibit d-letter after a lower-case letter in all applications where d-letter is active. The other, "dot after white space" in SmartCaps(tm), will inhibit d-letter in all places except the first character position of a word (not just after a lower-case letter), but it will do so only in those apps where SmartCaps is enabled and if SmartCaps is on. SmartCaps figures that if you really want a capital WITHIN a sentence, you'll push the period key before typing the word. SmartCaps is trying to help you keep proper nouns like "Lee" from becoming "LE". Both of those checkboxes are on the SmartCaps Settings screen.
Buddy works fine, but what you have is not Buddy -- it's garbage. I bet you transferred the COM and/or EXM file to your palmtop in "text" mode. That will corrupt the file because it adds line formatting characters. Do the transfer again, but be sure the file does not get changed. A properly loaded, uncorrupted copy of Buddy will NOT crash your machine.
There are two Buddy features that will automatically shift a blue key for you. Both are set from the "Blue Key Controls" screen of the Buddy EXM. You probably have the "Blue-Key Auto Inhibit" timer enabled in Memo. This feature will shift the blue keys for you if you push one within the specified number of seconds after typing a character. A little "tornado" character appears on the Memo title bar when this timer is running.
There are no bugs that will cause file corruption. Buddy.COM only reads two files (BUDDY.ENV and FILER.INI at startup), and it doesn't even know how to write a file. Buddy has been thoroughly exercised by a beta test team, and there are thousands of regular, satisfied users.
However, here are two things to watch out for:
- If you terminate sysmgr automatically using a macro, then Buddy will not know you did so and some Buddy features will not operate correctly when you reload sysmgr, and you will have to reboot to unload Buddy. If you need to terminate sysmgr, always do so manually (using MORE MENU A T or MENU-SHIFT-DEL) so that Buddy can see you do it.
- If you terminate sysmgr when there is a "dirty" (meaning changed and unsaved, not pornographic) file loaded in Memo, don't push "Cancel" in response to the prompt to save the file. Push "Yes" or "No." The Cancel option will cause Buddy to partial unload and get stuck until you warm boot.
(200LX only) If you are using the FILER.INI file, you might find that the Filer-to-application links (e.g., double-clicking on a text file in Filer to start Memo) do not operate and that autoexec.bat will be executed when d-clicked. There are two things you can do about this:
- You can instruct Buddy to use Memo for one or more of the three user extensions by entering "MEMO" (all capitals) for the "DOS program" assigned to the extension(s) in the Filer Settings screen of the Buddy EXM.
- The ultimate work around is to make FILER.INI go away while you start Buddy. Rename your FILER.INI to FILER.INX. Then (in your autoexec.bat):
del FILER.INI c:\bin\buddy.com copy FILER.INX FILER.INI
Remember to edit FILER.INX when making changes.