Make Compatible is a program developed by Microsoft that is included with Windows 9x operating systems. It changes per-program system settings in Windows to allow Windows 3.1 programs that are tailored specifically to that platform to execute under newer versions. The name of the program image file for Make Compatible is mkcompat.exe, and it is stored in the \Windows\System directory.
When it is invoked, one can choose the name of the Windows 3.1 application program image file using the "Choose Program" option on the "File" menu. After the program image file is chosen, Make Compatible by default displays a list of five options that can be set to alter the behaviour of Windows for that program when it is executed:
- Don't spool to enhanced meta files
- Give application more stack space
- Lie about printer device mode size
- Lie about Windows version number
- Windows 3.1-style controls
An advanced options mode, selectable via the "Advanced Options" selection on the "File" menu presents a longer list of options, allowing finer control of Windows 3.1 emulation if the particular application requires it.
Each line names an application program, and gives a hexadecimal numeric constant to associate with that program. The hexadecimal numeric constant encodes the compatibility bitflags for that particular application, that Windows applies when the application is executed. Make Compatible merely provides a graphical user interface for editing these flags in an easy way, rather than editing win.ini manually, with a text editor. It allows one to set and unset individual flags without having to know their numeric values.
The compatibility bitflags settable in win.ini are not documented in the WININI.WRI file that ships with Windows 3.1, or in the Microsoft Windows 3.1 Resource Kit published by Microsoft. They are listed as a simple set of defined constants (with names beginning "GACF_" for "GetAppCompatFlags"), without explanation, in the windows.h header file that is shipped with the Microsoft Windows 3.1 Device driver Development Kit. In Windows 3.1, the compatibility flags that are in effect for any given task in the kernel's Task Database are readable via the undocumented
GetAppCompatFlags() function that is exported from the KERNEL module.
Advanced mode flags
The flags are documented in Microsoft KnowledgeBase article #82860. They correspond to the "advanced mode" flags that are settable by Make Compatible's "Advanced Options" menu:
- 30 average width metrics
- This is bit #19 of the compatibility bits word, with hexadecimal value
0x80000, known by the symbolic name
GACF_30AVGWIDTHin windows.h. This flag causes Windows to re-scale all fonts by a factor of when calculating their average character widths. The reason for this is that one particular Windows 3.0 application, TurboTax, hard-coded the values that it was using for such size calculations, which failed to work correctly with the new TrueType-compatible font average width calculation method employed by Windows 3.1. This prevented people from using TurboTax to print their income tax return forms on PostScript printers.
- Always send NC_Paint
- This is bit #6 of the compatibility bits word, with hexadecimal value
0x40, known by the symbolic name
GACF_ALWAYSSENDNCPAINTin windows.h. This flag forces any call to
SetWindowPos()to cause the sending of
WM_NCPAINTmessage to all child windows. This is the Windows 3.0 behaviour. In Windows 3.1, the behaviour was changed so that the window message is only sent to those windows that need their non-client areas to be repainted. Some Windows 3.0 applications, however, relied upon always receiving this message, to determine whether child windows needed repositioning.
- Don't enum device fonts
- This is bit #14 of the compatibility bits word, with hexadecimal value
0x4000, known by the symbolic name
GACF_ENUMTTNOTEDEVICEin windows.h. This flag causes Windows 3.1 to turn the
DEVICE_FONTTYPEflag off in particular circumstances when an application that is wanting to print enumerates fonts. The particular circumstances are when the target printer is not either a dot matrix printer or a PostScript printer, and the fonts are TrueType fonts that are not resident in the printer itself. In such circumstances, some applications (including PageMaker and MGXDraw) misinterpret the flag and believe the font to be device-resident. (TrueType fonts can be uploaded by Windows to printers, and need not be resident on the device itself to be usable.) They then query the printer to see what sizes of the font it supports, and when that fails (because the printer doesn't know about the font until it is uploaded), they incorrectly assume that the font cannot be resized. Setting the
DEVICE_FONTTYPEflag to false in such situations prevents the applications from going wrong, and that is what this compatibility bitflag does.
- Don't send calcsize
- This is bit #17 of the compatibility bits word, with hexadecimal value
0x20000, known by the symbolic name
GACF_NCCALCSIZEONMOVEin windows.h. This flag forces the
WM_NCCALCSIZEmessage to be sent to a window that is being moved or resized. This is the Windows 3.0 behaviour. In Windows 3.1, the behaviour was changed so that the window message is only sent to those windows that were being resized. It was not sent if the window was merely moved. Some Windows 3.0 applications, however, such as Lotus Notes for example, relied upon always receiving this message.
- Enum Helv and Times Roman fonts
- This is bit #12 of the compatibility bits word, with hexadecimal value
0x1000, known by the symbolic name
GACF_ENUMHELVTMSRMNin windows.h. This flag works around a problem with applications that refused to work properly unless fonts with the exact names "Helv" and "Tms Rmn" were listed as present on the system by the Windows font enumeration API. The names are trademarks of Linotype company for particular fonts, Helvetica and Times Roman, and since Microsoft didn't ship those Linotype fonts with Windows 3.1, it could not enumerate them as present. This flag causes Windows to enumerate the "MS Sans Serif" and "MS Serif" fonts under the names "Helv" and "Tms Rmn", for compatibility with the applications that don't work without those exact names being used.
- Force extra windows words
- This is bit #8 of the compatibility bits word, with hexadecimal value
0x100, known by the symbolic name
GACF_MOREEXTRAWNDWORDSin windows.h. This flag works around a problem with applications that assumed the existence of window words (extra items of data associated by Windows with GUI windows) when they had not in fact informed Windows that extra window words were required. Windows 3.1, unlike Windows 3.0, bounds checks all uses of extra window words, and applications that assumed that they could use more space than they had asked for would thus fail. For applications run with this flag set, Windows 3.1 silently increased the total number of words requested by the application by an extra 4 bytes.
- Force printer text to new band
- This is bit #1 of the compatibility bits word, with hexadecimal value
0x2, known by the symbolic name
GACF_FORCETEXTBANDin windows.h. This flag causes Windows 3.1 to always use two bands when printing, the first for graphics and the second for text. Normally Windows 3.1 tries to print both in a single band. But applications such as WordPerfect assumed that a second band would always exist, and would always be where the text was, as had been the case in Windows 3.0. Freelance Graphics had a similar problem.
- Force TT fonts to graphics band
- This is bit #15 of the compatibility bits word, with hexadecimal value
0x8000, known by the symbolic name
GACF_FORCETTGRAPHICSin windows.h. This flag was to work around a problem with Freelance Graphics, where it wouldn't print using TrueType fonts unless they were printed as graphics.
- Global hooks only called for Win16 apps
- Ignore discardable segment attributes
- This is bit #0 of the compatibility bits word, with hexadecimal value
0x1, known by the symbolic name
GACF_IGNORENODISCARDin windows.h. This flag forces the
GEM_NODISCARDflag passed to
GlobalAlloc()by a program to be ignored. It worked around a bug in the run-time library supplied with Microsoft's own C compiler, Microsoft C version 6. The run-time library would erroneously set that flag in calls to
GlobalAlloc(), and any application compiled with that compiler would thus exhibit the behaviour.
- Ignore raster fonts
- This is bit #9 of the compatibility bits word, with hexadecimal value
0x200, known by the symbolic name
GACF_TTIGNORERASTERDUPEin windows.h. This flag prevents fonts of the same sizes from being enumerated as both bitmap and TrueType fonts. This was because several applications, including WordPerfect and Visual Basic, were not capable of handling that particular situation correctly.
- Ignore topmost windows
- This is bit #3 of the compatibility bits word, with hexadecimal value
0x8, known by the symbolic name
GACF_IGNORETOPMOSTin windows.h. This flag fixes a particular problem with cc:Mail that caused it to fail on Windows 3.1. It assumed that accessing the first window with
GetWindow(HWND,GW_HWND_FIRST)would return it the window of the application that it had just started with
WinExec(). But on Windows 3.1, which introduced the idea of "topmost" windows, this was no longer true. The flag caused Windows 3.1 to skip topmost windows when that particular API request was made.
- Module specific hack
- No HRGN 1
- This is bit #16 of the compatibility bits word, with hexadecimal value
0x10000, known by the symbolic name
GACF_NOHRGN1in windows.h. This flag reinstates a bug that existed in Windows 3.0 that was fixed in Windows 3.1. It did so because several applications, such as Microsoft Draw, worked around the bug themselves, and would fail to work correctly when the bug was eliminated. The bug was an error in the return value of the
GetUpdateRect()function, whereby in certain situations (where the entire window was invalid) it would return the coördinates of the update rectangle in window coördinates, rather than in logical coördinates as it was supposed to. In Windows 3.1, it always returned the update rectangle in logical coördinates. The applications that worked around the bug would perform the coördinate transform themselves to work around the bug, and end up updating the wrong parts of their windows on Windows 3.1.
- One graphic band and use print escapes
- This is bit #2 of the compatibility bits word, with hexadecimal value
0x4, known by the symbolic name
GACF_ONELANDGRXBANDin windows.h. This flag causes Windows 3.1 to use a single graphics band when printing in Landscape mode, consuming as much memory as needed for that band, and discarding whatever content would not fit into the band.
- Subtract clip siblings
- This is bit #14 of the compatibility bits word, with hexadecimal value
0x4000, known by the symbolic name
GACF_SUBTRACTCLIPSIBSin windows.h. This flag causes Windows 3.1 to handle window invalidation differently for top-level windows that do not have the
WS_CLIPSIBLINGSwindow style set, and their chlid windows. (In other words: It affects dialogue boxes and the controls on them.) With the flag set, Windows would not invalidate sibling child windows underneath (in the z-order) other
WS_CLIPSIBLINGSchild windows. The main reason for the flag was applications such as Lotus Notes 2.1, which implemented its own combo boxes as child windows, rather than as top-level windows (the system default combo box implementation). With this flag set, odd display problems with such windows would disappear.
- Support multiple printing bands
- This is bit #5 of the compatibility bits word, with hexadecimal value
0x20, known by the symbolic name
GACF_MULTIPLEBANDSin windows.h. This flag causes Windows 3.1 to always use multiple bands for printing, even when one band would be sufficient. This was to work around a problem in Freelance Graphics, which would assume that if only one band existed, and it was the entire page, it was the text band, and would not even attempt to print graphics. On Windows 3.1, the universal printer driver would sometimes be able to handle both text and graphics with a single band. By forcing the use of multiple bands, the problems that this would cause for Freelance Graphics were avoided.
- TT fonts are device fonts
- This is bit #4 of the compatibility bits word, with hexadecimal value
0x10, known by the symbolic name
GACF_CALLTTDEVICEin windows.h. This flag causes Windows 3.1 to always set the
DEVICE_FONTTYPEflag on any TrueType fonts that are enumerated using the Windows
EnumFont()API. This was to fix a problem with applications including AmiPro and WordPerfect, both of which assumed that all TrueType fonts available on a printer would be device-resident.
- Windows 3.1 palette behavior
Windows 3.1 defined 20 application compatibility flags. Windows 95 and 98 defined a further 11 flags, not documented in the KnowledgeBase article and not assigned symbolic constant names in windows.h, which are the remainder of the options accessible via the "Advanced Options" menu in Make Compatible:
- Disable 16 color brush cache and 55ms timer
- This is bit #29 of the compatibility bits word, with hexadecimal value
- Disable EMF spooling
- This is bit #26 of the compatibility bits word, with hexadecimal value
- Disable font associations
- This is bit #24 of the compatibility bits word, with hexadecimal value
- Don't attach input thread when journaling,
- This is bit #28 of the compatibility bits word, with hexadecimal value
- Don't Shutdown/Ignore certain faults/dequote commandline
- This is bit #25 of the compatibility bits word, with hexadecimal value
- Enable 3.x UI features
- This is bit #27 of the compatibility bits word, with hexadecimal value
- Force Win31 printer dev mode size
- This is bit #23 of the compatibility bits word, with hexadecimal value
- Increase stack size
- This is bit #22 of the compatibility bits word, with hexadecimal value
- Lie about device caps/no
- This is bit #20 of the compatibility bits word, with hexadecimal value
- Lie about windows version
- This is bit #21 of the compatibility bits word, with hexadecimal value
- Mirror fonts in win.ini
- This is bit #30 of the compatibility bits word, with hexadecimal value
- Tim O'Reilly, Troy Mott, and Walter J. Glenn (1999). "Make Compatible". Windows 98 in a Nutshell. O'Reilly. pp. 227–228. ISBN 978-1-56592-486-4.
- Charles J. Brooks (2002). A+ Certification: (Exams 220-221, 220-222) (4 ed.). Que. p. 799. ISBN 978-0-7897-2844-9.
- Ron Petrusha (1 August 1999). "Where Am I Running?". windowsdevcenter.com. O'Reilly Media, Inc.
- Ed Bott and Woody Leonhard. "Running Older Apps". "95 Only Undocumented Secrets". Ziff-Davis Publishing Company.
- Andrew Schulman, David Maxey, and Matt Pietrek (1992). "KERNEL: Windows system services". Undocumented Windows. Addison-Wesley. pp. 244–250. ISBN 0-201-60834-0.
- Rick Coogle. "Windows' 16-bit Program Compatibility Hacks". Retrieved 10 February 2009.
- Microsoft Windows 95 Resource Kit. Microsoft Press. 1995. pp. 718 et seq. ISBN 978-1-55615-678-6.
- "MKCOMPAT Makes Old Programs Behave". Smart Computing 8 (7) (Sandhills Publishing Company). July 1997.
- "How to Use Mkcompat.exe for Windows 3.1-Based Programs". Microsoft KnowledgeBase. 1.2 (Microsoft). 20 January 2007. KBID 173086.
- "The WIN.INI [Compatibility] Section". Microsoft KnowledgeBase. 1.0 (Microsoft). 25 December 2000. KBID 82860.