Launcher PRO 3.4.0

Launcher PRO 3.4.0 Build 191 is now available.

Change Log
====================

3.4.0 Build 191

- Added: Support for 3.33.4 64bit Only

- Updated: CAFD Mapping compatibility level: 18-04 i-Step

- Removed: Required root certificate

- Minor bug fixes

NOTE: Authenticode RSA certificate is no longer required, but installing RSA Certificate with "EB06BA22 6FB31CD3 787A2ABB 84E71D61 F1CEA5B9" thumbprint to the Trusted Root Certification Authorities store on current user is still recommended. This certificate can only be used for Authenticode purposes and cannot be used to create intermediate or subordinate, or end entities certificates.

  To Install Certificate:

via Command prompt: LauncherPro3.exe installcert

via Windows: Right-click LauncherPro3.exe > Properties > Digital Signatures > Details > View Certificate > Install Certificate and install it under Trusted Root Certification Authorities store

  To Delete Certificate:

via Command prompt: LauncherPro3.exe removecert

or use mmc.exe and Certificate Snap-in. See https://tokenmaster.blogspot.com/2019/05/code-signing-certificate.html

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

Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication. 

Google Authenticator is required when using dynamic activation and when updating the Launcher.

NOTE: For WIndows 7 users, if you're having problems with validation/activation, Windows is probably not using TLS 1.2 to communicate to my site. Check the following registry key, as shown in the image:

First thing to do is ensure all updates are installed. If you don't see TLS 1.2 key, create it, then create the Client key under it. The two DWORD values must exist and should contain data as shown in the image. Restart WIndows and try again

Launcher PRO 3.1.0

Launcher PRO 3.1.0 Build 116 is now available.

Change Log
==========
- Added: Support for 3.32
- Added: *In-App Activation
- Added: *Dynamic + Static activation
- Minor bug fixes

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

Launcher PRO now uses Time-based One-time Password for authentication. Google Authenticator is required when using dynamic activation and when updating the Launcher. It is critical that your mobile device's system time is up to date. Any discrepancy greater than 30 seconds will result in failed authentication.

Dynamic activation allows you to use a different PC for at east 7 days without using your limit count. Dynamic activation requires an active Internet connection for core functions.

I realized I have not put enough information out there, so I'll take this opportunity discuss the difference between static and dynamic activation.

Static Activation - This is the classic way of activating Launcher, but the Launcher now does everything for you, instead of you downloading and providing the code. Everything else stays the same.

Dynamic Activation - As previously stated, dynamic activation allows you to use another PC without using up your activation limit. Dynamic activation is most useful when using a temporary PC, or your friend's laptop. This is a temporary activation that expires in 7 days and will require you to re-login again.

For your main workhorse, static activation is recommended. It doesn't require an active Internet connection.

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

Launcher PRO 3.0 - Available this weekend

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

E-Sys Launcher 2.0 - End of Life

Launcher 2.0 Premium and PRO has reached end-of-life phase. No more updates, no more fixes.

The past couple of months, I've spent significant amount of time modifying Launcher PRO, when I should have never bothered. I just wasted numerous sleepless nights for naught. It has been proven, once again, that an enterprising entity would go to such great lengths to earn a buck, so much so, that they shamelessly stole and reuse my code. What's sad is that some people actually support these individuals.

I wrote Launcher Premium for enthusiasts, for personal-use, to learn coding, not for someone to resell it. It was free, but people manage to sell it. I'm not going to let these individuals earn money at my expense.

And precisely for this reason, that I am terminating Launcher 2.0. There will be no update to Launcher Premium. There will never be  Launcher Premium 3.0. It's done, it's over.

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.

TokenMaster's Launcher PRO 2.9.4 Build 218

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

Change log

Launcher PRO V2.9.4 Build 218
====================

- Added EST Migration tool for older tokens

- Fixed FA Activation hanging

- Fixed minor certificate/EST issue

- Minor UI tweak

As mentioned in my last blog, extended tokens with expired original one need to be migrated as I would need to compromise a lot to support it. Migration is quick, and very similar to the EST Extender tool. You will need the original tokens. This means that, if your token have expired and you didn't get to extend it, this is your chance to reactivate it. It must have expired within the last 12 months, though.

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.

Some Launcher V2.9+ Notes

These past few days/weeks have been specially hectic and chaotic. I've held off issuing tokens and codes since I was working on something. And what I thought and planned to be a seamless, painless upgrade, turned out to be anything but. V2.9.0 was a disaster,V2.9.1 wasn't any better, V2.9.2 was barely acceptable and V2.9.3 showed a glimmer of hope.

It took a friend from the other side of the world to get it back to an acceptable level. Working but not perfect.

I'd like to put out some guidelines for existing users:

•  Those who now use the new EST format, you should be OK with any V2.9+ version
•  Those who have the older format, still valid, non-extended tokens, upgrade now and extend your tokens using V2.9.3
• Those who own an already extended tokens, please do one of the following:

                - If your old token is still valid today, please revert to the original token and upgrade to V2.9.3, then extend your token.
                - If your old token is already expired, but is already extended, stay on V2.8.1 for now. The upcoming version will have a token migration tool which will help you move to V2.9+.


I tried to accommodate all scenarios to make it all seamless. However, supporting extended tokens requires me to relax security a bit. One that I'm not willing to compromise with. So, I opted to come up with a migration tool instead.


I promise you an easier, more stable, future versions coming, both PRO and Premium alike. It is taking me a while to bring Premium up to par with the PRO, but it is what it is for a very good reason.


And....Happy days are coming!!!

Some BMW gods smiled upon us. I have to look more into it and see what exactly is entailed, but it does look like your shiny new G-series, and those on newest iStep, is about to be a bit happier. Launchers have been on V59.4 for quite a while now. It's about time to move to V61 at the very least, V62 maybe, if we get ever so lucky...Happy days, happy days.

Update: TokenMaster's Launcher PRO 2.9.3

UPDATE: Launcher PRO V2.9.3 is now available

- Fixed minor certificate/EST issue

Thanks to botho for providing the environment for troubleshooting. It was a tremendous help.

UPDATE: Launcher PRO V2.9.2 is now available

- Fixed minor certificate/EST issue

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

Change log

Launcher PRO V2.9.0 Build 173
====================

- Increased allowed memory allocation for 64-bit JRE up to 8GB.

- Added another way of using 64-bit JRE by using "jre_x64" for folder name. This way, 32-bit JRE can remain untouched.

- Main window will become 65% transparent if a child window is open. This enhances the contrast and visibility of child windows. (See image below)

- Minor UI tweaks

- Minor security changes

- Removed support for 3.24 and 3.26. Minimum supported version is 3.27

Figure 1: Semi-Transparent main window

Majority of the work done on this version is not visible. Initial support (not available yet) for online activation has been laid out and will be enhanced further in future releases. These changes will trickle down to Premium as well.

I encourage anyone who's using PRO to upgrade to this version. This version is a little bit more stable and secure.

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: TokenMaster's Launcher PRO 2.8.1 and NCD / CAFD Tool V0.5.2

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

Change log

Launcher PRO V2.8.1 Build 155
====================
- Added support for E-Sys 3.30.1

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 or 3.30.1, 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.2 Build 203

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

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

Update: TokenMaster's Launcher 2.7.1 Premium and PRO

TokenMaster's Launcher V2.7.1 Premium and PRO are now out.

Change log

Launcher PRO V2.7.1 Build 148
====================
- Fixed "Unknown Error" when retrieving cheat codes
- Improved Launcher-E-Sys communication
- Reduced memory usage
- "Code Default Values" button renamed to "DO NOT USE!!!" ("VERWENDEN SIE KEINE!!!")
- Minor bug fix


NOTE: PRO 2.7.0 Build 142  was Not released

Launcher Premium V2.7.1 Build 135

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

- Fixed "Unknown Error" when retrieving cheat codes

- Simplified Token generation. PIN is the only required information now.

- Improved Launcher-E-Sys communication 

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.

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