We looked at Kingston's DataTraveler Reader last year and were reasonably impressed with it. While the internal memory was a little sluggish and the build quality left something to be desired, those qualms where overruled by the great price and the fact that viewed simply as a portable card reader it still made for a brilliant product - adding 2GB of flash memory to that was just the icing on the cake.
One year on and we have what might easily be referred to as the DataTraveller Reader's little brother, the DataTraveler Micro Reader. The name should give the game away that this particular device is exactly the same principle but applied to MicroSD cards, MicroSDHC and M2 cards. A 4GB MicroSDHC card costs less than £10 currently and such cards are supported by many mobile phones and MP3 players, making a reader able to accept the format fairly attractive.
Moving to MicroSD also alleviates one of the complaints we had with the SD version of the DataTraveler, namely the large size. Moving to a smaller memory card means that the new model is no larger than a normal memory stick. In terms of build quality, however, the same problems are present.
As with its predecessor the Micro Reader utilises a sliding plastic tab mechanism. This works well enough, but it feels cheap to use and doesn't give the impression that it would stand up to much abuse - not that we'd ever recommend subjecting it to any in the first place.
Other than those small gripes, though, the DataTraveler Micro Reader seems well built and should stand up to the rigors of day-to-day use. As with the SD-orientated version the Micro Reader can be used with a lanyard, which goes through a hole in the lid and then attaches to the memory stick. It isn't fancy, but it works.
As one would expect when plugging the device into a PC (or indeed Mac) it will take a few seconds to show up as two generic mass storage devices. Differentiating the internal and card's storage, the device's memory shows up as "KINGSTON" by default and this makes it easy to see which form of storage you're transferring to, while also avoiding an potential confusion between the two.