To view parent comment, click here.
To read all comments associated with this story, please click here.
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.
"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.
No, read again what you said, in full:
"This made me a bit nervous as I was running a pirate version of Win7. And ... it didn't work.
You knew you were running a pirated version of Windows, and it made you nervous about attempting an upgrade. So you were the first one to attribute failure directly to running hacked software, not me. You tried to take it back and then turn it around on me, but to do so is quite disingenuous.
Not at all; that is obviously the way you think but I tend to take all the facts into consideration. In your specific case it caused an issue, as you said. My point has been and still is that you are starting with a corrupt data set for your experiment, and even if the rest of your results are replicated elsewhere, your test itself is suspect.
No problem, bold text in these quotes is my analysis, the rest is you:
"This made me a bit nervous" - you suspected it would be a problem - "as I was running a pirate version of Win7. And ... it didn't work." - and your suspicion was correct.
"Precisely none of the issues I encountered were the result of the fact that my copy was pirated." - Flat out denial of what you stated above.
No, as I've stated four times now, I think your methodology is flawed. Perhaps the pirated software caused more than just the first issue, perhaps it caused none, perhaps it caused all of them. The fact that you ran the experiment with a known suspect data set makes it invalid, period.
There's simply no way to say that with 100% certainty, even if we completely ignore your first issue. To say otherwise is ludicrous. Re-run the experiment with a legal copy of Windows 7, and no matter the outcome, even if the first issue happens again, I will believe every word of it.
There's a very good chance you are right, but we'll never know for sure unless you conduct a proper test using legitimate installs.





Member since:
2005-06-29
1. That MS deliberately rigged its upgrade assistant to not work on pirated copies that are trying to go legitimate.
I never said that, don't misquote me. It's a given that if you're running a pirated or hacked OS, when you try legitimate updates they tend to fail. This is true of Windows as well as MacOS (Hackintoshes).
I never said that either. Again you put words in my mouth to prove your point. Not the right way to do things, dude.
Once again, I never said that. You have a perverse love of misquoting people, it seems. My issue is that if your methodology is knowingly flawed (as you proudly proclaimed when you said "This made me a bit nervous as I was running a pirate version of Win7") one has to wonder about the rest of your results.
I'll say it with emphasis this time so it sinks in: Run your tests on a valid Windows 7 install, or else a clean install of Windows 8, and I will take your evaluation at face value.
Edited 2012-10-31 02:47 UTC