Board index » delphi » Re: Activation-removal feature - how about Escrow?

2006-11-29 01:41:16 PM
delphi34
Didn't you write?:
mobo died. Refused to even beep despite me taking out every
darn component, except the power.
So, I pick up a new mobo (plus CPU and memory, since the
old CPU was a socket 478 one and 478 mobos aren't worth
investing anymore) yesterday. Then it hit me. Since
I've changed *ALOT* of components, I thought, "Oh {*word*99}.
WXP is gonna not like this." I was right. Had to
repair-install and was thinking of reactivating it
when I remembered MS updating their EULA on OEM systems.
Initial clarification from a MS techie? Replacing
the mobo means I no longer can use this XP OEM. I
need to buy a full fledge product. The same thing
with Office (also an OEM product). So right now,
I'm stuck with software that I can not use (but legally
purchased) and will have to buy the full product
of the Operating system AND Office (both software
combined costs more than the system itself!).
I am *extremely* PO'd. Unfortunately for me,
the co-worker isn't that Linux-literate and
thusly I am not able to hobble a decent Linux/KDE
system for her.
Did I mention that I *HATE* this new Activation
system? I did? Oh.
*sigh*
Edmund
 

Didn't you write?:
rather, that in relationship to the EULA. (Read: Windows XP, OEM.
Replaced mobo. 'nuff said.)
To be quite frank, I have no problems with companies wanting to
protect their products. I don't like activation systems.
But with forced to using the product (i.e. Windows), I have
no option but to go ahead and proceed with the activation.
What I DO mind, and I do hope Borland hears this, is the
EULA and its constraints/restraints with regards to the
activation system and particularly to OEM systems. I
*hate* reading EULAs. it is always based on interpretation
by lawyers and since I ain't one, I don't know if my
interpretation is right. And now that MS has taken
precedence in 'amending' the EULAs for XP, it makes it
even harder.
Thankfully, this WON'T be the case with Borland since
anything Borland sells *ISN'T* OEM and thusly, I'll
still be able to activate to my heart's content provided
it's only ONE system. At least, this is what I'm
inferring from this thread.
The old Delphi7 registration/product activation really
bites. Reinstall it, you need to go over the
registration again. it is irksome. The last time
I had to re-install my Delphi 7 was when my W2k BSOD'ed
badly and refused to boot. That irked me a lot.
But I digress.
Just my $0.02.
 

On Wed, 29 Nov 2006 13:41:16 +0800, Edmund <XXXX@XXXXX.COM>writes:
modules I had (swapping the "bank A" and "bank B" pair), and I had to
re-activate. This occured after the bios was reset, and for some
reason internet didn't work, so I couldn't do it automatically.
However, since I had to activate before logging in, I couldn't fix the
network settings to activate it!
So I had to dial up manually and talk to this guy. Best part imho was
when he asked me why I was activating... o.O Does he get people
calling the activation line for fun at 10pm a tuesday evening or
what?!
- Asbjørn
 

Call Microsoft and tell them that your are reactivating because you
had to reinstall your computer after a hard drive crash, they WILL
activate it, even if you changed the hard drive out. I activated this
way after replacing a hard drive and adding memory, but I needed
activation because it was a new install, not the same install on the
same hard drive.
They activated both Windows XP and Microsoft Office for me
without a problem.
As to the person below, I am sure Borland/CodeGear would want to
know why you are activating by phone if you were calling them, and
there was a heavily tested internet/direct dial-up option available in
the software.
Microsoft activations seem to have a limit (have to call after you
activate xxx times in xxx months, etc.), but it seems to decay off
and reset about every 6 months or so.
- Nate.
"Edmund" <XXXX@XXXXX.COM>writes

Nick Hodges (CodeGear) writes:
But, as i always say, Google is your friend.
Or in the case of software vendors, your worst nightmare.
In a simple search, nearly 700.000 sites showed up containing cracks
for Borland software.
--
 

Dave Nottage [TeamB] writes:
BDS Pro, Enterprise, Architect, you name it, it is there, cracked and
ready to use for those who want that kind of thing.
Me, for myself, i stay with my SA, which i will be renewing this month..
--
 

CodeGear did nice things to protect it by changing/updating the registration
DLLs when Update 2 was released, but there were cracks a day later.
I actually reported a few sites to that Borland email address the have
(or used to have) up. Doesn't seem they wanna bother with it.
All the ones I reported to Microsoft have been taken down, however.
- Nate.
 

Marco Caspers writes:
astalavista.box.sk/cgi-bin/robot
shows that the crackers are surprisingly uptodate.
( WARNING: Objectionable images may display in the sidebar )
 

insert name writes:
<snip>
as well, don't even know if they still exist, haven't been there in a
long time cause i buy my software.
--
 

("registered to Mr Smith ACME co."), that is the only way to restrict the
passing around of codes, as honest user won't want to see their good
name on files distributed all around the web.
But of course that won't help you in any fashion against keygens or
cracks that'll just remove the activation checks.
Eric
 

Eric Grange writes:
right? Otherwise, how would you make the connection between the name
and the number...?
--
Nick Hodges
Delphi Product Manager - CodeGear
blogs.borland.com/nickhodges
 

wrapped with registered downloads of update packs (every end-user gets a
slightly customized pack).
This way, if I download several updates, back them up somewhere, and at
a later point decide to use those backed up updates to reinstall,
they'll still contain my name even though I never had to reconnect to
the web.
different embed in different screens, and leave some in there that are
unused initially, but that a future update could make use of).
There are just two goals that should be aimed for, because they are the
only ones realistically achievable IMO:
1) Using original software should be more convenient than using a
cracked copy: if whatever activation scheme is more bothersome than
going on google/whatever and getting a cracked a version, you've lost
your time implementing the activation scheme.
2) Using cracked software or making your copy available should be made
/shameful/ in some fashion to avoid casual piracy. Like risking having
your name end up all around the web, or having a mention that tells any
real-world observer that you're not using software legally. You won't
scare many with lawsuits (everybody knows they're impractical), but good
old shame can still reach (those that matter anyway).
Eric
 

In article <45744333$XXXX@XXXXX.COM>, Nick Hodges (CodeGear)
writes:
(the ones we use): the customer fills in the order form and when they
press 'Buy' the CC is validated. SWREG/Plimus call our website with a
URL including the user name and product and our server delivers them
the next serial number and name-derived activation key which they
forward to the customer as part of the email receipt.
--
Tony Bryer SDA UK 'Software to build on' www.sda.co.uk
Shareware Industry Conference 2006 sponsor www.sic.org
 

Tony Bryer writes:
--
Nick Hodges
Delphi Product Manager - CodeGear
blogs.borland.com/nickhodges