Skip to main content

Drive Stamper

Drive Stamper is an application to facilitate the branding (or 'stamping') of USB drives (and any other removable media) by copying a set of files quickly and easy onto each. It's ideal for a small promotion or a small business that needs to quickly distribute the same files onto a lot of media units and wishes to save costs by doing it themselves.

The application, once loaded, will monitor your system for new drives and (if they have not already been stamped) will copy the files you specify onto the drive.

  • Download the latest installer for Drive Stamper from GitHub: Setup.exe
  • The source code for Drive Stamper is available from the Git repository.

Recommended use scenario

A small business needs to stamp their product's documentation onto a large number of USB drives but does not wish to pay a 3rd party to do this. They buy a set of USB drives, install Drive Stamper, set it up to stamp their documentation, and plug in a USB hub. They switch Drive Stamper into Automatic mode, and plug in as many drives as they can. As soon as all the drives are done, they pull them out and repeat the process. Drive Stamper automates the system's actions - removing the need to click and drag while the drives are in - considerably speeding up the process.

Basic use

On load, you are presented with the Drives view - a window showing all drives the system is currently monitoring.

Note that unless you alter the current project to allow it, Drive Stamper will ignore drives A:\, B:\, C:\ and D:\ as these are usually letters that signify where the floppy drives used to be (A and B), where the main hard drive is (C), and where the main CD-drive is (D) - drives that make sense to ignore.

In the screenshot on the right, drive E:\ has been detected and is noted to already be stamped.

Note that when there is no project loaded, or when there are no files in the current project, all drives will appear to be stamped as there is nothing to check for!

As you can see, there are 3 modes for Drive Stamper, selectable from the 3 radio button at the top of the view: Automatic, Semi-Automatic, and Manual.

  • Automatic: Drive Stamper will automatically try to stamp any new unstamped drive it comes across (not included in the ignore list).
  • Semi-Automatic: Whenever Drive Stamper detects a new drive that qualifies for stamping, it will ask you if you want to stamp it.
  • Manual: Drive Stamper will quietly detect new drives and wait for you to press the Stamp button on the Drives screen to stamp any new drives.

If at any time you think Drive Stamper has failed to notice a drive add or remove, you can refresh the list of drives using the Refresh button at the bottom of the view.

To specify some files for Drive Stamper to use, press the Edit... button to open the Project view.

The main component of the project view is a list of files to be stamped (copied) onto any new drives. In this screenshot it is empty (as you would expect to find it). To add files to it, click Add Files... To remove a file from it, click the file and select Remove.

If the Ignore missing files checkbox is checked, Drive Stamper will proceed to stamp a drive even if it cannot find all the files specified for the project - skipping over those it cannot find.

If the Overwrite files checkbox is checked, Drive Stamper will deliberately copy the specified files onto the drive, and overwrite any files with the same names that are already there.

In the bottom right corner of the window is the Ignore Drives box - containing a list of drive letters to ignore. By default, a, b, c, and d are selected - as these drives are commonly where the floppy drives were mapped (a and b), where the main hard drive is mapper (c) and where the main CD drive is mapped (d). You can alter these defaults and enable or disable the ignore function for any drive letters from a-z by checking or unchecking their boxes.

When done you can save the project from the Project menu.

On returning to the drives screen, you will note that the project name has now been updated, and any drives that may have seemed stamped will be shown as Ready instead.

Drive Stamper will continue to run after you close the Drives view - and it has an icon in the system tray (it uses the blue round information 'i' icon) from which you can open the Drives and Project views using the right-click menu.

Popular posts from this blog

Google Play Services with Android Studio

Edit: This post is extremely deprecated -- with prejudice! It was written in an era when Google Play Services were not well integrated with Android Studio project work, and Android Studio itself was in its infancy.

This is a very quick guide to incorporating Google Play Services with your new Android Studio project.

Edit: [16:20 22/05/2013] I'll investigate the runtime NoClassDefFound error reported in the comments, and follow up later!

Edit: [23:17 27/05/2013] I'm coming to the conclusion that - as many have already pointed out - you really do need to include the entire library project in your solution. I'll post an update once I've fully tested this. 

In the meantime, please consider the advice below to be deprecated!

The first thing to say is: I fully expect the advice and guidance about how to work in Android Studio to change over time. Android Studio is in early access preview right now, and I'll bet my bottom dollar (is that a thing?) that over time it becomes m…

What's the best way to handle the Android camera?

This article is adapted from a response I gave on Reddit to the question "What's the best way to handle the camera?" in r/androiddev...

The Camera and Camera2 APIs are far from painless to use. If you've ever written an app that uses the camera (embedded in an activity or not), you've almost certainly come up against orientation issues, stretched previews, or weird quirks that change from manufacturer to manufacturer...

There are three good libraries out there that can save you from many common pitfalls:
Google's (unofficial) CameraView library.Mark Murphy's CWAC-Cam2 library.Dylan McKintyre's CameraKit for Android library. Each has different strengths. If you don't have time to read this whole article, here's a quick rule of thumb:
If you want to capture photos in a full-screen preview, but you don't want to have to rely on the native camera app, then use CWAC-Cam2.If you want to embed a preview into your Activity, use CameraKit. It's f…

Manually Testing Web Services in Visual Studio

The first time you debug a web service after creating it, Visual Studio will launch the WCF Test Client - a very useful piece of kit - and preload it with the details of your service.

In this article, we'll look first at testing your WCF service, and then an all-too-familiar issue that might crop up and spoil your fun!

Using the WCF Test Client

The WCF Test Client looks a bit like SoapUI, and is pretty similar in purpose: It allows you to connect to a service, enter some parameters and submit them to any given service method to see what you get.

After the first time you run the WCF Client, Visual Studio will forget all about launching it again until you make significant changes to it - which means when you subsequently hit f5 or choose Debug, it won't run again. It's worth knowing how to bring it up...

You can find it again by launching the Visual Studio Command Prompt, and launching wcftestclient.exe from there.

Once connected, making use of it is as simple as filling in …