Sunday, 12 September 2004

Pulling this out of the cave that is my blog comments:

I've completed a real-use test of the Nikon D70 with the Seagate ST1 hard drive. I'm not a hardware tester, but I decided I'd just load it up and push it a bit and see what happened.

I shot 1365 pictures at full jpeg resolution, continuous fire mode for long sessions. This required the hard drive to run continuously for several minutes at a time. The camera showed 451 images left to go (free space remaining) when I reached the point where all 1365 images had been recorded.

At that point my camera's battery died - Now, before anyone goes off on a rant, it's important to note that it was not fully charged to start with (I had charged the camera battery a month before and used it some since then), and that I intentionally shot groups of of 100-300 continuous-fire images at a time in this test, with auto-focus on and the reflex mirror down in normal operating mode. Also, the LCD display on the back of the camera was not disabled, as I used it to view some of the images between the continuous-fire sessions (like watching a slow frame rate movie - that night be a fun project some other time, heheh). In other words, I was running it in full-battery-killer mode, on a partially charged battery.

With the Seagate drive in the Nikon D70 (in continuous-shot mode, recording in fine resolution JPEG mode at the largest image size setting: 3008x2000 pixels), the camera does its standard thing, buffering the first 9 shots with rapid fire of about 2 frames per second, then slowing down its frame rate to allow the media to store the data (about a frame per second). Time required to spin up the drive and display an image on the camera's screen when I push PLAY on the camera from a dead stop is right at two seconds.

Disk space used on the ST1 drive by the 1365 images: 3.15 GB (3,388,802,794 bytes)

Time required to copy all 3.15GB of files to my laptop hard drive using a Sandisk USB2 CF I/II card reader (as measured using the nifty stopwatch feature on the Rio Carbon, of course): 10 minutes, 1 second.

This Seagate drive is nice, and my surviving Rio Carbon is awesome, too. It seems plenty fast enough for me. Unfortunately I don't have a Sandisk 2 Ultra or similar to compare it to, but I have seen others comment its close to that speed. Anyone have more specific experience there?

Off-topic Rio Carbon thought of the day: If you're not an Audible.com subscriber, your should become one and listen to "The Daily Show with Jon Stewart Presents America (The Audiobook): A Citizen's Guide to Democracy Inaction." Freakin' hilarious. I listened to the whole thing on my Carbon while commuting. I have also downloaded "Hitchiker's Guide to the Galaxy Unabridged" (as read by Adams himself) and "Getting Things Done," which is also great stuff.

Related Links:



Add/Read: Comments [13]
Photography | Tech
Sunday, 12 September 2004 22:38:39 (Pacific Standard Time, UTC-08:00)
#  Trackback

Want Gmail? Go here and follow the instructions.

Sorry, all taken - will update when I have more. :-)



Add/Read: Comments [5]
Random Stuff
Sunday, 12 September 2004 22:24:38 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Saturday, 11 September 2004

Wow, the hits just went through the /. roof. My article with pics on breaking down the Rio Carbon got posted on slashdot.org [link]. I have changed the pics in the article to make them smaller (clicking the smaller version now loads the larger image), as the bandwidth was challenging the NIC in the server. Good thing I didn't do what someone thought I did. I also made some changes to my fat-fingered apostrophes to settle down the grammar-police crowd. :)

My blogging software, dasBlog (a .net-based app running on Windows 2003 by the way, hehehe), has held up quite well under the /. traffic load. I'll put together stats and post them for other dasBlog users, once this all dies down. My service provider, Stormhosts, held up very well, too.

Number of unique *.slashdot.org web sessions on Saturday: 20,358

The graphs of bandwidth used are pretty interesting - note the trafffic before the spike is for all web sites on that shared web server - after that it's pretty much all mine:

Here are some numbers showing unique user sessions per hour - meaning it's how many actual visitors hit the site per hour. Saturday is usually pretty darn slow day, but not this time, and the number/size of of images on the page being loaded was a real challenge:

6am  57
7am  65
8am  54
9am  68
10am 74
11am 102
12pm 3321
1pm  5069
2pm  3360
3pm  2661
4pm  2196
5pm  1721
6pm  1477
7pm  1279
8pm  1239
9pm  1157
10pm 1063
11pm 702
Some more numbers...
                    11SEP04    Daily Avg
Sessions 26,030 1,792
Pageviews 52,522 4,280

Hits 639,524 8,754 
Bytes Transferred 13.49 GB 175.35 MB

Note that RSS was about four to five times my Saturday normal at 4,426 sessions (about twice a normal weekday count), but at a very light bandwidth requirement. Score one more for RSS. Quick, someone write a manifesto! ;-)

So anyhow, I would like to formally apologize to my service provider, Stormhosts. Well, not really apologize per se - more like shoot them a big HAHAHA! ;-) Good test for your systems I guess eh? Their systems held up very nicely, and when I emailed them just in case alert as soon as I knew what was about to happen**, they got right on IM with me. We watched the performance counters together. Great service from those guys, as always. Recommended.

** Mandatory educational content: Many sites over time have fallen victim to the Slashdot Effect, a term used to describe the very common and overwhelming onslaught of sudden traffic to a web site and the resulting failure of said server. It's typical for web servers to simply choke under the load. At some point, I don't remember when, slashdot started releasing new items to their subscriber base for a short while before they release it to their general public web site. This informal early warning system allows just enough time for their notably large number of subscribers to hammer your server, with just enough time left over for you to panic and send an email to your personal web site's unsuspecting service provider that reads something like “HOLY CRAP LOOK OUT!” The slashdot subscriber visits that precede the general onslaught generally include such friendly comments left on a blog as, “What a really cool/lame story. Oh, and by the way - you're about to get slashdotted.”



Add/Read: Comments [8]
Blogging | Random Stuff
Saturday, 11 September 2004 09:28:38 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Friday, 10 September 2004

Interestingly, in an article by the Associated Press posted on the Security Pipeline web site, Microsoft is quoted as saying that their new biometric authentication products, which I posted about the other day, should not be used for securing important/sensitive data or networks:

"Curiously, Microsoft warns that the Fingerprint Reader shouldn't be trusted to secure access to corporate networks or to protect sensitive data, such as financial information.

"Basically, the company says it's about convenience, not security. That seems to rule out password-protected Web sites for credit cards, utilities, banking and others for which I might want to be spared having to remember and type a litany of passcodes."

Hmmm, well I guess I probably won't be ordering any of these to evaluate for work, then. :-) Maybe at home though. From the review, it appears they work well and that they passed the Silly Putty test, which is good. Despite Microsoft's advice regarding use of the equipment, I'll look forward to getting my hands on one of the devices to try it out for non-critical purposes.



Add/Read: Comments [3]
IT Security | Tech
Friday, 10 September 2004 20:31:15 (Pacific Standard Time, UTC-08:00)
#  Trackback

The other day I wrote about a post I saw in KC Lemson's blog that describes how to make sure Office files open in their respective program windows, rather than in Internet Explorer, when you click on a link to one on a web page.

A friend commented that it would be cool if you could get Adobe Acrobat Reader to behave that way too - that is, open PDF files the native program, not in an IE window.

Well, it turns out you can make it behave that way. Now, probably 99.9% of the people who use Acrobat Reader don't ever check out the settings that are available in the program, and it's no wonder: The dialog where you make those changes is not exactly where you'd expect to find it. You'd think the Tools menu would be the place to find the options, but it's not there... Yay Adobe. Instead, it's hidden in the bottom of the Edit menu. Click on Edit>Preferences, then click on the Internet section header:

Uncleck the Display PDF in browser option and save. That's it! When you click on a PDF file from there on out, it will download and open in Adobe Acrobat or Reader.



Add/Read: Comments [2]
Random Stuff | Tech
Friday, 10 September 2004 20:06:35 (Pacific Standard Time, UTC-08:00)
#  Trackback

Note: Due to the slashdot effect on this site, I posted smaller images on this page. If you need more detail, you can click on each one to view the larger size. I've also deleted about 80% of the referral link list below for performance reasons. There were more than 5,200 unique referall links listed on this one page. I've cut that down to about 600.

People who have tried to use a solid-state Compact Flash card in place of the hard drive in the Carbon have reported it is not working for them. I have not tried this myself. If anyone has been successful in getting a standard CF card to work when replaced in the Carbon, please email me and let me know: gregATgreghughesDOTnet

In addition, I have posted a followup with some real-world test results, using the drive in my Nikon D70 digital camera.

Want to use it in a PocketPC maybe? Check this out and see if it's for you.

As I described yesterday, I bought a very nice MP3 player, the new Rio Carbon 5GB model. It's awesome, and I already like it a lot. My original intent, though, was not to buy an MP3 player to listen to music, but instead to rip apart for its compact-flash size 5GB hard drive, for use in my Nikon D70 digital camera. I got the idea from a post on a message board. But once I saw the Carbon, I decided it was time to own an MP3 player, so I got two.

Rather than eating lunch today, I decided I would share my story of destruction. In part two of our saga, I tear into the second of the two Carbons I bought, pictures included.

Update: I had to reduce the image sizes due to a sudden and unexpected spike in traffic. I will put links on eack of the small images so you can load the larger version of each.

Note: If you decide to spend $249 on one of these things and tear it apart yourself, you do so at your own risk. Its value to Rio and the store where you bought it will instantly become $0, and your warranty will be a thing of the past. At your own risk, your mileage may vary, do not pass go, please tip your waitress. Oh, and whatever you do, don't come yelling at me. It's your own damn fault. In fact, you will probably end up with $249 worth of useless junk. You have been warned.

Okay, so first of all let me tell you right up front that I broke the thing to the point where I will have to use a little glue to put it back together. The Carbon has a metal back plate, and a plastic front plate, with a rubber surround. What I did not realize is that the front plate is in sections, as well. Not realizing this, I didn't remove the front plastic facing (the silver plastic with the LCD window and the Rio logo) from the body of the MP3 player. It is held in place with some adhesive. Just be careful while you remove it and it will come right off. Once off, it may be that there is a better way to get this thing apart than the method I used. If I will have to use some glue inside where it used to have screws holding things together, because I broke a few plastic threads on the plastic case where the screws were attached as I pried it apart.

While it looks from the outside like the rubber portion is a section all on it's own, it in fact is not. The rubber part is just glued to the plastic front plate, which is under the silver plastic front cover just mentioned.

How I got it apart (your mileage may vary, be careful): I started by working a small screwdriver around the case, prying very gently between the metal back plate and the rubberized section. There are a number of metal tabs that you will see inside as you go. Those hold the drive in place. Be careful and don't go too deep or apply too much pressure inside with your screwdriver, you will break things if you do, or you might crack the case. If you don't care about reusing the Carbon, you can afford to be a little more indiscriminate, but things are packed together pretty tight in the small case, so caution and taking one's time is warranted.

Once I worked all the way around with the small screwdrivers (I used 2, it helped keep things working along), I peeked inside to become a little bit familiar (there's a lot you just cannot see, though). Then I used a screwdriver inserted from the bottom of the case to get good leverage as pictured below, and worked the case loose.

In the end, I used my fingers, after loosening with the screwdriver, to take the case apart. Again, note that I broke the plastic threaded screw posts in the process. The end result was a front plate, a loose power button (just insert it back in place later), the top chrome-like trim plate (that has the holes in it for USB, earphones, etc), and the back plate with all the electronics attached. The front panel navigation button is loose when you disassemble it - it's held in place by the front plate.

There are two screws that you will need to remove from the face of the circuit board (the side with the LCD screen), and then you can start to swing the circuit board away from the hard drive. Below is the view from the side, pulling the circuit board up and away from the battery (lower left) and hard drive (in the lower center of the picture under the circuit board). The white block on top is the LCD.

Using a small flat-head screwdriver, I gently released the frame holding the hard drive from the back plate by prying the tab clips away slightly.

Taken apart, with the electronics removed from the metal back plate:

The black frame holding the hard drive simply pulls off. The 20-hour battery is shown folded away in the foreground of the below image, and the ribbon cable attaching to the Seagate 5GB drive is visible and accessible:

I used by thumbnail to gently disconnect the drive from the ribbon cable, releasing each side of the connection a little at a time. Be careful not to bend the pins if you intend to reuse the Carbon.

With the hard drive removed:

You simply peel the copper foil away from the drive, along with the foam padding:

In the end, parts parts parts:

The whole point of the exercise was to get a 5GB hard drive that I could insert directly into my Nikon D70 camera. I tentatively took the drive, crammed it in the CF slot of the camera, powered it up and formatted. After a nervous little period of flashing screen on the camera (FOR-FOR flashing over and over), the screen changed, as pictured below. That's showing the number of pictures I can take now using the hard drive. I was a little confused when it read 1.4 on the display, but then I noticed the “K” above the number. That's 1,400 images (estimated by the camera) at 6 megapixels. Wow!!! Cool!!! After taking a few pictures, I confirmed it works. Nice!!

Next thing will be to put a 256MB or 512 MB CF card back in there and load the Rio software on it, put it all back together, and see what happens.

Feel free to add your own experiences in the comments section, by clicking below. Please keep it clean and reasonably polite. Thanks. :-)



Add/Read: Comments [105]
Tech
Friday, 10 September 2004 13:08:19 (Pacific Standard Time, UTC-08:00)
#  Trackback