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

Launcher PRO 3.4.2 Build 216 is now available.

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

- Improved CAFD processing and mapping, 200-300% gain typical

- Suppressed dialog G271

- Minor UI change - unified Launch and Abort button

- Fixed: Application launch failure on some system

- Minor bug fixes

-Fixed: Loading VO causes crash

I made a lot of changes for this build, I contemplated on labeling it 3.5. I made some major improvements on CAFD processing and mapping. On my 5th Gen Core i5, using 3.33.4 x64, fully processing HU NBT CAFD takes about 5 seconds, and BDC CAFD shows in under 8 seconds. This is a huge improvement over previous versions where it takes about 20+ seconds to process HU NBT.

I'd be doing further changes in the coming days.

I suppressed the G271 dialog as it's getting too annoying. I don't think anyone cares about what it says anyway.

I also made improvements on the web side. There was an incident where nobody can login, even myself. It was because the server time was  way off. I had to do an emergency deployment and query Internet time to rectify the issue, so the web application doesn't rely on server time anymore.

I recommend everyone to upgrade to this build.

Launcher PRO 3.4.0

Launcher PRO 3.4.0 Build 191 is now available.

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

3.4.0 Build 191

- Added: Support for 3.33.4 64bit Only

- Updated: CAFD Mapping compatibility level: 18-04 i-Step

- Removed: Required root certificate

- Minor bug fixes

NOTE: Authenticode RSA certificate is no longer required, but installing RSA Certificate with "EB06BA22 6FB31CD3 787A2ABB 84E71D61 F1CEA5B9" thumbprint to the Trusted Root Certification Authorities store on current user is still recommended. This certificate can only be used for Authenticode purposes and cannot be used to create intermediate or subordinate, or end entities certificates.

  To Install Certificate:

via Command prompt: LauncherPro3.exe installcert

via Windows: Right-click LauncherPro3.exe > Properties > Digital Signatures > Details > View Certificate > Install Certificate and install it under Trusted Root Certification Authorities store

  To Delete Certificate:

via Command prompt: LauncherPro3.exe removecert

or use mmc.exe and Certificate Snap-in. See https://tokenmaster.blogspot.com/2019/05/code-signing-certificate.html

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

NOTE: For WIndows 7 users, if you're having problems with validation/activation, Windows is probably not using TLS 1.2 to communicate to my site. Check the following registry key, as shown in the image:

First thing to do is ensure all updates are installed. If you don't see TLS 1.2 key, create it, then create the Client key under it. The two DWORD values must exist and should contain data as shown in the image. Restart WIndows and try again

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. 

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.

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.

TokenMaster's Launcher PRO 2.9.4 Build 218

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

Change log

Launcher PRO V2.9.4 Build 218
====================

- Added EST Migration tool for older tokens

- Fixed FA Activation hanging

- Fixed minor certificate/EST issue

- Minor UI tweak

As mentioned in my last blog, extended tokens with expired original one need to be migrated as I would need to compromise a lot to support it. Migration is quick, and very similar to the EST Extender tool. You will need the original tokens. This means that, if your token have expired and you didn't get to extend it, this is your chance to reactivate it. It must have expired within the last 12 months, though.

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.

Some Launcher V2.9+ Notes

These past few days/weeks have been specially hectic and chaotic. I've held off issuing tokens and codes since I was working on something. And what I thought and planned to be a seamless, painless upgrade, turned out to be anything but. V2.9.0 was a disaster,V2.9.1 wasn't any better, V2.9.2 was barely acceptable and V2.9.3 showed a glimmer of hope.

It took a friend from the other side of the world to get it back to an acceptable level. Working but not perfect.

I'd like to put out some guidelines for existing users:

•  Those who now use the new EST format, you should be OK with any V2.9+ version
•  Those who have the older format, still valid, non-extended tokens, upgrade now and extend your tokens using V2.9.3
• Those who own an already extended tokens, please do one of the following:

                - If your old token is still valid today, please revert to the original token and upgrade to V2.9.3, then extend your token.
                - If your old token is already expired, but is already extended, stay on V2.8.1 for now. The upcoming version will have a token migration tool which will help you move to V2.9+.


I tried to accommodate all scenarios to make it all seamless. However, supporting extended tokens requires me to relax security a bit. One that I'm not willing to compromise with. So, I opted to come up with a migration tool instead.


I promise you an easier, more stable, future versions coming, both PRO and Premium alike. It is taking me a while to bring Premium up to par with the PRO, but it is what it is for a very good reason.


And....Happy days are coming!!!

Some BMW gods smiled upon us. I have to look more into it and see what exactly is entailed, but it does look like your shiny new G-series, and those on newest iStep, is about to be a bit happier. Launchers have been on V59.4 for quite a while now. It's about time to move to V61 at the very least, V62 maybe, if we get ever so lucky...Happy days, happy days.

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.

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.

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.

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.

Update: Work-in-Progress - Launcher PRO and Premium 2.6

My first blog post after I came back was rather nasty, so I thought I'd post something more like the usual stuff.

I just finished setting up my coding PC after it crashed. I guess it didn't like being idle for so long. Anyway, here's what I'm working at:

Launcher PRO and Premium V2.6.0
- Supports E-Sys 3.28.x
- PSdZData Mapping compatibility: V3.59.4

Premium necessitates generating new token. You'll be asked to provide a PIN and old tokens will no longer work.

Also working on NCD/CAFD Tool with mapping compatibility updated to PSdZData V3.59.4

I hope to get it done in the next 7 days or so. Stay tuned.

E-Sys Launcher PRO 2.5.5

E-Sys Launcher PRO 2.5.5 Build 120


E-Sys Launcher PRO 2.5.5 is now out.

- Added CAFD Translation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7 (E-Sys 3.26, 3.27) - Enjoy crisp resolution without down scaling your Ultra HD 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


Due to the last item, I had to release PRO first. Premium will follow soon with the same features and 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.

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO are now Out.

Launcher PRO 2.5.4 Build 115
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Added configurable Cheat Codes selection
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

Launcher Premium 2.5.3 Build 108
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

PRO Only. FDL Cheat Codes are now selectable.

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.

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher V2.5.0 - PRO and Premium are now available


Change Log:

Launcher PRO 2.5.0 Build 103
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0
- JRE x64 support. It's now possible to use > 1.8GB RAM. I tested 3.27 and is stable at 4GB. See E-Sys Launcher.pdf for instructions on using 64bit JRE


Launcher Premium 2.5.0 Build 97
- Fixed "High Resolution Fix" option
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0

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.

E-Sys Launcher 2.4.3 PRO and Premium and E-Sys 3.27.1 Update

E-Sys Launcher V2.4.3 - PRO and Premium is now available


Change Log:


Launcher PRO 2.4.3 Build 98, Launcher Premium 2.4.3 Build 85
- Fixed issue with failure to load with some system when querying available memory due to corrupted .NET Performance Counter Registry
- "High Resolution Fix" is now always enabled
- Massive addition to Cheat codes, courtesy of dmnc02, Otakar and ruben_17non - Thanks fellas!
- Fixed minor UI issue - Review button tooltip (reported by myfxp)





E-Sys 3.27.1 Notes

I've been using E-Sys 3.27.1 a lot recently and I noticed that it crashes a lot due to a myriad of issues. Something as simple as having the MSM Updated turned on could crash E-Sys. The good news is that MSM update is the last process in coding, so the crash does not pose big problem when coding. It's just so annoying.

Memory, or the lack thereof, could also crash E-Sys. So, when running on default memory settings and trying to code complex ECUs, like NBT, could crash it.

I've never seen this happen to previous versions of E-Sys. It was pretty good at handling exceptions, but 3.27.1 seems different.

Bonus Tip
If you are forced to run E-Sys using default memory settings (512MB), you can help it by moving some PSdZData folders you never use. Some folders you can safely move, so long as you don't own a series which uses them are the series folders inside kiswb. I have F30 so I moved the following folder:
   C:\Data\psdzdata\kiswb\S15A (used by G-Series)
   C:\Data\psdzdata\kiswb\K001 and C:\Data\psdzdata\kiswb\KE01 (used by BMW motorcycle?)
   C:\Data\psdzdata\kiswb\RR01 (used by Rolls Royce)
   C:\Data\psdzdata\kiswb\I001 (used by i-3, i-8)
   C:\Data\psdzdata\kiswb\F056 (used by Mini)

Moving the above folders prevent E-Sys from reading database associated with these series. These databases are read on startup and kept in memory while E-Sys is running, using precious memory.

If you have plenty of RAM and can run at least using the medium settings, then moving the above folders are not required. Again, only do this if you are forced to run using default memory settings.  

E-Sys Launcher V2.4.0

UPDATE: V2.4.1 is now out.

2.4.1 Build 93
- Fixed E-Sys 3.26.x compatibility
- Minor Bug fixes

I highly recommend everyone to upgrade to this version.



E-Sys Launcher V2.4.0 is now out!

Launcher PRO
====================
2.4.0 Build 90
- Removed CAFD Remapping Option on the UI. As before, untrimmed CAFD will not undergo further processing.
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Launcher Premium
====================
2.4.0 Build 78
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Here's a small video I made using PRO.

 

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher V2.3.0 PRO and Premium are out

E-Sys Launcher V2.3.0 PRO and Premium are out

Change Log

Launcher PRO 2.3.0 Build 85
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


Launcher Premium 2.3.0 Build 75
- Added Smart, Safe caching - Subsequent reading of CAFD/FAFP will be significantly faster
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


The dynamic Stack Memory allocation is based on available memory at the time of launching E-Sys. Free memory is queried and the maximum allowed value will be sent to E-Sys. This setting is separate from the ones configurable via the main Launcher UI. That handles the Heap memory which is more important to E-Sys (or any Java app, for that matter). How do you know it works? Look at your log files and find "javamem". You should see something like:

Java (used/javamem): 14,295,120 # Java (full): 24,379,392 # Java (max): 1,341,891,328 # Process (full/procmem): 205,340,672 # Process (virtual): 1,491,914,752 # Process (virtual max): 2,147,352,576

The first highlighted value is the Heap and achieved by setting it in the UI. The second highlighted value is determined dynamically and is assigned because I have about 2GB of RAM on this machine.

Note that Heap memory could fail and when it does, you'll see the following error:

The solution is either to restart your PC or select a lower memory settings. Stack memory is more forgiving as it is dynamically managed by the OS.


NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.