Both versions of E-Sys Launcher has been updated with fix to the mapping database. E-Sys Launcher Premium is now at version 2.0.5 Build 51 and can be found in the same usual link.
E-Sys Launcher PRO is now at version 2.0.7 Build 59. I changed the link for the PRO.
Additionally, as a result of people selling my software, I've implemented a control. PRO now requires one time activation code. Launcher PRO will ask you for an activation code when you first try to launch E-Sys. You can request for and enter an activation code directly from the tool.
If you are interested in E-Sys Launcher PRO 2.0, email me at fxxtokenmaster_at_GMail
Due to large number of people reselling my tools in China, I decided to completely ban China from using any of my tools, until further notice. Despite me asking these people to stop reselling, it seems there's no way they'd listen. It is quite unfortunate and disheartening, but when something designed for a good cause is misused for personal gain, I have to do something about it.
Sure, I can implement a sophisticated check, activation, server validation, hardware lock, ...etc., but the point is, I was hoping I didn't have to. I was hoping people would do the right thing. Evidently, that is asking too much.
Rather than punishing the entire community for the fault of the few, I decided to just shut these people out. Of course, there will never be a way to do it on an individual level, so the only choice is to ban the entire region.
Those who already have my tools can continue to use them. Those who resell and obtained them somewhere else will have to contend themselves with a faulty version. There's no upgrade path either.
I hope China will be the last to do this, because I can do this to other regions too.
Someone is repackaging my E-Sys Launcher PRO and packaging it as ESysLauncherPROSetup_2.0.0_Build_45.rar. This file didn't come from me. It appears the RAR file is password protected. If you see this file, do not download it for the following reason:
1) It is not for sale and whatever token that comes with it will be blocked and will be useless
2) Build 45 is the first release. The mapping data that came with this build is faulty. Check CAS and see if you get any descriptive text at all. That is just one of the many ECU affected. FEM, IHKA,KOMBI, NBT, CIC...etc. are also affected, some partially, others completely.
If you get the bright idea of updating the mapping data, don't bother. Encryption key is different and will be totally useless.
This is the kind of actions I absolutely abhor, it's despicable. You do something and someone is bound to exploit it.
UPDATE: I've been getting barrage of emails asking for token, or password or decryption key from this build. I don't know any password, nor decryption key, so please if you DO NOT ask me, if you insist on using this build.
I have released both E-Sys Launcher PRO and Premium 2.0 last week. I should have made this blog before releasing it but better late than never.
Here's a feature comparison between the versions of E-Sys Launchers.
The Premium is made specifically for individual and personal use only. For one's normal coding need, the Premium will fulfill 99% of that need.
I have added some limitations to prevent some entities from overusing the Premium. Some people are using the Premium to code for other people and charge a substantial fee. I don't have a problem with that practice, but when these very same people peruse the forum and the community's findings and leverage these knowledge for their business, all the while being too arrogant and not giving anything back, that rubs me off in a wrong way. When your whole coding skills is acquired by reading the forum, you shouldn't be too proud so as to say you are against sharing information, for without the forum, you have zero knowledge. Perusing it without so much as giving thanks to those who deserve it doesn't work well for me.
PSdZdata Mapping - Premium will only have the Datagroups, Functions and Parameter names. PRO will have comments as well.
PSdZdata Mapping Restriction - Premium requires you choose a series for your car. This is used when performing FAFP/CAFD mapping translation. If you open an FA.xml from a different series, no translation will be done. If you open an NCD or CAFD which doesn't apply to your chosen series, no mapping will be done and you'll simply see dots again. The Launcher warns you about the change when you select a series, so take heed.
Note that none of these reduce the functionality of E-Sys. These restrictions are only for PSdZdata mapping and you can use E-Sys the same way as you did before, with or without the Launchers.
"But I have 2 (or insert however many cars you have here) cars, what about me?" - You can change series after 3 days. Or better yet, upgrade to the PRO version. The PRO don't have any restrictions.
"I code for a fee" - Premium isn't for you.
PRO is not for free and is not for a fee either. If you are interested in E-Sys Launcher PRO 2.0, email me at fxxtokenmaster_at_GMail
It's been a long time since I wrote my last blog entry. Anyway, I've seen people getting frustrated with trimmed CAFDs and has started doing unimaginable things with their NCD files. While renaming NCD files sorta work, it should never be done like that. Some CAFDs have very little changes between versions but some have lots. Besides, the reason for updated CAFDs are to fix issues the engineer found. Using an NCD generated from older version defeats the purpose of the new version. If you're going to do that, might as well stick with an older version of CAFDs.
Over the last couple of weeks, I went back and dusted off my trusted tools. First off, I just released NCD / CAFD Tool V0.3. This version now supports trimmed CAFD and FA2FP files.
Taking this very same feature, I added it to E-Sys Launcher PRO 2.0, currently in limited Beta but is in very usable form.
3.26.1 with the Launcher:
Watch it in action:
If interested, send me an email at fxxtokenmaster_at_GMail
E-Sys
Launcher PRO (V1.0.4 as of this writing)is a Next-Generation Universal Token Solution for E-Sys Version
3.22.x and up (except 3.25.x due to bugs with E-Sys). The PRO version is for those who are already using my patchless
token solution.
User Interface
E-Sys Launcher Pro FEATURES 1) Increased Default Memory Allocation. E-Sys needs memory and
lots of it. Default setting is barely enough for simple cars like the
F20/F30s but is hardly sufficient for cars with complex ECUs (F15, F56...etc.). Most
coders do well by changing this settings but some aren't aware of this.
While it can be easily changed, E-Sys doesn't check the value and if you
set it too high, will prevent E-Sys from launching again. The PRO version
offers two additional settings over the Premium. Max and Custom.
2) Enhanced Overall System Stability. By ensuring E-Sys
gracefully shutdown and JVM properly recycled at the end of each coding
session, your system is kept optimized for the next session. Stock
E-Sys, more often than not, does not fully terminate when you exit the application. JVM lingers in the
background, hogging and leaking memory. The issue becomes more apparent
when you start/shutdown E-Sys numerous times, to a point where system
restart is required. The PRO version also adds additional setting that boost
stability of background tasks spawned by E-Sys
3) Zero E-Sys Configuration. With the launcher, there's no need
to reconfigure E-Sys to use different Soft tokens. Those with OEM or my
patchless token solutions can keep using it by clicking the Blue E-Sys
icon, while using the launcher will use the assigned token, all without
having to fiddle with the settings. The order in which you install E-Sys and the Launcher does not matter, as nothing gets modified.
4) Personalized and Individualized Token. The soft token you
create from existing patchless tokens will only be usable on your own
machine. It cannot be shared and reused on another machine. This also
means that someone can't sell you a token and expect it to work. With
the built-in Token Generator, creating soft token is as easy as pressing
a button. No fiddling around with some command line tool and creating
XML data by hand. The PRO version adds the ability to use patchless
tokens without having to extend/regenerate it.
5) Absolute Security. It became pretty easy to hack CAFD
recently. With the launcher, the risk of using hacked CAFD is reduced to
0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys
does, stopping it dead from its track. Coupled with individualized
token, there's no need to worry about hacked CAFD, even the ones that
are re-signed and encrypted. BUT, you have to have an unpatched E-Sys. Patched file works by ignoring digital certificates.
6) No-Touch Post Deployment. With the launcher, all you need is
to install E-Sys. Already installed E-Sys? No problem, just use the
launcher and it just works without adding, modifying, or editing
anything. Upgrading E-Sys? Go ahead, launch it and see it work.
7) Supports Multiple Versions/Side-by-Side Setup. If you have
multiple versions of E-Sys installed on your machine (like I do), the Launcher PRO
can be configured to launch each one with different launch mode. Even if you only have a single instance of E-Sys, it can be launched 4 different ways.
8) Supports 4 Different Launch Mode. The launcher PRO supports
different launch types. This means that you can use the launcher with an
OEM Soft Token and just take advantage of the higher memory settings or
enhanced stability, or both.
Note: Do not mix and match different solutions, it's not generally
recommended and could elevate the security risks the launcher is trying
to minimize.
Feature Comparison
Warning about E-Sys 3.26.x: Be warned that 3.26.x is not as stable as 3.24.3 and you may experience error especially when flashing, with or without the launcher. 3.25.x is worse. I am still using 3.24.3 for this reason.
Interested? Send me an email at fxxtokenmaster_at_GMail
My patchless token solution brought something new and something relevant when I introduced it. And now, E-Sys Launcher Premium, once again, changes the way we use E-Sys. When a simple patchless solution just doesn't cut it anymore, E-Sys Launcher Premium brings a whole new set of feature to the table and is the only true innovative contender to my own patchless solution.
Features:
- Increased default memory allocation. E-Sys needs memory and lots of it. Default setting is barely enough for simple cars like the F20/F30s but is hardly sufficient for cars with complex ECUs. Most coders do well by changing this settings but some aren't aware of this. While it can be easily change, E-Sys doesn't check the value and if you set it too high, will prevent E-Sys from launching. With the launcher, the memory allocation is doubled.
- Enhanced overall System stability. By ensuring E-Sys gracefully shutsdown and JVM properly recycled at the end of each coding session, your system is kept optimized for the next session. Stock E-Sys, more often than not, does not fully terminate. JVM lingers in the background, hogging and leaking memory. The issue becomes more apparent when you start/shutdown E-Sys numerous times, to a point where system restart is required. With the launcher, this is unlikely to happen.
- Zero E-Sys Configuration. With the launcher, there's no need to reconfigure E-Sys to use different Soft tokens. Those with OEM or my patchless token solutions can keep using it by clicking the Blue E-Sys icon, while using the launcher will use the assigned token, all without having to fiddle with the settings.
- Personalized and Individualized token. The soft tokens you create will only be usable on your own machine. It cannot be shared and reused on another machine. This also means that someone can't sell you a token and expect it to work. With the built-in Token Generator, creating soft token is as easy as pressing a button. No fiddling around with some command line tool and creating XML data.
- Absolute Security. It became pretty easy to hack CAFD recently. With the launcher, the risk of using hacked CAFD is reduced to 0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys does, stopping it dead from its track. Coupled with individualized token, there's no need to worry about hacked CAFD.
Note: Do not mix and match different solutions, it's not generally recommended and could elevate the security risks the launcher is trying to minimize. My patchless solution can safely co-exists with the launcher, however, but it won't be loaded while the launcher is running. The patchless solution will also be replaced soon.
