Skip to main content

Frivolous Lawsuit and/or Poor Marketing of the Day

Emerson filed a federal lawsuit in St. Louis on Monday, seeking to block the NBC television network from rebroadcasting the pilot episode of the new show "Heroes," which depicts a woman damaging her hand in a garbage disposal made by the company.

The Ferguson-based maker of electric products says NBC Universal Television Studios did not have the right to use the company's In-Sink-Erator brand disposal in the show without permission.


Yeah, we need to stand up to The Man! No way will I buy an InSink Erator the next time I purchase a disposal. Grrrrrrr. ;-)

This suit is so ridiculous. I'm surprised anyone even noticed this let alone allow it to affect a purchasing decision--on an oft-purchased disposal. Please. If this sticks, does that mean studios will have to ask permission for every single item used on the set? "Hey! That 6-panel Chuck's Doors door was used without permission! I'm filing suit!" Dumb. Dumb. Dumb.

Theories:
(1) Emerson is marketing-clueless. Firms pay millions for product placements such as this. They should ride the wave.
(2) Emerson is marketing-savvy. They know the lawsuit will generate lots of buzz. Any buzz is good buzz.
(3) Emerson is conniving and malicious. Emerson competes with General Electric (parent of NBC).

I'm leaning toward mostly #2 with a spot of #3. I'm sure some Emerson exec caught this on their 1080i and started plotting. Who else would go through the trouble of examining a garbage disposal at a high enough resolution to make out the brand?

When will companies stop doing stupid things?!

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i