Replies to post #101420 on Wave Systems Corp. (fka WAVXQ)

[zen 88]

doma- re: 3.5 shipped

Doesn't this only mean that STM has shipped the chips to some MB maker? I don't think it necessarily means that all the machines using those MB's have been built and are already sold. I look at it as 3.5 in the pipeline.

[rachelelise]

Doma

While I don't underestimate the efforts involved, I do think that another software firm who is part of the TCG and who has a year of background and another year to develop a solution, could produce competitve offerings. I also think that the Infineon software group could be given permission to build software that works with other TPMs and try to sell to those TPM manufacturers or to the PC OEMs.

The software group appears to be in a separate business unit and as you know, one of Infineon's units (not sure which has ownership and decision power) licensed their TSS and other related work product to Broadcom, leading to their replacement in hardware but maybe their inclusion in the next generation of HP Protect Tools.

Wave is positioned well right now and given the decision process at enterprises, maybe locked in whenever they activate, but Wave is so weak financially that they have less ability to respond to events.

[Vader]

Doma, in all due respect...


1st, re; the 3.5 M...that's 2 quarters of work by one supplier....I think Infineon could catch up in a new york minute if somebody decided that's the direction they wanted to go..

2nd, up until now, nobody from Infineon has got on this board to tell us they can't compete and that they don't and won't have a solution that eventually will. A company with less than 400K in quarterly revenues and almost out of cash can't begin to claim a competitive advantage that is insurmountable.

3rd, and perhaps most importantly, you said (and I agree) that we have 3.5 "potential" users...

The facts are that we have gone all in on STM, hoping the guys further down the foodchain, i.e. Dell and Seagate, can turn on the golden spiggot...

I don't see how WAVX can risk going it alone from this point on.