>>>> Problem:

ERTS versions earlier than 3.18 sometimes produce the error message
"EXKEY not connected" although EXKEY is present. The problem is
a wrong port timing on machines with fast CPU or CPU cache.

ERTS uses an internal value of hex 1000. This value must be
overwritten by a higher value, e.g. hex 4000.

Note that binary values within ERTS are swapped. A value
of hex 1000 is coded as 0010 wihtin the EXE-files.


>>>> Work around:

Patch your ERTS*.EXE files either by using any binary editor
or by using PATCH.COM.

Suggested steps for FIXEX patch:

   1: Make a backup copy of your original ERTS*.EXE files

   2: Extract FIXEX.ZIP into ERTS system directory

   3: call FIXEX.BAT (this will overwrite original files)


   FIXEX.BAT calls the PATCH.COM that searches for a target value
   and replaces all occurences by a new value.

   IMPORTANT: There are four different patch locations within each file
   with offsets close to each other. If more than four patch locations
   are found or none, abort the patch procedure and contact BeriSoft
   Cooperation.

   If no location is found, your ERTS version uses a different value
   than hex 1000. Look for other values by typing at the DOS prompt

   PATCH H ERTS.EXE B9____E2FE

   and see what values are listed as target locations. Then edit the
   FIXEX.BAT file by replacing the search sequence with the proper
   values.

   If after successfully patching the files, the error still occures
   try to set higher values (e.g. hex 8000). Remember that the search
   string must always match the value used within the file. If you want
   to change hex 4000 into hex 8000 you must change FIXEX.BAT by
   inserting B90040E2FE as the new search sequence.


Suggested steps for own binary patch:

   1:  Make a backup copy of your original ERTS*.EXE files

   2:  Replace binary sequence  B90010E2FE
                          with  B90040E2FE
       in all files