# $ 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.