Software update on SKY+ pace V1 boxes- Public relations farce!

"Zero Tolerance" wrote in message
...
On Sat, 1 Jul 2006 21:49:56 +0100, "Tumbleweed"
wrote:

all the new check did was to see if it was an original
drive and kill the box if it wasnt. It wasnt some accidental happenstance.

Well if that was the case then Sky wouldn't be rolling back the
software, would they? There's clearly no way they could get away with
that and therefore no reason for them to try. Why go out of their way
to **** off large numbers of paying customers? Not Sky's style.
--

What I meant was, it wasn't some wierd and subtle arrangement of
circumstances, it was "if not original drive kill it'. Hence, highly dumb
programming.

--
Tumbleweed

email replies not necessary but to contact use;
tumbleweednews at hotmail dot com

On Sun, 2 Jul 2006 18:28:50 +0100, "Tumbleweed"
wrote:

What I meant was, it wasn't some wierd and subtle arrangement of
circumstances, it was "if not original drive kill it'. Hence, highly dumb
programming.

Are you suggesting it was deliberately programmed to do that?

Programmatically, it seems more like a fault condition was occuring
when a non-original drive was installed - either because it was much
too large, or it somehow sufficiently differed from the 'expected
range' of installed drives in some less significant but still
measurable way. (e.g. Drive replacements)

It'll be a byproduct of the new 'System Healthcheck' option, I'm sure.


--

Zero Tolerance wrote:

Hold it! Your FTV Sky+ ?

I don't pay.

Ah, of course - so you don't record either. What exactly do you use it
for, then, just the optical output?

See my other past where I detailed the reasons.

--
Digibox problem? : A reboot solves 90% of these.
The Sky Digital FAQ: http://tinyurl.com/8vef5
UK TV overseas: http://tinyurl.com/6p73
BBC reception questions? ; http://www.astra2d.com/
Fed up with on-screen logos? : http://logofreetv.org/
----
Only the truth as I see it.
No monies return'd. ;-)

"Zero Tolerance" wrote in message
...
On Sun, 2 Jul 2006 18:28:50 +0100, "Tumbleweed"
wrote:

What I meant was, it wasn't some wierd and subtle arrangement of
circumstances, it was "if not original drive kill it'. Hence, highly dumb
programming.

Are you suggesting it was deliberately programmed to do that?


I am suggesting exactly that. Read digitalspy. I'm not suggesting it was
designed to do it because SKy wanted to shut down units with non-original
drives, it appears to have been a short cut to see if the drive was 'good'
but rather than check that they looked to see if they could read the
original drive spec and if they couldnt (because it wasnt an original drive)
decided it was therefore faulty!


--
Tumbleweed

email replies not necessary but to contact use;
tumbleweednews at hotmail dot com

On Mon, 3 Jul 2006 07:53:22 +0100, "Tumbleweed"
wrote:

Are you suggesting it was deliberately programmed to do that?

I am suggesting exactly that. Read digitalspy.

Strangely enough I don't consider Digitalspy's forum users to be an
accurate guide to the intentions of the programmers at Sky.

it appears to have been a short cut to see if the drive was 'good'
but rather than check that they looked to see if they could read the
original drive spec and if they couldnt (because it wasnt an original drive)
decided it was therefore faulty!

I don't buy it. If the software was "deciding" that the drive was
faulty it wouldn't stay in standby - it would just boot and display
suitable warning messges. Nobody would deliberately code such a
braindead response to an error condition.
--

"Zero Tolerance" wrote in message
...
On Mon, 3 Jul 2006 07:53:22 +0100, "Tumbleweed"
wrote:

Are you suggesting it was deliberately programmed to do that?

I am suggesting exactly that. Read digitalspy.

Strangely enough I don't consider Digitalspy's forum users to be an
accurate guide to the intentions of the programmers at Sky.

It was from one of the people who first (accurately) reported the cause of
the problem and the way the fix would be provided.



it appears to have been a short cut to see if the drive was 'good'
but rather than check that they looked to see if they could read the
original drive spec and if they couldnt (because it wasnt an original
drive)
decided it was therefore faulty!

I don't buy it. If the software was "deciding" that the drive was
faulty it wouldn't stay in standby - it would just boot and display
suitable warning messges. Nobody would deliberately code such a
braindead response to an error condition.

yeh, you and I would program it that way .......

--
Tumbleweed

email replies not necessary but to contact use;
tumbleweednews at hotmail dot com

Zero Tolerance wrote:

it appears to have been a short cut to see if the drive was 'good'
but rather than check that they looked to see if they could read the
original drive spec and if they couldnt (because it wasnt an original drive)
decided it was therefore faulty!

I don't buy it. If the software was "deciding" that the drive was
faulty it wouldn't stay in standby - it would just boot and display
suitable warning messges.

You should buy it. The Sky+ firmware has done something similar for
about 2 years and since that time any box without a working drive will
not boot. Previously the Sky+ would boot with or without a working
drive.
This seems to be merely an extension of the same check.


Nobody would deliberately code such a
braindead response to an error condition.

Nobody but Sky, perhaps.

--
Digibox problem? : A reboot solves 90% of these.
The Sky Digital FAQ: http://tinyurl.com/8vef5
UK TV overseas: http://tinyurl.com/6p73
BBC reception questions? ; http://www.astra2d.com/
Fed up with on-screen logos? : http://logofreetv.org/
----
Only the truth as I see it.
No monies return'd. ;-)