fix bug where startMsgFilter was looking for the wrong synchronization stamp.

DLL no longer uses Qt to make smaller and more portable, uses boost library instead.Fix bug where patches and some other metadata was not appearing in metadata view.Problems with failed readEcuIdentification requests in CAN Mitsubishis are ignored in case they are not supported in the current mode.Fix problems with FTP uploads of unknown ROMs.Fix bug where vehicle type dialog selects first item if you do not interact with tree view, even though another item is shown as selected.get Evo X recovery mode write back in ECU menu options.fix bug where reading response from kernel could report 'msg buffer too small' when it was not.fixed MSVC compiler library issue which made EcuFlash incompatible with Windows XP.added additional delays when communicating with Mitsubishi bootloaders to avoid the ECU occasionally not receiving bytes.

Update checker now looks at build numbers to notify you of incremental improvements that don't have a new minor version change.

Allow for other responses in wrx02 bootloader init sequence (possibly for ecutek'd ECUs).

mitsucan heuristically determines correct checksum area size.

adding clarification to message indicating nothing was written due to no differences in ROM images.

User Boot MAT is still not supported yet pending read support for this area.

Added SH boot mode support for SH725XX processors.File dialogs offer all ROM types by default.Changed driver signing certificates back to SHA1 from SHA256 for compatibility with pre-Win8 OS versions until MS release SHA256 kernel mode signing updates for these.Fixed MSVC compiler library issue which made J2534 DLL incompatible with Windows XP.Fixed Openport 1.3 driver INF file section naming error which was preventing this driver from installing correctly.The NASTF also maintains a Service Information Matrix which can help you find software for a particular make. This e-mail address is being protected from spambots. If you find other software which works (or has problems) please let us know at For this reason, we are maintaining a list here of software which is known to work with our cable. That said, there can be issues with OEM software not behaving in J2534 compliant ways due to bugs or design errors. A J2534 cable that supports the needed channel(s) (ISO9141/CAN/ISO15765/J1850) should work with any J2534-compliant software, OEM or third party.

Openport cable chevy