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

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Verified by Visa: Everything We Tell Folks to Avoid

Phishing is defined by F-Secure as: "Fraudulent e-mail or website claiming to be legitimate seeking indentifiable information. Phishing is an attempt to steal your personal data."When I recently attempted an online purchase from WalMart using my VISA card, being a security wanta-be, I immediately thought phishing when redirected to verifiedbyvisa.com and saw this dialog:

Seriously, these folks have to be kidding. You're asking for my personal data during a transaction and claim that's its a service "...at no additional cost." Wow! Thanks...but absolutely not, you jokers. As a malicious thief, I can go a long way with this data.

This is exactly the type of experience which aids malfeasance and the folks trying to steal personal data / identities. How long have we been working to educate folks to avoid providing this type of data under these type of circumstances? Years. And we're just now starting to turn the corner.

VISA, get rid of this! When folks submi…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…