Mobile Packager Installer Help For CAB and EXE Projects

by Mobile Packager Team 7. April 2013 05:57
 
The following are links to pages that contain copies of the content in our help files. These links will hopefully be useful to some of our users who are searching online for our Mobile Packager help content. 
 

Autorun.exe in Windows Mobile device storage card

by Mobile Packager Team 8. March 2009 07:36

Windows Mobile supports a feature to detect a newly inserted storage card and automatically load an application from the storage card into the memory of the Windows Mobile device. It also detects when the storage card removed from the mobile device and notifies the application that was loaded when the storage card was inserted to remove itself and perform a clelanup action.

The implementation simplicity of this feature is provided by renaming any executable application to Autorun.exe. This will make the renamed application(autorun.exe) ready to be launched automatically upon insertion of a storage card. However, after renaming the file, the file itself must reside in reside in a particular folder in the storage card. For example "\2577\autorun.exe" is valid auto run location for ARM processor based devices.

Processor Type       Autorun Folder on Storage Card
SH3                          10003
MIPS                         4000
ARM (SA1100)           2577
ARM (720)                 1824
x86                           686

If Windows Mobile was unable to find an autorun.exe under the special folder for the its processor type, it then checks for "\0\autorun.exe".

Note that autrun.exe does not directly run from the storage card. It is first copied to \windows" or "\windows\autorun\<storage card name>" folder on the mobile device by the Windows Mobile OS before it is launched.

In summary the steps are as follows (Because the device emulator is the one environment share in common, we will use that to demonstrate this feature).

  1. Rename file to autorun.exe.
    (Note in Mobile Packager this can be done by setting the output name to "autorun.exe" or by manually going to the output folder and renaming the generated output file for the current project).
  2. Copy the autorun.exe to a storage card under the correct subfolder ("\2577" for emulator)



  3. Insert the storage card into the the mobile device.
    To do this on the emulator you have to share the parent folder that contains the device specifc folder. In this example it will be "C:\Documents and Settings\Admin\My Documents\Mobile Packager Tests\Autorun Test\Output\Mobile".




    As soon as you click on the "OK" button of the "Emulator Propeties" window, the emulator simulates that as a storage card insertion and therefore will launch the autorun.exe that you created using Mobile Packager.

On a final note, because there can only be one aturun.exe in a given folder, you can't have multiple autorun executables to install separate applications. However, using Mobile Packager you can bundle your installation packages, cab files files and other items into one executable and this executable will be your autorun.exe.

Tags:

Testing Windows Mobile applications without a physical device.

by Mobile Packager Team 19. February 2009 15:57

To test your Windows Mobile applications and installations that you create with Mobile Packager, you don't need to use a physical device. Instead, you can use the standalone device emulator which is provided as a free download from Microsoft. You also don't need to have Microsoft Visual Studio to use the standalone device emulator. The emulator is also available localized in several languages. The current version of the Microsoft Device Emulator 3.0 was released in January of this year and can be downloaded here.

In addition to the standalone emulator itself, you will need to install emulator device images that will be used by the emulator. Emulator device images for the different localizations can be downloaded from here. To have a complete device emulation you will also need to install ActiveSync for Windows XP or Windows Mobile Device Center for a Windows Vista.

After you complete installing the above components, you can launch the device emulator manager "dvcemumanager.exe" that is usually located under "C:\Program Files\Microsoft Device Emulator\1.0\".

 

After you launch the device emulator manager you, you can connect to a particular device emulator image by selecting "right-click -> Connect" menu option. This will open the device emulator.

 

After connecting to the emulator device, you can cradle this device (as you would do with your physical device). To cradle the emulator device, select the "Cradle" menu option that is displayed when you right click on a connected device emulator item listed in the device emulator manager.

 

After cradling, you can copy files to the device emulator either browsing to he mobile device using windows explorer as you would navigate to any other folder. You can also specify a shared folder for the device emulator by going to the "File -> Configure" menu option on the device emulator. 

 

On the device emulator configuration window, you can specify a shared folder. This will allow you to browse to the shared folder from the device emulator without the need to copy a file to the device emulator. For example, when using Mobile Packager, you can make this shared folder to point to the "Mobile" output folder of your current project. This way you can simply navigate to the "Storage Card" folder from within the device emulator. You don't even need to cradle if you access a shared folder using this method.

 

Voila !! You can now test your applications or launch your setup files without the need for a physical device.

 

 It is almost as good as a real device. Actually, it is much better than a physical device if you are simply testing your Mobile Packager setup files.

Welcome to the mobile packager blog

by Mobile Packager Team 5. October 2008 07:21

Welcome to the Mobile Packager blog. We will update this blog and write articles about mobile application development, news updates and changes to our product Mobile Packager.

We hope that you enjoy this site and that some of our articles are helpful to you. Stay tuned for some insights into the development of Mobile Packager.

All Right Reserved © 2007-2013 Mobile Packager.