[drawkcab]

I just installed the Bonsai Beta. I selected my Palm username as part of the process, and synced it immediately after finishing the install. I received the following error in the hotsync log:

Quote

"Your Natara Bonsai evaluation period has expired! Synchronization was not performed.
Natara Bonsai synchronization failed"

When I opened the palm program, an error said:

Quote

"That is not a valid registration number for you Palm user name."

I checked both the desktop and palm registration numbers, and both still list the same registration I had for the previously installed version of Bonsai. I update pretty faithfully, so it would have been the most current version prior to the beta.

Was I not supposed to install the beta over the most current version of Bonsai, or is this some quirk of the beta? The hotsync log did confirm my Palm username, so I know I selected to correct one in the install. What do I need to change in order to get it syncing again.

Thanks,

Todd

Dell XPS m1210 running XP Pro SP3
Tungsten T w/ Palm OS 5.0

[drawkcab]

BTW, the desktop still says I have 30 days left in my trial. It is my Palm app that no longer recognizes the reg code. -Todd

[drawkcab]

I just realized a similar comment had been made in this topic and saw that a V5 reg number was required for the palm app. I did not realize this was the case before installing the beta (thought I had the 30 day trial for both the desktop and palm app), and would appreciate a temp v5 reg code. Otherwise, I will need to head back to V4 (I use Bonsai too much to have the hotsync not working).

Thanks,

Todd

This post has been edited by drawkcab: 29 June 2009 - 03:38 PM

[TomDavey]

drawkcab, on Jun 29 2009, 05:34 PM, said:

I just realized a similar comment had been made in this topic and saw that a V5 reg number was required for the palm app. I did not realize this was the case before installing the beta (thought I had the 30 day trial for both the desktop and palm app), and would appreciate a temp v5 reg code. Otherwise, I will need to head back to V4 (I use Bonsai too much to have the hotsync not working).

Hi Todd,

I'm the fellow who started the other topic. I'm been trying a few things to work around the 5.0.1 beta problem that began for me yesterday. So far I've had no luck, but maybe my experiences will shed some light.

To recap: yesterday I installed the 5.0.1 beta on my machine at home. I was delighted to find that the file-to-file syncing worked perfectly with the Pre. I then used ordinary HotSync with the beta and my Treo 750p. At this point, unlike yourself, I did not check my HotSync log, so I can't say whether the sync was successful or not. However, I did immediately notice two issues with Bonsai on the Treo:

1. Like you, I'm getting the message from Bonsai that says "Invalid number: That is not a valid registration number for your Palm user name."

2. Within Bonsai, and only with Bonsai and not other Palm apps, the alphabetic keys are disabled (i.e., they don't transmit characters) when working with the Outline hierarchy. Other keys, like Enter and Backspace, do work in Bonsai's Outline hierarchy. In Bonsai's Notes view, all keys work, including the alphabetic keys, as usual.

I'm assuming that problem #2 is caused by #1: post hoc, propter hoc. #2 seems like an anti-piracy mechanism. However, I won't be able to confirm causality until I solve problem #1 and find that #2 goes away as well.

To solve problem #1, I tried the following. I have a duly registered copy of Bonsai 4.1.2 running on my system at work. I regularly Hot Sync my Treo 750 between this machine and the one at home. I did so today. I verified that the sync completed successfully by visually comparing outlines between the desktop and the handheld, and by examining the Hot Sync log. So, all is well with the sync.

However, Bonsai on the Treo is still giving me the "Invalid number" message, and the alphabetic keys are still disabled. I'm surmising that at this point I'm going to have to do a full re-install of Bonsai 4.1.2 on the Treo to get the message to go away. Hopefully that will also solve the keyboard problem, if in fact the two problems are related.

Hope this info helps.

Regards,
Tom Davey

[Richard Murphy]

Sorry for the inconvenience. I have a posted an evaluation number for Bonsai v5 in the beta thread (second mesage of the thread).

[drawkcab]

Richard Murphy, on Jun 30 2009, 12:12 PM, said:

Sorry for the inconvenience. I have a posted an evaluation number for Bonsai v5 in the beta thread (second mesage of the thread).

Thanks, Richard! I am now happily syncing once more.

Todd

[TomDavey]

TomDavey, on Jun 29 2009, 08:42 PM, said:

However, Bonsai on the Treo is still giving me the "Invalid number" message, and the alphabetic keys are still disabled. I'm surmising that at this point I'm going to have to do a full re-install of Bonsai 4.1.2 on the Treo to get the message to go away. Hopefully that will also solve the keyboard problem, if in fact the two problems are related.

Hi Richard,

I can verify that the disabled keyboard situation is a "crippleware" feature intended, I guess, to frustrate software pirates. Both the "Invalid number" message and the disabled keyboard went away once I manually entered the beta reg code into the "Register" dialog on the handheld. Note that Hotsyncing with the beta was not sufficient; the new reg code (at least with build 3158; will try with 3166 next) was not transferred during the Hotsync.

Anyway, now that I've manually entered the beta reg code, all is well. However, I recommend that in a new build of the handheld software (if any is planned) that a message be displayed to let the user know that the keyboard is disabled because of an invalid reg #. At first I thought I had a hardware problem or a configuration goof of mine. It took me a long while to realize that the disabled keyboard was an anti-piracy mechanism.

BTW, I had no such difficulties with Bonsai running under Classic on the Pre, only on the Treo. At the moment my Pre's version of Bonsai is 4.2.7, build 2805. Is there any reason to reinstall the .prc from the latest beta on the Pre? I suppose that a fresh install would, for testing purposes, eliminate a possible variable?

Thanks,
Tom Davey

[Richard Murphy]

TomDavey, on Jul 4 2009, 02:57 PM, said:

I can verify that the disabled keyboard situation is a "crippleware" feature intended...

No, I ready cannot explain the disabled keyboard issue. We do not cripple the evaluation in any way except for enforcing the 30 day evaluation period.

For the Pre, I would suggest using the MotionApps Classic certified version of Bonsai v4.2.7. Nothing has changed with the Palm version of Bonsai since the 4.2.7 version. It is my understanding that unsigned/uncertified Palm applications will cause a warning to be displayed from the Classic emulator each time you run the application. Is this true or is the warning a one time only event (or maybe an option to not warn again)?