Someone is repackaging my E-Sys Launcher PRO and packaging it as ESysLauncherPROSetup_2.0.0_Build_45.rar. This file didn't come from me. It appears the RAR file is password protected. If you see this file, do not download it for the following reason:
1) It is not for sale and whatever token that comes with it will be blocked and will be useless
2) Build 45 is the first release. The mapping data that came with this build is faulty. Check CAS and see if you get any descriptive text at all. That is just one of the many ECU affected. FEM, IHKA,KOMBI, NBT, CIC...etc. are also affected, some partially, others completely.
If you get the bright idea of updating the mapping data, don't bother. Encryption key is different and will be totally useless.
This is the kind of actions I absolutely abhor, it's despicable. You do something and someone is bound to exploit it.
UPDATE: I've been getting barrage of emails asking for token, or password or decryption key from this build. I don't know any password, nor decryption key, so please if you DO NOT ask me, if you insist on using this build.
Thursday, May 14, 2015
Sunday, May 10, 2015
E-Sys Launcher 2.0 - PRO and Premium Feature Comparision
E-Sys Launcher 2.0 PRO vs. Premium
I have released both E-Sys Launcher PRO and Premium 2.0 last week. I should have made this blog before releasing it but better late than never.
Here's a feature comparison between the versions of E-Sys Launchers.
The Premium is made specifically for individual and personal use only. For one's normal coding need, the Premium will fulfill 99% of that need.
I have added some limitations to prevent some entities from overusing the Premium. Some people are using the Premium to code for other people and charge a substantial fee. I don't have a problem with that practice, but when these very same people peruse the forum and the community's findings and leverage these knowledge for their business, all the while being too arrogant and not giving anything back, that rubs me off in a wrong way. When your whole coding skills is acquired by reading the forum, you shouldn't be too proud so as to say you are against sharing information, for without the forum, you have zero knowledge. Perusing it without so much as giving thanks to those who deserve it doesn't work well for me.
PSdZdata Mapping - Premium will only have the Datagroups, Functions and Parameter names. PRO will have comments as well.
PSdZdata Mapping Restriction - Premium requires you choose a series for your car. This is used when performing FAFP/CAFD mapping translation. If you open an FA.xml from a different series, no translation will be done. If you open an NCD or CAFD which doesn't apply to your chosen series, no mapping will be done and you'll simply see dots again. The Launcher warns you about the change when you select a series, so take heed.
Note that none of these reduce the functionality of E-Sys. These restrictions are only for PSdZdata mapping and you can use E-Sys the same way as you did before, with or without the Launchers.
"But I have 2 (or insert however many cars you have here) cars, what about me?" - You can change series after 3 days. Or better yet, upgrade to the PRO version. The PRO don't have any restrictions.
"I code for a fee" - Premium isn't for you.
PRO is not for free and is not for a fee either. If you are interested in E-Sys Launcher PRO 2.0, email me at fxxtokenmaster_at_GMail
I have released both E-Sys Launcher PRO and Premium 2.0 last week. I should have made this blog before releasing it but better late than never.
Here's a feature comparison between the versions of E-Sys Launchers.
The Premium is made specifically for individual and personal use only. For one's normal coding need, the Premium will fulfill 99% of that need.
I have added some limitations to prevent some entities from overusing the Premium. Some people are using the Premium to code for other people and charge a substantial fee. I don't have a problem with that practice, but when these very same people peruse the forum and the community's findings and leverage these knowledge for their business, all the while being too arrogant and not giving anything back, that rubs me off in a wrong way. When your whole coding skills is acquired by reading the forum, you shouldn't be too proud so as to say you are against sharing information, for without the forum, you have zero knowledge. Perusing it without so much as giving thanks to those who deserve it doesn't work well for me.
PSdZdata Mapping - Premium will only have the Datagroups, Functions and Parameter names. PRO will have comments as well.
PSdZdata Mapping Restriction - Premium requires you choose a series for your car. This is used when performing FAFP/CAFD mapping translation. If you open an FA.xml from a different series, no translation will be done. If you open an NCD or CAFD which doesn't apply to your chosen series, no mapping will be done and you'll simply see dots again. The Launcher warns you about the change when you select a series, so take heed.
Note that none of these reduce the functionality of E-Sys. These restrictions are only for PSdZdata mapping and you can use E-Sys the same way as you did before, with or without the Launchers.
"But I have 2 (or insert however many cars you have here) cars, what about me?" - You can change series after 3 days. Or better yet, upgrade to the PRO version. The PRO don't have any restrictions.
"I code for a fee" - Premium isn't for you.
PRO is not for free and is not for a fee either. If you are interested in E-Sys Launcher PRO 2.0, email me at fxxtokenmaster_at_GMail
Wednesday, April 15, 2015
NCD/CAFD Tool and E-Sys Launcher PRO 2.0, Now support trimmed CAFD files
It's been a long time since I wrote my last blog entry. Anyway, I've seen people getting frustrated with trimmed CAFDs and has started doing unimaginable things with their NCD files. While renaming NCD files sorta work, it should never be done like that. Some CAFDs have very little changes between versions but some have lots. Besides, the reason for updated CAFDs are to fix issues the engineer found. Using an NCD generated from older version defeats the purpose of the new version. If you're going to do that, might as well stick with an older version of CAFDs.
Over the last couple of weeks, I went back and dusted off my trusted tools. First off, I just released NCD / CAFD Tool V0.3. This version now supports trimmed CAFD and FA2FP files.
If interested, send me an email at fxxtokenmaster_at_GMail
Over the last couple of weeks, I went back and dusted off my trusted tools. First off, I just released NCD / CAFD Tool V0.3. This version now supports trimmed CAFD and FA2FP files.
Taking this very same feature, I added it to E-Sys Launcher PRO 2.0, currently in limited Beta but is in very usable form.
3.26.1 with the Launcher:
Watch it in action:
Sunday, December 14, 2014
E-Sys Launcher PRO
E-Sys Launcher Pro
E-Sys Launcher PRO (V1.0.4 as of this writing) is a Next-Generation Universal Token Solution for E-Sys Version 3.22.x and up (except 3.25.x due to bugs with E-Sys). The PRO version is for those who are already using my patchless token solution.
User Interface
E-Sys Launcher Pro FEATURES
1) Increased Default Memory Allocation. E-Sys needs memory and lots of it. Default setting is barely enough for simple cars like the F20/F30s but is hardly sufficient for cars with complex ECUs (F15, F56...etc.). Most coders do well by changing this settings but some aren't aware of this. While it can be easily changed, E-Sys doesn't check the value and if you set it too high, will prevent E-Sys from launching again. The PRO version offers two additional settings over the Premium. Max and Custom.
2) Enhanced Overall System Stability. By ensuring E-Sys gracefully shutdown and JVM properly recycled at the end of each coding session, your system is kept optimized for the next session. Stock E-Sys, more often than not, does not fully terminate when you exit the application. JVM lingers in the background, hogging and leaking memory. The issue becomes more apparent when you start/shutdown E-Sys numerous times, to a point where system restart is required. The PRO version also adds additional setting that boost stability of background tasks spawned by E-Sys
3) Zero E-Sys Configuration. With the launcher, there's no need to reconfigure E-Sys to use different Soft tokens. Those with OEM or my patchless token solutions can keep using it by clicking the Blue E-Sys icon, while using the launcher will use the assigned token, all without having to fiddle with the settings. The order in which you install E-Sys and the Launcher does not matter, as nothing gets modified.
4) Personalized and Individualized Token. The soft token you create from existing patchless tokens will only be usable on your own machine. It cannot be shared and reused on another machine. This also means that someone can't sell you a token and expect it to work. With the built-in Token Generator, creating soft token is as easy as pressing a button. No fiddling around with some command line tool and creating XML data by hand. The PRO version adds the ability to use patchless tokens without having to extend/regenerate it.
5) Absolute Security. It became pretty easy to hack CAFD recently. With the launcher, the risk of using hacked CAFD is reduced to 0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys does, stopping it dead from its track. Coupled with individualized token, there's no need to worry about hacked CAFD, even the ones that are re-signed and encrypted. BUT, you have to have an unpatched E-Sys. Patched file works by ignoring digital certificates.
6) No-Touch Post Deployment. With the launcher, all you need is to install E-Sys. Already installed E-Sys? No problem, just use the launcher and it just works without adding, modifying, or editing anything. Upgrading E-Sys? Go ahead, launch it and see it work.
7) Supports Multiple Versions/Side-by-Side Setup. If you have multiple versions of E-Sys installed on your machine (like I do), the Launcher PRO can be configured to launch each one with different launch mode. Even if you only have a single instance of E-Sys, it can be launched 4 different ways.
8) Supports 4 Different Launch Mode. The launcher PRO supports different launch types. This means that you can use the launcher with an OEM Soft Token and just take advantage of the higher memory settings or enhanced stability, or both.
Note: Do not mix and match different solutions, it's not generally recommended and could elevate the security risks the launcher is trying to minimize.
Feature Comparison
Warning about E-Sys 3.26.x: Be warned that 3.26.x is not as stable as 3.24.3 and you may experience error especially when flashing, with or without the launcher. 3.25.x is worse. I am still using 3.24.3 for this reason.
Interested? Send me an email at fxxtokenmaster_at_GMail
E-Sys Launcher PRO (V1.0.4 as of this writing) is a Next-Generation Universal Token Solution for E-Sys Version 3.22.x and up (except 3.25.x due to bugs with E-Sys). The PRO version is for those who are already using my patchless token solution.
User Interface
E-Sys Launcher Pro FEATURES
1) Increased Default Memory Allocation. E-Sys needs memory and lots of it. Default setting is barely enough for simple cars like the F20/F30s but is hardly sufficient for cars with complex ECUs (F15, F56...etc.). Most coders do well by changing this settings but some aren't aware of this. While it can be easily changed, E-Sys doesn't check the value and if you set it too high, will prevent E-Sys from launching again. The PRO version offers two additional settings over the Premium. Max and Custom.
2) Enhanced Overall System Stability. By ensuring E-Sys gracefully shutdown and JVM properly recycled at the end of each coding session, your system is kept optimized for the next session. Stock E-Sys, more often than not, does not fully terminate when you exit the application. JVM lingers in the background, hogging and leaking memory. The issue becomes more apparent when you start/shutdown E-Sys numerous times, to a point where system restart is required. The PRO version also adds additional setting that boost stability of background tasks spawned by E-Sys
3) Zero E-Sys Configuration. With the launcher, there's no need to reconfigure E-Sys to use different Soft tokens. Those with OEM or my patchless token solutions can keep using it by clicking the Blue E-Sys icon, while using the launcher will use the assigned token, all without having to fiddle with the settings. The order in which you install E-Sys and the Launcher does not matter, as nothing gets modified.
4) Personalized and Individualized Token. The soft token you create from existing patchless tokens will only be usable on your own machine. It cannot be shared and reused on another machine. This also means that someone can't sell you a token and expect it to work. With the built-in Token Generator, creating soft token is as easy as pressing a button. No fiddling around with some command line tool and creating XML data by hand. The PRO version adds the ability to use patchless tokens without having to extend/regenerate it.
5) Absolute Security. It became pretty easy to hack CAFD recently. With the launcher, the risk of using hacked CAFD is reduced to 0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys does, stopping it dead from its track. Coupled with individualized token, there's no need to worry about hacked CAFD, even the ones that are re-signed and encrypted. BUT, you have to have an unpatched E-Sys. Patched file works by ignoring digital certificates.
6) No-Touch Post Deployment. With the launcher, all you need is to install E-Sys. Already installed E-Sys? No problem, just use the launcher and it just works without adding, modifying, or editing anything. Upgrading E-Sys? Go ahead, launch it and see it work.
7) Supports Multiple Versions/Side-by-Side Setup. If you have multiple versions of E-Sys installed on your machine (like I do), the Launcher PRO can be configured to launch each one with different launch mode. Even if you only have a single instance of E-Sys, it can be launched 4 different ways.
8) Supports 4 Different Launch Mode. The launcher PRO supports different launch types. This means that you can use the launcher with an OEM Soft Token and just take advantage of the higher memory settings or enhanced stability, or both.
Note: Do not mix and match different solutions, it's not generally recommended and could elevate the security risks the launcher is trying to minimize.
Feature Comparison
Warning about E-Sys 3.26.x: Be warned that 3.26.x is not as stable as 3.24.3 and you may experience error especially when flashing, with or without the launcher. 3.25.x is worse. I am still using 3.24.3 for this reason.
Interested? Send me an email at fxxtokenmaster_at_GMail
Friday, October 31, 2014
E-Sys Launcher - New Universal Token Solution for E-Sys
E-Sys Premium Launcher Version 1.0.3.16
My patchless token solution brought something new and something relevant when I introduced it. And now, E-Sys Launcher Premium, once again, changes the way we use E-Sys. When a simple patchless solution just doesn't cut it anymore, E-Sys Launcher Premium brings a whole new set of feature to the table and is the only true innovative contender to my own patchless solution.
- Increased default memory allocation. E-Sys needs memory and lots of it. Default setting is barely enough for simple cars like the F20/F30s but is hardly sufficient for cars with complex ECUs. Most coders do well by changing this settings but some aren't aware of this. While it can be easily change, E-Sys doesn't check the value and if you set it too high, will prevent E-Sys from launching. With the launcher, the memory allocation is doubled.
- Enhanced overall System stability. By ensuring E-Sys gracefully shutsdown and JVM properly recycled at the end of each coding session, your system is kept optimized for the next session. Stock E-Sys, more often than not, does not fully terminate. JVM lingers in the background, hogging and leaking memory. The issue becomes more apparent when you start/shutdown E-Sys numerous times, to a point where system restart is required. With the launcher, this is unlikely to happen.
- Zero E-Sys Configuration. With the launcher, there's no need to reconfigure E-Sys to use different Soft tokens. Those with OEM or my patchless token solutions can keep using it by clicking the Blue E-Sys icon, while using the launcher will use the assigned token, all without having to fiddle with the settings.
- Personalized and Individualized token. The soft tokens you create will only be usable on your own machine. It cannot be shared and reused on another machine. This also means that someone can't sell you a token and expect it to work. With the built-in Token Generator, creating soft token is as easy as pressing a button. No fiddling around with some command line tool and creating XML data.
- Absolute Security. It became pretty easy to hack CAFD recently. With the launcher, the risk of using hacked CAFD is reduced to 0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys does, stopping it dead from its track. Coupled with individualized token, there's no need to worry about hacked CAFD.
Note: Do not mix and match different solutions, it's not generally recommended and could elevate the security risks the launcher is trying to minimize. My patchless solution can safely co-exists with the launcher, however, but it won't be loaded while the launcher is running. The patchless solution will also be replaced soon.
Main UI:
Soft Token Generator:
See it in action:
My patchless token solution brought something new and something relevant when I introduced it. And now, E-Sys Launcher Premium, once again, changes the way we use E-Sys. When a simple patchless solution just doesn't cut it anymore, E-Sys Launcher Premium brings a whole new set of feature to the table and is the only true innovative contender to my own patchless solution.
Features:
- Increased default memory allocation. E-Sys needs memory and lots of it. Default setting is barely enough for simple cars like the F20/F30s but is hardly sufficient for cars with complex ECUs. Most coders do well by changing this settings but some aren't aware of this. While it can be easily change, E-Sys doesn't check the value and if you set it too high, will prevent E-Sys from launching. With the launcher, the memory allocation is doubled.
- Enhanced overall System stability. By ensuring E-Sys gracefully shutsdown and JVM properly recycled at the end of each coding session, your system is kept optimized for the next session. Stock E-Sys, more often than not, does not fully terminate. JVM lingers in the background, hogging and leaking memory. The issue becomes more apparent when you start/shutdown E-Sys numerous times, to a point where system restart is required. With the launcher, this is unlikely to happen.
- Zero E-Sys Configuration. With the launcher, there's no need to reconfigure E-Sys to use different Soft tokens. Those with OEM or my patchless token solutions can keep using it by clicking the Blue E-Sys icon, while using the launcher will use the assigned token, all without having to fiddle with the settings.
- Personalized and Individualized token. The soft tokens you create will only be usable on your own machine. It cannot be shared and reused on another machine. This also means that someone can't sell you a token and expect it to work. With the built-in Token Generator, creating soft token is as easy as pressing a button. No fiddling around with some command line tool and creating XML data.
- Absolute Security. It became pretty easy to hack CAFD recently. With the launcher, the risk of using hacked CAFD is reduced to 0. Hacked CAFDs are prevented from loading, exactly the way stock E-Sys does, stopping it dead from its track. Coupled with individualized token, there's no need to worry about hacked CAFD.
Note: Do not mix and match different solutions, it's not generally recommended and could elevate the security risks the launcher is trying to minimize. My patchless solution can safely co-exists with the launcher, however, but it won't be loaded while the launcher is running. The patchless solution will also be replaced soon.
Main UI:
Soft Token Generator:
See it in action:
Wednesday, October 15, 2014
Random Musing #2 - "Good Artists Copy, Great Artists steal"
"Good Artists Copy, Great Artists Steal" - Picasso
I've recently chanced upon the above quote, and I thought it couldn't be more fitting that what's happening lately.
To start with, one troll has launched a witch hunt against me. It has been going on for a while now, but one I always ignored since I didn't think he deserves any of my attention. I guess his animosity towards me started when he couldn't crack my token, despite me telling him exactly my process in a numerous and lengthy email. It was detailed, short of writing the code myself and giving it to him. I now realized that even if I did that, he wouldn't get it anyway.
Another guy showed up in the forum recently. The troll saw a chance to pounce on me and throw numerous accusations and took a jab at every single chance he gets. I'm pissed off, but I ignored it. But I'm still pissed off, so much so that I stayed away from the forum. THAT is how much I'm pissed off. I enjoyed hanging out in the forum but I can't stand this guy.
Let's see what he's accusing me of:
1) I don't share anything. - Really? I've told this guy everything, it's not my fault that he doesn't understand any of it. I think he equates sharing to spoon-feeding -which I never believe in. You know the proverbs: "Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"? This is what I believe in.
As far as I'm concerned, I've been sharing information in the forum. I've given tools that help fellow coders. And this troll dared accuse me. The thing is, if you search his posts, not a single one is helpful. He likes to answer like "Search the internet". That is the most asinine answer anyone could ever come up with. 90% of his posts is asking for help and he's as clueless as can be, because the answer to his question is already provided in the very thread he's asking.
2) "I am just a seller" - Well, if you don't recognize my tools as help, then yeah, I'm just a seller. I sell my own original work though. I don't rip people of their work. And there's a reason why I'm selling tokens and giving away my more valuable tools. I could have sold my tools too, but I don't see any reason.
Here's the kicker -this troll sells tokens as well. Tokens he got from a stolen information, tokens he got for free, tokens provided to him by the other guy. If you belong to any European BMW Forum, he has likely offered you "his" token via PM.
He claims he developed this token, but boy, you can bet your bottom dollar he didn't do anything because none of this make sense to him.
The other guy took several jab as me as well. First, he called my assertion that there's a danger in a patched solution, despite having a proof, FUD. I thought that was funny and absurd at the same time.
He came up with a token solution he claims is safe and will accept any token -both of which is false. By working with the troll above, they were able to come up with a solution similar to mine. I say "similar" because it's not the same. Not as secure as my solution -close but not quite.
"Good Artists Copy..." Too bad they only settled in copying. That is already a failure, in my opinion.
By the way, there was a thread over at Bimmerfest which was already deleted as it gotten crazy. The troll looked down at people and started calling them names and what-not. In that very thread, he did admit that he was studying my solution, along with one other guy. I find this preposterous and disrespectful. Never have I encountered a forum where one could be so blatant and open in disrespecting another member. He dared accuse me of being "just a seller". He's dirtier and stinkier than the mud he's throwing at me. Yes, I sell tokens, but he sells tokens provided by others. And he tried to crack my solution...
You may be saying, "But you cracked BMW's solution as well". Yes I did, I did crack it. I copied the idea. BUT I didn't stop there. I made the idea my own and made it better - "Great Artists Steal". The fact that my token would only work with my solution is a proof of that. I worked hard to make my solution secure so no modified CAFD would work, so our car remains secure from malicious intent. We're talking about a $40,000 (at least) cars anyway.
And here's one more kicker. The other guy says "save your money and donate it to charity"
(Note: Other name redacted upon request)
What happened? Did the world turned upside down. Why dis and accuse someone of doing something when in fact, it is them doing it?
I am very disgusted and disheartened with all of these. I believe in humanity but these things are certainly taking their tolls on me...
Lastly, truth be told, I give a lot of people free tokens. Some insisted on donating but I don't accept personal donations. I told these people if they're serious about donating, to donate it to their local Children's Hospital or Cancer institute. I support these two institutions. I believe they're doing this world a huge favor.
Now, I never intend to disclose this because I believe helping others is just natural, it's being human. It's not something you do and then tell the world about it. But, with all the accusations thrown at me recently, I can only take so much. The people I helped could speak for this...
Picasso is indeed one of the brilliant mind of his times - "Good Artists Copy, Great Artists Steal"
Note: I know this is ranting. I just had to let it off. There will be no other similar post in the future.
I've recently chanced upon the above quote, and I thought it couldn't be more fitting that what's happening lately.
To start with, one troll has launched a witch hunt against me. It has been going on for a while now, but one I always ignored since I didn't think he deserves any of my attention. I guess his animosity towards me started when he couldn't crack my token, despite me telling him exactly my process in a numerous and lengthy email. It was detailed, short of writing the code myself and giving it to him. I now realized that even if I did that, he wouldn't get it anyway.
Another guy showed up in the forum recently. The troll saw a chance to pounce on me and throw numerous accusations and took a jab at every single chance he gets. I'm pissed off, but I ignored it. But I'm still pissed off, so much so that I stayed away from the forum. THAT is how much I'm pissed off. I enjoyed hanging out in the forum but I can't stand this guy.
Let's see what he's accusing me of:
1) I don't share anything. - Really? I've told this guy everything, it's not my fault that he doesn't understand any of it. I think he equates sharing to spoon-feeding -which I never believe in. You know the proverbs: "Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"? This is what I believe in.
As far as I'm concerned, I've been sharing information in the forum. I've given tools that help fellow coders. And this troll dared accuse me. The thing is, if you search his posts, not a single one is helpful. He likes to answer like "Search the internet". That is the most asinine answer anyone could ever come up with. 90% of his posts is asking for help and he's as clueless as can be, because the answer to his question is already provided in the very thread he's asking.
2) "I am just a seller" - Well, if you don't recognize my tools as help, then yeah, I'm just a seller. I sell my own original work though. I don't rip people of their work. And there's a reason why I'm selling tokens and giving away my more valuable tools. I could have sold my tools too, but I don't see any reason.
Here's the kicker -this troll sells tokens as well. Tokens he got from a stolen information, tokens he got for free, tokens provided to him by the other guy. If you belong to any European BMW Forum, he has likely offered you "his" token via PM.
He claims he developed this token, but boy, you can bet your bottom dollar he didn't do anything because none of this make sense to him.
The other guy took several jab as me as well. First, he called my assertion that there's a danger in a patched solution, despite having a proof, FUD. I thought that was funny and absurd at the same time.
He came up with a token solution he claims is safe and will accept any token -both of which is false. By working with the troll above, they were able to come up with a solution similar to mine. I say "similar" because it's not the same. Not as secure as my solution -close but not quite.
"Good Artists Copy..." Too bad they only settled in copying. That is already a failure, in my opinion.
By the way, there was a thread over at Bimmerfest which was already deleted as it gotten crazy. The troll looked down at people and started calling them names and what-not. In that very thread, he did admit that he was studying my solution, along with one other guy. I find this preposterous and disrespectful. Never have I encountered a forum where one could be so blatant and open in disrespecting another member. He dared accuse me of being "just a seller". He's dirtier and stinkier than the mud he's throwing at me. Yes, I sell tokens, but he sells tokens provided by others. And he tried to crack my solution...
You may be saying, "But you cracked BMW's solution as well". Yes I did, I did crack it. I copied the idea. BUT I didn't stop there. I made the idea my own and made it better - "Great Artists Steal". The fact that my token would only work with my solution is a proof of that. I worked hard to make my solution secure so no modified CAFD would work, so our car remains secure from malicious intent. We're talking about a $40,000 (at least) cars anyway.
And here's one more kicker. The other guy says "save your money and donate it to charity"
What happened? Did the world turned upside down. Why dis and accuse someone of doing something when in fact, it is them doing it?
I am very disgusted and disheartened with all of these. I believe in humanity but these things are certainly taking their tolls on me...
Lastly, truth be told, I give a lot of people free tokens. Some insisted on donating but I don't accept personal donations. I told these people if they're serious about donating, to donate it to their local Children's Hospital or Cancer institute. I support these two institutions. I believe they're doing this world a huge favor.
Now, I never intend to disclose this because I believe helping others is just natural, it's being human. It's not something you do and then tell the world about it. But, with all the accusations thrown at me recently, I can only take so much. The people I helped could speak for this...
Picasso is indeed one of the brilliant mind of his times - "Good Artists Copy, Great Artists Steal"
Note: I know this is ranting. I just had to let it off. There will be no other similar post in the future.
Thursday, August 28, 2014
3.26
So, 3.26, came out a couple of weeks ago. And yes, this one's done :) It was provided by one BMW god who's always looking out for us, mere BMW mortals :)
There's not much difference you can see on the UI side. But on the inside, it is a lot better, leaner, more mature than 3.25 was. It's a lot cleaner, and is actually usable.
3.26 requires PSdZ version 5.0.1 or newer. None of the current PSdZdata released as of today, satisfies this requirement. One good member of Bimmerfest contacted me with a valuable information. He has access to PDX Template V3 and that template contains the proper PSdZ library required by 3.26. The short of it, I go it working by using PSdZdata 53.3 and applying the template.
3.26 is OK, definitely better than 3.25, but I'm still on the fence when it comes to 3.24.3. I personally think 3.24.3 is the best release so far.
NOTE: My token works for all versions, from 3.22.x to now, 3.26
UPDATE: 9/1/2014 - PSdZdata V53.5 just came out and it works with 3.26 as it's now on the required PSdZ version..
There's not much difference you can see on the UI side. But on the inside, it is a lot better, leaner, more mature than 3.25 was. It's a lot cleaner, and is actually usable.
3.26 requires PSdZ version 5.0.1 or newer. None of the current PSdZdata released as of today, satisfies this requirement. One good member of Bimmerfest contacted me with a valuable information. He has access to PDX Template V3 and that template contains the proper PSdZ library required by 3.26. The short of it, I go it working by using PSdZdata 53.3 and applying the template.
3.26 is OK, definitely better than 3.25, but I'm still on the fence when it comes to 3.24.3. I personally think 3.24.3 is the best release so far.
NOTE: My token works for all versions, from 3.22.x to now, 3.26
UPDATE: 9/1/2014 - PSdZdata V53.5 just came out and it works with 3.26 as it's now on the required PSdZ version..
Subscribe to:
Posts (Atom)