Known bugs list - EFILive V3
Report: EFI3.0-0013
Description: Program crashes on
second and subsequent attempts to record or playback datastreams.
Reported by: Testing
Date: 29-May-2000
Problem: The frame counter is not
being reset. This problem was introduced as a side effect of EFI3.0-0012.
Solution: The frame counter is now
reset when a new datastream is required.
Version: This problem is resolved
in EFILive v3.0.2.02 or later.
Temporary workaround: Exit and
restart EFILive v3.
Report: EFI3.0-0012
Description: The EVAL version of
EFILive v3 is easily hacked to allow the 350 frame limit to be changed to any
higher value.
Reported by: Barry (you've got too
much time on your hands) Tisdale
Date: 25-May-2000
Problem: The original design of
EFILive v3 called for dynamic memory allocation to store ALDL-frames. When the
limit was reached EFILive automatically allocated more heap space to the
ALDL-frame buffer. This meant that by changing a few bytes in the executable one
was able to bypass the 350 frame limit.
Solution: ALDL-frame allocation is
now static. Changing the executable code to bypass the 350 frame check is now
potentially dangerous because the ALDL-frame buffer will not automatically
resize and will most likely result in memory corruption and "Windows:
illegal operation errors".
Version: This problem is resolved
in EFILive v3.0.2.01 or later.
Temporary workaround:
Report: EFI3.0-0011
Description: Importing a vehicle
definition file (*.xml) sometimes displays the error message: "<date>
is not a valid date".
Reported by: Testing
Date: 25-May-2000
Problem: The date format
differences between US style dates (MM/DD/YY) and Australian style dates
(DD/MM/YY) was not being handled correctly by the import/export routines.
Solution: Under investigation.
Version:
Temporary workaround: Edit the
*.xml file with a text editor and change the date to the correct format for your
locality. The third line of the *.xml file begins with the meta-tag
<cdsVehicles> and towards the end of the line you find:
date="dd/mm/yy" or date="mm/dd/yy" depending on the locality
settings of the machine from which the *.xml file was exported. Change this date
to be in the correct format for your locality.
Report: EFI3.0-0010
Description: The registration
window displays the error "Friday, 31 December 2049 is not a valid
date".
Reported by: Barry Tisdale
Date: 25-May-2000
Problem: The date format
differences between US style dates (MM/DD/YY) and Australian style dates
(DD/MM/YY) was not being handled correctly by the license key validation
routines.
Solution: The date format as
specified in "Windows Control Panel - Regional Settings" is now used
to determine the date format.
Version: This problem is resolved
in EFILive v3.0.2.01 or later.
Temporary workaround: There is no
workaround
Report: EFI3.0-0009
Description: When exporting vehicle
definitions to *.xml and the definition includes conversion table information
the export will fail with error: cdsConvTablesField "Converted" not
found.
Reported by: Barry Tisdale
Date: 22-May-2000
Problem: The export routine
incorrectly references a field using the name "Converted" instead of
the correct name: "Value".
Solution: The correct field name is
now used.
Version: This problem is resolved
in EFILive v3.0.1.45 or later
Temporary workaround: To export a
vehicle definition that contains conversion table information - first change all
the data stream attributes are of type "Lookup table" to type
"Scaled value". This means that EFILive v3 will not attempt to export
any conversion tables. You can use the export/import feature in the "Edit
Conversion Tables" window to export the required conversion tables to
standard text files. These text files can be re-imported later. The table's code
and description are not exported/imported - you will need to re-enter the code
and description if/when performing a "data-destructive" upgrade.
Report: EFI3.0-0008
Description: When notes are
configured to be displayed on the charts and more than one table of information
is being processed the flags are incorrectly displayed every second frame.
Reported by: Testing
Date: 10-May-2000
Problem: Flags are only plotted on
the charts when their value changes (either from 0 to1 or from 1 to 0). When
multiple tables are being processed the flag is only present in one table. This
was confusing EFILive into "thinking" that the flag was changing value
each time a different table was processed.
Solution: Flags are now tagged with
their table of origin and are only processed when that table is being processed.
Version: This problem is resolved
in EFILive v3.0.1.44 or later
Temporary workaround: There is no
workaround.
Report: EFI3.0-0007
Description: When the monitor
window displays the error message: "No echo was received from Max232"
it is not displayed in the same color as other errors.
Reported by: Testing
Date: 14-May-2000
Problem: The error messages was
being sent to the monitor window as a received packet rather than as an error
message.
Solution: The error message is now
sent to the monitor window as an error message.
Version: This problem is resolved
in EFILive v3.0.1.44 or later
Temporary workaround: There is no
workaround.
Report: EFI3.0-0006
Description: When capturing data
from certain ECM/PCM's there exists a small timing window after receiving a
heartbeat which must elapse prior to sending a request for data.
Reported by: Barry Tisdale
Date: 5-May-2000
Problem: EFILive does not allow for
this timing window .
Solution: Extra timing
configuration has been added.
Version: This problem is resolved
in EFILive v3.0.1.44 or later
Temporary workaround: There is no
workaround.
Report: EFI3.0-0005
Description: Can't enter a specific
number (like 25) in Milliseconds Between Requests box; as soon as the first
number is entered, advice box pops up, wipes out your entry on clearing.
Reported by: Barry Tisdale
Date: 5-May-2000
Problem: EFILive checks for values
less than 100ms and displays a dialog box warning that frames may be dropped if
such an aggressive capture rate is used. The <100 check is being triggered
when the first digit is being entered.
Solution: The warning is now
displayed as a "tool tip" and the background of the drop down list box
changes to red.
Version: This problem is resolved
in EFILive v3.0.1.44 or later
Temporary workaround: Copy the
value from another application (such as notepad) and paste it into the drop down
list box. Use CTRL-V to paste the previously copied value
Report: EFI3.0-0004
Description: When importing v2
*.ald files, the chart specification for stream attributes is not imported
correctly if more than four series are specified for any chart. In CarBytes v2
more than four series per chart was allowed - in EFILive v3 only four series per
chart is allowed.
Reported by: Barry Tisdale
Date: 29-Apr-2000
Problem: The v2 *.ald import
facility was not checking for nor correcting chart series specifications that
were greater than four. Attributes that were non-charted attributes in the v2
*.ald file were being incorrectly added to the charted-attributes list and
denying legitimate charted-attributes from being added to the charts.
Solution: The v2 *.ald import
facility now treats charted attributes with a series specification of greater
than four as a non-charted attribute. Attributes that are not explicitly set as
'Chart' in the v2 *.ald file now have their chart and series values set to 0 to
prevent them from being added to the charts.
Version: This problem is resolved
in EFILive v3.0.1.44 or later
Temporary workaround: After the v2
*.ald file has been imported, the charted attributes may be corrected manually
in the "Edit Data Stream Attributes" window.
Report: EFI3.0-0003
Description: With "large
fonts", EFILive incorrectly auto-sizes text fields that are aligned with
the parent window's right edge. The fields extend past the right edge of the
window.
Reported by: Beta testing
Date: 10-Apr-2000
Problem: Under investigation.
Solution:
Version:
Temporary work-around: There is
currently no work around.
You can always try extending the
size of the window to reveal more data in the text fields.
Report: EFI3.0-0002
Description: When the chart
inspector is active, the charts' scroll bar can sometimes become visually
corrupted and the charts' scrolling may become erratic.
Reported by: Beta testing
Date: 05-Apr-2000
Problem: Under investigation.
Solution:
Version:
Temporary work-around: Save the
ALDL data stream if required, then exit and restart EFILive.
Report: EFI3.0-0001
Description: If/When certain errors
occur during ALDL recording the ALDL and/or CHATTER buttons remain disabled.
Thus preventing any further use of those buttons.
Reported by: Beta testing
Date: 01-Apr-2000 (No this is not
an April fools joke)
Problem: Under investigation.
Solution:
Version:
Temporary work-around: Click the
STOP button. |