Basic Troubleshooting When Having Problems with Delta

Last reviewed: June 26, 1995
Article ID: Q131862
The information in this article applies to:
  • Microsoft Delta for Windows, version 1.0

SUMMARY

Many Delta problems can be resolved by following some very basic steps. This article lists those steps and describes the kinds of errors these steps help to resolve. Most of this information is not documented in either the books or the Help files.

MORE INFORMATION

Frequently-Encountered Errors

The following types of error messages are very common and are resolved by following the steps listed in this article:

  • Errors dealing with temporary files.
  • Errors dealing with STATUS.MVM.
  • Errors when trying to execute commands such as SYNCHRONIZE, JOIN, ADD, CHECK OUT, CHECK IN and so on.
  • Errors opening MVMDIFF.EXE.

Step-by-Step Troubleshooting

  1. Make sure the AUTOEXEC.BAT file contains the following variable declarations. While Delta does not implement the TEMP variable, it does use the TMP or the STAT directory tree if the TMP does not exist. Make sure there are no trailing spaces at the end of either of these variable declarations:

    SET TMP=C:\DOS SET TEMP=C:\DOS

  2. Make sure the AUTOEXEC.BAT file has C:\DELTA as the first item in the PATH statement:

    PATH=C:\DELTA;C:\DOS...

  3. If dealing with a networked environment, set the LOCALDRIVES variable in AUTOEXEC.BAT. There should be no space before or after the equal sign or between the comma-delimited drive letters:

    SET LOCALDRIVES=D,E,F

  4. Make sure that there is at least one unassigned drive letter. Delta makes a drive assignment, so it needs to have a drive letter available.

  5. If using the LASTDRIVES variable, make sure there are some unassigned drive letters between A and the value LASTDRIVES is set to. If in doubt, use this setting:

    SET LASTDRIVES=z

  6. If the computer has a SCSI hard drive or CD-ROM drive, try using a semicolon to change the TimerCriticalSection=5000 line in SYSTEM.INI file to a comment:

    ;TimerCriticalSection=5000

  7. Make sure the SYSTEM.INI file has one and only one "device=*vmcpd" line in the 386Enh section. The MVMDIFF.EXE file fails if the virtual coprocessor device statement (device=*vmcpd) is missing or repeated in the SYSTEM.INI file. Delta appears to be working in MS-DOS (outside windows), but it issues the MVMDIFF.EXE error when checking in a text file from within Windows.


Additional reference words: 1.00
KBCategory: kbusage kbtshoot kbdocerr
KBSubcategory: Delta


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 26, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.