Next: , Previous: , Up: Conditional Statements in the Configuration File   [Index]


6.4.2 Conditions that can be tested

We already saw that operating system names can be used as conditions for the IF command. Below, you see the complete list of conditions that can be used:

IF OS2
IF OS/2

These conditions are true if you are running the OS/2 version of MsgEd TE

IF DOS

These conditions are true if you are running any DOS version (16 bit or 32 bit) of MsgEd TE.

IF DOS16

This condition is true if you are running the standard 16 bit DOS version of MsgEd TE.

IF 386

This condition is true if you are running the 32 bit DOS version of MsgEd TE.

IF W32

This condition is true if you are running the Windows 95/98/NT version of MsgEd TE.

IF UNIX

This condition is true if you are running any Unix version (Linux, FreeBSD, AIX, Rhapsody, ...) of MsgEd TE.

IF LINUX

This condition is true for any version of MsgEd TE that announces itself as ‘MsgEd/LNX TE’.

IF 0

This condition is always false. It is useful if you want to disable a large part of the configuration file, but do neither want to erase it nor to place semicolons in front of each line. Simply place IF 0 and ENDIF around such a part of the configuration file.

IF 1

This condition is always true.

IF variable=value

This condition is true if the specified environment variable has the specified value. For example, on OS/2, IF HOSTNAME=mycomputer will be true only if you have set HOSTNAME=mycomputer in your config.sys file, or if you have given the set HOSTNAME=mycomputer command on the command line before starting MsgEd TE.


Next: Usage example for Conditionals, Previous: Formulating Conditional Statements, Up: Conditional Statements in the Configuration File   [Index]