LinuxWorld

Using U3 to create portable programs

Last week we began a discussion of U3, an emerging standard for controlling and managing applications stored on a USB, flash or thumb drive.

This is a very cool idea that creates portable programs - in the sense that they can be carried on physical media from one machine to another and be run with or without being installed. When they exit, they leave no data behind.

As cool as U3 is, a serious issue is that it is very narrowly focused, applying only to Windows 2000, XP and 2003. That leaves all those Windows 95, 98 and ME systems out in the cold (and rightly so) along with Macs and Linux.

Programs engineered to be U3-compatible are different from regular Windows programs because U3 applications are not hard-wired to the directory structure or any operating system components on the host computer and are independent of the Windows Registry.

There are three types of U3 applications: U3 LaunchPad (U3LP), U3 LaunchPad+ (U3LP+) and U3 Aware (U3A).

U3LP Applications are Windows applications that are installed on the U3 device along with their configuration data, user preferences and associated files.

U3LP+ applications are like U3LP applications but are bundled with and use the U3 Device API (DAPI) dynamic link library (DLL). The U3 DAPI DLL, which uses C-based function calls, lets applications communicate directly with U3 thumb drive hardware. For example, applications that use cookies stored on the U3 drive or that check the U3 thumb drive's unique ID must be compliant with U3LP+.

U3A applications are programs installed on the host PC that use the U3 DAPI DLL to detect and communicate with U3 thumb drives inserted into the host. These are standard Windows applications with specific support for U3 devices. The U3 Software Developers documentation gives the following examples of U3A applications:

A Windows Login service that uses U3 smart devices as tokens.

A Windows backup tool that supports U3 devices, enabling data to be securely backed up to a password protected private area on the device.

React: Give us your thoughts on the issues here.
Use this form to start a public discussion with other Linux World users on this article.
Log In | Register for an account (Why you should)

Note: Register to have your user name appear; otherwise your comment will show up as "Anonymous."

*Anonymous comments will only appear once they are approved by the moderator.

Newsletter sign-up

Sign up for one of Network World's newsletters compliments of Linux World

Linux & Open Source News Alert
Web Applications Alert
Video & Podcast Alert
Security: Threat  Alert
Virtualization Alert

Email Address: