Have solved the problem with

Have solved the problem with the nBlog inactive action icons and nHTML error.

I purchased a second Newton. It was half the price of my first unit and had both covers. However, it has a very rough screen. Clearly this system has seen lots of use. Even though it is old and scruffy, it became my principle unit. As the principle unit it was the first to get an nBlog installation. This unit is different then my first. When it starts up its default screen is “Extras.” It also had the previous owners specialty software installed. Was never quite sure what all the pieces of this software were. It got me thinking that perhaps something was interfering with the functionality on nBlog. So I installed nBlog on my backup unit. Success…these two problems did not exist. Next, I did a hard reset on my scruffy Newton and reinstalled all packages. Since I have a 8Meg memory card, package reinstallation was simply a matter of a backup of unit 1 and restore on unit 2. Problem solved. nBlog action icons were now active and hHTML displayed.

A Hard Reset is:
“Caution: A hard reset erases all data, third-party applications, and information in the MessgePad internal memory.
To do a ” hard reset,” follow these steps:
1. Remove any PC cards or application cards inserted in the
2. MessgePad.
3. Press and hold the Power key while momentarily pressing the Reset button on the bottom of the MessgePad.
4. Continue holding down the Power key until a message appears asking if you want to erase your data completely.
5. Tap Yes.
6. When another message appears telling you that all data will be erased, tap OK. “

With this success, the next step was to publish. With great enthusiasm I composed a my greatest blog post and tapped the Publish icon. Data was sent, and a reply received ??

“Error: Client
Failed to locate method (publish) in class (blogger) at
/usr/local/lib/perl5/site_perl/5.6.1/SOAP/Lite.pm line 2195.”

I quickly ran mt-check.cgi to verify proper installation of SOAP::Lite. It reported back that everything was OK. I posted the problem on the nBlog Forum. Perhaps this problem has been seen before.