Initial Testing of
the IBM MicroDrive 340
By Chuck Davis, Copyright 1999
Version 1.01 Revised Tuesday, June 29, 1999
[an error occurred while processing this directive]Introduction
Today, in a ridiculously oversized shipping box, I received a 340Mb MicroDrive from IBM. After sifting through what seemed to be endless packaging material, and boxes within boxes, I finally found what IBM describes as the "worldís smallest and lightest hard drive ever produced".
Iíve had a nonfunctional engineering mock-up of the drive for some time, so I knew what to expect in terms of size, but words cannot convey what itís like to behold a functional unit.
Sure, weíre all aware of the advances in silicon, so when Intel releases a new chip, we might get excited about the speed, but I do we really appreciate the engineering that goes into such innovation? Because itís mechanical, like a masterfully built Swiss timepiece; IBMís tiny MicroDrive forces you to appreciate the in your face technology behind itís design.
But technology aside, there are practical considerations, like speed, durability, power consumption, and temperature. How fast is it, especially when compared to a CF memory card? Is it noisy?
Because it is a hard drive, I found myself treating it like itís oversized siblings, delicately handling it like a Faberge egg, until I inadvertently knocked it of my desk where it fell 2 Ĺ feet to the carpeted floor, apparently no worse for the wear.
Though IBM states that the drive is officially "shipping" today, they are in fact only going to key accounts and integrators. Expect general availability in retail within the next 30-45 days.
The unit supplied to me by IBM is an "engineering unit", so there are some differences between this unit and what you will be able to buy in the retail channel. Most notably, the retail drive uses a different revision of the firmware, so it is supposed to be even faster than the drive I have. Aside from that, the changes are cosmetic, with the retail drive having a ridge at the top so you can easily remove it from the CF+ slot, and the retail drive will have a label identifying the capacity of the drive.
After just a few hours with the MicroDrive, it becomes clear that it not only represents great technology, but that it is truly a platform enabler. I can only speculate as to how the capacities of these tiny drives will increase in the future, but what I can tell you is that now that they are here; things will never be the same. The promise of anywhere, anytime, computing is now truly viable, and large scale, micro-sized storage allows us to fully exploit it.
Couple the frenetic pace of developments in this space in just the last few months, color screens, multimedia capability, micro sized storage, both mechanical and solid state; and the recent announcements concerning wireless capability and all I can say is hang on for the ride!
The drive looked as though it had just come out of the micro miniaturization oven, with no labeling, save a barcode sticker to offset itís shiny aluminum casing. The drive feels solid, with four screws on top, and three on the bottom joining the two halves of the drive together. The measurements and weight matched IBMís published specifications.
One cool thing is on the back of the drive, the back assembly is solid aluminum, bolted down with tiny screws and is covered with what seems to be a very durable plasticine. Well, there is an arc shaped slot cut out that allows you to see a portion of the drive platter and the drive head arm. When the unit is in a Casio E-10X, with the CF+ hinge off, you can see the arm moving and drive spin during reads and writes! Hopefully, that will also be in the retail version.
I had to strain to hear it. The drive is nearly silent.
Susceptibility to Vibration
Because the drive is mechanical, I was curious if mild to moderate vibration would cause a perceptible decline in performance while playing continuous loop audio from the drive. While not scientific, I rattled the Casio pretty well, and the drive never skipped a beat.
In the both the E-100 and the E-105, the drive was recognized by Windows CE 2.11, StarTap reported the drive as having a total capacity of 357,941,248 bytes, completely clean, the drive yielded 341Mb of usable space for storage. I guess lBM likes round numbers when they publish capacity, but you do get an extra meg.
Since there is no effective way to benchmark storage devices on CE, I used my IBM ThinkPad and Norton SysInfo to compare throughput in terms of Mb/Sec for a Lexar 64Mb 4X CF card with adapter card against the IBM MicroDrive with adapter card. Also, I included the benchmarks for my laptop drive, itís a 14.1GB drive with an average seek time rated at 12ms for comparison to what a "normal" drive yields.
Note: Iím not sure if the retail version of the MicroDrive will ship with a CF Type II adapter, but I quickly learned that all of my adapter cards were CF only and would not accommodate CF Type II. Faced with having to transfer large files using ActiveSync at 115K, I quickly located my Dremel tool and made one of my CF adapters into a "convertible" to accommodate the MicroDrive. So those of you that have adapters and intend to get a MicroDrive or any other storage medium that is in the CF Type II form factor, you might want to ensure your adapter or reader has the physical clearance for a CF Type II card.
Norton Sysinfo Performance Comparison
Heat Buildup and Dissipation
Given that the operating temp of the E-10X is 0C to 40C ( 32F Ė 104F) and we know the E-10Xís run a little warm anyway, heat was a concern of mine. Here are the measurements after 1 hour continuous use playing looping audio:
*The IBM MicroDrive chassis is constructed of aluminum, where the Lexar CF casing is PVC.
Battery LifeHereís how long the batteries lasted before getting a low power warning, then finally shutting the unit down, or completely draining the battery.
Originally, I conducted this test playing looping audio, but the Casio Mobile Audio Player would occasionally time out yielding inaccurate results. So I created two tests. The first test continuously plays a .CMF movie clip using the Casio Mobile Video Player. Itís a high load test because the screen remains active, while playing both video and audio. It also serves as a good indication of what you could expect in terms of "real world" results if you intend to view a large video file, or a series of video files over a period of time.
The second test, thanks to input from Dr. Will Hou, is a combination of reading from and writing to the media. Using NSBasic I wrote a program that reads, then writes a series of files to the storage media while measuring the time to do so. This second test takes into consideration the power demands of write operations in addition to read operations measured in the previous test.
Additionally, the varying file sizes allows for the measurement of differences between activities that utilize the 128K onboard cache of the MicroDrive, and those that exceed it.
The following controls were enforced: Only the E-105 was used for these tests. The battery was fully charged prior to the start of the tests. The screen brightness was set to the lowest level for battery powered operation. The audio was set to the lowest volume short of muting the speaker. The operating temperature of both the battery and the E-105 was 22.5C / 72.6F at the start of the test.Continuous Playback of a 1.2Mb .CMF Movie File with Audio (Read Only)
* The MicroDrive has a power threshold that is higher than the Automatic Power Down threshold within the Casio E-10X. Before the Casio automatically turns off due to insufficient battery power, the MicroDrive shuts itself off. Any resources contained on the media instantly become unavailable. Continuous Read/Write Operations**
**Results are being tabulated and will be published in version 1.02 of the testing.
Top View - Lexar CF, MicroDrive
Connector Side View - MicroDrive, Lexar CF
ConclusionI would like to than the following people their help in the publication of these results:
Future revisions of this document will incorporate additional tests.
You can the author via email at: Chuck Davis
[an error occurred while processing this directive]