Rockeiro

As a nearly 20 year user of Stardock products, I understand the licensing but I was pointing out the difficulty of it under my personal cirmcumstances and work flows, in case there's ever a change of heart. After all, with IPv6 mac addresses and processor IDs on the host machine and coming from the same NATted host IP you would thing it's easy enough to confirm the one user is the only one using it. My last word. Thanks for the discussion.

I know it's been a while. The thread is still of interest to me and honestly I forget to reply at the time. If I'm only running one VM at a time on my personal computer, then doesn't this satisfy the the terms you stated? You would sell a corporate license for *one* concurrent activation? I realize this is a constant issue for software developers but I (me myself) am not a multitasking machine and as a singularity, have only one current session, yet I am expected to pu

I read the software license. Nothing what so ever about virtual machines. I have only one physical machine. I have multiple virtual machines (VMWare). I use only one or the other and not the two simultaneously. So why can't I license products on my VMs as well as my primary physical machine with the same license? The argument will probably go to the point that is a VM considered another machine even though it's just software on the one physical machine?

As there's no apparent forum for Fences (strange that a publix beta has no way to feedback to developers), I'll drop this issue here. I have discovered that if you want to use Fences, you WON'T be using IconX. Windows-D lets you switch between the two though. Interesting. While in the Fences desktop space, which actually is your original Windows desktop, double clicking the background (to clear all the icons and give you a clean desktop, switches me back to my IconX desktop. I