Sunday, January 7, 2018

Launcher PRO 3.0.2 is Out

Launcher PRO 3.0.2 build 72 is now out

Change Log:
- Fixed: Using DE locale shows corrupted characters i.e., About dialog
- Fixed: Using High DPI Fix produces error
- Fixed: In locale where extended characters are mostly used, Launcher PRO may fail to launch application if installed in default folder
- Custom memory maximum value is back to 8GB. NOTE: Only for x64 JRE. For 32-bit JRE, High is the maximum value that can launch app consistently
- Updated and optimized CAFD mapping

NOTE: Please do not download the app and then request for activation code. It doesn't work that way. I spent significant amount of time verifying and responding to emails and request for code is a huge chunk of it, and it's already taking its toll on me. I had to slow down responding to emails in the last couple of days because there's no time left for me to work on the Launcher, and I know I have a few fixes that I needed to do. I also help people remotely and this adds up. I'm trying really hard to keep up with my emails, but there's not a lot of time in a day, but I assure everyone that you will hear from me.

And lastly, do not request and post your email address in the comment section. Send all inquiries to fxxtokenmaster_gmail_com. I do not respond to any emails posted here.

Thanks for your understanding.

Thursday, January 4, 2018

Troubleshooting Launcher PRO 3.0: Launcher Opens but does not launch application

I've heard several reports now that in some instances, mostly non-English locale, Launcher PRO fails to launch the application and just disappears. Please try the following:

Method 1: Check the memory settings. If you are using stock JRE (32-bit JRE), High is the most you should set it at. Anything higher will likely fail. If setting to Medium or High solves the problem, then you're done. If not, proceed to Method 2.

Method 2:
 a) Copy the contents of  C:\Program Files (x86)\TokenMaster\Launcher PRO to a temporary folder, say C:\Temp.
 b) Run LauncherPRO.exe. If the application is launched successfully, proceed to the next step. If not, please contact me via email at fxxtokenmaster_gmail_com
 c) Uninstall Launcher PRO 3.0
 d) Install Launcher PRO, but change the location to <Drive>:\Program Files (x86)\TokenMaster\LauncherPRO. - Note: remove the space between  Launcher and PRO.
 e) If the application is launched successfully, you're done, else, proceed to the next step
 f) Reinstall Launcher PRO, but change the location to <Drive>:\LauncherPRO.
 g) If the application is launched successfully, you're done, else, contact me via email.

I am still looking into this issue and hope to resolve it real soon.

Saturday, December 30, 2017

Launcher Updates

Well, this post is about what has been happening lately, and I thought I'd post a quick update.

Launcher PRO V3.0 has been out for a few days now. Got some report that High DPI isn't working, so I'll definitely fix that in the next build.

I still receive a few activation code requests, so I'll probably create a video guide. The thing is, once you got access to my site, you can do everything yourself without my help. Input the request code, generate activation code, download, and activate Launcher. That is it.

Some browser apparently don't show the code immediately, like IE/Chrome/FF does. If this happens to you, wait for at least 15 minutes, go back to the page, and you should see it, ready for download.

Launcher Premium - as stated in my other post, is no longer supported and I stopped generating activation codes for it. It is what it is.

Using JRE x64 -  I almost always use x64 now a days. It's really sweet on RAM allocation and usage. To use 64-bit JRE, download the 64-bit version from Oracle and install it. Find the location of the app where the folder "jre" is. Create a new folder named "jre_x64" and copy all the cotents of JRE/JDK to this folder. NOTE: Ensure there is no environment settings for _java_options. Some apps automatically set this, but it's more trouble than it's worth. It's a bad advise that is widely used.

Response Time - My email responses are delayed by two days. I'm trying to catch up as fast as I can but with the holidays and family around, they take priority over anything else.

Fake Receipts - well, this is really disappointing. I'm getting tons of them now, where as before, I see one or two here and there. I'm genuinely surprised and stumped with this trend. I mean WHY??? I seriously don't know how to deal with this and it's taking me a lot of time verifying.

I have a degree in digital forensic...just kidding, I'm just a guy who knows his way around MS Paint ;). Believe me, I know how to detect manipulated images. If you're paying some guy to create fake receipts for you, you should check your priorities.

Lastly...Happy Holidays and Happy New Year!!! Enjoy your family and the holiday. See you next year, especially if you don't drink and drive.

Thursday, December 21, 2017

Launcher PRO 3.0 - Available this weekend

All-New Launcher PRO 3.0 - Available this weekend. See 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.

Sunday, October 8, 2017

TokenMaster's Launcher PRO 2.9.11 Build 306

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

Change log

Launcher PRO V2.9.11 Build 305
- Fixed activation on freshly installed Launcher
- Added feature to exclude Knowledge Bases (KisDB)
- Minor bug fixes

V2.9.11 added the capability to exclude some selected knowledge bases. Without this feature, all KB databases are loaded, hogging and wasting memory resources. Resources which 32-bit JRE doesn't have a lot of. It doesn't matter whether you have 2GB or 16GB, 32-bit JRE can only allocate so much. This is one of the driving factor why I introduced the use of 64-bit JRE.

This scenario poses problems to some users, specially does who have the X cars, because BDC_Body needs significant amount of memory. And while CAF for these complex ECUs may be loaded successfully, JRE often times, is left with not enough memory to process other stuff, like mapped CAFDs.

In the preceding image, I selected all I's, K's, R's, and S(G)-series, because I don't have any car belonging to those series, certainly not Rolls-Royce. The selected options will be prevent from loading. When I selected these series, they no longer show up as target in connection window, and the corresponding KIS DBs are no longer loaded. These save JRE both some processing time and memory.

Java (used/javamem): 117,964,784 # Java (full): 147,849,216 # Java (max): 1,073,741,824 #

Java (used/javamem): 77,492,896 # Java (full): 93,323,264 # Java (max): 1,073,741,824 #
It's not a whole lot, but when you put into perspective how much RAM can 32-bit JRE use per process, it's certainly significant.

Saturday, September 23, 2017

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.