Launcher PRO 5.0.1

 Launcher PRO 5.0.1 Build 36 is now available

Launcher PRO V5.0.1 is rewritten from the ground up for Windows 10, 11 64bit only on bare metal machine, meaning, no virtual machines. Supported Versions are 3.35.0, 3.36.0, 3.36.1, 3.36.2, 3.38.2 64bit only, with more to come.

Version 5.0 supports both CAFD versions 1.0 and 2.0. Slowly, but eventually, BMW is moving to online signing all coding data, starting with Coding 2.0 (SP2021), and now Coding 3.0. Signature methods for these CAFD uses RSA 2048 to RSA 4096 and Elliptic curves (ECCP 256 – ECCP 521. These will be very limiting in the future. As of the latest PSdZ data, Launcher PRO V5 supports online signing of known CAFD using authenticated keys and proper coding proof stamp. I'm probably letting off more than I should, but we'll get there eventually.

Launcher PRO V5.0 sports streamlined modern Metro UI. There are 5 selectable themes to choose from. Add as many supported apps as possible and double-click when ready to run.

Launcher PRO V5.0 makes Google Authenticator optional, but is very convenient, so might as well use it. All Time-based One-time Password generator Authenticator, i.e., Microsoft Authenticator, are supported, not just Google Authenticator. More importantly, no more PC activation. Launcher PRO V5.0 is no longer tied to a particular PC. Use anywhere, anytime. It's just like the old dynamic activation, but unlimited.

 

Launcher PRO V5.0 departs from its predecessor in handling KIS database. It's now an Opt-in model where you have to choose which KIS is loaded, as opposed to Opt-out model used in the old version. At least one KIS must be selected

Settings can be temporary or can be applied every time. Either way, you have total control

FAQ:

Q: Can I install on 3 PCs?

A: Yes. There's actually no limit on the number of PCs, so if you have 5 PCs, go ahead and install it on all 5 PCs. The only limitation is that only 2 PCs are active at any given time, so if you move to the 3rd or so PC, you just need to authenticate again.

Q: How long is the license?

A: 3 years is the standard length of the license with no PC limitation

Q: My account says I activated 2 PCs and cannot activate anymore

A: Ignore the website. It was built for V3.0 and I can't update it until V3.0 dies. It will only show the first 2 codes, but really, it is meaningless for V5.0. There is no static or dynamic activation in V5.0

Q: Can I activate more than 1 PC?

A: Err, I just said, there is no static, nor dynamic activation in V5.0 :)

Q: I have a V3.0 license, can I use V5.0?

A: Updates are free, and V5.0 is and upgrade to to V3.0, so yes, you can.

Q: What happens to my V3.0 license?

A: Nothing. It will be as is. If you get a new license now, you will have an extended license. So if you have a year left on the old one, you will end up with 4 years, total.

If you still have active key/s, head out to https://www.fxxtokenmaster.com and grab Launcher PRO V5.0

Launcher PRO 3.7.0 and Website Update

Launcher PRO 3.7.0 Build 315 is now available.

Change Log

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

3.7.0 Build 315

- Huge improvement in CAFD processing (BDC, NBT and MGU in the low 2s)

- Better, more accurate CAF mapping and translation

- Significant reduction in memory usage

- Improved 32-bit app performance and stability

- Better handling of low memory condition in 32-bit app

- Fixed: Bug in JNI component that was introduced in V3.2+

- Minor bug fixes

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

This is a must-have update. It's more stable all around. 32-bit app has been causing low-memory condition, resulting anywhere from failed mapping to app crash. I put extensive work on this build to significantly reduce memory usage, improve stability and enhanced the performance of the mapping module. The following image shows the timing when opening HU NBT and BDC_BODY CAF.

Like the new graphic, I'd like to call this the Concept 4 Edition. Like the Concept 4, the Launcher is just leaner, meaner and faster all around.

To fully appreciate the improvements, use the 64-bit versions. It's just way so much better. When using 32-bit versions, expect the Launcher to fallback to slower method most of the time due to memory constraint. It's no slouch at all, but it's nowhere near the performance it can achieve when using 64-bit versions.

Website Update

My web host has been doing changes to their infrastructure, causing unintended side-effect on my app. I noticed a couple of days ago that validation has been failing, and upon further investigation, found that my web host did drastic settings changes which caused a critical function of my web app to fail. I scrambled to find a solution and worked around this changes, since they won't acquiesce to reverting the changes. Anyway, I'm glad to announce that I rewrote the affected portion of my website, so login/validation is working again. 

If you have been experiencing problems recently when trying to login/activate, please try again and let me know if the issue persist.

**Don't use the comment section to ask where to get it and stop posting your email addresses

Launcher PRO 3.6.0

Launcher PRO 3.6.0 Build 288 is now available.

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

3.6.0 Build 288
- Added: Support for 3.34 64bit Only
- Improved PSdZ Handling and Translation
- Minor bug fixes

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

V3.34 is really interesting, but appears to be an indication of how things are, going forward. The easier way to deal with it would have been to provide an alternate REST API for signing and encrypting NCD, but I don't believe in encrypting user's data.  It's my NCD, I'd like to not be locked out of it, so I chose the harder way. NCD files remain not encrypted. Properly signed, but not encrypted.

It appears to be well-coded and stable. I like this version a lot.


**Don't use the comment section to ask where to get it and stop posting your email addresses

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

Launcher PRO 3.1.1 Build 133 is now available.

Change Log
====================
3.1.1 Build 133
- Added: Support for 3.32.1 32 and 64bit
- Minor Update: FA and CAFD Mapping 
- Minor bug fixes


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


Now that a native 64bit app is out, I am planning to drop support for 32bit versions. There's just no reason to use 32bit anymore. For what we do, and what the application demand, 64bit just makes a lot of sense. I just wished it came out a lot sooner. It took several years for 64bit to be natively supported, and as the first person to painfully and intensively shoehorned, countlessly and tirelessly tested, used and experimented on 64bit JRE, I can't tell you enough how excited I am hearing and anticipating the release of 3.32.1 x64. I've been counting the days since I've heard of it back in February, only to be disappointed upon learning about a month ago, that I can't work on it immediately. 

Anyway, I'm just glad to be able to add support to it. This version still supports both 32 and 64bit, but hopefully, not for long. I hope to exclusively use 64bit.



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

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. 

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

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.