I found I was running out of space with all of my DVDs and such, even after adding an eSATA port multiplier and a few 1TB drives. I only have one drive slot left, and while at first I thought I’d fill it, I realized that doesn’t leave me much wiggle room in the event of a real emergency where I need to do some fancy drive swapping. As such, I decided to replace one of the 500GB drives with a 2TB drive. The 500GB drive I took out will stand ready as a replacement for the system drive should catastrophe strike.

I started the upgrade with about 750GB free because I wanted to be sure there was enough free space to remove the 500GB drive without losing any data.

Post upgrade, I have a total of 7.73TB in storage with 2.08TB free.

[

Given that I’ve figured DVD images run about 6.7GB each, that gives me room for another 300 DVDs before I run out of space. Of course, when I hit a bit over 1TB free, I’ll have to consider what my upgrade options are in case I need to remove a 1TB drive to replace it with something larger.

UPDATE 1/9/2010: Turns out I got a bad drive. The first night it was in I got a bunch of errors from WNAS.SYS telling me something about “VRM temperature too high.” Doesn’t make a ton of sense, but that’s what happened. Anyway, that first night it totally disappeared from the storage pool, as if by magic. The second night I decided to re-seat it (thinking “bad connection”) and run chkdsk on all drives. Got the WNAS errors again and a bunch of disk errors, so… back it goes. Most of my drives are Western Digital and the drive I tried out was a Samsung. Being a little technology-superstitious, I’ll probably get a WD drive as a replacement.

UPDATE 1/15/2010: I put a Western Digital Caviar Green 2TB drive in and I’m back up to 7.73TB. So far I’m not seeing any of the weird WNAS.SYS errors I was seeing before which leads me to believe I had a bad drive. Every other drive in the system, save the system drive, is a WD Caviar Green drive, and I’ve had good luck with them, so I’m hoping my luck will hold.

UPDATE 1/16/2010: I see the WNAS.SYS temperature warning errors again, but it appears that so many in succession is generally understood to be some sort of bug in the driver rather than a health issue. The system didn’t restart itself or anything, so I guess I’ll just watch it. One thing I found while I was looking for the solution to the WNAS.SYS issue is this article over on the HP site that says how Samsung SpinPoint drives will suddenly “disappear” from the system and it’s a compatibility issue. As it turns out, that’s the type of drive I ordered that failed - a Samsung SpinPoint 2TB. Looks like the WNAS.SYS error and the drive failure were unrelated. I’m still watching how this WD drive behaves. I can ignore false errors in the logs (though it’s fishy that they show up when I add a 2TB drive - maybe I’m crossing some size boundary that causes the bug to show up?), but if a drive “disappears” on me, that’s trouble. I’ll probably wait a week or so before putting any additional info on the server that might make it so I can’t remove the drive.

UPDATE 6/16/2010: Be careful of using the WD Green drives. Only some model numbers appear to be good.

In dealing with today’s technology, I feel like I’m inundated with what I usually refer to as “fiddly shit”: constant, tiny maintenance tasks to make sure things are still working together correctly. No one task is a big deal; most take under five minutes to fix. Some are larger or more chronic issues that require research and troubleshooting over the course of weeks. Let me throw out some examples of recent issues:

Wireless networking at home. I got Verizon FiOS and the router they provide only does wireless-G networking. I wanted a faster network to accommodate my gaming and my media, so I added a wireless-N access point. This added a ton of fiddly shit to my list.

• Access point setup and maintenance. I bought a DAP-1522 for its supposedly easy setup. Setting the thing up was not nearly as straightforward as the instructions would have you think. Even now, once I have it set up, I find sometimes that it won’t connect things at wireless-N speeds, dropping them back to wireless-G. Rebooting the access point (pulling the plug) sometimes fixes this, but also requires me to reboot anything that was previously connected to the network because for some reason things won’t just reconnect.
• Conversion to WPA security. There is also an undocumented “feature” on the DAP-1522 that makes it such that if you use WEP security the access point will not let you have wireless-N connectivity. Everything only ever connects at wireless-G. Not documented anywhere, mind you, so some time was spent on the phone to support for this. I was able to connect at N speeds after switching to WPA security… but I have devices (like a Nintendo DS) that only support WEP, so now I have to either support two different wireless networks (WPA with wireless-N via the access point and WEP with wireless-G via the FiOS router) or just not connect the old devices. Right now: no old devices.
• USB wireless adapters and Windows 7. I upgraded everything to Windows 7 at home and while I love the OS, the drivers don’t seem to be quite up to snuff for any of the USB wireless-N adapters I have. They work… mostly. I found that in some cases you have to install not only the driver but also the stupid “configuration utility” that the manufacturer provides and then things work, even if you don’t use that utility or even ever open it. Also, if the computer goes to sleep and wakes up, it disconnects and reconnects to the network over the course of about the first minute after you log in. It’s stable after that, but come on. Oh, and the wireless-N built-in adapter on my Dell Studio Hybrid just will not connect at N speeds, always preferring G. Still don’t know what’s up with that.

Windows Home Server. I love my Windows Home Server, don’t get me wrong, but there are some fiddly things that crop up.

• Random disk errors. Every two or three months I’ll get an error that says my system disk is having problems. I run the repair, everything checks out, and all is well with the world again for the next two or three months. Is it the weird disk replication thing they have going on? Is it PerfectDisk for Windows Home Server doing a disk defragmentation number on me? Disk actually going bad? Who knows.
• More random disk errors. Since upgrading to Power Pack 3, I had a thing where every week or so the server would just stop responding to any requests at all. You ended up having to reboot the server hard and it would all come back. The lockup seemed to correspond to a scheduled task I had running on a client machine that would do a full directory listing of a really large set of files and archive the list. (My DVD library isn’t duplicated, so if a drive dies and I lose files, at least I’ll know what to re-rip.) Error log looked like it just stopped communicating with the eSATA port multiplier. I found some upgraded drivers and we’ll see how that goes.

Media sharing. I’ve got my media center solution that I’m working on and one of the biggest challenges is figuring out what format the media should be in. DLNA spec supports some formats, Windows Home Server supports some formats, Windows Media Center supports some formats… but which is the right one for me? I’m lucky to have found something like Asset UPnP that will transcode audio formats into something more universal, but that’s just audio. What about video?

Video editing. I got a Creative Vado HD for Christmas. I like the recording capability but the little editor that comes with it is severely lacking. If you don’t want to use that editor, at least on Windows, you’re into something like Sony Vegas. But if you want to edit the videos the Vado records, you have to figure out that there’s another codec you have to install.

My point on all this is that I’m a geek and I have the knowledge and skills to at least know where to start to figure this sort of thing out. What do the non-geeks do? Do they just give up and use everything out of the box and accept the crappy limitations of the products and complain they don’t work? Do they get a geek friend/family member to just continually come fix it?

I can see the appeal of things like the homogenous environment. If you just give in and accept the box in which a specific brand (Apple, Sony, whatever) places you, everything pretty much works together. If they don’t have a product that does what you want, well, it’s just “not possible” right now and you wait.

As I get older, I won’t lie - this sort of thing appeals to me. I’m tired of tweaking and fixing and fighting the fiddly shit that is inherent with getting all this to work together. I don’t mind investing time in getting things set up and configured appropriately as long as I don’t have to keep adjusting and reconfiguring and troubleshooting. I just want it to work. It should. Why doesn’t it?

I have some files (like my local Subversion repository, some documents, etc.) that I need to sync between computers and I was recommended Dropbox as the way to get that done. I signed up, installed it, and it works brilliantly.

That said, my primary complaint is that it only synchronizes files inside a special “My Dropbox” folder that it creates. Anything you want to synchronize has to live in there. Thing is, while I don’t mind changing the location of some things, like my documents, I really would rather not change the location of other things, like my local Subversion repository. I like it in “C:\LocalSVN” rather than “C:\Documents and Settings\tillig\My Documents\My Dropbox\LocalSVN” or whatever.

Turns out you can use the magic of symbolic links to fix that right up. If you create a symbolic link (junction point) inside “My Dropbox” to content that actually lives outside “My Dropbox” then the content gets synchronized just fine but can live wherever you want.

If you are in Windows XP, you’ll need to go get a free copy of Junction and put it somewhere in your path like your C:\Windows\System32 folder. In Windows Vista or Windows 7, you’ll use the built-in “mklink” command.

1. Get Dropbox set up and synchronizing on your computer without the external content.
2. Open a command prompt as an administrator on your machine.
3. Change to the “My Dropbox” folder that you set up. In Vista or Windows 7 it’ll be like: cd "\Users\yourusername\Documents\My Dropbox" In Windows XP it’ll be like: cd "\Documents and Settings\yourusername\My Documents\My Dropbox"
4. Create a directory link to the folder containing the external content. In Vista or Windows 7 it’ll be like: mklink /d "External Content" "C:\Path\To\External Content" In Windows XP it’ll be like: junction "External Content" "C:\Path\To\External Content"

That’s it. Dropbox will see the symbolic directory link as a new folder with content it needs to synchronize and it’ll get done.

Note that you can do things the other way around, too - move the content into the “My Dropbox” folder and then create the symbolic link from the original location into the moved content… but this way it means you don’t have to do the moving to begin with. Admittedly, I kinda wish I had figured this out before I moved everything, but now I know.

I got a Creative Vado HD camera for Christmas from Jenn and have been messing around a bit with it. I like the recording quality, but I found in Windows Vista you have to install an H.264 codec in order to get the videos to play in Windows Media Player. (In Windows 7 they provide an H.264 codec for Windows Media Player so you don’t have to install anything else.)

While playback is fine and dandy, I’m not really interested in editing the videos I take with the camera in the simplistic editor they provide. I suppose if I just zapped something really quick to jam up on YouTube that’d be great, but I find I end up with several clips where I need to trim the start/end on them, maybe crossfade them into each other - nothing really major, but more than the little app offers. I have Sony Vegas to do my video editing and it works great.

Except on H.264.

See, Windows does not come with a codec that Sony Vegas can use to edit these files. You can get the audio, but not the video. Really dumb, and dumber still that Sony didn’t pre-package one just in case, particularly since H.264 is so popular.

The answer: x264vfw - a free, open-source Video for Windows H.264 codec.

Once you install x264vfw - three clicks, tops - magically everything works the way you want it to. Playback in Windows Media Player, editing in Sony Vegas… fantastic.

Note that I have seen other solutions for this posted elsewhere encouraging you to install the whole K-Lite Mega Codec Pack and everything that comes with it. That’s overkill. You only need a VFW (Video for Windows) H.264 codec, and K-Lite uses x264vfw internally anyway. I’m a fan of only installing the things you absolutely have to, and just x264vfw will take care of it.

UPDATE 1/4/2010: This appears to have broken in Sony Vegas 10. I had it working in Vegas 9 and for various reasons upgraded to Vegas 10 and now it doesn’t work. It appears that the recommendation in the Sony Vegas knowledge base is to use Windows Live Movie Maker to convert the video to a different format (since Windows can read/play it but Vegas can’t). For that purpose, I created a new custom setting in Windows Live Movie Maker with the following values:

• Width: 1280
• Height: 720
• Bit rate: 8500
• Frame rate: 30
• Audio format: 192kbps, 48kHz, stereo

The width, height, and frame rate match the Vado HD video. The other values are just slightly higher quality than the Vado so you won’t lose too much quality in the conversion. Doing a few tests, I don’t really notice a difference in the source and converted materials.

After conversion, Sony Vegas easily reads the files and you can edit them as expected.

Personally, I think it’s pretty lame that Windows Live Movie Maker can read these files but a higher-end program like Vegas can’t. You would think Vegas would take advantage of the same set of codecs WLMM does… but apparently not.

I just finished upgrading the last of our computers at home to Windows 7 and now that I have Windows Live Writer installed I figured I’d do my yearly retrospective - see what’s gone on this year and recap.

In January I found that they were ending Google Notebook so I had to move all of my notes over to PBworks. That was sort of painful, but I’m really enjoying PBworks now and I have a ton of stuff in there. I also released version 2.2.1.0 of CR_Documentor, a bug fix release.

In February I showed you how to upgrade your Windows Home Server capacity with an eSATA port replicator and upgraded my main TV to a 52” Samsung LN52A750 (still great, and still recommended).

March was pretty eventful. I upgraded my blog to Subtest 2.1.0.5. I reflected a bit on why it’s a good idea to keep a cool head in a tough situation. I ran into some User Account Control issues in Windows Server 2008 and wrote about some power toys that will help you out with that as well as providing my own Visual Studio related elevation toy. I went to MIX09 and blogged all three days (1, 2, 3). My MIX trip then spun off some travel luggage recommendations.

At the beginning of April I found that most of my network configuration problems were due to Verizon updating my FiOS router automatically, requiring me to restore my router to factory defaults more than once since then. I found that an HDMI switchbox can help solve issues where your TV loses the HDMI signal when your computer goes to sleep. Jenn and I took a three-day vacation to Vegas, which is always a good time. I released version 2.3.0.1 of CR_Documentor and put out a solicitation for input (with not much response, to be honest). I wrote about some challenges I’ve faced while trying to write multi-tenant ASP.NET apps. I also wrote about some challenges I faced with my Blackberry due to the Facebook application - if you’re having trouble synchronizing, check your default services.

May found me offering some tips on proper use for bullet lists and finishing off the ripping of all of my DVDs. (Did you know an average DVD is 6.7GB?) I wrote a script to automatically set the album artist on your iTunes tracks. I reviewed ASP.NET 3.5 Enterprise Application Development with Visual Studio 2008. I explained how to get iTunes music playing in Windows Media Center, though Windows 7 fixes a lot of the issues there. Plus I showed you how to use the MSBuild engine in your programs and take advantage of the file finding functionality in there.

June started out where I showed you how to use Typemock Isolator to skip generic constructors. I got an HD camcorder and struggled with the file formats. I reflected a bit on blogs that rip off content and publish it as their own. I talked about defragmenting your Windows Home Server drives, then I went to see the B-52s in concert. June ended on a huge down note, though, as my Grandma Jeanne passed away at 86.

July started out with a nifty trick - I showed how to change Windows Service runtime behavior using Typemock Isolator. I also showed you how to get the Windows OS version from inside MSBuild. I talked about the SQL Server installer constantly requiring a reboot (which always seems to be the case for me) and how to fix it. I updated my custom NAnt tasks to .NET 2.0. On a personal note, my birthday was awesome and I went to see Tears for Fears in concert. The biggest thing in July, though, was Jenn and I running our own fireworks shoot in Sandy. Scary and exhilarating.

August started out brilliantly with one of our famous 24 marathons. I discovered the coolness that is Asset UPnP on Windows Home Server and showed you how to back Windows Home Server up to MozyHome. I showed you how to write Firefox extensions using Visual Studio and I even released one of my own - Firefox NTLMAuth, a plugin to help you with Windows pass-through authentication in Firefox.

Jenn and I started September with a trip to Victoria, BC, Canada - good times. I found a little gotcha when using the Windows Vista DVD burner and it tells you there aren’t any files to burn. I updated my iTunes metadata copying program for the latest iTunes. I reviewed Professional ASP.NET MVC 1.0. Jenn and I went to see The Killers in concert (awesome!). I posted a couple of ASP.NET AJAX tips - using ASP.NET AJAX String.format() in jQuery validation and parsing currency values. Finally, I created a quick DXCore plugin that helps other plugin writers explore contexts.

In October I started out with another jQuery/ASP.NET AJAX tip - converting relative to absolute paths. I did a one-year retrospective with my Windows Home Server. I discovered the hugest gotcha with the “COMPLUS_Version” environment variable and the .NET runtime

• I wish that was more clearly documented. And, finally, this year we had 243 trick-or-treaters on Halloween.

In November I had to manually uninstall a Windows Home Server add-in and showed how to upgrade PerfectDisk for Windows Home Server. I ran into a weird edge case with XML serialization while debugging a Visual Studio add-in. I did some work on my Media Center and figured out the Windows 7 supported media formats, how to fix that one-pixel line in Windows Media Center playback, and talked a bit about metadata and artist names on music files. I showed how to create icons for your context menu items in DXCore and how to put your log4net.config outside your app.config/web.config file. November ended, as it always does, with my least favorite holiday ever.

In December I updated my Subtext database maintenance page for Subtext 2.1.0.5, but I did two other programming things that I was more proud of: I released a DXCore plugin, CR_CodeTweet, that lets you tweet code snippets from inside Visual Studio; and I released a Windows Live Writer plugin that lets you upload images to ImageShack. As part of that ImageShack upload plugin, I figured out how to post multipart/form-data using .NET WebRequest.

Overall, the year was decent, but not great. Like everyone else, we’ve had our challenges with the economy. There have been a couple of fairly difficult personal issues to face as well. On the bright side, Jenn and I are both healthy, and we’ve got a nice place to live, we both have jobs, and we’re otherwise doing well, so I can’t say we’re in a bad spot. I’ll be glad to see 2009 past and I look forward to seeing what 2010 holds.