Problem:

A client installed his application on Windows Vista for the first time. The machine had Application Server for Net Express 5.0 (i.e. Micro Focus Server 5.0)  installed.

The application was character based and required settings in ADISCTRL. In partucular it required function keys to be enabled.

Testing led him to believe that ADISCTRL was not being read and that defaults were therefore being taken.

Yet, the same configuratiopn worked correctly on XP and previous Windows versions.

Resolution:

When the application was distributed the preset copy of ADISCTRL was copied into the Application Server directory (eg C:\\Program Files\\Micro Focus\\Server 5.0\\bin).

As this was Application Server he was not able to run adiscf to make the appropriate adjustments.

When running the application the F-Keys (and other settings such as having the enter key work as a tab key) were not being recognized.

The PATH was checked and seemed correct.

COBDIR was also set to the Application Server directory as adis uses COBDIR -

set COBDIR=C:\\Program Files\\Micro Focus\\Server 5.0\\bin

If ADISCTRL was moved to the local working directory it worked ok.

Finally got it to work with ADISCTRL only in the Application Server directory by setting COBDIR, but with the value set in quotes.

eg

set COBDIR="C:\\Program Files\\Micro Focus\\Server 5.0\\bin"

This worked correctrly.

On XP he did not have to set COBDIR to access ADISCTRL in the Application Server directory.