The cross platform SDK (Release 9) has obsoleted some functions that are replaced by new cross platform functions. One of these functions is LoginToFileServer, which is to be replaced by NWLoginToFileServer.
Issue 1: NWLoginToFileServer currently has an incompatibility when used in NLMs however.
If you use NWLoginToFileServer in an NLM, you cannot open a remote file using fopen, sopen, FEsopen, etc. If you specify a filename as such: SERVER/VOLUME:DIR/FILENAME the file cannot be opened.
The problem is that NWLoginToFileServer obtains a type of connection that the file open commands don't understand, so the file cannot be opened.
If you are opening remote files in an NLM using a bindery connection, you need to continue to use LoginToFileServer for the time being.
Issue 2: One other issue is with the header file NWBINDRY.H. With the cross platform sdk, header files are now contained in more directories that in the past. First of all, some header files are contained in the cross platform include directory:
sdkcd9 wsdkinclude
and the NLM specific header files begin in:
sdkcd9 wsdkinclude lm
Some filename are the same in the two directories, one being NWBINDRY.H. These files differ greatly, containing different constant values because of HIGH/LOW order of the bytes.
For example: sdkcd9 wsdkinclude wbindry.h contains:
sdkcd9 wsdkinclude lm wbindry.h contains:
If you are using NWLoginToFileServer you must use NWBINDRY.H in the cross platform directory, otherwise the object type will not be as expected and you will receive 0x00fc (no such object) errors since it doesn't recognize the object type.
If you are using LoginToFileServer you must use NWBINDRY.H in the NLM directory or the same symptom occurs as described above.
| icon003.exe | 19.4 K | 2005-04-06 |
© 2009 Novell, Inc. All Rights Reserved.
