Unauthorised access and the running of unauthorised software on computers belonging to a third party is most certainly a crime in Germany and the EU.

Will be interesting to see if it's ever enforced.

It already has been in Germany, a loooong time ago.

Alinator

Sorry guys but this thread would need to be moderated...

---

Do you want to get banned for 31 years and your account & credits deleted at a Boinc project ? Predictor@home is your best choice.

Sorry guys but this thread would need to be moderated...

Why so? I see some good healthy debate and hasn't gotten ugly at all.

---

Sorry guys but this thread would need to be moderated...

Why so? I see some good healthy debate and hasn't gotten ugly at all.

Why ?
As usually, the thread is becoming a mess...

---

Do you want to get banned for 31 years and your account & credits deleted at a Boinc project ? Predictor@home is your best choice.

Sorry guys but this thread would need to be moderated...

Why so? I see some good healthy debate and hasn't gotten ugly at all.

Why ?
As usually, the thread is becoming a mess...

Could you do me the favor of describing the mess.

---

Sorry guys but this thread would need to be moderated...

Why so? I see some good healthy debate and hasn't gotten ugly at all.

Why ?
As usually, the thread is becoming a mess...

Long?... Yes, but still relatively on-topic for the most part. No mess.
Why do you feel it needs moderation?

---

SETI.USA - Uniting the United States stats!

Why so? I see some good healthy debate and hasn't gotten ugly at all.

Why ?
As usually, the thread is becoming a mess...

Could you do me the favor of describing the mess.

The real mess is that of the shoddy Windows OSes that support viruses and trojans and all the other long term exploits in the first place!

I'm still amazed that users have put up with the mess and frustrations (and wasted time, and extra expense) for so long. Must be some very good Marketing there...

And yes, there are good alternatives.

Regards,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Why so? I see some good healthy debate and hasn't gotten ugly at all.

Why ?
As usually, the thread is becoming a mess...

Could you do me the favor of describing the mess.

The real mess is that of the shoddy Windows OSes that support viruses and trojans and all the other long term exploits in the first place!

I'm still amazed that users have put up with the mess and frustrations (and wasted time, and extra expense) for so long. Must be some very good Marketing there...

And yes, there are good alternatives.

Regards,
Martin

yeah, I prefer the alternatives too.

---

Must be some very good Marketing there...

Not good, just unethical, sometimes illegal. Just look at the history of OS/2 and Microsoft's blackmail of IBM for an example.

Unfortunately, Microsoft have built up the wealth, and the power that goes with it, to ride rough-shod over the law and anyone who gets in their way.

---

Be lucky

Neil

Oh my my, now it is Microsoft's fault lololol. ;o)

---

And the beat goes on
Sonny and Cher

BOINC Wiki

Oh my my, now it is Microsoft's fault lololol. ;o)

Sheep.

---

Sheep.
[/quote]

BAAAAA!

---

Now, I know why they errored out (and it was operator-error, not hardware), but given that it is sometimes human nature to jump to all kinds of conclusions based on little evidence, it is simply easier to keep them hidden.

Why would an open discussion compel one to hide systems? There is nothing forcing anyone to read, or respond to a discussion thread and open discussion MIGHT even resolve problems.

Good open discussions based on facts are never a bad thing.

But anything can follow from a false premise.

At the beginning of this thread, we've got someone who everyone assumed was guilty of spreading a virus to raise his score. Maybe, and maybe it's someone who doesn't like that individual and managed to get his account key.

In my case, the false premise was that all lost work units are caused by hardware problems. I knew that I fat-fingered the reset-project button, and I knew the effects, and I knew I would be more careful in the future.

Problem solved, no further discussion needed.

---

In my case, the false premise was that all lost work units are caused by hardware problems. I knew that I fat-fingered the reset-project button, and I knew the effects, and I knew I would be more careful in the future.

That certainly wasn't my premise; indeed, you've provided an example of exactly the sort of thing I was talking about. Knowing that users will sometimes lose a pile of WUs from inadvertently resetting a project could be valuable to someone developing the software with regard to the 'human interface': maybe it would be a good idea to pop up a confirmation dialog, at least when there's work in the cache, especially considering that (one hopes!) the reset-project function isn't needed very often. Anyway, I don't mean to pick on you--I'm sure most of us had many such a slip of the fingers, or of the brain for that matter--I'm just saying that even if you had little to learn from the experience, it could be in some way a useful datum to the project.

---

In my case, the false premise was that all lost work units are caused by hardware problems. I knew that I fat-fingered the reset-project button, and I knew the effects, and I knew I would be more careful in the future.

That certainly wasn't my premise; indeed, you've provided an example of exactly the sort of thing I was talking about. Knowing that users will sometimes lose a pile of WUs from inadvertently resetting a project could be valuable to someone developing the software with regard to the 'human interface': maybe it would be a good idea to pop up a confirmation dialog, at least when there's work in the cache, especially considering that (one hopes!) the reset-project function isn't needed very often. Anyway, I don't mean to pick on you--I'm sure most of us had many such a slip of the fingers, or of the brain for that matter--I'm just saying that even if you had little to learn from the experience, it could be in some way a useful datum to the project.

... which might be a valid point if resetting was truly detrimental to the project as a whole.

Most likely, the other three results were returned, formed a quorum and the work was done. Worst case, someone else had a problem and the work was reassigned.

A few people may have gotten credits a few days later than expected.

BOINC and BOINC projects have to recover from a multitude of problems like this one without intervention.

... and while you may not want to pick on me, for some, picking on people has been developed into a high-art.

Clearly, with a RAC of 88 or so, if I'm cheating, I'm not very good at it.

---

In my case, the false premise was that all lost work units are caused by hardware problems. I knew that I fat-fingered the reset-project button, and I knew the effects, and I knew I would be more careful in the future.

That certainly wasn't my premise; indeed, you've provided an example of exactly the sort of thing I was talking about. Knowing that users will sometimes lose a pile of WUs from inadvertently resetting a project could be valuable to someone developing the software with regard to the 'human interface': maybe it would be a good idea to pop up a confirmation dialog, at least when there's work in the cache, especially considering that (one hopes!) the reset-project function isn't needed very often. Anyway, I don't mean to pick on you--I'm sure most of us had many such a slip of the fingers, or of the brain for that matter--I'm just saying that even if you had little to learn from the experience, it could be in some way a useful datum to the project.

... which might be a valid point if resetting was truly detrimental to the project as a whole.

Most likely, the other three results were returned, formed a quorum and the work was done. Worst case, someone else had a problem and the work was reassigned.

A few people may have gotten credits a few days later than expected.

BOINC and BOINC projects have to recover from a multitude of problems like this one without intervention.

... and while you may not want to pick on me, for some, picking on people has been developed into a high-art.

Clearly, with a RAC of 88 or so, if I'm cheating, I'm not very good at it.

He's talking about software improvements, your morphic spin of the issue and conditions he describes only dilutes your ability to project any sense of,well... sense. No false premise there.

---

He's talking about software improvements, your morphic spin of the issue and conditions he describes only dilutes your ability to project any sense of,well... sense. No false premise there.

The original question was "why would anyone choose to hide their systems?"

... and my response is that, while interesting, that information contains a whole lot of "what happened" and very little about "why."

Mostly it seems to lead to statements like "Your Pentium MMX seems to have a lot of client errors -- more than 30% -- you should fix it or throw it away!"

But, it is not my place to say. Nor would I presume to say that you should run all Linux, or all Windows.

... and I don't want to defend my choices any more than I want to question yours.

---

He's talking about software improvements, your morphic spin of the issue and conditions he describes only dilutes your ability to project any sense of,well... sense. No false premise there.

The original question was "why would anyone choose to hide their systems?"

... and my response is that, while interesting, that information contains a whole lot of "what happened" and very little about "why."

Mostly it seems to lead to statements like "Your Pentium MMX seems to have a lot of client errors -- more than 30% -- you should fix it or throw it away!"

But, it is not my place to say. Nor would I presume to say that you should run all Linux, or all Windows.

... and I don't want to defend my choices any more than I want to question yours.

True but to a point. I believe the thread is more or less talking and postulating on cheating, and whether or not hiding ones computers would be indicative of cheating.

I conform to the idea that someone who has 301,000 RAC, while at the same time hiding their computers, could be...and it only raises the question. As I have said many times before, questions will be asked. For that matter, anyone who has 301,000 RAC should be looked at. But not by you or me, but by those who serve in a decision making capacity.

By the way, others have offered me constructive advice after looking at my machines. I appreciated it as well. You can't go from one extreme to the other.


Edit note: To fix various typos.

---

The real mess is that of the shoddy Windows OSes that support viruses and trojans and all the other long term exploits in the first place!

Trojans in particular are not windows-specific. Trojans are particular to users who are just a little tiny bit too trusting.

If Linux was as widespread as Windows, we'd see a whole lot more Linux trojans.

Viruses are a different story, you can harden an OS against those.

---

The real mess is that of the shoddy Windows OSes that support viruses and trojans and all the other long term exploits in the first place!

Trojans in particular are not windows-specific. Trojans are particular to users who are just a little tiny bit too trusting.

If Linux was as widespread as Windows, we'd see a whole lot more Linux trojans.

Viruses are a different story, you can harden an OS against those.

And as I am paranoid, therefore I run Linux :)

---