Copyright: Copyright © 1997, 1998 by Microsoft Corporation.  All Rights Reserved.
Citation: Copyright © 1997, 1998 by Microsoft Corporation.


Introduction
Introduction to MDT

The Microsoft Minidriver Development Tool (Microsoft MDT) is a Windows XP® software tool designed for easy development of minidrivers that enable the Microsoft Universal Printer Driver (Unidrv) to support new non-Postscript® printers.

•      Minidriver New Wizard

Property sheet-based wizards for creating new file, project and converting projects.

•      Minidriver Conversion Wizard

Automatically converts existing minidriver files to versions that can be used with Windows XP Unidrv.

•      Generic Printer Description (GPD) Editor

Syntax-checking text editor for modifying the GPD files that make up Unidrv minidrivers.

•      Unidrv Font Metrics (UFM) Editor

Property sheet-based editor for modifying Unidrv Font Metrics files.

•      Glyph Translation Table (GTT) Editor

   Property sheet-based editor for modifying Glyph Translation Table files.

•      String Resource Editor

Dialog box for modifying text strings contained in a minidriver's resource file (.rc file).

•      Minidriver Workspace

Window-based editing workspace for a Unidrv minidriver, providing access to the minidriver's GPD, UFM, GTT, and resource files.

•      INF Wizard

Automatically creates INF files required for installing Unidrv minidrivers.

For additional information about the Microsoft Universal Printer Driver (Unidrv), see the Windows XP DDK.


Minidriver Workspace

A minidriver workspace contains all of the files associated with minidrivers that use a single resource DLL. Workspace information is stored in an .mdw file. A workspace maintains the following information:

•	The list of files used to create a minidriver resource DLL, along with their resource identifiers. These files include the RC file and all GTT and UFM files.

•	The GPD files that use the resource DLL.

Within a minidriver workspace, you can edit GPD, UFM, and GTT files. You can also edit string resources defined by the RC file.

Each printer model must be described by a separate GPD file. However, it is common to use a single resource DLL for several printer models, with the various models sharing a set of resources ( such as UFM and GTT files, and string tables). Thus several GPD files, each describing a different printer model, are typically associated with a single resource DLL.

Each workspace should include all of the GPD files associated with a resource DLL, so the workspace can access all identifiers for fonts and other resources. GPD files can be added to and deleted from a workspace.

To create a minidriver workspace, select New from the File menu (or press CTRL+N) to start the Minidriver New Wizard

When the wizard completes a creating new project or conversion, MDT displays a minidriver workspace window so you can edit minidriver files.


Minidriver Conversion Wizard

The Minidriver Conversion Wizard converts binary minidrivers, used with previous versions of Windows and Windows NT, into text-based minidrivers for Windows XP. When you use the Wizard, it creates a Windows XP minidriver by converting the following files:

Input files	File Contents	Output Files
Windows GPC files	Printer capability descriptions	Windows XP GPD files
Windows PFM files	Font descriptions	Windows XP UFM files
Windows CTT files	Glyph translations	Windows XP GTT files
Additionally, the wizard generates resource files (.rc files) with the correct file names and resource identifiers.

The wizard creates a minidriver workspace, which allows you to easily edit all of these files. You can also edit string resources.

If the wizard detects errors within a .gpd file, it adds error messages to the file as comments.

The wizard creates localized minidrivers, using built-in code page information, without requiring the use of a system set up for the locale in which the minidriver is to be run.

For more information about minidriver creation, see Creating a Minidriver.

To run the Minidriver Conversion Wizard, select New from the File menu (or press CTRL+N) and go to the converters tab and select the project button, Then follow the wizard’s instruction.


INF Wizard

The INF Wizard automatically creates an INF file for your minidriver. INF files are required for installing Unidrv minidrivers, and are described in the Windows XP DDK.

Before the INF Wizard creates an INF file, it allows you to customize the file contents. The Wizard places the new file in a window within the minidriver workspace, so you can view the file and make additional modifications, if necessary.

The INF Wizard is available whenever a minidriver workspace window has focus.

To create an INF file:

Select Generate INF in the File menu (or press F9) to run the INF Wizard, then follow the wizard's instructions. This creates an INF file window.

To check an INF file's contents:

While an INF file window has focus, select Check INF in the File menu (or press F8). This verifies that the files listed in the INF file exist.

To modify an INF file:

While an INF file window has focus, select Change INF in the File menu (or press F9) to rerun the INF Wizard, then follow the wizard's instructions. This modifies the contents of the INF file window.

To save an INF file:

Select Save or Save As in the File menu, or close the INF file window and select Yes in the resulting pop-up window.


Glyph Translation Table (GTT) Editor

A glyph translation table specifies the selection strings required to print characters associated with the code points within code pages. The GTT editor is a property sheet-based dialog box that allows you to modify selection strings, add code points, and change the code pages used.

When you open a .gtt file, MDT creates a GTT Editor Window. You can open a .gtt file by the following methods:

•	In the minidriver workspace window, double-click on a GTT name under the workspace's "GTTs" tree node.

•	In the Windows Explorer, double-click on the file's name.


Unidrv Font Metrics (UFM) Editor

Each of a printer's device-resident fonts must be described by a Unidrv font metrics file (.ufm file). The UFM editor is a property sheet-based dialog box that allows you to modify a font description. The editor lets you view and modify the C-language structures used for creating .ufm files.

0	All structures displayed by the dialog box are described in the Windows XP DDK. You should refer to the DDK for information about each structure's members.

1	When you open a .ufm file, MDT creates a UFM editor window. You can open a .ufm file by the following methods:

•	In the minidriver workspace window, double-click on the name of a font under the workspace's "UFMs" tree node.

•	In the Windows Explorer, double-click on the file's name.

•	In the GPD Editor Window, double-click on the associated font's resource identifier, if the identifier is represented numerically in the .gpd file.


Generic Printer Description (GPD) Editor

The characteristics and capabilities of each printer model supported by Unidrv must be specified by a generic printer description, contained in one or more .gpd files. The GPD editor is a text editor that allows you to view, modify, and check the syntax of a .gpd file.

0	When you open a .gpd file, MDT creates a GPD Editor Window. You can open a .gpd file by the following methods:

•	In the minidriver workspace window, double-click on a GPD name under the workspace's "GPDs" tree node. This creates a GPD Editor Window.

•	In the Windows Explorer, double-click on the file's name.


String Resource Editor

A single resource file (.rc file) is associated with each minidriver workspace. The string resource editor allows you to add, remove, or modify string resources contained in the .rc file.

0	To edit a minidriver's string resources, you must open a String Resource Editor Window. Two methods are available:

•	Double-click on "Strings" under the "Resources" tree node in the minidriver workspace window.

•	Double-click on a string's resource identifier in the a GPD Editor Window, if the identifier is represented numerically in the .gpd file.


String Resource Editor Window

A String Resource Editor window displays the string resources contained in a single .rc file. One .rc file is associated with each minidriver workspace. For existing string resources, you can modify resource identifier numbers and associated text strings, or you can delete the resource. You can also add new string resources.

To edit a string resource:

Double-click on the resource's identifier or text string, then use the keyboard to modify or replace the existing identifier or text string.

To add a string resource:

Use the Up Arrow and Down Arrow keys to highlight an existing resource, then press Insert and type in new values. The new resource is added above the resource you highlighted.

To delete a string resource:

Use the Up Arrow and Down Arrow keys to highlight an existing resource, then press Delete.


Master Units

Master units are the least common multiple of the various resolutions your printer supports. Typically, they represent the highest resolution provided. For more information about master units, see the Windows XP DDK.


Font Units

A font unit is the smallest addressable unit within a font's em square. Font units are used to specify all font measurements except resolution (which defines the master units), italic angles (specified in 10ths of a degree) and character weights (specified without units).

0	If a font is scalable, font units might have a greater resolution than master units. If a font is not scalable, font units are identical to master units.


About Box

The About dialog box describes the program version, and gives you some information about the your system.

•	The version of MDT you are running

•	Memory and disk space currently available on your system

•	Code pages currently available on your system

•	All code pages known by your system

If a code page is listed by number but does not include a description, a definition of the code page's purpose was not available when the Minidriver Development Tool was released.


Tip of the Day

The Tip of the Day dialog box presents a series of useful tips for using the Minidriver Development Tool and working with minidriver source files. The tips are stored in a file named tips.txt, in the directory in which the program files reside. Each tip is a line in the file. If others in your organization will be using this program, you might want to add your own tips to the file.


Creating a Minidriver

A Unidrv minidriver consists, minimally, of one or more .gpd files and a resource DLL. The resource DLL defines all text, icon, bitmap, and font resources required by the minidriver. Additionally, .ufm and .gtt files might be needed to describe the characteristics of device-resident fonts.

There are several ways for the MDT to create a Unidrv minidriver for Windows XP

1.	You can use the Minidriver New Wizard for creating a new project from the scratch with your selected template (.gpd file)

2.	If you have an existing Win16 or Win32 minidriver, created for earlier versions of Windows or Windows NT, you can convert it by using the Minidriver Conversion Wizard.

3.	If you just want use existing resource and gpd files, you can base the minidriver on one provided with the Windows XP DDK. You can find sample .gpd files under the /gpd subdirectory of the Windows XP DDK.

For each sample .gpd file, an associated .rc file can be found in the DDK's /gpdres subdirectory. Copy and rename the .gpd and .rc files you intend to use, then modify them as needed.

If the new printer supports device fonts, .ufm and .gtt files must be provided. You might be able to use .ufm and .gtt files supplied with the DDK (modified if necessary).

An additional step to creating a minidriver involves building a resource DLL.

After a minidriver has been created, it can be installed using an INF file. You can use the INF Wizard to create an INF file automatically.


Building a Resource DLL

Build a resource DLL is different by what you have used for creating a project. If you used Minidriver New Wizard, the target directory would contain an .rc file that lists the .gtt and .ufm files needed to build the resource DLL, and source, makefile, .def for build. In this case, you just save the project first and then go to DDK’s free or checked build environment (The .rc file is not created until you save the workspace file in the workspace.)

However, if you used Minidriver Conversion Wizard, the target directory would contain only an .rc file that lists the .gtt and .ufm files needed to build the resource DLL. You can find templates for the other files you will need in the DDK samples. To build a resource DLL in the target directory, you must add the following files to that directory:

•	A sources file specifying the files to be built, and the target file's name, path, and type. You can copy this file from one of the DDK's minidriver subdirectories and edit it as needed. (If you are basing your sources file on one in the DDK, you should place the target directory be under the \gpdres subdirectory of the DDK's printer sources path.)

•	An unedited copy of makefile. A copy of this file is located in each of the DDK's minidriver subdirectories.

•	A module definition (.def) file, containing the resource DLL's name in the file's LIBRARY statement.

After these files have been placed in the target directory, you can start the DDK's free or checked build environment and type build. (For more information about build environments and the build utility, see Windows XP DDK documentation.)

Within the minidriver's .gpd file is a *ResourceDLL entry. This entry must identify the name of the minidriver's resource DLL. For more information about the *ResourceDLL entry, see Windows XP DDK documentation.

If you are supporting several printer models that share common resources, it is best to create a single resource DLL that can be used by all of the models' minidrivers. This technique saves both disk space and the amount of time required to localize minidrivers.

Microsoft provides stdnames.gpd with the Windows XP DDK. This file identifies string resources for many standard text strings used with printer minidrivers. Whenever possible, use the strings identified by stdnames.gpd instead of replicating them in your resource DLL.


Minidriver New Wizard

The Minidriver New Wizard has three tabs entitled New File, Project, and Converter. You can use each wizard for creating a file, creating a project, and the conversion of a project, pfm or ctt.

File Tab

The wizard can create new file (.GPD, .UFM, and .GTT) from the scratch in this page.

Project Tab

The wizard can create a new project from the scratch based of template.

The wizard can create the minidriver workspace window, which allows you easily edit all of gpd, ufm and gtt files.

Additionally, the wizard generates build environment files such as .rc, makefile, source,.def files. If you want to use these resources for adding more models, you just add the file names into the source file after creating or copying .gpd files into project directory.

The wizard provides an option to add a new template into the project template list. This added template file (.gpd) copied to under \\template directory of minidev.exe root. If you want to change the contents of template, you can modify this file directly.

The ufm and gtt files that need to be added into the wizard through Project creation should not have the read-only active.

The wizard use pcl.txt file, which will be created at minidev.exe root after first project creation, when they create strings in the .rc file. You can edit or add new strings into pcl.txt for your own template (.gpd) file.

Converter Tab

The wizard provides converters for project (Minidriver Conversion Wizard), PFM, and CTT.

The PFM converter wizard allows conversion from PFM to UFM through a specific GTT file and code page, but this wizard does not support DBCS code page.

The CTT converter wizard provides conversion from CTT to GTT through selected code page.


Minidriver Workspace Window

The workspace window provides a tree view of the components of a minidriver workspace. Workspace components include one resource file (.rc file) and all the .ufm, .gtt, and .gpd files associated with the .rc file.

The top node of the tree contains the workspace name. The minidriver conversion wizard sets this name to match the name of the workspace's .rc file. To change the workspace name, right-click on the node and select Rename from the node's context menu.

Expanding the top node reveals nodes for resources (.ufm files, .gtt files, and strings) and the model information (.gpd files). The number of items the node contains is a part of each node’s label.

Lower-level nodes represent each .ufm, .gtt, and .gpd file contained in the workspace.

A context menu is provided for each node of the tree view. To see a node's context menu, right click on the node. These menus vary by node type, but typical options include expanding and collapsing the nodes, changing display names or file names, and adding or removing files.

A workspace's component list is stored in a .mdw file. If you add, remove, or modify tree nodes in the workspace window, you can save the changes by selecting Save or Save As from MDT's File menu. You can also use Save As to make a copy of a workspace.

MDT allows you to open several workspace windows at once.

To create a new workspace:

Select New from the File menu (or press CTRL+N) to start the Minidriver New Wizard then go to a Project tab for creating a project from the scratch or go to a Converter tab for using conversion wizard..

To edit a .ufm, .gtt, or .gpd file:

In the workspace window, double-click on the node representing the file you want to edit, or highlight the node and press Enter.

To add a .ufm, .gtt, or .gpd file to a workspace:

In the workspace window, right-click on the "UFMs", "GTTs", or "GPDs" node and select Add from the context menu.

To remove a .ufm, .gtt, or .gpd file from a workspace:

In the workspace window, right-click on the UFM, GTT, or GPD file's tree node and select Remove from its context menu.

To change the name of a .ufm, .gtt, or .gpd file:

In the workspace window, expand the file's node to reveal a node containing the file's name. Right-click on this node and select Rename from the node's context menu.

For .gpd files, the filename node also contains the path. If you change the path of a .gpd file, the file is moved the next time it is saved.

To edit resource strings:

Double-click on the "Strings" node.

To create an INF file for a minidriver:

Select Generate INF from the File menu, which starts the INF Wizard.

To save changes to workspace tree nodes:

Select Save or Save As from the File menu.

To make a copy of a workspace:

Select Save As from the File menu.

Workspace Shortcut Keys

F2	Open a node label for editing, if it can be edited.
F8	Check the currently open INF file.
F9	Start the INF Wizard.
F10	Display a selected node's context menu.
Up Arrow Down Arrow Page Up Page Down	Navigate the tree without expanding or contracting it.
Left Arrow Right Arrow	Expand (right) and collapse (left) the currently selected tree node.
Delete	Remove the currently selected item, if it can be removed.
Enter	Cause a node's default action to occur. For most nodes, this expands or collapses the node.  For file nodes, it opens the file for editing.


GTT Editor Window

Each GTT editor window displays the contents of a single Glyph Translation Table file (.gtt file). Each .gtt file contains the selection strings Unidrv must send to the printer to select characters within selected code pages. The file also contains the selection strings Unidrv must send to select specific code pages.

The GTT editor includes two tabs:

•	Code Points and Encodings

•	Code Pages Used

For more information about Glyph Translation Table files, see the Windows 2000 DDK.


Code Points and Encoding Tab

The Code Points and Encodings tab displays the selection string for each code point contained in the .gtt file.

You can sort the displayed information by selection string, by code point, or by code page by clicking on any of the column titles.

If you type a letter or number, the list will scroll to the first selection string that begins with the typed character.

To edit a selection string:

Right-click on the selection string you want to edit, then select Change Selection String from the context menu. These strings must be specified in C-language string literal format. Non-alphanumeric characters are represented using the hexadecimal escape (\xnnn). For example, \x1B represents the ASCII escape character. The octal escape (\nnn) is not allowed.

To add a code point:

Right-click anywhere in the code point list and select Add... from the context menu. A list of unused code points will be displayed. Select one or more unused code points from the list, then click on OK.

To select several code points, hold down the Shift key while clicking on each code point. To select a range, click on one code point then hold down the Ctrl key while clicking on another code point.

Each unused code point appears only once on this list, even if it is contained in more than one available code page. After you have added a code point, you can change its code page.

To delete a code point:

Right-click on the code point you want to delete, then select Delete... from the context menu.

To change the code page used for a code point:

Right-click on the code point for which you want to change the code page, then select Change Code Page from the context menu. A list of available code pages will be displayed. Select a code page from the list. (To make additional code pages available, go to the Code Pages Used tab.)

Note that when you change the code page for a code point, the editor does not verify that the code point is defined in the new code page.

Keyboard Shortcuts

F2	Edit the currently selected selection string.
F10	Add a code point.
Delete	Remove the currently selected code point.


Code Pages Used Tab

The Code Pages Used tab allows you to view and change the list of available code pages and, optionally, to specify the command strings that must be sent to the printer to select or deselect each code page.

To make a code page available:

Click on the Add Page... button, and select a code page from the list.

To make a code page unavailable:

Select a code page name, then click on Remove.

To specify a command string that selects or deselects a code page:

Select a code page name, then type the strings in the Select and Deselect boxes.

Specify selection strings in C-language string literal format. The hexadecimal escape (\xnnn) must be used for non-alphanumeric values. The octal escape (\nnn) is not allowed.


UFM Editor Window

Each UFM editor window displays the contents of a single .ufm file. Each .ufm file describes a device-resident font. Font descriptions consist of a set of C-language structures. Each tab in the editor window allows you to view and modify the contents of one or more of these structures.

All .ufm file structures are described in the Windows 2000 DDK. You can find each structure's name in the DDK index.

Headers Tab

Allows you to modify the .ufm file's UNIFM_HDR and UNIDRVINFO structures.

IFIMETRICS Tab

Allows you to modify the .ufm file's IFIMETRICS structure.

EXT METRICS Tab

Allows you to modify the .ufm file's EXTTEXTMETRIC structure.

Widths Tab

Allows you to modify character widths, in font units, for variable pitch fonts.

Kerning Pairs Tab

Allows you to specify kerning pairs. If the kern amount is a positive value, the two characters are moved further apart; if the value is negative, the characters are moved closer together.

Units for Font Metrics

Scalable fonts are described in arbitrary font units. These units are mapped to master units at the unscaled size of the font, using information on the Scalability Metrics tab.

For all other fonts, metrics are specified in master units.


GPD Editor Window

Each GPD editor window displays the contents of a single .gpd file. The editor window allows you to view, modify, and check the syntax of the .gpd file.

When the Minidriver Conversion Wizard creates a .gpd file, it inserts warning and error messages, where needed, as comments. You can locate these messages by searching for "Warning" or "Error". The messages identify entries you'll probably need to modify. The messages remain in the file until you delete them.

The keywords contained in GPD files are defined in the Windows 2000 DDK. Each GPD keyword begins with an asterisk. You can find GPD keywords in the DDK browser's index.

To open a .gpd file:

You can open a .gpd file using any of the following techniques:

·	In the Minidriver Workspace Window, double-click a .gpd file name (or right-click to use the file's context menu).

·	Select Open from MDT's File menu.

·	Double-click on the file's name in the Windows Explorer.

To edit a .gpd file:

After you have opened a .gpd file, you can edit it within the window's edit box. MDT's Edit menu provides Copy, Cut, Paste, Find, Replace and Go To options.

To find text within a .gpd file:

Type the text you are looking for in the toolbar's edit box, then click on the toolbar's N (Next) or P (Previous) button.

Alternately, you can select Find from MDT's Edit menu.

To go to a specific line within a .gpd file, select Go To from MDT's Edit menu, then type a line number in the pop-up window.

To check .gpd file syntax:

To check the syntax of the currently open .gpd file, do the following:

.	Select the level of error reporting you'd like by using the File menu's Set Error Level option. Higher error level numbers cause more types of errors and warnings to be reported.

.	Select Check Syntax from the File menu, or click on the toolbar button, or press F7.

Error and warning messages are displayed in the lower edit box. Some of these messages identify a line number within the .gpd file. If you click on one of these messages, the upper edit box will scroll to the referenced line.

To match braces, parentheses, and brackets:

Place the cursor next to any brace, parenthesis, or bracket character and press CTRL+]. The editor will attempt to find the matching brace, parenthesis, or bracket by searching either forward or backward.

To enable or disable editing aids

Click on Editing Aids in the Edit menu. This enables or disables the GPD editor's ability to assist you in specifying valid keywords and values.

Shortcut Keys

F1	Help.
Ctrl+F	Find.
F4	Go to the next message in the error/warning list.
Shift+F4	Go to the previous message in the error/warning list.
F7	Check syntax.


Main menu command summary

Commands

File menu

Edit menu

View menu

Window menu

Help menu


File Menu Commands

The File menu offers the following commands:

New	Creates a new minidriver workspace.
Open	Opens an existing minidriver workspace, or a .gpd, .ufm, or .gtt file.
Close	Closes an existing minidriver workspace, or a .gpd, .ufm, or .gtt file.
Save	Saves the current minidriver workspace, or a .gpd, .ufm, or .gtt file.
Save As	Saves the current minidriver workspace, or a .gpd, .ufm, or .gtt file, using a specified name.
Exit	Closes MDT.


Edit Menu Commands

The Edit menu offers the following commands:

Undo	Reverses previous editing operation, if possible.
Cut	Deletes data from the document and moves it to the clipboard.
Copy	Copies data from the document to the clipboard.
Paste	Pastes data from the clipboard into the document.
Find	Finds text in a .gpd file.
Replace	Finds and replaces text in a .gpd file.
Go To	Goes to a specified line in a .gpd file.
Editing Aids	Enables/disables editing aids in the GPD editor window.


View Menu Commands

The View menu offers the following commands:

Toolbar	Shows or hides the toolbar.
Status Bar	Shows or hides the status bar.


Window Menu Commands

The Window menu offers the following commands, which enable you to arrange multiple views of multiple documents in the application window:

Cascade	Arranges windows in an overlapped fashion.
Tile	Arranges windows in non-overlapped tiles.
Arrange Icons	Arranges icons of closed windows.
Window 1, 2, ...	Goes to specified window.


Help Menu Commands

The Help menu offers the following commands, which provide you assistance with this application:

Tip of the Day	Allows you to browse selected tips on using the program.
Help Topics	Offers you a table of contents for topics on which you can get help.
About	Displays the MDT version number, as well as system information.


File New command
New Command (File Menu)

Use this command to create a new workspace using the Minidriver Conversion Wizard.

You can open an existing document with the Open command.

Shortcuts

Toolbar:

Keys:	CTRL+N


File New dialog box

Specify the type of document you wish to create:

Minidriver Workspace

Glyph Translation Table (GTT)

Device Font Information (UFM)

Generic Printer Description (GPD)


File Open command
Open command (File menu)

Use this command to open an existing document in a new window.   Use the Window menu to switch among the multiple open documents.  See Window 1, 2, ... command.

You can create new documents with the New command.

Shortcuts

Toolbar:

Keys:	CTRL+O


File Open dialog box

The following options allow you to specify which file to open:

File Name

Type or select the filename you want to open.  This box lists files with the extension you select in the List Files of Type box.

List Files of Type

Select the type of file you want to open:

Minidriver Workspace

Glyph Translation Table (GTT)

Device Font Information (UFM)- this option is not available in the Beta 1 version.

Generic Printer Description (GPD)

Drives

Select the drive in which Minidriver Development Tool stores the file that you want to open.

Directories

Select the directory in which Minidriver Development Tool stores the file that you want to open.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


File Close command
Close Command (File Menu)

Use this command to close a window within a minidriver workspace. If one of the editor windows is active, it will be closed. If the workspace window is active, all windows associated with the minidriver are closed. If any files have been changed but not saved, MDT will ask you if you want to save the changes.

You can also close a document by using the Close icon on the document's window, as shown below:


File Save command
Save Command (File Menu)

Use this command to save the contents of the window that is currently active. If you want to change the name and directory of the file in which the window contents are stored, choose the Save As command.

Shortcuts

Toolbar:

Keys:	CTRL+S


File Save As command
Save As Command (File Menu)

Use this command to save and name the active document.  MDT displays the Save As dialog box.

To save a document with its existing name and directory, use the Save command.


File Save As dialog box

The following options allow you to specify the name and location of the file you're about to save:

File Name

Type a new filename to save a document with a different name.  A filename can contain up to eight characters and an extension of up to three characters.  Minidriver Development Tool adds the extension you specify in the Save File As Type box.

Drives

Select the drive in which you want to store the document.

Directories

Select the directory in which you want to store the document.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


File 1, 2, 3, 4 command
1, 2, 3, 4 Command (File Menu)

Use the numbers and filenames listed at the bottom of the File menu to open the last four documents you closed.  Choose the number that corresponds with the document you want to open.


File Exit command
Exit Command (File Menu)

Use this command to end your Minidriver Development Tool session.  You can also use the Close command on the application's Control menu. MDT prompts you to save changes to minidriver files, if you have not yet saved the changes.

Shortcuts

Mouse:	Double-click the application's Control menu button.

Keys:	ALT+F4


Undo/Can't Undo Command (Edit Menu)

Use this command to reverse the last editing action, if possible. The name of the command changes, depending on the last action. The Undo command changes to Can't Undo if the last action cannot be reversed.

Shortcuts

Toolbar:

Keys:	CTRL+Z


Cut Command (Edit Menu)

Use this command to remove selected data from the active window and store it in the clipboard. This command is only available if data is currently selected.

Cutting data to the clipboard replaces the contents previously stored there.

Shortcuts

Toolbar:

Keys:	CTRL+X


Copy Command (Edit Menu)

Use this command to copy selected data from the active window and store it in the clipboard. This command is only available if data is currently selected.

Copying data to the clipboard replaces the contents previously stored there.

Shortcuts

Toolbar:

Keys:	CTRL+C


Paste Command (Edit Menu)

Use this command to insert a copy of the clipboard contents at the insertion point. This command is unavailable if the clipboard is empty.

Shortcuts

Toolbar:

Keys:	CTRL+V


Find Command (Edit Menu)

Use this command within the GPD editor window to locate text within a .gpd file. MDT displays a pop-up dialog.

Shortcuts

Keys:	F3


Replace Command (Edit Menu)

Use this command within the GPD editor window to locate and replace text within a .gpd file. MDT displays a pop-up dialog.


Go To Command (Edit Menu)

Use this command within the GPD editor window to move the cursor to a specified line within a .gpd file. MDT displays a pop-up dialog.

Shortcuts

Keys:	CTRL+G


Editing Aids Command (Edit Menu)

Use this command within the GPD editor window to enable or disable the editor's editing aids.


View Toolbar command
Toolbar Command (View Menu)

Use this command to display and hide the Toolbar, which includes buttons for some of the most common commands in MDT. A check mark appears next to the menu item when the Toolbar is displayed.

See Toolbar for help on using the toolbar.


Toolbar

The toolbar is displayed across the top of the application window, below the menu bar.  The toolbar provides quick mouse access to many functions supplied by MDT.

To hide or display the Toolbar, choose Toolbar from the View menu (ALT, V, T).

Click	To

Create a new minidriver workspace.

Open an existing document. MDT displays the Open dialog box, in which you can locate and open the desired file.

Save the active document or template with its current name.  If you have not named the document, MDT displays the Save As dialog box.

Remove selected data from the document and stores it on the clipboard.

Copy the selection to the clipboard.

Insert the contents of the clipboard at the insertion point.

Print the active document.


View Status Bar Command
Status Bar command (View menu)

Use this command to display or hide the status bar on the bottom of the GPD editor window.

The left side of the GPD editor window's status bar displays the error or warning message that is currently selected within the editor's error list. The right side of status bar lists the current location of the cursor within the .gpd file being edited.


Cascade Command (Window Menu)

Use this command to arrange multiple opened windows in an cascading, overlapped fashion.


Tile Command (Window Menu)

Use this command to arrange multiple opened windows in a tiled, non-overlapped fashion.


Window Arrange Icons Command

Use this command to arrange the icons in the main window.


1, 2, ... Command (Window Menu)

MDT displays a list of currently open windows at the bottom of the Window menu.  A check mark appears in front of the name of the active window.  Choose a window from this list to make it active.


Index command (Help menu)

Use this command to display the opening screen of Help.  From the opening screen, you can jump to step-by-step instructions for using Minidriver Development Tool and various types of reference information.

Once you open Help, you can click the Contents button whenever you want to return to the opening screen.


About command (Help menu)

Use this command to display the copyright notice and version number of your copy of Minidriver Development Tool.


Help Using Help Command
Context Help command

Use the Context Help command to obtain help on some portion of Minidriver Development Tool.  When you choose the Toolbar's Context Help button, the mouse pointer will change to an arrow and question mark.  Then click somewhere in the Minidriver Development Tool window, such as another Toolbar button.  The Help topic will be shown for the item you clicked.

Shortcut

Keys:	SHIFT+F1


Title Bar

The title bar is located along the top of a window.  It contains the name of the application and/or the document.

To move a window, drag its title bar.

A title bar may contain the following elements:

Application Control-menu button

Document Control-menu button

Maximize button

Minimize button

Name of the application

Name of the document

Restore button


Size command (System menu)

Use this command to display a four-headed arrow so you can size the active window with the arrow keys.

After the pointer changes to the four-headed arrow:

1.	Press one of the DIRECTION keys (left, right, up, or down arrow key) to move the pointer to the border you want to move.

2.	Press a DIRECTION key to move the border.

3.	Press ENTER when the window is the size you want.

Note:  This command is unavailable if you maximize the window.

Shortcut

Mouse:	Drag the size bars at the corners or edges of the window.


Move command (Control menu)

Use this command to display a four-headed arrow so you can move the active window or dialog box with the arrow keys.

Note:  This command is unavailable if you maximize the window.

Shortcut

Keys:	CTRL+F7


System Minimize Command
Minimize command (application Control menu)

Use this command to reduce the Minidriver Development Tool window to an icon.

Shortcut

Mouse:	Click the minimize icon [image] on the title bar.

Keys:	ALT+F9


Maximize command (System menu)

Use this command to enlarge the active window to fill the available space.

Shortcut

Mouse:	Click the maximize icon [image] on the title bar; or double-click the title bar.

Keys:	CTRL+F10 enlarges a document window.


Next Window command (document Control menu)

Use this command to switch to the next open document window.  Minidriver Development Tool determines which window is next according to the order in which you opened the windows.

Shortcut

Keys:	CTRL+F6


Previous Window command (document Control menu)

Use this command to switch to the previous open document window.  Minidriver Development Tool determines which window is previous according to the order in which you opened the windows.

Shortcut

Keys:	SHIFT+CTRL+F6


Close command (Control menus)

Use this command to close the active window or dialog box.

Double-clicking a Control-menu box is the same as choosing the Close command.

Note:  If you have multiple windows open for a single document, the Close command on the document Control menu closes only one window at a time.  You can close all windows at once with the Close command on the File menu.

Shortcuts

Keys: 	CTRL+F4 closes a document window

ALT+F4 closes the <<YourType>> window or dialog box


Restore command (Control menu)

Use this command to return the active window to its size and position before you chose the Maximize or Minimize command.


Switch to command (application Control menu)

Use this command to display a list of all open applications.  Use this "Task List" to switch to or close an application on the list.

Shortcut

Keys:	CTRL+ESC

Dialog Box Options

When you choose the Switch To command, you will be presented with a dialog box with the following options:

Task List

Select the application you want to switch to or close.

Switch To

Makes the selected application active.

End Task

Closes the selected application.

Cancel

Closes the Task List box.

Cascade

Arranges open applications so they overlap and you can see each title bar.  This option does not affect applications reduced to icons.

Tile

Arranges open applications into windows that do not overlap.  This option does not affect applications reduced to icons.

Arrange Icons

Arranges the icons of all minimized applications across the bottom of the screen.


Find Dialog
Find dialog box

Use this dialog box to find specific strings in the GPD file.


Replace Dialog
Replace dialog box

Use this dialog box to find replace one string of characters in the GPD file with another.


No Help Available

No help is available for this area of the window.


No Help Available

No help is available for this message box or menu item.


Structure creation failure

The required structure for the highlighted directory could not be created.  The typical causes are:

•	The name used contains invalid characters for the file system.

•	The drive, or some other part of the path before the final component of the path, is invalid.

•	A file with the same name as the listed directory, or one of the subdirectories in the structure, already exists on the drive.

•	A root directory may be full.

•	You do not have write access to the target drive or directory.

The structure depends upon the target.  For Windows 2000, GTT and UFM subdirectories will be created. For Windows NT 4.0 and earlier versions, RLE and IFI subdirectories will be created.

Necessary Action:

Select a destination you have write access to, and give it a valid name.  Also make sure the subdirectory names are not a problem.  You can use an existing complete or partial structure with impunity.


Error log query

You have GPD file errors from the conversion of the workspace, recent syntax checks, or both in the workspace you have just opened or created.

Answering Yes causes a GPD editor to be launched for each GPD that has errors.  This can save you looking through multiple files to find the ones that have the errors.

Answering No brings you to the Workspace editor without opening any other windows.


No unmapped code points

You have asked to add code points to a GTT file, but all available code points in the supported code pages are already in use.

Necessary action:

If you want to add additional code points, go to the Code Pages Used tab, and add a code page to the GTT that contains the point or points you wish to add.


Minidriver Conversion Failure

This message usually is preceded by a message that gives more detail as to the cause of the conversion failure.  You cannot convert the 16-bit minidriver as it is currently defined.

Necessary action:

Should have been specified in the message or messages preceding this one.  Usually it is because files are missing from the 16-bit minidriver sources, or incorrect CTT Ids were used in one or more PFM files.


Unable to run UniTool

For some reason, the UniTool program could not be started.

Necessary action:

You do not need to run UniTool from the Wizard.  Try canceling the conversion, ending the program, and then running UniTool from Explorer, or a command prompt.  If UniTool will not run, try rebooting your machine, and if that fails to produce results, try installing the DDK again.