Can someone recommend a home theater receiver?

Our new place has Polk 5.1 speakers mounted on the walls (well, actually we need to buy a subwoofer since the owners took that with them, but nevertheless…) so it seems like the right time to put my NAD C340 2 channel amp in another room and upgrade to a surround sound system. There are so many receivers out there – how to choose a very good quality one that’s under, say $1000?

We might be getting HD soon, so I figure HD switching and upconversion will be really nice to have. Multi-room and iPod integration are pluses. Not sure what else to look for. Mainly I just want something that’s fairly easy to use and has nice clean sound for movies, TV, and music.

Since we have a built-in entertainment center with cabinet doors, I’d like to also find something that catches the IR signals from our remotes and retransmits it to the components inside the cabinet.

Recommendations?

Windows Haikus

Just some weird stuff that popped into my head a few days ago while I was installing Windows on one of my spare PCs.

Everything I do
Always requires a reboot
What a crap OS

My life with Windows
Is never-ending reboots
Then blue screen of death

Have your own haiku that you want to contribute? Post below in the comments.

I’d like to move it, move it…

…but I can’t.

Well we’ve moved all our stuff from the old place to the new place. Only problem is we have a zillion boxes to unpack now and we don’t know where to put anything and our feet are kind of achey from going up and down stairs carrying heavy boxes.

DSL move fiasco

Today our AT&T DSL stopped working. I tried the usual rebooting of the router and modem to no avail.

A few days ago I placed an order with AT&T to move our DSL to our new place as of Saturday the 8th. Well at least I thought I did. AT&T tech support says the order was effective today and that’s why our DSL is gone. Should be a simple matter to just turn it back on for a couple more days, right? Well at least some of the customer support people think that there is nothing that can be done. Another guy told me “it should be working now”. Since up to that point minus 30 seconds it had not been working, I asked what he had done. Silence. After asking in 2 or 3 more ways, he answered with a vague response which I am not sure of but I think it amounted to “No I didn’t do anything, but I checked and it should be working.” Umm, well it’s not. Recognizing a dead end when I see one, I thanked him for his time and hung up. I’ll probably try to call a few more times as usually I find some techs are way better than others and often you just need the right one to solve the problem.

The real kicker for me is that I thought I was being smart by calling early to schedule the move so we wouldn’t have any interrution in service, but now as a result of calling early, I’ve got an interruption in service. Perhaps it’s wiser to just wait until you’re at a new place before moving service. I figure the time right before the move is more hectic than afterwards, so waiting may be a good tradeoff.

Installer crash puts a damper on Dapper

Up until now I had not tried installing Dapper from scratch. I had only upgraded an existing Breezy system to Dapper and it went very smoothly.

Tonight I attempted to use the Dapper CD to install Dapper on to a 40 GB hard drive of which I had already had Windows 2000 setup in a 12 GB NTFS partition. The live CD boot up just fine and then I double-clicked install and answered all of the questions and let Dapper decide how to partition and format the remaining space. It did so and then proceeded to copy files only to crash when 81% through. The crash was in a program called “ubiquity” and there is a bug report here. I actually tried the install several times and it failed with the same error.

The nasty thing was that GRUB was never installed and the unusable /dev/hda2 ext3 Ubuntu root partition was set bootable so the system is not bootable, including my previously working Windows 2000. I fixed this by booting into the Dapper live CD and using fdisk to turn off the boot flag for /dev/hda2 while turning it on for the /dev/hda1 NTFS partition. This restored my ability to boot Windows.

It’s really unfortunate that a bug this serious wasn’t fixed before the release and before thousands of 6.06LTS CDs got shipped all over the world.