Just a heads up for everyone... If you change the name of your computer, all your RAD Studio registrations will need to be made again and it continues to count the one on the 'old' computer name. And in my case, that just caused all my versions to stop working because I 'hit my registration limit'. So now I can't do work until someone at Embarcadero resets my count. What a stupid thing to tie a reg count to the computer name. I had a very valid reason for renaming my computer, now I am paying the price as I have something I need to get done tonight before I leave town tomorrow morning.
Just a heads up for everyone... If you change the name of your computer, all your RAD Studio registrations will need to be made again and it continues to count the one on the 'old' computer name. And in my case, that just caused all my versions to stop working because I 'hit my registration limit'. So now I can't do work until someone at Embarcadero resets my count. What a stupid thing to tie a reg count to the computer name. I had a very valid reason for renaming my computer, now I am paying the price as I have something I need to get done tonight before I leave town tomorrow morning.
Buyer be ware... ARGH!
Buyer be ware... ARGH!
Fred Ahrens http://license.codegear.com/lservers/elise.jsp http://docwiki.embarcadero.com/ELC/en/Installing_ELC
ReplyDeleteFWIW, after upgrading to Windows 10 my Delphi license remained valid.
ReplyDeleteAnd this is why the rest of the world moved to open source development tools many years ago. You're not going to be shut down by renaming a PC, lack of Internet connection, "license count limit", DRM that might as well be trying to break the record for largest prime number found before starting, etc. This whole discussion is "so 90's". :-(
ReplyDeletehttp://www.osnews.com/story/26563/Why_I_Use_Generic_Computers_and_Open_Source_Software
>Here's a real-world example. My motherboard died last
>summer. I removed the boot disk from the dead system
>and plopped it into another, then booted that Linux
>instance on the target computer. Problem solved!
>Windows won't let you do this. Its hardware-bound
>Registry, authentication procedures, and licensing all
>specifically prevent it. They're designed to. Why? So you
>don't steal Microsoft's software. Microsoft places its
>needs to protect its ownership of Windows software
>above your need to solve your crisis. (Remember, you do
>not own the copy of Windows you "bought," Microsoft
>owns it. You only licensed it.)
>
>Microsoft has every right to protect its property. But that's
>not our problem. Our problem is fixing our motherboard
>failure. Because of their agenda, Microsoft makes our life
>more difficult. Their software limits your flexibility -- on
>purpose. Heck, you can't even move an installed app from
>one disk to another without special software. The Registry
>-- Microsoft's control choke point -- prevents it.
>
>OSS lets you easily move software across machines or
>disks or operating systems with just a command or two. I
>replicate operating systems, applications, and data how
>and when I need to. No Registry, licensing, authentication,
>hardware binding, or other artificial barriers make my job
>more difficult.
Because a small amount of people abused a feature everyone else have to suffer. EMBT continually treats us like criminals, from the DRM here to Interbase developer edition shutting down every four hours to the non-compete clause in the EULA, etc. I don't think they realized that the world changed and no one needs to steal software anymore.
>I'm talking about companies installing on multiple
>computers and having multiple developers sharing a
>license.
As if there are 200-developer Delphi companies... if these companies are that poor, they would never have paid for multiple licenses in the first place. Bill Gates once famously said he'd rather people pirate WIndows and figure out how to monetize them later than have them switch to another OS. He understood that people tend not to look at new products unless they're having problems with existing ones, so if they leave they might never come back. Given the state of Delphi today, I'd rather have people using/promoting a cracked copy of Delphi than switching over to Visual Studio Community Edition for free and never coming back.
In fact, Visual Studio Community Edition is much more of an existential threat to Delphi's existence (C++, C#, ASP.NET/Javascript/Typescript, F#, VB.NET
, and Python in one box with professional grade IDE and dev tools) than a handful of pirates.. Lots of time spent worrying about the latter, and no official response to the former. Actually, the first response I saw after the ground-shaking announcement from MS was Tim Del Chiaro advising people to order now before the price goes UP (yes, the only response to VSCE was a $100 price INCREASE). Worrying about copy protection in a world in which the most popular Windows-based development tool is now free to companies making under $1 million for 5 devs is like rearranging the deck chairs on the Titanic.
ReplyDelete