Wow, sorry to hear you're all sharing the pain, but it's good to know it's not an isolated problem.
Given WMtoiPhoneconvert's report of firmware 2.0 causing this problem on an original iPhone, I think I'll wait a couple of weeks for a firmware update.
Those without shortages in their area, who can easily get replacements, might as well get them (that should certainly give Apple an incentive to work on the firmware fix!)