Update: TokenMaster's Launcher PRO 2.8.0 and NCD / CAFD Tool V0.5.1

TokenMaster's Launcher PRO V2.8.0 is now available.

Change log

Launcher PRO V2.8.0 Build 153
====================
- Added support for E-Sys 3.29
- Added support for E-Sys 3.30

NOTE 1: While it support 3.29, I find 3.29 is too buggy for any useful purposes. I tried fixing some of the stuff, but I gave up and retracted my changes. There's just too many to fix. 3.30 appears to be stable but I just started using it a couple of days ago, I haven't had the chance to fully test it.

If you are not planning on using 3.30, there's no reason to update to this version. 

NOTE 2: I'm holding off on the Premium update for now as I'm contemplating a few changes. As much as I would like to release it, people just won't stop trying to exploit it for their own advantage.

I'm not always around to generate activation code, so I need to device something more autonomous. I just came back and I have zero idea at the moment.

NCD / CAFD Too V0.5.1 Build 201

====================

- Minor bug fixes

NOTE: Please do NOT request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Launcher V2.6.1 PRO and Premium, NCD / CAFD Tool V0.4.0 Update - Updated 11/08/2016

TokenMaster's Launcher 2.6.0 Premium and PRO are now Out.

[Updated: 11/08/2016]
Launcher V2.6.1 Pro and Premium Builds 130 and 122, respectively, are now out. These updates addresses the initial issues found with the previous releases.

Launcher PRO 2.6.0 Build 128
- Added support for E-Sys 3.28.x
- PsdZdata mapping compatibility upgraded to V3.59.4
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- Added FDL Cheat Codes online update
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

Launcher Premium 2.6.0 Build 119
- Added support for E-Sys 3.28.x
- Added CAFD Transalation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7, JRE8 (E-Sys 3.26, 3.27, 3.28) - Enjoy crisp resolution without down scaling your display
- Fixed issue with HKFM_LS. Older PSdZ library and other ECUs do not need to expand CAF, but HKFM_LS does, and is sensitive to delay. Launcher is now modified to only perform translation when requested from the GUI
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

A few notes on these features:

.NET Framework 4.5.2 is now required due to new features added. It can be downladed from this link: https://www.microsoft.com/en-us/download/details.aspx?id=42642

For Premium only. You will be asked to generate a token. I have changed the way token is generated for V2.6.

- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF - I find it annoying that the CAF Viewer defaults to \data\CAF. This is one of the more frequently asked questions I get. CAF viewer opens CAF files, FDL-Editor opens NCD files. They don't mix. CAF Viewer now defaults to \Data\psdzdata\swe\cafd, when Launchers are used.

- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure) - The following picture is self-explanatory.

When previewing or applying changes, the selected item(s) will change color as a visual aide and indicates the status of the code. Blue means accepted, Orange means partially (for multiple code location), and Red means the value is outside the acceptable range.

- Added FDL Cheat Codes online update - FDL Cheat Codes can be updated if it's updated by the author and uploaded to Github repository.

NCD / CAFD Tool V0.4.0 is also now available. PsdZdata mapping compatibility upgraded to V3.59.4  

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Update: Work-in-Progress - Launcher PRO and Premium 2.6

My first blog post after I came back was rather nasty, so I thought I'd post something more like the usual stuff.

I just finished setting up my coding PC after it crashed. I guess it didn't like being idle for so long. Anyway, here's what I'm working at:

Launcher PRO and Premium V2.6.0
- Supports E-Sys 3.28.x
- PSdZData Mapping compatibility: V3.59.4

Premium necessitates generating new token. You'll be asked to provide a PIN and old tokens will no longer work.

Also working on NCD/CAFD Tool with mapping compatibility updated to PSdZData V3.59.4

I hope to get it done in the next 7 days or so. Stay tuned.

E-Sys Launcher PRO 2.5.5

E-Sys Launcher PRO 2.5.5 Build 120


E-Sys Launcher PRO 2.5.5 is now out.

- Added CAFD Translation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7 (E-Sys 3.26, 3.27) - Enjoy crisp resolution without down scaling your Ultra HD display
- Fixed issue with HKFM_LS. Older PSdZ library and other ECUs do not need to expand CAF, but HKFM_LS does, and is sensitive to delay. Launcher is now modified to only perform translation when requested from the GUI


Due to the last item, I had to release PRO first. Premium will follow soon with the same features and fixes.

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO are now Out.

Launcher PRO 2.5.4 Build 115
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Added configurable Cheat Codes selection
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

Launcher Premium 2.5.3 Build 108
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

PRO Only. FDL Cheat Codes are now selectable.

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Running E-Sys and Java 64-bit

NOTE: The following section is experimental and not recommended for general use. Use at your own risks.

Update: E-Sys 3.24 has also been tested with JRE x64

E-Sys comes with its own 32bit Java Runtime Environment (JRE) and since it’s 32bit, maximum memory that can be allocated is 2GB. The runtime uses about 200MB, leaving about 1.8GB usable memory for the application. This free memory must be contiguous, however, before it can be use by JVM. So, just because you have 16GB of RAM, doesn’t mean you can allocate full 1.8GB to E-Sys. This is also the reason why sometimes, it works with 1GB+, other times, you can only allocate 512MB.

Enter JRE 64bit. JRE x64 appears to not have the limitation of JRE 32bit in that I can consistently allocate 4GB of RAM every single time. I only tested with E-Sys 3.27 since I can only find JRE 7 x64. E-Sys 3.24 needs JRE 6. Here are the steps:

1)  Download and install vcredist_x64.exe from this link: https://www.microsoft.com/en-us/download/details.aspx?id=40784
2)  For E-Sys 3.26 and newer Only: Download and install JRE 7 x64 from here: https://mega.nz/#!DN813aCD!B5bLE8yC2RuGRGUfI-yioO8FG5qZUIu5QHunyKEPjFw or from Oracle if you have an account
3) For E-Sys 3.24 Only: Download and install JRE 6 x64 from here: https://mega.nz/#!3YcjVShK!Zq3QH-2_WSCdpRRvNa7Ocikbyp44_bM0aWNtxZOatNs or from Oracle if you have an account 
4) Delete or relocate the content of  the JRE folder under E-Sys (C:\EC-Apps\ESG\E-Sys\jre)
5) Copy the contents of the JRE you installed into E-Sys JRE (from C:\Program Files\Java\jre6 or C:\Program Files\Java\jre7 to C:\EC-Apps\ESG\E-Sys\jre)
6)  Run E-Sys Launcher and configure memory as you see fit.

I can run E-Sys consistently using 3.5 and 4GB RAM allocated to it.

How to check how much memory is allocated to E-Sys.
1)  Open the current log file (usually in C:\Data\Logs)
2)  Search for "javamem".
You should see something like the following:
Java (used/javamem): 17,016,928 # Java (full): 127,795,200 # Java (max): 4,260,102,144 # Process (full/procmem): 486,379,520 # Process (virtual): 5,224,296,448 # Process (virtual max): 140,737,488,224,256


The number in bold (4,260,102,144) is the maximum memory JVM can use, in this case, just a tad bit lower than 4GB.

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher V2.5.0 - PRO and Premium are now available


Change Log:

Launcher PRO 2.5.0 Build 103
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0
- JRE x64 support. It's now possible to use > 1.8GB RAM. I tested 3.27 and is stable at 4GB. See E-Sys Launcher.pdf for instructions on using 64bit JRE


Launcher Premium 2.5.0 Build 97
- Fixed "High Resolution Fix" option
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys Launcher 2.4.3 PRO and Premium and E-Sys 3.27.1 Update

E-Sys Launcher V2.4.3 - PRO and Premium is now available


Change Log:


Launcher PRO 2.4.3 Build 98, Launcher Premium 2.4.3 Build 85
- Fixed issue with failure to load with some system when querying available memory due to corrupted .NET Performance Counter Registry
- "High Resolution Fix" is now always enabled
- Massive addition to Cheat codes, courtesy of dmnc02, Otakar and ruben_17non - Thanks fellas!
- Fixed minor UI issue - Review button tooltip (reported by myfxp)





E-Sys 3.27.1 Notes

I've been using E-Sys 3.27.1 a lot recently and I noticed that it crashes a lot due to a myriad of issues. Something as simple as having the MSM Updated turned on could crash E-Sys. The good news is that MSM update is the last process in coding, so the crash does not pose big problem when coding. It's just so annoying.

Memory, or the lack thereof, could also crash E-Sys. So, when running on default memory settings and trying to code complex ECUs, like NBT, could crash it.

I've never seen this happen to previous versions of E-Sys. It was pretty good at handling exceptions, but 3.27.1 seems different.

Bonus Tip
If you are forced to run E-Sys using default memory settings (512MB), you can help it by moving some PSdZData folders you never use. Some folders you can safely move, so long as you don't own a series which uses them are the series folders inside kiswb. I have F30 so I moved the following folder:
   C:\Data\psdzdata\kiswb\S15A (used by G-Series)
   C:\Data\psdzdata\kiswb\K001 and C:\Data\psdzdata\kiswb\KE01 (used by BMW motorcycle?)
   C:\Data\psdzdata\kiswb\RR01 (used by Rolls Royce)
   C:\Data\psdzdata\kiswb\I001 (used by i-3, i-8)
   C:\Data\psdzdata\kiswb\F056 (used by Mini)

Moving the above folders prevent E-Sys from reading database associated with these series. These databases are read on startup and kept in memory while E-Sys is running, using precious memory.

If you have plenty of RAM and can run at least using the medium settings, then moving the above folders are not required. Again, only do this if you are forced to run using default memory settings.  

E-Sys Launcher V2.4.2 - PRO and Premium

E-Sys Launcher V2.4.2 - PRO and Premium is now available

Launcher PRO
====================
2.4.2 Build 95
- Fixed multi-group parsing of FDLCodes.xml
- Added Cheat Codes Review


Launcher Premium
====================
2.4.2 Build 82
- Fixed multi-group parsing of FDLCodes.xml
- Added Cheat Codes Review


Parsing of FDLCodes.xml as intended is now working properly. I also added a Cheat Codes Review to preview the changes before codes are applied to FDL.

As usual, no request from this page, please.

E-Sys Launcher V2.4.0

UPDATE: V2.4.1 is now out.

2.4.1 Build 93
- Fixed E-Sys 3.26.x compatibility
- Minor Bug fixes

I highly recommend everyone to upgrade to this version.



E-Sys Launcher V2.4.0 is now out!

Launcher PRO
====================
2.4.0 Build 90
- Removed CAFD Remapping Option on the UI. As before, untrimmed CAFD will not undergo further processing.
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Launcher Premium
====================
2.4.0 Build 78
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Here's a small video I made using PRO.

 

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher V2.3.0 PRO and Premium are out

E-Sys Launcher V2.3.0 PRO and Premium are out

Change Log

Launcher PRO 2.3.0 Build 85
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


Launcher Premium 2.3.0 Build 75
- Added Smart, Safe caching - Subsequent reading of CAFD/FAFP will be significantly faster
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


The dynamic Stack Memory allocation is based on available memory at the time of launching E-Sys. Free memory is queried and the maximum allowed value will be sent to E-Sys. This setting is separate from the ones configurable via the main Launcher UI. That handles the Heap memory which is more important to E-Sys (or any Java app, for that matter). How do you know it works? Look at your log files and find "javamem". You should see something like:

Java (used/javamem): 14,295,120 # Java (full): 24,379,392 # Java (max): 1,341,891,328 # Process (full/procmem): 205,340,672 # Process (virtual): 1,491,914,752 # Process (virtual max): 2,147,352,576

The first highlighted value is the Heap and achieved by setting it in the UI. The second highlighted value is determined dynamically and is assigned because I have about 2GB of RAM on this machine.

Note that Heap memory could fail and when it does, you'll see the following error:

The solution is either to restart your PC or select a lower memory settings. Stack memory is more forgiving as it is dynamically managed by the OS.


NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher V2.2.2 PRO and Premium are out

E-Sys Launcher V2.2.2 PRO and Premium are out.

Change Log:

E-Sys Launcher Premium 2.2.2 Build 72
- Added support for E-Sys 3.27.1





E-Sys Launcher PRO 2.2.2 Build 80
- Added support for E-Sys 3.27.1
- Added 2 missing functions in FEM found by valley_nomad

Tested on Windows 7, 8.1, and 10, both 32 and 64 bit versions


If you are interested in E-Sys Launcher PRO 2.x, email me at fxxtokenmaster_at_GMail

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher Premium V2.2.0 Build 68

E-Sys Launcher Premium V2.2.0 Build 68 is out.

Chaange log:
- Added support for E-Sys 3.27
- Added support for FLE in PSdZData
- Added 2 missing functions in FEM found by valley_nomad

Last item is what I envisioned mapping is going to be, when I created CAFD Remapping. A community effort. Because let's face it, if we don't get untrimmed CAFD/FAFP, any new or moved functions, like the case of ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN, will go unnoticed. But, if the community starts testing these new functions and determine what they do, then we'll have a fighting chance. I named these new/moved functions (PfExternalMirrorMaster_1_1_1, PfExternalMirrorMaster_8_8_1, ...etc.) as I know they mean something, I just don't know what they are. So, thank you, valley_nomad, for testing these (previously) unknown functions.

You can find the new build in the usual place. And lastly, please do not request for download link here. Enjoy!

E-Sys Launcher PRO V2.2.1 Build 78

E-Sys Launcher PRO V2.2.0 Build 75 is out.

Change Log:
2.2.1 Build 78
- Added Advanced Optimization JVM options - takes advantage of advanced optimizations available with JRE 6 (E-Sys 3.24) and 7 (3.26 and 3.27).

2.2.0 Build 75
- Added support for E-Sys 3.27
- Added support for FLE ECU in PSdZData
- Optimized library

Tested on Windows 10, 8.1, and 7 - i386 and x64

If you are interested in E-Sys Launcher PRO 2.x, email me at fxxtokenmaster_at_GMail

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys 3.27 and E-Sys Launcher 2.0 PRO

Newest E-Sys 3.27.0 now running on E-Sys Launcher 2.0 PRO. Still Alpha quality but pretty much working. See the following quick demo.

Launcher shown in the video is not out yet, nor is it ready. It will be when I'm comfortable but for now, stick with what you have.

Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding

E-Sys Launcher: C157, F999...etc.

This post will also serve as Frequently Asked Questions regarding different error being encountered while using Launcher.

Suspect File(s)

As of Version 2.0, both Launchers will not load patched/modified files. Some token solution used insecure patch files. Launcher is designed to prevent loading such files.

Resolution: It's advisable to abort launching, then reinstall E-Sys from a trusted source.


Java Virtual Machine Launcher

Your PC does not have enough contiguous free memory.

Resolution: Either restart your PC, or choose a lower memory settings.

Can't change car series, defaults to F999 (Premium Only)
Someone wrote a tool to reset the Launcher, so I had to enforce a default value. Instead of being able to select a series upon installation, a default value is now used.



[C157]  Condition Not Correct. General error.
If you are getting code 157 when trying to open FDL editor, and the description is "Condition Not Correct. General error.", stop playing with the computer's date. Launchers will detect this and will consider it tampering and will refuse to authenticate with E-Sys.

Resolution: Fix date and reinstall E-Sys. 

E-Sys Launcher PRO and Premium 2.1.0 Update

Both versions of E-Sys Launcher has been updated with some new features.

E-Sys Launcher PRO is now at version 2.1.0 Build 68 and can be found in the same usual link.

Change Log:

• Integrated PIN/Token authentication. No more inputting of PIN in E-Sys. The launcher does both validation and takes care of authentication where and when it's needed.
• Added Smart, Safe caching - Reading CAFD/FAFP files is now about 60% faster.
• PSdZData compatibility set to V55.1/15_03_502. New PSdZData Mapping table with updated functions. 

E-Sys Launcher Premium is now at version 2.1.0 Build 58 and can be found in the same usual link.
Change Log:

•  Integrated PIN/Token authentication. No more inputting of PIN in E-Sys. The launcher does both validation and takes care of authentication where and when it's needed.
• PSdZData compatibility set to V55.1/15_03_502. New PSdZData Mapping table with updated functions. 
• Added additional chassis/car series (G-Series, RR..etc.)

Note: Launcher Premium is now in support/quick fix engineering mode, which means no more major functionality will be added in the future. As I mentioned in one forum, I am disgusted by people trying to remove the limitation imposed on the software. I hate being second guessed and I really hate being screwed by fellow developers. There is an unwritten law that we all must abide and screwing a fellow developer is a major offense.

E-Sys Launcher 2.0 - PRO and Premium Feature Comparision

E-Sys Launcher 2.0 PRO vs. Premium

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

NCD/CAFD Tool and E-Sys Launcher PRO 2.0, Now support trimmed CAFD files

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

E-Sys Launcher Pro


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