Developer Pointers
Articles and Tips: article
01 Dec 1997
Novell Technical Information Documents
All of the Technical Information Documents (TIDs) discussed below are available at the following locations:
The Novell Technical Solutions Database on CompuServe (GO NTID)
The DeveloperNet Support World Wide Web site (http://devsup.novell.com)
The DeveloperNet Support Bulletin Board (801-861-5836)
Disabling Nagle Algorithm for TCP/IP Socket using TLI Interface
|
Author: |
EE |
|||
|
DocumentID: |
TID101383 |
|||
|
Date: |
9/9/97 4:17 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
XBSDE002.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
TCPIP.NLM version 3.1 enables the Nagle Algorithm by default. This sample code demonstrates how to disable the function. This feature is introduced in the TLI interface for TCP/IP in TCPIP.NLM version 4.00e or above.
Detailed Description
In TCPIP.NLM version 3.1, the Nagle Algorithm is enabled by default, but you can disable it by using t_optmgmt()function.
The Nagle Algorithm prevents excessive bandwidth utilization by applications that send many small packets. It allows slight delays before sending individual small packets in order to combine them into a single larger packet.
File Information
Self-Extracting File Name: XBSDE002.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
XBSDE002.TXT |
(this file) |
||||
|
TLINAGLE.C |
5812 |
9-9-97 |
4:22 PM |
||
|
TLINAGLE.NLM |
6687 |
9-9-97 |
4:22 PM |
||
|
XBSDE002.MSG |
226 |
9-9-97 |
4:22 PM |
How to use the ActiveX session control collections in Delphi 3
|
Author: |
HW |
|||
|
DocumentID: |
TID101410 |
|||
|
Date: |
10/9/97 4:11 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
3COLLCT.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
The current release of the ActiveX controls exposes a problem when being used with Delphi 3, in that Delphi is not able to translate all of the interfaces of the session control into a VCL. Thus, the collection methods of the ConnectedTrees, ConnectedServers and ConnectedVolumes cannot be used in a straightforward way.
Note: This limitation does not affect the use of the controls with Visual Basic.
Detailed Description
Consider the following:
nTrees : Integer; nTrees := session.ConnectedTrees.Count;
The above statement will result in a compile time error, as Delphi is not able to resolve the dispatch interface for the collection. The following workaround will let the program run correctly:
nTrees : Integer; connectedTrees: Variant;
connectedTrees := session.ConnectedTrees; nTrees := connectedTrees.Count;
Now the dispatch interface of the collection is queried, rather than the session dispatch interface.
Admittedly, this workaround is rather kludgey. The initial problem will be addressed in release 1.1 of the controls set.
File Information
Self-Extracting File Name: D3COLLCT.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
D3COLLCT.TXT |
(this file) |
||||
|
D3COLLCT.MSG |
407 |
10-7-97 |
5:11 AM |
DOS Application hangs in DS operation
|
Author: |
HW |
|||
|
DocumentID: |
TID101393 |
|||
|
Date: |
9/17/97 8:46 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
BCNDS.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
DOS applications compiled with Borland C that attempt to access data that requires name resolution to a nonlocal replica may appear to hang.
Detailed Description
Currently, this problem appears to be due to a code optimization error in the compiler that occurs when compiling some code in NETDOS16.LIB. The issue has been seen exclusively when operations such as NWDSRead or NWDSSearch require name resolution to switch between two nonlocal replicas. The error causes the application to enter an endless loop without any network traffic. Engineering is investigating ways to work around this problem.
File Information
Self-Extracting File Name: BCNDS.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
BCNDS.TXT |
(this file) |
||||
|
BCNDS.MSG |
142 |
9-17-97 |
1:47 AM |
Account expiration date semantics for NDS
|
Author: |
HW |
|||
|
DocumentID: |
TID101380 |
|||
|
Date: |
9/2/97 3:21 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
EXPIDATE.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
NWAdmin has an "Account has expiration date" check box for user accounts. However, there is no corresponding NDS attribute.
Detailed Description
In the NetWare 3.x bindery, the expiration of an account could be disabled by setting the expiration date to zero. This will not work in NDS. NDS uses the mere existence of the "Login Expiration Date" to determine whether or not an account has an expiration date. Thus, to prevent an account from expiration, you need to remove the above mentioned attribute from NDS. To enable expiration, specify a date.
File Information
Self-Extracting File Name: EXPIDATE.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
EXPIDATE.TXT |
(this file) |
||||
|
EXPIDATE.TXT |
1911 |
9-2-97 |
3:20 AM |
||
|
EXPIDATE.MSG |
125 |
9-2-97 |
3:20 AM |
Set TCP keep-alive timer value using TLI
|
Author: |
EE |
|||
|
DocumentID: |
TID101385 |
|||
|
Date: |
9/10/97 2:29 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
XBSDE003.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
TCPIP.NLM version 4.00e lets you change the timer value of the keep-alive packets.
Detailed Description
The TCP implementation supports a feature popularized by the BSD implementation known as keep-alive packets. Keep-alive packets check whether a peer TCP is still functioning. Keep-alive packets periodically poll the remote machine if the connection has been idle. This sample demonstrates how to set the timer value of the keep-alive packets using t_optmgmt function. You need TCPN04.exe (TCPIP.NLM version 4.00e or above) for this to work.
File Information
Self-Extracting File Name: XBSDE003.EXE
|
Files Included: |
Size |
Date |
Time |
|||
|
XBSDE003.TXT |
(this file) |
|||||
|
TLIALIVE.C |
6016 |
9-9-97 |
4:23 PM |
|||
|
TLIALIVE.NLM |
6717 |
9-9-97 |
4:23 PM |
|||
|
XBSDE003.MSG |
86 |
9-9-97 |
4:23 PM |
|||
|
XBSDE003.TXT |
2106 |
9-9-97 |
4:23 PM |
Delphi causing compiler problems with vol.13, NetNDS32
|
Author: |
HW |
|||
|
DocumentID: |
TID101417 |
|||
|
Date: |
10/13/97 6:56 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
ID3IMP13.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
When developing with Delphi and the NWSDK vol.13, the compiler will complain about several functions missing from NetNDS32. It looks something like this:
Error: <NetNds32.pas< (line): Unsatisfied forward or external declaration: 'function name'.
Detailed Description
The reason for the above behavior is that some new functions were added to the SDK, but their mappings are missing from the .imp files. This will be fixed with the next release of the NetWare SDK.
As an interim fix, modify your netnds32.imp file located under <nwsdk<\include\delphi as follows:
After line 163, insert the following:
|
Function NWDSListPartitionsExtInfo; |
StdCall; external 'NETWIN32.DLL' index 1171; |
|
Function NWDSGetPartitionExtInfoPtr; |
StdCall; external 'NETWIN32.DLL' index 1172; |
|
Function NWDSGetPartitionExtInfo; |
StdCall; external 'NETWIN32.DLL' index 1173; |
After line 225, insert the following:
|
Function NWDSPutAttrNameAndVal; |
StdCall; external 'NETWIN32.DLL' index 3048; |
||
|
FunctionNWDSPutChangeAndVal; |
StdCall; external 'NETWIN32.DLL' index 3049; |
||
|
Function NWDSReadObjectDSIInfo; |
StdCall; external 'NETWIN32.DLL' index 3050; |
||
|
FunctionNWDSGetDSIInfo; |
StdCall; external 'NETWIN32.DLL' index 3051; |
FileInformation
Self-Extracting File Name: ID3IMP13.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
ID3IMP13.TXT |
(this file) |
||||
|
ID3IMP13.MSG |
251 |
10-10-97 |
6:24 AM |
Using NDS as Security Database for NetWare Telephony Services
|
Author: |
PS |
|||
|
DocumentID: |
TID101387 |
|||
|
Date: |
9/16/97 10:37 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
NDSTELE1.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
When using NetWare Telephony Services with NDS as the security database (SDB), NWAdmin reports 'SDB Access Error: Modify object failed - no permissions (520)' when attempting to modify users' telephony attributes.
Detailed Description
When NetWare Telephony Services is installed, an object called TSAdmin is created in the Organization container of the NDS tree. This object is used to allow the Telephony Services security database access to the users in the tree. In order for the TSAdmin object to allow the SDB to modify users' Telephony attributes, TSAdmin must be made a trustee of the SDB container and the organization container for which user access is required. The required rights to add for the trustees are as follows:
For the SDB Container
Make TSAdmin a trustee of the SDB object, with Supervisor Object Rights and All Property Rights.
For the Organization Container
Make TSAdmin a trustee of the Organization object (e.g., O=MyCompanyName), with Browse Object Rights and Compare, Read, and Write Property Rights.
This will give TSAdmin the rights it needs to access the SDB, and it will give the SDB the necessary access rights to modify users' Telephony attributes.
File Information
Self-Extracting File Name: NDSTELE1.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
NDSTELE1.TXT |
(this file) |
||||
|
NDSTELE1.MSG |
216 |
9-16-97 |
8:46 AM |
How to set the [Root] level context with the Directory Control
|
Author: |
HW |
|||
|
DocumentID: |
TID101382 |
|||
|
Date: |
9/4/97 2:27 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
IXROOTST.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This TID discusses some issues that arise when changing trees using the session and directory controls. For simplicity, code snippets are given in Visual Basic.
Detailed Description
The released directory control allows you to construct the FullName property of a directory control from a given tree name and a context. The tree name could be one of the ConnectedTrees properties of the session control. When changing to a new tree, the FullName has to be initialized properly. If the desired target context for the new tree is not known, the most likely choice for the starting context is [Root].
However, if the context is set like this:
Dim strNewContext As String Dim tree As NWDirLib.NWDir
strNewContext = tree.FullNameFromTreeAndContext("SomeTreeName", "[Root]")
subsequent attempts to retrieve items using the Item method will fail:
Dim ndsEntry As NWEntry Set ndsEntry = tree.Entries(GUIItem.Text)
This will produce an error 601, "Entry not found."
To avoid this, the FullName construction above should be changed to include an empty string rather than "[Root]". Afterwards, item retrieval will work as expected.
A fix for the described behavior is slated for the next release of the controls.
File Information
Self-Extracting File Name: IXROOTST.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
IXROOTST.TXT |
(this file) |
||||
|
IXROOTST.MSG |
163 |
9-4-97 |
2:25 AM |
Login.dat missing in SDK 12 for NWLoginUI
|
Author: |
MM |
|||
|
DocumentID: |
TID101392 |
|||
|
Date: |
9/17/97 8:45 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
IMMLOGIN.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
Matching versions of LGNW9532.dll, LOGINW95.dll, and login.dat are required for using NWLoginUI. Login.dat is included in this tid.
Detailed Description
The major and minor version numbers of LGNW9532.dll, LOGINW95.dll, and login.dat have to match before you can run an application that calls NWLoginUI. Login.dat stores the resources and is located under the windows\nls\english area. The version number can be checked by the ndir command, as shown below:
ndir Loginw95.dll /ver
The dlls in release 12 are version number 1.85.xx (xx is the revision number, which does not matter). Release 12 did not include login.dat; I included it with this tid. The current client requestor does not contain the most updated DLLs and login.dat. So, you have to make sure that you copy those dlls to the windows\system directory.
File Information
Self-Extracting File Name: IMMLOGIN.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
IMMLOGIN.TXT |
(this file) |
||||
|
LOGIN.DAT |
60928 |
9-16-97 |
3:16 PM |
||
|
IMMLOGIN.TXT |
2318 |
9-16-97 |
3:16 PM |
||
|
IMMLOGIN.MSG |
132 |
9-16-97 |
3:16 PM |
NWDSPutChange has wrong ordinal inNetnds32.imp
|
Author: |
HW |
|||
|
DocumentID: |
TID101411 |
|||
|
Date: |
10/9/97 4:12 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
D3PTCHGE.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
The NWDSPutChange function has a wrong ordinal (1032) in the SDK header file netnds32.imp. This ordinal actually belongs to NWDSDefineAttr. Calling the wrong ordinal will crash the caller.
Detailed Description
The workaround is to change the ordinal for NWDSPutChange in the header file to 1016. This problem has been reported to Engineering and a fix should be available with a future SDK release.
File Information
Self-Extracting File Name: D3PTCHGE.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
D3PTCHGE.TXT |
(this file) |
||||
|
D3PTCHGE.MSG |
189 |
10-7-97 |
5:11 AM |
Token commander SendMail dialog
|
Author: |
RL |
|||
|
DocumentID: |
TID101397 |
|||
|
Date: |
9/19/97 2:08 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GW5XOB32.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample application uses the token commander and the Object API to display a GroupWise Sendmail dialog with a file attached. If you pass a filename as a command-line parameter to the application, then the attachment will appear in the Sendmail dialog. If you don't include a filename as a command-line parameter, you will get a Newmail dialog without a file attached.
File Information
Self-Extracting File Name: GW5XOB32.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GW5XOB32.TXT |
(this file) |
||||
|
TCSEND.EXE |
225792 |
9-19-97 |
11:02 AM |
||
|
SEND.DFM |
415 |
9-19-97 |
11:02 AM |
||
|
SEND.PAS |
3501 |
9-19-97 |
11:02 AM |
||
|
TCSEND.DPR |
184 |
9-19-97 |
11:02 AM |
||
|
GW5XOB32.MSG |
363 |
9-19-97 |
11:02 AM |
Object Selector Sample for ActiveX controls
|
Author: |
HW |
|||
|
DocumentID: |
TID101386 |
|||
|
Date: |
9/10/97 2:29 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
XSELECT.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample implements an object selection tool for NDS with the look and feel of the Windows 95 common dialog controls. It allows browsing and selecting objects in a specified tree and permits filtering by one or more object classes. You may either use it as a reference for the DeveloperNet 2000 directory control or exploit is as an OLE server to select objects from within your RAD program.
Detailed Description
This sample has been superseded by the VBSelect sample.
File Information
Self-Extracting File Name: XSELECT.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
XSELECT.TXT |
(this file) |
||||
|
EXPLORER.FRM |
14573 |
9-10-97 |
8:05 AM |
||
|
EXPLORER.FRX |
7559 |
9-10-97 |
8:05 AM |
||
|
MAIN.BAS |
1870 |
9-10-97 |
8:05 AM |
||
|
README.TXT |
562 |
9-10-97 |
8:05 AM |
||
|
SELECTOR.CLS |
3237 |
9-10-97 |
8:05 AM |
||
|
XSELECT.VBP |
789 |
9-10-97 |
8:05 AM |
||
|
XSELECT.TXT |
2073 |
9-10-97 |
8:05 AM |
||
|
XSELECT.MSG |
390 |
9-10-97 |
8:05 AM |
NLM Authentication Example
|
Author: |
RL |
|||
|
DocumentID: |
TID101376 |
|||
|
Date: |
8/22/97 2:48 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
XDSA7.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
NLMs have traditionally hosted file-server-centric services. With NDS, more and more developers are wanting to capitalize on the global nature of NDS to store NLM configuration information, take advantage of service location, and use other aspects that enhance NLM services. Some issues exist about providing NLMs with persistent identity and security between loads without user intervention when file servers come up. This example demonstrates a method to provide this type of solution.
File Information
Self-Extracting File Name: XDSA7.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
XDSA7.TXT |
(this file) |
||||
|
DSACCESS.C |
30640 |
8-22-97 |
2:22 PM |
||
|
DSACCESS.H |
4386 |
8-22-97 |
2:22 PM |
||
|
EXAMPSRV.C |
25791 |
8-22-97 |
2:22 PM |
||
|
EXAMPSRV.NLM |
10749 |
8-22-97 |
2:22 PM |
||
|
TEXT.TXT |
1209 |
8-22-97 |
2:22 PM |
||
|
XDSA7.TXT |
2066 |
8-22-97 |
2:22 PM |
||
|
XDSA7.MSG |
468 |
8-22-97 |
2:22 PM |
OS/2 applications can only handle LPT1-3
|
Author: |
JB |
|||
|
DocumentID: |
TID101394 |
|||
|
Date: |
9/17/97 8:46 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
OS2LPT.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
LPT ports 1-3 can be handled through the NWSDK APIs, but LPT 4-9 cannot.
Detailed Description
Although newer revisions of the OS/2 requester allow you to capture LPT 1-9, the SDK implementation currently only allows for 3 printers to be handled. This is going to be fixed in the libraries coming with SDK Vol. 14.
File Information
Self-Extracting File Name: OS2LPT.EXE
|
Files Included: |
Size |
Date |
Time |
|
|
OS2LPT.TXT |
(this file) |
|||
|
OS2LPT.MSG |
73 |
9-17-97 |
1:47 AM |
Step sample C3PO with VB 5
|
Author: |
RL |
|||
|
DocumentID: |
TID101398 |
|||
|
Date: |
9/29/97 5:11 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GW5XOB33.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample is similar to the BrainShare class for C3POs only using Visual Basic. The original class used Delphi code. The zip file includes paths for files. Duplicate files exist for each step.
File Information
Self-Extracting File Name: GW5XOB33.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GW5XOB33.TXT |
(this file) |
||||
|
VBC3PO.ZIP |
136625 |
9-29-97 |
5:11 PM |
||
|
GW5XOB33.MSG |
183 |
9-29-97 |
5:11 PM |
When to use NWDSOpenMonitoredConn
|
Author: |
MM |
|||
|
DocumentID: |
TID101401 |
|||
|
Date: |
10/6/97 1:58 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
IMMDSMON.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
If an application relies on the workstation being logged in, NWDSOpenMonitoredConn can be an effective API to use.
Detailed Description
If an application relies on the workstation being logged in, NWDSOpenMonitoredConn can be an effective API to use. It will fail if the workstation is not logged in, and it will always return a connection to a server with a read/write replica to the logged in object. This will be a performance enhancement if the application is going to work with the logged in user object.
What is a Monitored Connection?
NWDSLogin creates a monitored connection so DS can track such things as concurrent logins of the same user from multiple sessions or workstations, login time restrictions, etc. This allows DS to let a user authenticate to as many servers as needed without breaching the concurrent login restrictions. Because NWDSLogins are relative to an NDSTree, the monitored connection created is relative to the NDSTree. A workstation (user) therefore will have a monitored connection for every tree that it is currently logged into.
File Information
Self-Extracting File Name: IMMDSMON.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
IMMDSMON.TXT |
(this file) |
||||
|
IMMDSMON.MSG |
116 |
10-6-97 |
1:58 PM |
Sample Admin API (VB5 app)
|
Author: |
RL |
|||
|
DocumentID: |
TID101419 |
|||
|
Date: |
10/16/97 5:01 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GW5XOB34.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample application is a duplicate of GW5xOB30, except that this sample is written in VB5 instead of Delphi.
You need to be logged in to the server as admin for this application to work.
File Information
Self-Extracting File Name: GW5XOB34.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GW5XOB34.TXT |
(this file) |
||||
|
ADMINAPP.VBW |
44 |
10-16-97 |
5:00 PM |
||
|
ADMIN.FRM |
10812 |
10-16-97 |
5:00 PM |
||
|
ADMINAPP.EXE |
18944 |
10-16-97 |
5:00 PM |
||
|
ADMINAPP.VBP |
626 |
10-16-97 |
5:00 PM |
||
|
GW5XOB34.TXT |
1842 |
10-16-97 |
5:00 PM |
||
|
GW5XOB34.MSG |
195 |
10-16-97 |
5:00 PM |
Session control properties changed for release
|
Author: |
HW |
|||
|
DocumentID: |
TID101381 |
|||
|
Date: |
9/4/97 2:27 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
IXSESSPR.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
The properties for the ActiveX session control have changed for the release of the controls. The syntax is now compatible with Microsoft's ADSI naming format.
Detailed Description
The Beta release of the session control had two separate properties to define a session's current default context and tree. For the release, this has been changed to be just one, DefaultFullName. This is the same as for the directory control, where the switch had been made with the first Beta already.
Also, there are the following two new properties:
ServerNames TreeNames
They can be used to enumerate the trees and servers on a network. Previously, a developer using the controls had to rely on the GUI dialog to enumerate the resources. The new properties provide more control to the developer.
Also, the full name syntax now includes the NDS name space prefix "NDS:", which makes it compatible with Microsoft's ADSI naming format and JNDI.
File Information
Self-Extracting File Name: IXSESSPR.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
IXSESSPR.TXT |
(this file) |
||||
|
IXSESSPR.MSG |
162 |
9-4-97 |
2:25 AM |
Admin API sample
|
Author: |
RL |
|||
|
DocumentID: |
TID101389 |
|||
|
Date: |
9/17/97 8:45 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GW5XOB30.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample application will connect to the system object and add a user to the currently connected domain. You must have admin rights to the server for this application to work.
File Information
Self-Extracting File Name: GW5XOB30.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GW5XOB30.TXT |
(this file) |
||||
|
APP_OBJ.PAS |
4612 |
9-16-97 |
10:45 AM |
||
|
APP_OBJ.DFM |
2767 |
9-16-97 |
10:45 AM |
||
|
ADMN_API.DPR |
192 |
9-16-97 |
10:45 AM |
||
|
ADMN_API.EXE |
237568 |
9-16-97 |
10:45 AM |
||
|
GW5XOB30.MSG |
181 |
9-16-97 |
10:45 AM |
Object API MultiThreads sample application (Delphi APP)
|
Author: |
RL |
|||
|
DocumentID: |
TID101390 |
|||
|
Date: |
9/17/97 8:45 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GW5XOB31.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This sample creates three threads and lists messages of a GroupWise 5 mailbox. Threads 1 and 3 list messages using an AllMessagesIterator. Thread 2 lists all messages in the inbox.
File Information
Self-Extracting File Name: GW5XOB31.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GW5XOB31.TXT |
(this file) |
||||
|
THREADS.EXE |
214528 |
9-16-97 |
10:45 AM |
||
|
THREADS.DPR |
230 |
9-16-97 |
10:45 AM |
||
|
MAIN.DFM |
1647 |
9-16-97 |
10:45 AM |
||
|
MAIN.PAS |
8547 |
9-16-97 |
10:45 AM |
||
|
THREAD.PAS |
6716 |
9-16-97 |
10:45 AM |
||
|
GW5XOB31.MSG |
186 |
9-16-97 |
10:45 AM |
E-mail types in Email attribute of the NDS Base Schema
|
Author: |
KB |
|||
|
DocumentID: |
TID101391 |
|||
|
Date: |
9/17/97 8:45 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
XNDSSCH1.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
The NDS base schema defines an EMail Address attribute that can contain a type and an actual ASCII address. The E-mail types are defined in this TID.
Detailed Description
The NDS base schema defines an EMail Address attribute which can contain a type and an actual ASCII address. The E-mail types are defined as follows:
|
SMF 70 |
Type 1 |
||
|
SMF71 |
Type 2 |
||
|
SMTP |
Type 3 |
||
|
X.400 |
Type 4 |
||
|
SNADS |
Type 5 |
||
|
PROFS |
Type 6 |
||
|
GroupWise |
Type 7 |
File Information
Self-Extracting File Name: XNDSSCH1.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
XNDSSCH1.TXT |
(this file) |
||||
|
XNDSSCH1.MSG |
153 |
9-16-97 |
11:00 AM |
ActiveX: Maintaining multivalued attributes with Delphi 3
|
Author: |
HW |
|||
|
DocumentID: |
TID101416 |
|||
|
Date: |
10/13/97 6:56 PM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
D3MVALUE.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
This is a sample that demonstrates how to maintain multivalued NDS attributes with the DeveloperNet ActiveX controls and Delphi 3.
Detailed Description
The sample uses the members of a group object to show how to add and delete multiple attribute values at once. The code was built using Delphi 3 and version 1.0 of the DeveloperNet ActiveX controls.
File Information
Self-Extracting File Name: D3MVALUE.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
D3MVALUE.TXT |
(this file) |
||||
|
MULTIVAL.PAS |
11416 |
10-10-97 |
6:24 AM |
||
|
MULTIVAL.DFM |
1339 |
10-10-97 |
6:24 AM |
||
|
D3MVALUE.DPR |
1969 |
10-10-97 |
6:24 AM |
||
|
D3MVALUE.DOF |
1170 |
10-10-97 |
6:24 AM |
||
|
D3MVALUE.EXE |
271360 |
10-10-97 |
6:24 AM |
||
|
D3MVALUE.MSG |
131 |
10-10-97 |
6:24 AM |
NWGetServerCommandSetInfo corrupts large strings
|
Author: |
HW |
|||
|
DocumentID: |
TID101402 |
|||
|
Date: |
10/7/97 5:11 AM |
|||
|
Alert status: |
Yellow |
|||
|
Information type: |
Issue |
|||
|
Readme for: |
GTSETCMD.EXE |
|||
|
Novell productclass: |
NetWare API |
|||
|
Novell product andversion: |
NetWare SDK |
|||
|
Category: |
None |
Abstract
NWGetServerCommandSetInfo garbles strings larger than 50 bytes.
Detailed Description
There is a problem with the interpretation of the server data in the client library, in that the client assumes that the data is length preceded, but it is not. Engineering has fixed this problem. A corrected version of the function should be available with Vol.14.
File Information
Self-Extracting File Name: GTSETCMD.EXE
|
Files Included: |
Size |
Date |
Time |
||
|
GTSETCMD.TXT |
(this file) |
||||
|
GTSETCMD.MSG |
65 |
10-7-97 |
5:11 AM |
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.