By: Brenton Blawat

To most problems, it is recommend most Users should RTFM and STFW. Q: What happens when reading the manual leaves you even more confused than beginning and searching the web results in NO coherent results for the product?!? A: Well you get my BIT Tangents to listen to….

Understanding Packages

There are four types of Wavelink packages which can be created:

Auto Run – Provides the ability to execute multiple commands after the deployment of a package. So what exactly does this mean?

The execution of Auto Run commands don’t actually work as you would expect. The Auto Run commands have to be specified in the “Startup Command”. While you’d think you can specify multiple commands, the commands don’t always parse correctly from the Package Builder for an Auto Run Package. As a result, Wavelink Support, and my recommended methodology is to create a auto execution file within the package named : autoexec.bat

This file .BAT file is only allowed to have 1 command contained in it. This is a result of a bug within the Package Builder Software and the way the mobile devices parse the file. As a result, and more perplexing, the a caveat of the software is that it only accepts the following:

1. Single Line

2. No Triggers

3. No spaces to execute other items.

4. Startup command must read exactly: autoexec.bat

Note: The startup command MUST say only autoexec.bat (NO relative path to the file is required) and the autoexec.bat must be configured in the ‘APPS’ ‘Install Drive’ within the package for proper execution (install path should be left blank). Surprisingly enough, the Enabler is smart enough to know that by saying ‘autoexec.bat’ it needs to look in the \Application\Avalanche\Packages\Files\AVA\APPS\APP_NAME\ directory for the file.

Commands which will NOT work:

Copy \Application\Brent.CPY \Windows\Brent.CPY

<– technically the spaces are considered triggers. –>

Cmd.exe /c brent.bat

<– again the use of triggers –>

Commands which WILL work:

\Application\brent.bat

<– My recommended usage –>

\Program Files\BrentsApplication\brent.bat

<—While there is a space, it is still a singular line. –>

Getting the Auto Run to Work correctly

I always recommend two .BAT files with the use of Auto Run Packages. With the inability of the Enabler to parse multiple lines in the autoexec.bat, I call a secondary .BAT file to execute the commands I need to occur. This provides me with a stronger command base and the ability to run IF EXIST, IF NOT EXIST, DEL, COPY, MKDIR, >, ECHO, or any other command that is supported by Pocket CMD.

#1 Setup the autoexec.bat – Create a new .BAT file named autoexec.bat

#2 Mapping to second .BAT – place in the autoexec.bat a single line that states the location of the new .BAT file. The location MUST be the absolute location of the .BAT file.

E.G.

\Application\brent.bat

or

\Application\Avalanche\Packages\Files\AVA\App_Name\Brent.bat

#3 Create the second .BAT file – Create the secondary .BAT file on the system. Place as many command line parameters in the .BAT file as necessary for the package.

#4 Placing of the files within the package – The Autoexec.bat file MUST be located in the ‘APPS’ ‘Install Drive’. The second .BAT should be located in either ‘C’ ‘Install Drive’ and the ‘\Application\’ ‘Install Path (first example) or the the ‘APPS’ install drive (second example).

** For more information on building this package; read my Creating an Auto Run Wavelink Avalanche Package.

**Also, for those devices that do not natively support .BAT extensions, you will need to add .BAT registry customization by reading my .BAT Execution for Pocket PC 2003 article.

Support – This provides the ability to place files on the device. In short, the Support Package enables a user to place specific files into specific locations.

Note: While Support Packages do not support the autoexec.BAT syntax, the Support Packages do enable the Post Install Scripts. This allows certain registry entries and files to be imported into the system via their scripting engine.

My Recommendation: Use Support Packages when you want to place files onto the device without the requirement of additional commands. If additional commands are required, create an Auto Run Package.

Application – This provides the ability to place files onto the device, and adding a launch-able icon to the Enabler.

My Recommendation: Don’t use this feature. This all goes back to the Software Profiles. I strongly recommend setting up Software Profiles for individual departments for the handheld devices. In this create an enabler confi package to include the Applications which are required. This enables the Users of these devices to have the same icons and same items on their desktops. Software Profiles are much easier to support and the “one offs” will be eliminated.

Config – This is a method to configure or change a specific file. I’ve avoided the use of Config Packages as there are better methodologies to get around using this type of packages.

My Recommendation: Don’t use this feature. If a file need to be configured, redeploy the file as a Support Package or redeploy the entire software package. This a better solution as upon an update of a software package on the Avalanche server will only send the specific files which were updated; not the entire package.

For More Training: Go to Wavelink Training (Click Here)

Info on Author: Brenton Blawat is a Wavelink Consultant who has worked closely with the Avalanche product for over 5 years. He has integrated Wavelink AMC (and variants) into a multitude of corporations including but not limited to: Seneca Foods Corporation, American Eagle Outfitters, and Alexian Brothers Health System.

** BIT Tangents nor any of its contributors are liable for damages as a result of following these instructions. These instructions are intended as guidelines for best practices and are to be used at the executioners own risk! All re-productions / digital copies of this content must be approved in writing by an authorized representative of BIT Tangents. **