MicroSquirt.com read only forum (Jan.15,2018)

I have tried using the Megatune 225p1 with my 2.88 Microsquirt and I get the 0-8000 rpm error documented in the manual. However using the 225p3 version of the Megatune software I keep getting megatune.ini error messages. I have read re-read the manuals/ help files, placed the 2.8 ini in the car1 file, yet cannot get it to "Activate" as this is greyed out. Looked at CODE VARIANT till I am blue in the face. Anybody done this? and be prepared to walk a newbie through it.

I am just trying to get used to the Megatune software and configure the settings, before I start wiring things up. I have tried the seatch engine, run circles in browser pages, forwards and backwards.

If I have missed a section in the manual I am sorry for not seeing it, but I have been looping on this for six hours now and it's extremely frustrating, yet getting the USB/serial adaptor on a Mac running Windows XP wasn't.

Day 2
Downloaded the 2.25 off the help page and this one has a dedicated MicroSquirt Folder, but no Car1 folder. I can activate the MicroSquirt and it has the 2.8 ini file in it, and the MegaTune will open, and it doesn't oscillate the RPM gauge.

However next time I open it it says there is an error, the ini file is version 2.87 , not 2.88 and warns of dire errors, corrupt tables etc.

Tried downloading and inserting the version 2.88 file into this folder, activating it and now it can't open the Megatune.ini and will not open the MegaTune software.

Am I being MegaThick here, because this is frustrating to say the least. Is there a section on the help pages that is consistent?
Do I start with the 2.25p1 version that has the MegaTune and MicroSquirt folders in the MtCfg folder or should I be using the 2.25p3 version that has no MicroSquirt folder, just a Car1 folder when you use the MtCfg app?

PS Understand the bit about CODE_VARIANT now it wasn't opening in an editor when I was viewing it.

A little later, I finally got there, but it doesn't seem that straight forward.

Finally saw the ECU type header under the Fuel Set Up>General and I was using 2.25p1. Prior to this I loaded the 2.883 s19 file into the MicroS, downloaded the 2.88 ini, changed the UNSET SET values for the MSI MSII, created a new project, dropped the 2.88 ini in there, activated it, and although I haven't configured a few things and got error messages accordingly, everything seems fine.

I just don't get why I made hard work of it, just gotta &