I tend to agree with you on the concept of "simultaneous use". Some packages used to specifically allow this (WP 5.x, I believe). However, if you read most modern EULAs closely, they don't allow this.

If it was easy to move an app around from machine to machine a "one CPU/HD" enforcement policy might be reasonable. However, most modern apps need to be "installed" (.OCX registration, registry entries, etc.) so clearly this is not a viable option, even for those apps that could be contained on a CD. Repeated installations/uninstallations can lead to .DLL hell and other system stability problems.

I am strict in enforcing the simultaneous rule. If there is ANY CHANCE the software may be used on more than 1 machine at once, I license accordingly.

>An interesting question arose in my office. We are all licensed users of Visual Studio. On occasion, we may want(need) to bring some work home with us. Also, some of us are studying other parts of Visual Studio (VB primarily), and would like a copy of the software on our home computer to play with. We don't all have a couplke hundred of dollars to spend on an application which we will not be using much.
>
>Someone on our team informed us that there is a loophole of sorts in most software licensing agreements. The way it was explained to me, when you buy a software license, it does not mean that it can only be installed on one machine; it means that the licensed software can only be running on one machine AT A TIME.
>
>If I use the software on my work desktop machine from 8:00am to 6:00pm, run the same license on my notebook computer from 6:00pm to 8:00pm, then run the same software license on my home machine from 8:00pm to 11:30pm, I am perfectly within the license agreement. Although the same software license is installed on multiple machines, only one copy of the licensed software is running at any time, and it is being run by the license holder.
>
>I have not done the actual legal research to determine if this is kosher, and so far I have not installed my work copy on my home computer. What are your thoughts on the matter, and is this something that you yourself do?
>
>Bill