• Windows 11 - DMAP V7.4 and later versions run correctly under Windows 11 provded that S Mode is swtched off. This is a simple one-off procedure that is explained on the first occasion that any software that is not S Mode compatible is run.

• With the release of Windows Vista, onwards, Microsoft no longer include the 32-bit Help system file (WinHlp32.exe) needed by earlier versions of DMAP (and many other 32-bit programs).
  Solution: Upgrade to the latest version of DMAP (which uses Compiled HTML for its Help system).

  Note also that the entire DMAP Help documentation can be accessed via the 'DMAP Documentation' icon on the Start Menu.

• 64-bit versions of Windows Vista, 7, 8, 10 and 11: The 64-bit versions of the Windows operating system do not support 16-bit programs, so DMAP V6.5 and earlier versions of DMAP will not run under 64-bit Windows.
  DMAP V7.0 and later versions of DMAP are 32-bit and will run under 64-bit Windows, but the InstallShield installer on the installation CD for DMAP V7.0 to V7.3 fails because it is 16-bit. This was recified in DMAP V7.3a.
  Solution: If you have DMAP V7.3 or earlier, upgrade to the latest version of DMAP.

• If you create a new data file but DMAP displays the error message 'File Not Found', it may be caused by the way recent versions of Windows deals with and displays file names. Unlike earlier versions of Windows, recent versions allow very long file names and also multiple 'extensions'. So, for example, if you use Notepad to create a boundary file and then save it as a file named berks.bdy, Notepad will actually save it as berks.bdy.txt and DMAP will not find it when it looks for berks.bdy. In addition, when you use Windows Explorer (File Explorer in Windows 8 onwards) to look for berks.bdy it appears to exist because, by default, Explorer does not display the full file name! A solution to this is to change the settings of Explorer:

  Windows 95/NT
  Select View|Options... and then make sure that the check box labelled 'Hide MS-DOS file extensions' is unchecked.

  Windows 98/ME/2000/XP
  Select View(or Tools)|Folder Options... then select the View tab and make sure that the check box labelled 'Hide file extensions for known file types' is unchecked.

  Windows Vista
  Select Organize|Folder and Search Options, then select the View tab and make sure that the check box labelled 'Hide file extensions for known file types' is unchecked.

  Windows 8/10
  Select File|Change folder and search Options, then select the View tab and make sure that the check box labelled 'Hide file extensions for known file types' is unchecked.

  After changing this settting, you can then see the real full file name and change it if necessary. To avoid the misnaming of files when saving them, the file name can be placed between double quotes, for example, "berks.bdy". Remember also that versions of DMAP before V7.0 do not accept long file names, so the file name must consist of a maximum of 8 characters for the name and a maximum of 3 characters for the extension.

Below is a list of some known, mostly minor, problems which can occur in some circumstances with earlier versions of DMAP. If you are significantly affected by any of these problems, the solution is to request an update to the latest version.

• Stray lines appear across maps digitized with the DMAP Digitizer for co-ordinates south or west of the SW Grid Reference Map Parameter. Affects V6.5f and V6.5g. Fixed in V6.5h.
• UTM Grid References in Latitude Zone N (0° - 8°N) inaccurately interpreted. Affects V5.0 to V6.5b.
• Scrollbars for adjusting map colours, symbol colours and quantity grey levels do not function correctly. Affects V6.0 to V6.3a, particularly when running under Windows NT.
• Save All facility for PostScript files (EPS and PS) may allocate incorrect file names. Affects V5.5 and V5.6. Fixed in V5.6a.
• Coincidence total for first grid reference encountered in DIS file may be incorrect if Key switched on during generation of coincidence totals. Affects V4.0 to V5.3.
• System Resources dwindle with repeated map production. Affects versions of DMAP before V5.2a under Windows 95, and versions before V4.6 under Windows 3.x.
• Metafiles too tightly clipped, sometimes leading to partially missing grid numbers or map frame when imported into some types of word processor software. Affects versions of DMAP before V4.7.
• Error message: "Polyline Failed". Affects DMAP version V4.5 only.
• EPS files not accepted by some types of software running under UNIX and Commodore/Amiga systems. Affects versions of DMAP before V4.6.
• Metafiles not accepted by some types of word processor software. Affects versions of DMAP before V3.0a.
• Symbol type assignment priority for duplicated grid references may be incorrect in some circumstances. Affects versions of DMAP before V3.0.
• Printer setup dialogue does not display all installed printers when multiple printers are installed on the same port. Affects DMAP version V1.0 only.

Below is a list of some run-time errors which can occur with inappropriate data or map parameters. The most likely cause(s) of these errors are also listed.

• File access denied
  • This error message is displayed when DMAP attempts to write data to a file but the file attributes have been set to Read-only. The main way in which this occurs is when files have been copied from one location to another via a CD Writer. Most CD Writers automatically set file attributes to Read-only during the copying process, and this is adverseley affecting all sorts of software, including DMAP. In the Dmapw folder, the following files must NOT be Read-only: all .PAR files, DMAPFGP.TXT, and the temporary .$$$ files. To correct the situation, use Windows Explorer to locate these files, right-click on the file name, choose Properties from the floating menu, and then make sure that the check box labelled Read-only is unticked.
• I/O error 32
  • Caused by one of the data files being open in another program. Solution: Close the program in which the data file is open.
• run time error 104 or I/O error 104
  • Caused by one of the data files being a binary file rather than a text file. Most often caused by saving a data file as a word processor 'document' rather than a 'text' or 'non-document' file. Solution: open the file in your word processor and re-save as a text file.
• run time error 200 or invalid floating point operation or floating point division by zero
  • Caused by Symbol Size Map Parameters being set to zero.
  • Caused by NE Grid Reference Map Parameter being set to same value as SW Grid Reference Map Parameter.
  • Caused by moving the mouse during a 'Save All' or 'Print All' operation. Solution: do not move the mouse during these operations.

If you wish to update to the most recent version of DMAP, Contact Alan Morton

Home Page