Fung you haven't been following closely enough. I've never contacted the company, never even considered it, many others did though. I talked to the T/A twice and NASD twice, and NASD called me back after they spoke with Nasdaq.
This all on the 18th, the day after the error was figured out by many of us....I just like to confirm with mine own ears some things.
"the error was posted by Jim Bishop. He stated he tried to warn the company, but they stated something to the effect of "this is how we're doing it".