Bill,

>Running a compact executable .EXE from Distribution Kit with supporting library file FOXDX260.ESL on the path.
>
>When this message came up before, placing FOXDX260.ESL on the path solved the problem. Not this time...

After checking around in some old UT message, I believe I have found the problem. Check the shortcut properties Memory tab and be sure that Extended Memory is set to either an actual value or to Auto. (Also leave the checkbox "Uses HMA" checked).

The default is NO Extended memory, which sends the EXE looking for the pair of foxd2600.eso and .esl. I tested via Remote Desktop and it looks like that's the key to the message you were getting.