Thursday, August 3, 2017

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.

Saturday, July 29, 2017

Update: TokenMaster's Launcher PRO 2.8.0 and NCD / CAFD Tool V0.5.1

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

Change log

Launcher PRO V2.8.0 Build 153
====================
- Added support for E-Sys 3.29
- Added support for E-Sys 3.30


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, 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.1 Build 201
====================
- 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.

Wednesday, March 22, 2017

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.

Monday, March 13, 2017

Update: Launcher Premium 2.7.0 and NCD / CAFD Tool V0.5.0

Launcher 2.7.0 Premium and NCD / CAFD Tool 0.5.0 Alpha


Change Log:

Launcher Premium 2.7.0 Build 132
- Added configurable Cheat Codes selection
- "Code Default Values" button renamed to "DO NOT USE!!!" ("VERWENDEN SIE KEINE!!!")
- Windows XP is supported again
- Minor bug fix



Cheat Code selection on Startup.


This feature should have been included in the first release. I've discuss this a long time ago here: Code Default Values

NCD / CAFD Tool 0.5.0 Build 198 Alpha
- Minor bug fix


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.

Friday, January 27, 2017

Small updates, workaround,...etc.

I've been having short trips lately, so I started lagging behind my emails again. I know it is very frustrating to not receive response within the day, and I'm sorry for that, but I really don't have a choice. I don't bring my tools and apps with me, so I'm not able to provide a useful reply.

I have some send an email and several follow ups within the same day for several days. What I do, is open my email and start at the oldest unread ones and work my way up and process a small set up to whatever I can accommodate on that day. If you send several follow ups, what it does is push your email farther and farther down the queue. Again, I apologize. It's my fault but not much I can do either.

=====

FDL Cheat Codes bug. The latest release of Launchers includes new FDL cheat code for Korea. However, this introduced a bug as well, where you'll see "Unknown Error" when trying to fetch codes. It's caused by this file. You can remove the XML as a workaround, until I get around to fixing it.

=====
Some people have been using Premium and keep advancing date until it no longer works. Then send me an email asking me to fix it. That was put in there for a reason and don't expect help from me if you'd do that. Premium is for those people who code their own car. If you have the need to change the date to code another car, then it's not for you. This has been happening a lot to a point where I find it annoying.

=====
But there's more...

There's a few people asking for activation codes. That's not a problem in itself and I'd give one when I get to it, but when the same people ask for multiple activation codes, that's when I have issues with it. Premium is not for those people.

=====
And more...

Some E-Bay sellers are selling the Launcher. Well, I can't stop you from buying free software.

=====
And finally...

There's something that has been happening lately that I find very troubling, that I have to write about it. Some people have been sending me fake receipts and recycled receipts. I have received quite a lot, more than 20 of those. So many that a pattern has emerged, and showed a few particular demographics are behind it. I mean, come on now. How jaded and twisted can one be to resort to that thing?  It's just very disheartening and makes me lose interest. :(

Wednesday, November 23, 2016

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.

Saturday, November 5, 2016

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.