From: Scott W. <swa...@my...> - 2003-03-01 20:34:50
|
On Sat, 1 Mar 2003, Jan Erik Mostr=F6m wrote: > 2003-03-01 13:38: Scott Wallace <swa...@my...> is > believed to have typed: >=20 > > Great! I took a quick look at your website and noticed that > > this is built for Mac OS X. I should tell you that there is a > > problem with the Mac version of Palm Desktop that prevents it > > from transferring pilotdb databases to the palm correctly. I > > don't know if you've tried to get pilot-link > > (http://www.pilot-link.org) to work on OS X, but it is one way > > to get /complete/ databases to the palm. If you do have it > > working (and have found a place to download binaries), you > > could send the url to the newgroup? A number of people have > > run into this problem, but there is no easy way to change the > > db format to deal with this bug in the mac palm desktop. >=20 > How does this bug manifest itself? I haven't had any problems at all > with this since I switched to OS X (about a year ago now). Hm, well, I don't have a mac, so I'm not positive. But a number=20 of users with macs (os x and os 9.whatever) and palm desktop 4.0 have sai= d=20 they had trouble installing pilot databases from the web. A year or two=20 ago, I found an article on the web saying that the mac palm desktop only=20 transmitted part of a database's AppInfo Block, basically it was limited=20 to a fairly small size, like 512 bytes or something. Since DB stores a=20 bunch of stuff in the appinfo block (the db schema, all calculated field=20 scripts, views, etc) it seemed like this was likely the culprit for mac o= s=20 people that had trouble installing databases they d/l from the web, or=20 that they had backed up on a previous hotsync. (the trouble manifests as= =20 pilotdb not being able to open a particular database) But if you're=20 using the mac os 4.0 desktop and not having this trouble, then I my=20 initial guess must be wrong. -Scott |