SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Nokia (NOK)
NOK 6.970+2.0%Nov 10 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: carranza2 who wrote (21199)7/16/2002 7:46:08 AM
From: Eric L  Read Replies (1) of 34857
 
Good Morning Garbage Mouth,

Tsk, Tsk, Tsk.

Just can't clean it up can you?

<< Do I take it that AWE did not report five FATAL crashes thanks to Nokia? >>

The AWS filing states that there were 5 fatal errors, and 2 major errors reported over the period from 4/22 through 6/2 in the Portland FOA on the Nokia RAN for Nokia S10.

The final "major" problem (companion software in BST) was undergoing root cause analyses when the filing was made on or around June 7.

Root cause of the original 8 bugs had been identifed prior to the filing and patches were being tested with a consolidated patch due June 10 in AWS lab with the patch for the final "major" problem tentatively due June 17 pending identification of root cause.

All the PCS carriers went through this type of thing as digital wireless networks went live in 95 through 97, and early PCS-1900 (GSM-1900), IS-95, and IS-136 networks were debugged - with the IS-95 networks being debugged last and taking longest.

This is pretty Ho Hum stuff even though there is an FCC mandate in place that all carriers are having some problems complying with for a multitude of reasons, and obviously Nokia could have some liability to AWS over this one. Rest assured, Nokia and AWS are capable of working that out. AWS has been here before ... with several vendors.

<< Jorma did not get a communication from AWE--probably blistering--putting him personally on notice of the problem? >>

Jorma Ollila recieved a communication from a prudent AWS Chairman John Zeglis on May 17. It was probably terse and to the point and it is doubtful that it contained any of the blasphemy you attributed earlier to Mr. Zeglis.

<< Why don't you ... >>

Let it ALL hang out ...

- Eric -
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext