Linked by Thom Holwerda on Tue 30th Oct 2012 18:10 UTC
Permalink for comment 540636
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2005-10-19
I attributed those things to you because they can be inferred by previous things that you said. For example you said:
"your words were it didn't work, which was a direct result of using a pirated copy".
This means that you believe the first issue I raised was a result of using a pirated copy. If this is the case then you must logically believe that anyone else having this problem must also be running a pirated copy. See how I make that connection?
This also implies that either you think that MS deliberately rigged it not to work on pirated systems, or you think it's just a coincidence, and I just wanted to clarify which you believed.
You said:
"you already admitted it caused an issue before denying it later"
When did I admit that it caused an issue?, and when did I deny it? Please paste the text.
Frankly, I think that you read the first paragraph of my post, got annoyed that I pirated some software, and shot off at the mouth. And you've been trying unsuccessfully to make your position tenable since then.
Bottom line. None of my issues; I repeat NONE of my issues were caused by piracy.
They are all a result of a very crap upgrade implementation by Microsoft, and had you read on, you would have quickly realised that.