QuickCab

by Tim Kremer (tim@foolproof.net)

 

 

Description

QuickCab is a standalone utility for making CAB files that are compatible with Microsoft Windows Mobile Pro (TouchScreen).  It might be compatible with other versions of Windows Mobile, but has not been tested with them. 

 

What is a CAB file?

A CAB file is a compressed file that may contain Files and Registry Settings that will be installed onto a Smartphone.

 

Why is this important?

If you write software, or make customizations to your Smartphone, chances are that you need a convenient way to install them to your device.  By putting all of the files and settings into a CAB file, it can be distributed and installed much more easily and in an automated fashion.

 

NOTE:  Requires the Microsoft .NET Framework 3.5 which can be obtained here.

 

Background (boring…you can skip this part)

The author of this program is a regular-guy with no illusions that he is anything more than an amateur developer.  He likes to hack his Windows Smartphone and because of that he tended to rebuild it a lot.  In an effort to save time, he began to create Windows Cab files that contained his favorite customizations and the files he always wanted on his phone.  The problem is, creating a Cab file is a tedious multi-step process and requires hand-editing .INI and .XML files.  So, the author decided to write a utility to quickly create Cab files that suited his needs.  If anyone else can benefit from this work, so be it.  With the exception of the compression routines, QuickCab was written in C# and initially took about 30 hours to write.

 

Known Issues

·         See the included “Known Issues.txt” document

 

Version History

 

2.0

Major Rewrite of the GUI and internal storage routines

Fixed many button and selection errors

Added Shortcut support

Added support for Vista UAC

Added support for compressed cabs

Added ability to prevent uninstall

Removed support for Setup.dll

 

1.0

Initial Public Release

 

0.5

 

 

Initial Beta Release.  Buggy as all hell.  Distributed to a handful of similar nut-jobs who, like the author, are willing to run not-ready-for-prime-time software in order to work out programming errors.

 

License Agreement (important…please don’t skip this)

The author of this software is an individual, not a company, and does not have the resources to hire a lawyer just to write an in-depth License Agreement that normal people cannot understand.  In short, you may use it; you may share it.  Just don’t make money from my work.  Here are the terms of this software:

·         The author, Timothy J. Kremer, retains all rights to this software.  He is making it available for anyone to use, but he is not giving it away.

·         You are granted a license, at no charge, to use this software for personal, educational or government use.  Commercial use requires special permission from the author.

·         You may make copies of this software and share it in its unmodified form with anyone as long as the original documentation and Copyright notice are included.

·         This license is not transferable and may be revoked by the author at any time and for any reason.

·         You may NOT charge a fee, monetary or otherwise, to share or distribute this software.

·         You may NOT modify, disassemble, or reverse-engineer this software in any way.

·         You may NOT derive any other software, modules, scripts, works, or applications from this software, documentation, or portions of either.

·         This software was written for the author’s (Timothy J. Kremer) personal use.  You are using this software at your own risk and the author will not be held liable for any damages – direct or indirect – for data loss, loss of productivity, or any other damage that may occur as a result of using this software.

·         If you do not agree to all of these terms, you must not use this software and must remove all copies from all machines under your control.

·         Exceptions or modifications to this License Agreement must be approved by the author (Timothy J. Kremer, tim@foolproof.net) in writing.