TID100893 (IFESR001) - SetCurrentNameSpace() Failure Multiple Vols

From Developer Community

ABSTRACT:

SetCurrentNameSpace() Failure On A Volume Other Than SYS

DETAILED DESCRIPTION

SYMPTOM A developer had the OS/2 name space on a test volume but not on volume SYS. From a file system monitoring hook the developer was calling SetCurrentNameSpace(OS2NameSpace) which was returning error code 255. When the OS/2 name space was installed on volume SYS, SetCurrentNameSpace() succeeded.

CAUSE The current working volume (CWV) was still SYS, where the OS/2 name space was not originally installed.

SOLUTION Just setting the CWV did not correct SetCurrentNameSpace() from failing on NetWare 3.12 until the developer also set the current working directory (CWD) to the root (). Of course, this directory will be found on all volumes.

Before calling SetCurrentNameSpace() in a multiple volume environment, set the CWV and CWD. API's to perform these operations include FESetCWVnum(), FESetCWDnum(), and FESetCWVandCWDnums().

[edit]