                         MM2Pilot
                         ========

This is the readme file for a fairly simplistic Meeting Maker to pilot 
conversion routine.  I'm sure it could easily be modified for other 
imput formats if desired.


BACKGROUND
----------

Recently, a tool (convdb) was posted to the "net" that took a simple text 
file input, and created a pilot datebook database.  This DB could then be 
easily imported -OR- used to replace the existing DB on the pilot 
DeskTop (on the PC).

Since I wanted to get to an older version of Meeting Maker (not
supported by any of the normal commercial conduits like Intellisync),
and now there was a tool to create a Pilot DB, I knew I could craft 
a solution.

I wrote a simple perl routine to parse the text from MM's export text
function and convert it to the format used by convdb. Then, using a
simple .bat file to string them together, you can create a simple,
one-way (MM -> Pilot) transfer process.

The premis (right now) is that Meeting Maker is the master, and 
Pilot is a READ ONLY device...There is no Syncronization back the other 
direction.  In fact, you can change the "HotSynch" settings to customize
the synch for the datebook so that the desktop version always replaces 
the version on the pilot.

SETUP
-----
To set up for you environment, First unpack the .zip file into any 
directory you choose.  I put mine into the pilot desktop folder as a 
directory called MM2Pilot, but any location is fine. I have NOT included
the convdb.zip file.  You need to get that too and extract the convdb.exe, 
but I did include the cygnus dll (cygwin.dll) mentioned in the convdb
README file, along with just the basic perl binaries to make this work.

Then, edit the mm2pilot.bat file to define your file locations, etc.

You MUST edit in your locations, and set the options properly for 
your particular environment (MM location, Pilot UserName, etc.)

I have set mine up to copy the export.txt file (output from MMM) to 
the local directory. Then I execute the perl code to convert it. This
creates an output file called convdb.txt. The convdb.exe reads this
file, and creates a Pilot DB (output.dba). You can either import this
file, or let the script copy it to the Pilot Desktop, and replace
the current datebook.dat file. (this is what I do, but you can do either)

You can also simplify things in Meeting Maker if you remove all the 
unnecessary export filters. This simplifies the export process, since MM
will default to the first filter it finds. They are located in the 
mmexport folder under your meeting maker installation directory.  Keep 
the one for TEXT (text.exp) - All the others can be removed.

It also saves a "click" if you delete the original "export.txt" file
in your mm2pilot.bat file. That way you are not constantly bugged with
a dialog box to confirm replacing the existing file.


USING THE PROCESS
-----------------
To use this process, export the calendar from MM, run the m2pilot.bat 
file, and then run the HotSynch process...and BINGO...your MM data is 
in your pilot.

BUGS
----
None that I know of at this time. Please let me know if you find 
anything else...

Scott Baeder
baeder@cadence.com

