                            InterSystems Corporation
                         Open M for Windows, Version 6.2
                                 March 22, 1995
================================================================================
This is the read me file for DTM 6.2. It contains information that did not
make it into the printed release notes.
--------------------------------------------------------------------------------


DTM Component
=============
A problem with DDP was fixed where the command "S ^X=1.2" would set the value
of ^X equal to 0 in the database.

A problem was fixed where saving a routine from Visual M could cause
a corrupt object code message when the routine was either executed or
zloaded.

An enhancement to the network hardening code has been made. Previously, if a
ISNET connection to a unix machine was made, and the unix box either was
brought down or crashed, and then came back up again, the pc would go into
its hardening loop and remain there until the unix node was marked up again
using the %msqlnet utility. Now the connection is automatically made without
having to mark it up.

The new TCP networking code has been removed from this release. It will be 
available in the next DTM release.

During installation, there is a check for EMS support that looks to see if a
particular driver has been installed. This check will fail if 32-bit file access
is on or you are running Windows NT (or you really don't have EMS support).
You will be warned, but installation will proceed. You will need to make sure
that EMS support is available before you can run DTM.


Visual M Component
==================
Known Problems
--------------
Warning: Beyond 500 characters in a line there be dragons and GPFs!
The line length limit in the M/DeskTop Editor is 511 characters.
This is longer than many M implementations allow.
In most situations, the check on line length is missing at input time,
causing catastrophic failure (GPF) as you exceed the limit.
We'll put the safety checks in the next release.

Changes in Release from FT4
---------------------------
In the installation, if you already have a DTM key file, you will not be
prompted again.

A bug in the dtwx.386 VxD has been fixed. The bug caused MVB server jobs to
disconnect whenever some other DOS box was shut down. Visual M applications
then automatically started another slave server, but without the original
state information. This caused applications to just stop working, as if
communication had been lost with DTM.

The Program Manager Program Group has been thinned out.
Online help has had a major upgrade. A single help file is now provided,
with access to all of the help for all topics. A single demo application is
also provided, that runs any of the available demonstration programs.

Four additional sample directories have been added.
DYNACTRL demonstrates management of dynamically created controls.
DYNAFORM demonstrates management of dynamically created forms.
DYNALIST is an expansion of an earlier demo of long list boxes,
logically containing more members than Windows can handle.
DEMOBOSS is the demo program manager.

Changes in FT4 from FT3
-----------------------
The M/DeskTop editor now supports macro code as defined in the Open M/SQL DBMS
product.

A number of cosmetic and small functional improvements have been made to the
M/DeskTop editor. These include navigation key combinations, autoindent, and
Undo and Redo functions.

The timeout for the automatic startup of the MVB server has been increased to
60 seconds from 20 seconds. This is long enough to support any of the
anticipated target machines.

Three new samples have been included, two small Visual M samples and one showing how to
access DTM from a C or C++ application.

Note: The Visual M custom controls follow documented Visual Basic 3.0 standards
for interfaces. Unfortunately, Microsoft Visual C++ 1.5 does not support all of
the features of Visual Basic above 1.0. Thus Visual C++ cannot use the M/VB
control at the present time. Similarly, PowerBuilder does not support Visual
Basic 3.0 fully, and will thus not work with the M/VB control. The M/DeskTop
control provides Visual M development features for Visual Basic, and is thus not
relevant for other environments.

Changes in FT3 from FT2
-----------------------
Field Test 3 was not generally distributed. It consisted of some changes made
to DTM only.

Changes in FT2 from FT1
-----------------------
CUSTOM.BAS was left out of the released setup kit example. This is a necessary
component if you are building a setup kit of your own.

The default installation target directory was not shown in the initial dialog
box.

The Notice label (lower right) on the main installation background screen was
too far left on 640x480 screens. The logo overlapped it.
