Launcher PRO 3.5.1

Launcher PRO 3.5.1 Build 216 is now available.

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

3.5.1 Build 2.6.1
- Fixed: Opening Settings screen crashes Launcher

3.5.0 Build 252

- Reduced and improved memory utilization

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

There's quite a bit of changes to this version, mainly, handling of JVM, less memory utilization and minimal use of temporary files. There's still tons of room for improvement.

I did test this on Win7 x86 FR, Win10 x86 TR, Win10 x64 RU and Win10 x64 EN, so hopefully, any compatibility issue is minimized.

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. 

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.