Launcher PRO 3.2.0

Launcher PRO 3.2.0 Build 144 is now available.

Change Log
====================
3.2.0 Build 144
- Added: Support for 3.33.0 32 and 64bit
- Added: Support for 3.32.2 32 and 64bit
- Updated: CAFD Mapping using 17-11 iStep as base for greatest compatibility with the newest PSdZdata
- Minor bug fixes

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store


Looks like 32bit is going away real soon. 3.33 gives you warning when using the 32-bit version.  This version still supports both 32 and 64bit.



NOTE: Please Do NOT use the comment section to request software. 

Launcher PRO 3.0 - Available this weekend

All-New Launcher PRO 3.0 - Available this weekend. See www.fxxtokenmaster.com for details...

TokenMaster's Launcher PRO 2.9.6 Build 255

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

Change log

Launcher PRO V2.9.6 Build 255
====================

- Added support for E-Sys 3.31.0

- Migrated to full 64-bit architecture

- Added "Check for Updated Version"

- Minor Bug Fixes

First of the few online features. Check for new update on startup. If an update is available, the icon will change its color to blue. You can then click on the Update icon to open a browser pointing to the update location. 

This version is full 64-bit architecture. I'm not sure how many are still using 32-bit version of Windows, but the new components I added forced me to select either 32-bit or 64-bit, there's no flexibility. I chose 64-bit.

The V1 EST Migration tool was meant to only migrate previously extended active tokens. People have complained and they wanted to extend an already expired token. I made it so a token can be extended IF, and only IF, the new end date is still a future date. Typically, this is 1.5 additional years. SO, if your token expired 19 months ago, it can't be any more expired than that.

  

NOTE: I just came back from a short travel. I'll start catching up on my emails.

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: Launcher PRO V2.6.2

TokenMaster's Launcher 2.6.2 PRO is now Out.

Launcher PRO 2.6.2 Build 135

- Added ability to load Developer-signed CAFD files. Signature must be properly calculated for this to work. Tampered files are still blocked.

Launcher was designed with security in mind, not an after-thought. That being the case, we do have some brilliant minds out there, and allowing a modified, properly vetted, CAFD file can be beneficial. Starting with version 2.6.2, CAFD files properly signed with developer certificate and correct digital hash will be allowed, but ONLY IF the user chooses to do so. So, how does this work? Let's start with the following image:

Default is Not Allowed. This setting is not saved, so every time the Launcher starts, this is the default. You get the PSdZ error above, whenever a modified, or in this case -developer-signed, CAFD is requested.

Now, when you click on it, you'll get the following message:

You need to acknowledge the message, and understand that from that point forward, everything you do can have a catastrophic result. The button will turn Red while this setting is active. You can turn this on or off at will, and you will get the same message every time it is turned on.

Be careful when loading developer-signed CAFD and do not share it if you encounter one. And I hope nobody abuses this feature. 

NOTE: Please do not request via the comment section. I do not monitor the comments actively nor will answer any requests from this blog. 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.

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.

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 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 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

NCD / CAFD Tool V0.2.1 Alpha

Just realeased a new version of NCD/CAFD Tool, now with search function added on FA/FP Viewer.
 No pictures this time.

Enjoy: NCD/CAFD Tool V0.2.1

FDL Coding on my BMW F30

FDL Coding Demonstration using my EST Software Token, done on my BMW F30. The video is meant to help those who are quite new to coding their BMW F-Series cars. This is how I do it, of course, I learned from people in the forum too.

Check it out, let me know what you think:

Enjoy!


If you're interested in obtaining a software token, send me an email: fxxtokenmaster(at)Gmail

TokenMaster's EST Software Token Demo

I made a video showing how my EST Software token works. Check it out and let me know what you think :)

If you're interested in obtaining a software token, send me an email: fxxtokenmaster(at)Gmail

EST Software Token

As any other software architect/developer, I always crave for new version of a software. I'm excited to learn of its new feature, and E-Sys is no exception. Only caveat, I needed a new PSdZ and a new software token. I learned that somebody was selling a token for some amount and I thought it was exorbitant compared to what it can do. It's relatively cheap, don't get me wrong, but I wasn't ready to pay for something that cost that much and does very little. So, I looked into it and there are probably a hundred ways I could have done it but I settled on one method, which I think would be the best and would give me the greatest flexibility. The result? An EST Software token that doesn't require modifying any of the stock files. A Software token that can be used without modification across several versions. One file, that isn't version-specific.

So, I went and ventured. By mid of August, I was ready with my file. I tested it with my own car. I wasn't worried because I know, the token is only necessary in allowing FDL coding. The token have nothing to do with the actual programming. And I made sure to not change anything I didn't have too. I love my car and which is why it's hard for me to trust somebody else's work. I can never trust something without me fully understanding what it actually does, or what has been done with it and what it's weaknesses are, if any.

The day I was about to release my token, I came across a posting at Bimmerfest that claims to be selling a token for a cheaper price. It was a guy from Korea. I was lucky enough to be able to check it out and downloaded the file. One look at it and I knew I was never going to use it. It is patched, and the certificate was custom generated using his own CA. This was one of the method I thought about and had I been too lazy, would have implemented the same. The method that was used entailed modifying the Crypto module that will render signature and hashing matching unnecessary. I knew it will work but I crossed this method out early on. With it, it's possible to modify a CAFD, distribute it and before you know it, we'd end up with lots of dead car. Why? Because somebody will exploit this and I guarantee, distribute it maliciously with the intent of spreading harm. Color me paranoid, but I worked in the security industry for too long to trust a seemingly innocent file. BMW thought a great deal on securing their files and I wasn't willing to start ignoring the benefit of a signed and secured document.

Back to the software token. While I'm confident that my token works, I was also late in the game and I needed a leverage. I asked for testers and I chose the testers carefully. I made sure they all belong to different continents to cover as much timezones available, and I was lucky to achieve this goal. All testers were great and some actually did more than I expected and I really appreciated that.

So anyway, it was a huge success for me -and for the coding community -although a lot of people will never realize this.

Oh, and that other guy who also sell tokens? That's not the end of it. I'll get back to him in another post.