A small bug was reported in the base network editor, module 2.12 version 4.2 (you can check the VERSIONS file in the ETC directory if you are not sure which version is installed on your system). During a "LINK MODIFY" operation using the "ALL DATA" attribute option, the attributes "LANES" and "VOLUME DELAY FUNCTION" are not updated in the data base, even if the user has entered new values. Since this problem occurs only with the "ALL DATA" option, the problem can easily be circumvented by activating the individual attribute boxes.
We always strongly warn users that the data base may be corrupted
if the execution of an EMME/2 module is interrupted by powering off the system,
by use of Ctrl-C on PCs or by a "kill -9" on Unix systems.
Fortunately, the EMME/2 data base file emme2bank is quite
robust and survives most power failures and other abnormal program terminations.
However, if such an abnormal termination happens in module 1.22 during or
just after a "copy scenario" operation, there is a possibility that
the data base might be left corrupted. The signs of such a corruption
would be warnings of the type "Inconsistency detected for internal file ...".
If this ever happens to you, do not attempt any further
operations on this data base and call INRO or the EMME/2 Support Center
for assistance. Chances are that this way we can help you to repare the
damage.
Remember: Never shut down, reboot or interrupt the system when a EMME/2 Module is running!
A problem experienced only by PC users who use a graphic tablet using
the Summagraphics Summasketch or MM-Series binary protocol was corrected.
This bug in the E2TABDRV SummaMMb protocol would cause the crosshair cursor
to make a small erroneous step backwards about every 1/4 inch along the
path moved. Since this problem is only present when using the binary
transmission format, it can be overcome easily by using the
ASCII transmission protocol SummaMMa. If you prefer to configure your
tablet to use the binary protocol (e.g. because of other software you
run on your system), please contact INRO or the EMME/2 Support Center
for an updated version of E2TABDRV.
If you are using EMME/2 with a recent version of the IBM or Microsoft mouse driver software, such as MOUSE v6.24, you might have experienced a very annoying delay of half a second or more before every mouse interaction. This is due to a design change (bug?) in the Microsoft driver software and is not present in earlier versions, such as 4.62 or 5.03. A small program to eliminate this delay has been developed by INRO and is now available to users.