Activation File Delphi 2010 .slip 11
Patrick Fog
I've successfully copied the files from these folders to a thumb drive and moved them to a new computer. Note that part of the registration information is the local computer name, so in order to work on a different machine (or a clean Windows install on the same machine) the computer name needs to stay the same. Just name the computer the same, copy the .slip files to the same location on the new machine, and then install Delphi/RAD Studio.
I have Tokyo Starter installed in a Win10 vm, along with a number of other Delphi versions. I fired up the vm, and ran Starter -- it worked no problem. I let Windows do some updates, then ran Starter again -- and again no problem. I don't know what to think. Is it possible there's some corruption in your Tokyo install? What makes you think Emba has withdrawn the Starter license?
That's a pretty global statement. But again, what makes you think the Starter license has been withdrawn (for everyone)? So it "doesn't work" -- did you get some kind of message (error or otherwise)? Have you heard from others who've had the same problem? If so, did they get some kind of message?
I had a similar issue in that I had a catstrophic failure that destroyed my Desktop PC HD, I had the Tokyo Promo Starter edition installed and all the serials backed up on NAS, but I can no longer activate the Starter Promo license even on the same PC that has the same name. What is the point of an license that never expires if you can't activate / register it?
Now support tells me the Starter Promo registration limit is reached, 3 Registration limit, even though I am trying to re-register / re-activate on the same PC. I gather the problem is that I have re-installed it more than once on either Desktop or Laptop.
I got some advice that I should have had the *.slip files backed up as well and ready for restoration, they are stored in the hidden %ProgramData% folder. I've done that for the laptop now, I suppose that will get blocked as part of a future update.
It is possible the installation is detecting a corrupted or outdated license file. Either because of previous version serial numbers you have registered that has no subscription or previous trial licenses you have used that is being detected by the registration.
Install finished. Set up my library paths. Installed madExcept. In the process of installing my components and Delphi shut down, Emb error web page displayed. ONLY thing I had installed was madExcept (NOT a new version, old version).
Download and install telerik fiddler classic, set it up so it (and you) can watch all the https traffic. (tools/options/https)
And see what is getting sent out, and coming back when you fire up delphi.
Despite the fact that the installation was identical, it took just as long as a fresh install. But never mind that. Once finished, I launched XE4 expecting to be presented with the registration/activation wizard to register and activate the new serial number.
But at least I could see that, indeed, my XE4 installation was still licensed using the old license serial number. Not my own one. Not the one used to actually install the product on this most recent occasion. And no, there were not two licenses present for XE4. Just the one.
After a bit more digging around on the internets, I found a reference to the location of some other .slip files, in ProgramData\Embarcadero (I can only think that the one in the License folder of the installation itself is just there for decoration?)
Hazaa! Finally, I was presented with the registration and activation wizard, already filled out with the correct, new license serial number, and was able to finally register the product and active my license serial number against my EDN account.
Oh well, at least what should have taken 30 seconds or a couple of minutes, at most, only took the best part of TWO HOURS! (Now that I know about those additional .slip files, it will be much quicker next time of course, as it will be for you, dear reader ? ).
Upgrades to the past view versions are only available to holders of licenses to the immediately prior 3 versions iirc. 1 further version usually remains eligible for a few months. As of now, If you are a Delphi 2009 or earlier user and you want XE4, then you have to buy a new user license.
Problems with the licensing system on the other hand have only gotten worse over the years since the introduction of activation. This particular one probably existed before but this was the first time it bit me.
I am using Lazarus v3.10 on Ubuntu 12.04, (Code Typhon distribution), works great. I left Delphi at version 6, so cannot comment on the starting speed. One of the item that bothered me in earlier versions of Lazarus versions F12 toggling problem, now it is fixed. The docking of the windows worked great too, IMHO, much better than D6. I am not familiar with the facilities of the latest Delphi, guess some of us may require to stay Delphi because of the new features, or it may be a corporate decision?
If you are a current/returning parent, we have already created an account username (usually your email address) and password for you. If you cannot remember or do not know your username or password, email us at help...@delphian.org
After getting a lot of the basics down, we are redoing our CAD so we tweak our design using what we've learned. So we have a few sub-assemblies built that we are going to use to make the final assembly easier and quicker to put together. The problem is that we are trying to "save a mirror assembly" for a rack-and-pinion lift and we end up with a scrambled assembly with a bunch of warnings.
Okay, I understand what you are doing now. I am not a big fan of the mirror components command, especially when it involved mechanisms. That might just be me, being too particular about how the assembly is structured. I'm not exactly sure what the issue is at this point without seeing the model itself. Is there any chance you can share the model via your Windchill project or some other secure file sharing mechanism?
Hi, sorry about getting stuck in moderation. I saw your post on chief delphi and came back to find it. Can you share screen shots of the model tree and graphics before and after the mirror component operation?
We tried it again to make a picture for you and it worked correctly this time, so I'm not sure what was happening. It didn't work many times before that! We have the two gears and a rack-and-pinion that are set up as mechanisms. They did not carry over to the mirror, though, and it didn't like the servo horn so we told it to omit it.
When we add these to the drive train, we are not how sure to connect them into one larger connected lift (see second picture). When we connect them by a Tetrix piece between the two arms that rotate up and down using a coincident constraint on a couple of the holes, then they either work for a little while and then one of them slips apart or the entire arm becomes stuck and won't rotate.
b1e95dc632