Hi Sergey,

This involves 200+ PCs. I was able to faithfully reproduce the error on EVERY Win95 PC. It consistently works without problems on Win2K.
I have temporarily worked around the problem by Mapping the server/path to Drive letters (I was trying to avoid that).

Re the Novell Client - even it if does relate to it, it currently is beyond the scope/time constraints of the project to re-image that many PCs.

Why am I using GBLib?
1. Legacy
2. Necessity. I use some functions that I am not aware can be duplicated without it:
a> Workstation/default Server time synchronization
b> Query whether the logged-in user belongs to a specific Novell group
I do use it for other functions that could be replicated using VFP or Win functions.


>Hi Ashley,
>
>Did you check Novell client on that PC? BTW, what are you using GPLIB for?
>
>>Help!
>>I have just created a bootstrap loader program for my app.
>>It was previously called by a WinBatch loader which mapped Novell servers/paths to drive letters and called the app with the app and data paths as drive letters.
>>My bootstrap uses UNC paths instead, using a lookup table to get the appropriate paths.
>>This works perfectly under Win2K, and (I am told)under Win 98.
>>Under Win 95b (I don't have a choice here), I get an error message:
>>"NetWare Error: 0xf. Refer to GPLIB.HLP (Error Messages)"
>>The GPLIB help file does not list 0xf under Error Messages.
>>I was able to duplicate the error in the Run Window by manually calling the app with the UNC paths.
>>
>>Why just the problem with win 95?
>>
>>TIA