VisorCentral.com - Hotsync w/ 8MB Flash Module

Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Hotsync w/ 8MB Flash Module (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=10682)

Posted by potter on 01-08-2001 04:33 PM:

When HotSynching with my 8MB Flash Module in my Visor Deluxe, everything appears to work fine. However, if I then check the HotSync log on the PC, I find the last few lines to read something like:

code:   -- Backing up db AvantGo to file C:\Palm\PotterM\Backup\AvantGo.PRC
System synchronization failed
Protocol Error: Handheld file not found.  (4003)
HotSync operation complete 01/08/01 10:14:57 AM

The file mentioned in the first line given above is on my Flash Module and not in main memory, and varies as I change files on my Flash module. If I remove the Module before the HotSync, everything works fine. This error happens at Home and at Work. Home is under Windows 98 using a USB cradle. Work is under Windows NT 4.0 using a serial cradle. Both are using the 3.1.0H version of the HotSync Manger. Both are using the standard System conduit. I cannot say when this error first started, since it is a silent error, it was apparently some time before I noticed it.

Posted by Tom LaPrise on 01-08-2001 10:50 PM:

Move that one file back into RAM (off the module). If a file gets written to or changed during a HotSync, it can't be on the module.

__________________
"Yeah, he can talk. It's gettin' him to shut up that's the trick!"
-Shrek

Posted by potter on 01-09-2001 03:23 PM:

Alas that does not apply here. AvantGo is the executable, not one of the data file. It does not change. If I move the file that the HotSync is complaining about from Flash-Memory to Main-Memory, it then just changes to complaining about another. In resent times I have seen it complain about AvantGo's and HandyShop2's application files (HandyShop does not have a conduit associated with it), and an iSilo Document file (which does not change).

Posted by potter on 01-15-2001 03:38 PM:

After a few email exchanges with Handspring's Technical Support, this was their final reply:

quote:
Thank you for contacting Handspring Technical Support.

We do not recommend that you hotsync your Visor with the Flash Module installed. Even though the computer doesn't exchange data withe module. It can be "seen" during the hotsync process and sometimes cause hotsync errors such as the one you mentioned in your e-mail to occur. Remove the module from the Visor before you hotsync.

Regards,
Handspring Technical Support

I do not like this answer, but oh well.

Posted by Bret Snyder on 01-15-2001 05:43 PM:

Install BackupBuddy and let it backup everything on your Visor and flash module.

__________________
Bret Snyder<BR>If you don't know where you're going,<BR>You'll probably end up somewhere else.

Posted by potter on 01-15-2001 08:11 PM:

quote:
Originally posted by Bret Snyder
Install BackupBuddy and let it backup everything on your Visor and flash module.

I am considering that ... $29.95 vs. $0, partial backups vs. full managed backups.

Posted by potter on 01-15-2001 08:23 PM:

After some experimentation on my own I found:

Palm Desktop 3.01 from Handspring's site does NOT have this error (Hot Sync Manager 3.0.2Hb).
Palm Desktop 3.1 from Handspring's site DOES have this error (Hot Sync Manager 3.1.0H).
Palm Desktop 3.01 from Palm's site does NOT have this problem (but no USB either) (Hot Sync Manager 3.0.2).
Palm Desktop 4.0 from Palm's site DOES have this problem (but also no USB) (Hot Sync Manager 3.0.4).

After further experimentation I settled on the following:

Installed Palm Desktop 4.0 from Palm's site.
Made a copy of bakcn20.dll, the backup conduit.
Installed Palm Desktop 3.01 from Handspring's site overtop of the 4.0, but selected custom and then disabled everything but the Hot Sync Manager. Told the installer to keep the "third party" conduits.
Put the bakcn20.dll copy back in place.

This appears to work, but of course will be unsupported by Handspring or Palm.

Posted by potter on 01-15-2001 09:13 PM:

quote:
Originally posted by potter
This appears to work, but of course will be unsupported by Handspring or Palm.

I jumped the gun. This does not work. The Palm Desktop refuses to come up, giving an error dialog box stating "The ordinal 1000 could not be located in the dynamic link library PalmCmn.dll". Obviously that DLL is too old.

[Edited by potter on 01-15-2001 at 04:19 PM]

All times are GMT. The time now is 04:03 AM.

Show 20 posts from this thread on one page