"No work for you!" Good thing I have a habit of pressing Ctrl+Shift+S often. This is so stupid. Of course, nothing in their "common solutions" applies. Of course, the mere fact that they need a "common solutions" page for a license validation BUG should tell them something!

-

"No work for you!" Good thing I have a habit of pressing Ctrl+Shift+S often. This is so stupid. Of course, nothing in their "common solutions" applies. Of course, the mere fact that they need a "common solutions" page for a license validation BUG should tell them something!

Comments

  1. Nicholas RingNovember 15, 2015 at 1:45 PM

    PIRATE!!! ;-) Just kidding. I suffered from that back in XE and I have a funny feeling that it might have been a 3rd party add-on that was playing around in memory to a degree that the IDE didn't like...

    ReplyDelete
  2. Brandon StaggsNovember 15, 2015 at 1:48 PM

    I use Parnassus Bookmarks and Navigator.  I suppose one of those could be causing the problem, BUT, merely making use of the IDE's plugin features should not cause license validation errors.  I have complained about this before: a license validation system that is so fragile should not be combined with a punitive action when it triggers. The IDE should NEVER shut down without saving work (as it did) or mess with saving features.  It is obviously prone to error and there is no reason to take such a chance at ruining someone's workflow.

    ReplyDelete
  3. Nándor KissNovember 15, 2015 at 1:50 PM


    Some time ago I used a cracked version of Delphi. Cracked version doesn't have this thing...

    ReplyDelete
  4. Nicholas RingNovember 15, 2015 at 3:08 PM

    Brandon Staggs The Add-On I had did some low, low level things (I think) - But those two should be fine.

    An over zealous A/V probing too deep in to the IDEs memory? Just stabbing in the dark :(

    Nándor Kiss Sad sad thing to which you say is true :(

    ReplyDelete
  5. Jeroen Wiert PluimersNovember 16, 2015 at 3:15 AM

    The checks are less buggy now, but I think it's a sin that they made this a "quit Delphi now" feature.

    ReplyDelete
  6. David MillingtonNovember 16, 2015 at 4:55 AM

    Brandon Staggs So far as I know (as the author) neither of those plugins should cause that error. If you're worried, please make sure you're updated to the latest version of each.

    ReplyDelete
  7. David HeffernanNovember 16, 2015 at 5:14 AM

    I highly doubt it's anything to do with the plugins.  I've found the need to do a repair install periodically when facing this.

    ReplyDelete
  8. Jeroen Wiert PluimersNovember 16, 2015 at 9:30 AM

    I've had this numerous times over the years, both with and without plugins. I've a very strong suspicion that the major causes are wild pointer bugs overwriting some state. As soon as it overwrites part of the licensing state (which in my opinion should be write protected as by design it is bound to "quit now"), it quits Delphi.

    ReplyDelete
  9. Dany MarmurNovember 16, 2015 at 11:18 AM

    This is actually the only serious bug I have not suffered from. D5-XE 7... Congrats: me :)

    ReplyDelete

Post a Comment