View Single Post
Posts: 992 | Thanked: 738 times | Joined on Jun 2010 @ Low Earth Orbit
#57
Originally Posted by ndi View Post
a) Get it fixed?
Donate it to "will it blend?"?.

b) If you mean a730W, it's a 2003 system on a 2004 device. That was over 7 years ago. Is that what you base your Windows experience on?

You cast an error prone system as the inability of a giant corporation to write code? I see.
What little faith I had in MS being able to produce decent products had all gone by around the Win3.1 era. Write code is not the same thing as write good code.

Anyway, let us try some logic.

* It was definitely not doing that when they sold it, otherwise it would have been returned and melted for scrap.
It was definitely doing anything when I bought it since it was still inside its box. And if defective products are melted for scrap and not sold then we would have whole heaps of molten MS install media all over the world and extra tonnes of toxic gases circulating the atmosphere.

* The quality of code doesn't diminish with time. Hardware stability and performance does.
Clearly MS missed that memo.

Add those together and it's pretty clear to me you have a hardware problem.
Probably the same hardware problem whereby a computer running Linux will do so happily for weeks on end, whereas the same computer running Windows will get a BSOD if you so much as sneeze too hard.

Not a software fault. So, bottom line is, get it fixed.
I have long stopped using it and got a Zaurus to replace it. And the best way to fix it would probably be this: http://www.handhelds.org/moin/moin.cgi/MyPal730