David Bengtson [mailto:[EMAIL PROTECTED]] wrote:
Dave> Actually, since Plucker doesn't support VFS yet, I need to install it
Dave> to a configurable directory so that MSMount or PiDirect can see it.
Dave> I tried changing the destination and it doesn't seem to work.

Both MSMount 1.0 and PiDirectVFS 1.02 are working for me on an M500. Earlier
versions of both programs tend to cause fatal errors. It's better if you run
the viewer itself from RAM rather than from the card. Also can be problems
with some third-party launchers. I'm using Lancher III 3.02 successfully.
Native VFS support will be nice in the viewer. Would prefer an PiDirectVFS
type implementation over MSMount as it doesn't move the entire database to
RAM right away but as it is needed.

TL

-----Original Message-----
From:
Sent: Friday, October 05, 2001 7:02 PM
To: Plucker List
Subject: Re: Plucker install to VFS?


Hi Dirk

(Thanks for the Easy to install Windows Package)


I would be happy to help in anyway that I can. If that involves
running some test cases, then I'd be happy to do that.


Dave



On Fri, 5 Oct 2001 15:13:05 +0200, you wrote:

>"David" == David Bengtson <[EMAIL PROTECTED]> writes:
>
>David> the day. In the morning, I'd just like to hotsync and go. Is
>David> there are way to get the Plucker runsync to install to a Memory
>David> Stick? (I'm using a Clie 610, if that makes a difference) This
>
>Does it mean that plucker should prepare the databases for install on
>the memory stick in the same way as the palm install tool does it if
>you select "Change destination"?
>
>If yes, that is possible. I have written some code to do that some
>time ago, but since my palm does no have an extension slot and the
>palm emulator does not emulate the memory slot good enough to simulate
>the sync with an VFS device i cannot test this.
>
>If you wan't spend a little bit time with answering a few questions an
>run a few test write me an mail, then i could add this function.
>
>cu,
> Dirk
>
>BTW: i leave home now until sunday, so no response until mondy, and no
>1.1.3 release, sorry.
>

Reply via email to