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) -- Ignore unavailable to you. Want to Upgrade?


To: elmatador who wrote (24939)5/7/2003 11:47:13 PM
From: waitwatchwander  Read Replies (1) | Respond to of 34857
 
>>>>> maximum outside radius ending in England

How did Nokia find to Texas?



To: elmatador who wrote (24939)5/8/2003 7:42:46 AM
From: 49thMIMOMander  Read Replies (1) | Respond to of 34857
 
Who would realistically not be a little careful with MSFT??

Considering MSFT's regular and original habits, tactics and track record??

As well as the bloathing products, motor-hood welded closed, secrete
sauces, bugs, etc special features inside.

Usually it is difficult enough to get something working just by itself and
to interface to a windows system, worse if some features are embedded
and unpredictable to make it even worse.

It is anyway only some months since MSFT made their own developer's site
incompatible with both Netscape and Opera, impossible to uninstall the
latest mediaplayer,etc,etc..

Not to forget regular security in terms of viruses, backdoors, passwords, e-mail,
bank accounts, SIM cards,etc,etc... additionally with backdoors through Bluetooth.
(and the still disastrous, unsafe, unstable memory-handling of wincrash)

Some of the reasons the telecom operators and manufacturers already
in 1995 decided to concentrate on a operating system and GUI which
would not even be attackable through Wall Street.

Telecom operators, banks, etc have a lot of experience in how to not handle
important real-time system which deal with lots of cash, customers and traffic,
and now it is additionally a question of not having to set up 24-hour service
for the customers.

That is, there is enough of demanding, difficult stuff to implement, upgrade,
improve,etc without having to additionally play cat and mouse games without
access to actual source code and functional debuggers, no error logging,
at least a running on a system designed to be fail-safe.

WinCrash is still best suited for applications which only communicate through
some standardized, third party interfaces, cables to some other more relieable systems,
additionally well isolated by other small, exchangable, third party embedded systems.

Additionally important, vital information should not be stored on a WinCrash-reformat-reinstall
system as incremental backups are kind of unsupported.

Ilmarinen

Not that MSFT does not try, they have been working on it ever since they managed
to sucessfully mess up OS2 and even admitted WinME and WinCE were a bad but
desperate, strategic mistakes.

However, there is always the hope born by the promise of the next yearly version.