<?xml version="1.0" encoding="UTF-8"?>
<pInstaller xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.handx.net/devtool/pInstaller/schema/pInstaller.xsd">
<!-- The previous two lines are required as the first two lines for any pInstaller project.  They establish that this is 
an xml document which follows the pInstaller Schema-->
<!--First, we specify the product name -->
	<productName>Sample Palm App</productName>
<!-- Now we need to include information for the COM Installer.  This installs COM support into the palm desktop and
is required to run a COM conduit.  At about 1.4MB, it adds a chunk to your installer, but without it, your conduit
will not run on most instances of HotSync -->
         <COMInstaller>
<!-- The name of the COM installer will pretty much always be the same -->
                <fileName>PalmCOMInstaller.exe</fileName>
<!-- You probably want to hide the COM Installer when it is running -->
                <runHidden>true</runHidden>          
<!-- close up the COM Installer section-->
         </COMInstaller>
<!-- Now we'll list our installation files. -->
<!-- First we indicate that we are describing an installation file -->
	<installationFile>
<!-- Now we specify the file name -->
		<fileName>samplePalmApp.prc</fileName>
<!-- Now we specify the destination as $PALM_DEVICE  this is a special variable which will
place the file on the palm device, rather than the PC. -->
		<destination>$PALM_DEVICE</destination>
<!-- Each Installation file in this example is in fileGroup "0", which
indicates that it is a required file.  If we wanted users be able to select individual files for installation we
would create other File Groups in this xml document, and assign the files to those groups. -->
		<fileGroup>0</fileGroup>
<!-- close up this installation file -->
	</installationFile>
<!-- Now we indicate that we are describing another installation file -->
	<installationFile>
<!-- Now we specify the file name -->
		<fileName>SampleConduit.dll</fileName>
<!-- Now we specify the destination as $HOTSYNCDIR  this is a special variable which will
place the file in the HotSync directory.  Generally, this is the best place to install a conduit. -->
		<destination>$HOTSYNCDIR</destination>
<!-- Again, we specify that this is a required file. -->
		<fileGroup>0</fileGroup>
<!-- Now we indicate that this is a conduit -->
		<conduit>
<!-- For a COM conduit, the file name should always be COMConduit.dll. -->
		         <fileName>COMConduit.dll</fileName>
<!-- Each conduit must be associated with a creatorID on the Palm.  Specify that here.  DON'T USE THE EXAMPLE! -->
		         <creatorID>saPA</creatorID>
<!-- Assign a priority between 0 and 4 (lower numbers get called first).  Generally, stick with the default of 2 -->
		         <priority>2</priority>
<!-- Now specify the Display Name for your conduit -->
		         <name>Sample Palm App NiftyCOMSync Conduit</name>
<!-- Now we set the COM specific settings for our conduit -->
		         <COMSettings>
<!-- Now specify the COM Client If your conduit is a standard executable (.exe), then this value is the full path 
and file name of your client conduit for example, C:\Program Files\Microsoft Visual Studio\VB98\VB6.exe.
If your conduit is an ActiveX server, this value is the notification object's PROGID (also called the
Programmatic ID) - for example, Sampl3Palm.CNotify.  -->
                                       <COMClient>SamplePalm.CNotify</COMClient>
<!-- Now close up the COMSettings group -->
		         </COMSettings>
<!-- Close up the conduit element -->
		</conduit>
<!-- Chances are, your conduit DLL will need to registered (as in regsvr32.exe).  Specify true here to register the dll -->
	<registerDll>true</registerDll>
<!-- close up this installation file -->
	</installationFile>
<!-- now we close up the pInstaller element-->
</pInstaller>
