The ftype command sets up an association between a file type name, and a string to be used to execute it. File type names are created using the assoc command.
With no arguments, all file associations are displayed in two tab-delimited columns. The first column is the file type name, and the second is the string that is executed when that file type is executed.
With one argument, the single file association (for Open) for the file type given is displayed.
With two arguments, a new file association is created, or a current one is replaced.
The syntax of the command to execute is defined by the Explorer. %1 is replaced by the short name of the file being executed; %L is replaced by the long name; and %* is replaced by the name of any arguments to the file.
Be careful when using %L. Eventually, any quotation marks in the value of %L are stripped off and the argument passed to the command may contain file names with spaces. Such file names can cause problems with some commands. If this is a concern, you should use %1 instead of %L.
displays all associations for the specified file type, not just those for Open. Instead of the usual two column display, this option produces a three column tab-delimited display of the form:
<file type> <association command> <command string>
displays or sets the file association for the specified association command (assoc_cmd). For example
-cEdit displays are the associations for Edit.
You cannot specify both the
The following example first uses assoc to associate the .ksh file name extension with the mks_shell file type, and then uses ftype to set the command to be run for that file type.
assoc .ksh mks_shell ftype mks_shell "wstart -Nm sh.exe -H --\"%L\" %*"
The following command displays the editing association for the mks_shell file type:
ftype -c Edit mks_shell
while the following command sets up a new editing association for that file type:
ftype -c Edit mks_shell "viw %1"
Possible exit status values are:
ftype and assoc are named after similar commands built into cmd.exe.
This command is actually implemented as a shell script, changing the appropriate registry entries using the registry command. MKS cannot be responsible for proper functionality of this code if you alter the ftype.ksh file in any way.
Windows 2000. Windows XP. Windows Server 2003. Windows Vista. Windows 7. Windows Server 2008. Windows 8. Windows Server 2012.
MKS Toolkit for System Administrators
MKS Toolkit for Developers
MKS Toolkit for Interoperability
MKS Toolkit for Professional Developers
MKS Toolkit for Enterprise Developers
MKS Toolkit for Enterprise Developers 64-Bit Edition
MKS Toolkit 9.5 Documentation Build 3.