When a client launches our Windows Foxpro 2.6 application, he immediately gets an "API Library Not Found" error. He's on a Banyan Vines network (without USC NET MAP), running WIN95. The EXE, ESL, and FLLs are in the same directory. Previously, this worked fine under Windows 3.11. This conficutlarion is standard and is delivered on CD-ROM. We haven't encountered this problem before.

We've noticed that there are five characters prior to the volume name in the path.

Thanks for your help.