Omni Systems, Inc. |  | Mif2Go User's Guide, Version 55 |  |  |  |  |

> D Technical support for Mif2Go > D.3 How to request help > D.3.1 If the problem involves a crash

### D.3.1 If the problem involves a crash

If you are getting a Windows error message such as the following:

DCL NT console driver has encountered a problem and needs to close.

This means your Mif2Go conversion caused a crash.If the crash happens when Mif2Go is converting a FrameMaker index, see §5.5 Converting FrameMaker-generated files; you might need to add character formats to page numbers. Otherwise, try the following debugging options:

[Options]

; NoNameDel = No (default),

; or Yes (prevent deallocation of name memory)

NoNameDel=Yes

; NoMemDel = No (default) or Yes (prevent deallocation of all memory)

NoMemDel=Yes

First set NoNameDel=Yes. If the conversion still causes a crash, try setting NoMemDel=Yes. Your conversion might run to completion with one or the other of these options; in any event, document the result, so Omni Systems programmers can investigate.

Note: When you set either of these options to Yes, memory deallocation is prevented only while dcl.exe is running; at the end of that (usually brief) process, all memory used by Mif2Go is always freed; no memory leaks occur.

Next: Scope the problem.

> D Technical support for Mif2Go > D.3 How to request help > D.3.1 If the problem involves a crash

| Mif2Go User's Guide: D.3 How to request help |  | Mif2Go User's Guide: D.3.2 Scope the problem |