KR> and if it proves to be such then the likelihood of it being caused
KR> by the re-configuration is 3 parts of 1% of absolutely bugger all (:

RS> Fraid not. And you cant explain why if your story about it
RS> being the fault of Pauls system, why no one else saw it. You
RS> were the only one who had done a complete 'end to end' reconfig,
RS> it bit you after that, and that surprises you ?  Nuts.

RS> Every single bit of the sequence you have stated can be
RS> explained by a single TH1 somehow on your system which
RS> caused your Binkley to refuse a TH1 from Pauls. And when
RS> that occurred AFTER your 'end to end' reconfig,

RS> its far more likely than anything else that the reconfig caused that.

KR> see my previous message,

Didnt help much.

KR> since the problem actually occurred before the reconfig,
KR> it sort of cuts the legs from under this theory doesn't it?

Nope, really hasnt changed a damned thing on the question of your
proclamation that it cant have been the fault of your system. The
fundamental thing that YOU cant escape is that no one else has seen
that effect, Pauls system thinking the file is refused, when it wasnt,
and I just dont believe your system really was untouched for 12 months
prior to the 19-May and even if it was, that still leaves open some
possibilitys like a glitch in your drive subsystem causing your Bink
to refuse the TH1 or something as simple as a lack of free space.

And when those last two are absolutely classic examples of things
that can make a system work for months and then bite you, you just
plain CANT proclaim that it cant be your system.

--- PQWK202