Developer Pointers
Articles and Tips: article
01 Apr 1998
Novell Technical Information Documents
All of the Technical Information Documents (TIDs) discussed below are available at thefollowing 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)
SET Parameters Info: FSE_HIDE, setCmdCategory #12
|
Author: |
WS |
|
Document ID: |
TID101522 |
|
Date: |
2/24/98 4:48 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SETPARM.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
Q: What is the use of the FSE_HIDE flag in SET parameters?
A: You can scan, view, and change these "hidden" parameters with APIs or SET, but the menu-driven tools ServMan or SET (without specifying the parameter) will not display these "hidden" parameters (i.e., you need to know the parameter names before being able to change them).
Q: What is setCmdCategory #12. It is not listed in the documentation or header files?
A: The setCmdCategory list for NWFSE_SERVER_SET_CMDS_INFO in the Cross-Platform structures stops at category #11; it should also contain category #12: "Directory Services".
File Information
Self-Extracting File Name: SETPARM.EXE
|
Files Included: |
Size |
Date |
Time |
|
SETPARM.TXT |
(this file) |
||
|
SETPARM.MSG |
606 |
2-24-98 |
4:48 AM |
Return structure for NWScanPhysicalLocksByFile
|
Author: |
WS |
|
Document ID: |
TID101507 |
|
Date: |
2/12/98 4:03 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DLLUPD4.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The return buffers for the function NWScanPhysicalLocksByFile may look different for 16-bit and 32-bit code because the 32-bit DLLs seem to use 32-bit padding. This has to be taken care of in the header declaration. The correct padding would change the declarations to the following:
TYPE
PHYSICAL_LOCK2 = Record
{$IfDef Win32}
loggedCount : nuint16;
{$else}
loggedCount : nuint8;
{$EndIf}
shareableLockCount : nuint16;
recordStart : nuint32;
recordEnd : nuint32;
connNumber : nuint16;
taskNumber : nuint16;
lockType : nuint8;
{$IfDef Win32}
filler : nuint8;
filler2 : nuint16;
{$EndIf}
End;
PHYSICAL_LOCKS2 = Record
nextRequest : nuint16;
numRecords : nuint16;
locks : Array[0..31] Of PHYSICAL_LOCK2;
curRecord : nuint16;
reserved : Array[0..7] Of nuint8
End;
It is recommended that you modify the declarations in NWSYNC.INC accordingly.
File Information
Self-Extracting File Name: DLLUPD4.EXE
|
Files Included: |
Size |
Date |
Time |
|
DLLUPD4.TXT |
(this file) |
||
|
DLLUPD4.MSG |
997 |
2-12-98 |
1:15 AM |
Delphi Sample: Call the Win95 GUI Login
|
Author: |
WS |
|
Document ID: |
TID101517 |
|
Date: |
2/12/98 4:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DGUILOG.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
GUILOGIN is a 32-bit Delphi 2.x/3.x application for Windows 95 that illustrates the use of Delphi with NetWare APIs. It will allow you to spawn the Windows 95 Login Dialog.
Detailed Description
General information on how to use Delphi with the NetWare SDK can be found in the HOW-TO.DOC file.
To run the application, you need access to the 32-bit NetWare LGNW9532.DLL as provided with the NetWare Client software.
Platform Windows Win95
Compilers Borland Delphi 2.x/3.x
Functions Used GUILOGIN demonstrates the NWLoginUI NetWare API function.
File Information
Self-Extracting File Name: DGUILOG.EXE
|
Files Included: |
Size |
Date |
Time |
|
DGUILOG.TXT |
(this file) |
||
|
UNIT1.PAS |
2907 |
2-12-98 |
12:51 PM |
|
UNIT1.DFM |
623 |
2-12-98 |
12:51 PM |
|
READ.ME |
570 |
2-12-98 |
12:51 PM |
|
NWLOGIN.INC |
27829 |
2-12-98 |
12:51 PM |
|
NWLGUI.INC |
5406 |
2-12-98 |
12:51 PM |
|
NWADMIN.ICO |
766 |
2-12-98 |
12:51 PM |
|
NETWARE.ICO |
766 |
2-12-98 |
12:51 PM |
|
GUI_UNIT.DFM |
1809 |
2-12-98 |
12:51 PM |
|
HOW-TO.DOC |
5748 |
2-12-98 |
12:51 PM |
|
GUILOGIN.RES |
876 |
2-12-98 |
12:51 PM |
|
GUILOGIN.DPR |
225 |
2-12-98 |
12:51 PM |
|
GUILOGIN.DOF |
1137 |
2-12-98 |
12:51 PM |
|
GUI_UNIT.PAS |
3460 |
2-12-98 |
12:51 PM |
|
LGNW9532.PAS |
1814 |
2-12-98 |
12:51 PM |
|
DGUILOG.MSG |
160 |
2-12-98 |
12:51 PM |
MSGTOOLS
|
Author: |
WS |
|
Document ID: |
TID101523 |
|
Date: |
2/24/98 10:17 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MSGTOOLS.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
Q: My NLM that uses NWSNUT runs fine on NetWare v4.1x, but on NetWare 3.1x, it fails with the message: "NWSNUT-4-10-47: This NLM contains no messages."
A: When loading your files on NW v3.1x, either load the NLM from SYS:SYSTEM, or add the location of the NLM to the NLM search path using the console command SEARCH.
File Information
Self-Extracting File Name: MSGTOOLS.EXE
|
Files Included: |
Size |
Date |
Time |
|
MSGTOOLS.TXT |
(this file) |
||
|
MSGTOOLS.MSG |
321 |
2-24-98 |
10:17 AM |
Updated GroupWise 5 Tokens Documentation
|
Author: |
RL |
|
Document ID: |
TID101521 |
|
Date: |
2/19/98 10:47 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
GW5XTK01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
This is updated token documentation for GroupWise 5. It has a description of the tokens and for each parameter of each token. Open the Tokens.html file which contains an index to the other files.
File Information
Self-Extracting File Name: GW5XTK01.EXE
|
Files Included: |
Size |
Date |
Time |
|
GW5XTK01.TXT |
(this file) |
||
|
GW5TOKNS.ZIP |
105642 |
2-19-98 |
10:47 AM |
|
GW5XTK01.MSG |
199 |
2-19-98 |
10:47 AM |
Problems with Include Files for Delphi
|
Author: |
WS |
|
Document ID: |
TID101513 |
|
Date: |
2/12/98 4:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DELINC1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
There are some problems with the declarations of the SDK functions for Pascal/Delphi.
Detailed Description
Return structure for NWScanPhysicalLocksByFile The return buffers for the function NWScanPhysicalLocksByFile may look different for 16-bit and 32-bit code, since the 32-bit DLLs seem to use 32-bit padding. This has to be taken care of in the header declaration. This may also depend on the DLL versions used. The correct padding would change the declarations to the following:
TYPE
PHYSICAL_LOCK = Record
{$IfDef N_ARCH_32}
loggedCount : nuint16;
{$else}
loggedCount : nuint8;
{$EndIf}
shareableLockCount : nuint16;
recordStart : nuint32;
recordEnd : nuint32;
connNumber : nuint16;
taskNumber : nuint16;
lockType : nuint8;
{$IfDef N_ARCH_32}
filler : nuint8;
filler2 : nuint16;
{$EndIf}
End;
PHYSICAL_LOCKS = Record
nextRequest : nuint16;
numRecords : nuint16;
locks : Array[0..31] Of PHYSICAL_LOCK;
curRecord : nuint16;
reserved : Array[0..7] Of nuint8
End;
Changes are required in NWSYNC.INC and NWSYNC.PAS.
Return structure for NWScanConnectionsUsingFile The return buffers for the function NWScanConnectionsUsingFile may look different for 16-bit and 32-bit code, since the 32-bit DLLs seem to use 32-bit padding. This has to be taken care of in the header declaration. The correct padding would change the declarations to the following:
TYPE
CONN_USING_FILE = Record
connNumber : NWCONN_NUM;
taskNumber : nuint16;
lockType : nuint8;
accessControl : nuint8;
lockFlag : nuint8;
{$IFDEF N_ARCH_32}
filler : nuint8;
{$EndIf}
End;
CONNS_USING_FILE = Record
nextRequest : nuint16;
useCount : nuint16;
openCount : nuint16;
openForReadCount : nuint16;
openForWriteCount : nuint16;
denyReadCount : nuint16;
denyWriteCount : nuint16;
locked : nuint8;
forkCount : nuint8;
connCount : nuint16;
connInfo : Array[0..69] Of CONN_USING_FILE
End;
Changes affect the NWFILE.INC and NWFILE.H.
File Information
Self-Extracting File Name: DELINC1.EXE
|
Files Included: |
Size |
Date |
Time |
|
DELINC1.TXT |
(this file) |
||
|
DELINC1.MSG |
130 |
2-12-98 |
11:01 AM |
Problems with Delphi IMP files
|
Author: |
WS |
|
Document ID: |
TID101512 |
|
Date: |
2/12/98 4:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DELIMP1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
There are some bugs in the Delphi import files that might cause problems.
Detailed Description
Problems with IMP files in Vol 14 are as follows:
Two Names for Function 1157 in NetWin32.dll Function 1157 in NetWin32.dll is declared as NWDSOpenConnToNDSServer in NETNDS32.IMP and NETNDS16.imp, but as NWDSCONNECTTONDSSERVER (with typo) in NETCON32.IMP and NETCON16.imp.
NWGETNWNETVERSION Declared Differently The function NWGETNWNETVERSION is declared as function in NETCON32.imp and NETCON16.imp, but as procedure in NETNDS32.imp and NETNDS16.imp
NWDSFREEFILTER Declared Differently The function NWDSFREEFILTER is declared as prodedure in NETNDS32.IMP and NETNDS16.imp, but declared as procedure in NETCON32.IMP and NETCON16.imp
Bad Index Number for NWDSPutChange in Import Files The function NWDSPutChange has an incorrect index declaration in the 32-bit Pascal IMP files. It says index 1032, but should be 1016. The 16-bit declarations seem to be OK.
Missing declarations in NETNDS16.IMP Add the declarations shown in Figure 1 to NETNDS16.IMP.
Figure 1: Declarations to be added to NETNDS16.IMP
Function NWDSListPartitionsExtInfo; external 'NETWIN16.DLL' index 1171;
Function NWDSGetPartitionExtInfoPtr; external 'NETWIN16.DLL' index 1172;
Function NWDSGetPartitionExtInfo; external 'NETWIN16.DLL' index 1173;
Function NWDSPutAttrNameAndVal; external 'NETWIN16.DLL' index 3048;
Function NWDSPutChangeAndVal; external 'NETWIN16.DLL' index 3049;
Function NWDSReadObjectDSIInfo; external 'NETWIN16.DLL' index 3050;
Function NWDSGetDSIInfo; external 'NETWIN16.DLL' index 3051;
File Information
Self-Extracting File Name: DELIMP1.EXE
|
Files Included: |
Size |
Date |
Time |
|
DELIMP1.TXT |
(this file) |
||
|
DELIMP1.MSG |
127 |
2-12-98 |
11:01 AM |
Dynamic IPX Socket Number Range
|
Author: |
EE |
|
Document ID: |
TID101524 |
|
Date: |
2/26/98 1:26 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IIPXE001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The range of the dynamic IPX Socket number obtained using IPXOpenSocket or SPXOpenSocket is from 0x4000h through 0x7FFFh inclusive.
Detailed Description
The SDK documentation documenting the dynamic IPX Socket range is not consistent. This documentation bug will be fixed in the June 1998 SDK release (CD version 16). The dynamic IPX Socket number range is from 0x4000h through 0x7FFFh inclusive. To obtain a dynamic socket within this range, call IPXOpenSocket or SPXOpenSocket and passing socketNumber as 0x0000 as shown below:
unsigned short dynamic_socket = 0x0000; IpxOpenSocket(&dynamic_socket);
To set the number of maximum open IPX sockets on NetWare, load SPXCONFG.NLM.
File Information
Self-Extracting File Name: IIPXE001.EXE
|
Files Included: |
Size |
Date |
Time |
|
IIPXE001.TXT |
(this file) |
||
|
IIPXE001.MSG |
129 |
2-26-98 |
1:26 PM |
Serial Numbers for Multiple Licenses
|
Author: |
WS |
|
Document ID: |
TID101520 |
|
Date: |
2/17/98 11:50 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
WSERIAL.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The APIs GetNetworkSerialNumber and NWGetOSVersionInfo will only retrieve the serial number of the first installed license. If a NetWare v4.x/v5.x server has multiple licenses installed, the additional serial numbers cannot be retrieved. To get the serial numbers you can call the VERSION console command on the server. The NDS attribute "Serial Number" is not used for the server class.
This has been submitted as an enhancement request.
File Information
Self-Extracting File Name: WSERIAL.EXE
|
Files Included: |
Size |
Date |
Time |
|
WSERIAL.TXT |
(this file) |
||
|
WSERIAL.MSG |
442 |
2-17-98 |
11:50 AM |
Issue: Incorrect Pascal Declaration of LCONV.Date_format
|
Author: |
WS |
|
Document ID: |
TID101518 |
|
Date: |
2/16/98 12:58 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
LCONV1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
LCONV.Date_format is incorrectly declared as char in NWLOCALE.INC (SDK vol 13/14, probably also in vol 15), while it should be an nint like in the NWLOCALE.H. Because these types have different sizes, this may result in memory overwrites and unspecified program crashes or errors. Until this is fixed in the headers, please redefine LCONV.date_format as nint in NWLOCALE.INC and recompile.
File Information
Self-Extracting File Name: LCONV1.EXE
|
Files Included: |
Size |
Date |
Time |
|
LCONV1.TXT |
(this file) |
||
|
LCONV1.MSG |
393 |
2-16-98 |
12:57 AM |
NWSipxGetMaxTsduSize Returns 534 on Windows 95
|
Author: |
EE |
|
Document ID: |
TID101508 |
|
Date: |
2/12/98 4:03 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ISPXE001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
NWSipxGetMaxTsduSize will return a TSDU value of 534 if you have an older version of Novell Client 32 for Windows 95 installed. The new intraNetWare Client 2.2 for Windows 95 will return -1 if you call NWSipxGetMaxTsduSize.
Detailed Description
NWSipxGetMaxTsduSize will return a TSDU value of 534 if you have an older version of Novell Client 32 for Windows 95 installed. In this case, you must fragment data messages larger than 534. The new intraNetWare Client 2.2 for Windows 95 supports scatter/gather which will return SIPX_CONN_UNLIMITED_TSDU (-1) when you call NWSipxGetMaxTsduSize.
If the maximum TSDU value is equal to SIPX_CONN_UNLIMITED_TSDU, you can send any size data message to the peer system, and the API will automatically fragment the data message according to the output mode selected in the CIOutputMode connection endpoint parameter. By default, CIOutputMode is set to SIPX_CONN_FRAGMENT and data received is fragmented as necessary for delivery to the peer system. So, you do not have to set CIOutputMode if you want the large size data message to be fragmented automatically.
File Information
Self-Extracting File Name: ISPXE001.EXE
|
Files Included: |
Size |
Date |
Time |
|
ISPXE001.TXT |
(this file) |
||
|
ISPXE001.MSG |
220 |
2-12-98 |
1:16 AM |
32-Bit Delphi v2.0 Import Units for NW SDK
|
Author: |
WS |
|
Document ID: |
TID101519 |
|
Date: |
2/17/98 3:31 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DEL32SDK.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The INC and IMP files that used to be in this update (DEL32SDK) are obsolete and have been removed, since the appropriate files are included with the current versions of the NetWare SDK.
The attached HOW-TO document describes how to use the SDK with Delphi v1.x, v2.x, and v3.x.
File Information
Self-Extracting File Name: DEL32SDK.EXE
|
Files Included: |
Size |
Date |
Time |
|
DEL32SDK.TXT |
(this file) |
||
|
READ.ME |
2248 |
2-17-98 |
3:31 AM |
|
HOW-TO.DOC |
5748 |
2-17-98 |
3:31 AM |
|
DEL32SDK.TXT |
2104 |
2-17-98 |
3:31 AM |
|
DEL32SDK.MSG |
283 |
2-17-98 |
3:31 AM |
NWSIPX Send and Receive Programs that Deal with Large Data Size
|
Author: |
EE |
|
Document ID: |
TID101525 |
|
Date: |
2/26/98 5:43 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XSIPXE01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The send program sends 100 messages with a 32K data size for each message to a peer receive program using the callback event notification method
Detailed Description
NWSIPX API will support autofragmenting of any data messages larger than the maximum transport service data unit (TSDU) supported by the underlying SPX protocol stack on Windows NT and Windows 95 (with intraNetWare Client v2.2 for Windows 95 installed). The send and receive programs use callback event notification method to send and receive messages. Other event notifications methods (blocking and user event) are also used in these programs.
File Information
Self-Extracting File Name: XSIPXE01.EXE
|
Files Included: |
Size |
Date |
Time |
|
XSIPXE01.TXT |
(this file) |
||
|
RECVPROJ.ZIP |
1181473 |
2-26-98 |
5:43 PM |
|
RECVCBK.CPP |
14393 |
2-26-98 |
5:43 PM |
|
SENDCBK.CPP |
11669 |
2-26-98 |
5:43 PM |
|
SENDPROJ.ZIP |
1166403 |
2-26-98 |
5:43 PM |
|
XSIPXE01.MSG |
140 |
2-26-98 |
5:43 PM |
Additional Information about NWGetPathFromDirectoryBase
|
Author: |
WS |
|
Document ID: |
TID101515 |
|
Date: |
2/12/98 4:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XGETBASE.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
SDK Volume 14: NWGetPathFromDirectoryBase
It should be pointed out in the pathName description or the Remarks section that NWGetPathFromDirectoryBase returns the path as a length-preceded array with generic (namespace-independent) separators.
The parameter description for NWGetPathFromDirectoryBase says: len (OUT) Points to the path length and specifies how much of the buffer pointed to by the pathName parameter was used. It should read: len (IN/OUT) Points to the path length and specifies how much of the buffer pointed to by the pathName parameter was used. Initialize to the length of the buffer to hold the path.
File Information
Self-Extracting File Name: XGETBASE.EXE
|
Files Included: |
Size |
Date |
Time |
|
XGETBASE.TXT |
(this file) |
||
|
XGETBASE.MSG |
26 |
2-12-98 |
11:02 AM |
Delphi Sample: NWGetDriveStatus
|
Author: |
WS |
|
Document ID: |
TID101511 |
|
Date: |
2/12/98 4:03 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DDRVSTAT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
The function NWGetDriveStatus allows to retrieve drive mapping status and the mapped drive in multiple formats (Vol, UNC, NW). Sample code for Delphi v1.x, v2.x, and v3.x is included.
See the READ.ME and HOW.TO for details.
File Information
Self-Extracting File Name: DDRVSTAT.EXE
|
Files Included: |
Size |
Date |
Time |
|
DDRVSTAT.TXT |
(this file) |
||
|
UNIT1.PAS |
2978 |
2-12-98 |
11:01 AM |
|
UNIT1.DFM |
645 |
2-12-98 |
11:01 AM |
|
UNIT1.DCU |
3549 |
2-12-98 |
11:01 AM |
|
READ.ME |
688 |
2-12-98 |
11:01 AM |
|
NETWARE.ICO |
766 |
2-12-98 |
11:01 AM |
|
HOW-TO.DOC |
5748 |
2-12-98 |
11:01 AM |
|
DRVSTT32.RES |
876 |
2-12-98 |
11:01 AM |
|
DRVSTT32.DSK |
2853 |
2-12-98 |
11:01 AM |
|
DRVSTT32.DPR |
161 |
2-12-98 |
11:01 AM |
|
DRVSTT16.DPR |
161 |
2-12-98 |
11:01 AM |
|
DRVSTT16.RES |
794 |
2-12-98 |
11:01 AM |
|
DRVSTT16.OPT |
354 |
2-12-98 |
11:01 AM |
|
DRVSTT32.DOF |
558 |
2-12-98 |
11:01 AM |
|
DDRVSTAT.MSG |
212 |
2-12-98 |
11:01 AM |
Parental Rights on NW v3.x/v4.x Servers
|
Author: |
WS |
|
Document ID: |
TID101516 |
|
Date: |
2/12/98 4:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XPARENT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
You may find several references to obsolete (NW v2.x) "Parental" rights in the SDK documentation.
The "Parental" right on NW v2.x was quite similar to the "Access Control" right on NW v3.x/v4.x. For all functions that affect NW 3.x (or newer) targets, the documentation text should be modified to something like the following:
"The requesting workstation must have access control rights for 3.x/4.x/5.x servers or parental rights for 2.x servers."
Examples of affected functions are listed below:
NWAddTrustee()NWAddTrusteeToDirectory()
NWDeleteTrusteeFromDirectory()
NWModifyMaximumRightsMask()
NWSetDirectoryInformation()
File Information
Self-Extracting File Name: XPARENT.EXE
|
Files Included: |
Size |
Date |
Time |
|
XPARENT.TXT |
(this file) |
||
|
XPARENT.MSG |
26 |
2-12-98 |
11:02 AM |
NDS Browser for Delphi v1.x/2.x/3.x
|
Author: |
WS |
|
Document ID: |
TID101510 |
|
Date: |
2/12/98 4:03 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DBROWSE.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
Sample code showing a DS browser compatible with Borland Delphi versions 1.x, 2.x, and 3.x.
File Information
Self-Extracting File Name: DBROWSE.EXE
|
Files Included: |
Size |
Date |
Time |
|
DBROWSE.TXT |
(this file) |
||
|
DBROWS16.DPR |
266 |
2-12-98 |
11:01 AM |
|
DBROWS32.RES |
876 |
2-12-98 |
11:01 AM |
|
DBROWS32.DPR |
341 |
2-12-98 |
11:01 AM |
|
DBROWS32.DOF |
872 |
2-12-98 |
11:01 AM |
|
DBROWS16.RES |
794 |
2-12-98 |
11:01 AM |
|
DBROWS16.OPT |
343 |
2-12-98 |
11:01 AM |
|
DELPHI_U.PAS |
34313 |
2-12-98 |
11:01 AM |
|
DBROWSE.MSG |
92 |
2-12-98 |
11:01 AM |
|
DBROWS16.DOF |
872 |
2-12-98 |
11:01 AM |
|
U_VARS.PAS |
1429 |
2-12-98 |
11:01 AM |
|
U_ABOUT.PAS |
488 |
2-12-98 |
11:01 AM |
|
U_ABOUT.DFM |
691 |
2-12-98 |
11:01 AM |
|
U_ABOUT.DCU |
2267 |
2-12-98 |
11:01 AM |
|
READ.ME |
929 |
2-12-98 |
11:01 AM |
|
NETWARE.ICO |
766 |
2-12-98 |
11:01 AM |
|
MAIN.PAS |
4925 |
2-12-98 |
11:01 AM |
|
MAIN.DFM |
2002 |
2-12-98 |
11:01 AM |
|
MAIN.DCU |
7126 |
2-12-98 |
11:01 AM |
|
HOW-TO.DOC |
5748 |
2-12-98 |
11:01 AM |
Sample: Call NetWare v4.x NCPs (Pascal for DOS)
|
Author: |
WS |
|
Document ID: |
TID101528 |
|
Date: |
3/5/98 6:35 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SC4X01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
This Pascal DOS sample contains a PASCAL source unit (NW40.PAS) and a test program (NW40TEST.PAS) showing how to setup the request buffers and how to interpret the reply.
The samples have been tested with Borland Pascal v7.0 (Real Mode) and will probably work in all Borland Pascal versions from v4.0.
The source can also be easily translated to other programming languages like BASIC or whatever you prefer, as long as you can call Int 21h.
Detailed Description
The following set of APIs is documented here:
|
NW40_ChangeConnectionStateNW40_ClearConnectionNumberNW40_GetConnectionListNW40_SetWatchDogDelayIntervalNW40_GetExtendedVolumeInformationNW40_GetObjectEffectiveRightsNW40_ActiveLANBoardListNW40_CPUInformationNW40_GetCacheInformationNW40_GetServerInformationNW40_GetKnownNetWorksNW40_GetKnownServersNW40_GetNetworkRouterInformationNW40_GetNLMsLoadedNW40_GetOSVersionInformationNW40_GetProtocolStackByBoardNW40_GetServerSetCategoriesNW40_GetServerSetCommandsInfoNW40_GetIPXSPXInformationNW40_GetLANCommonCountersNW40_GetLANConfigurationNW40_GetNLMInformationNW40_GetUserInformationNW40_GetVolumeSwitchInformationNW40_MonitorNDSConnectionNW40_PingForNDSNCPNW40_ReturnBinderyContext |
Note: These files were uploaded to CompuServe/NovUser in 1993.
File Information
Self-Extracting File Name: SC4X01.EXE
|
Files Included: |
Size |
Date |
Time |
|
SC4X01.TXT |
(this file) |
||
|
NW40TEST.PAS |
16365 |
3-5-98 |
6:35 AM |
|
NW40TEST.EXE |
20080 |
3-5-98 |
6:35 AM |
|
NW40.PAS |
48550 |
3-5-98 |
6:35 AM |
|
SC4X01.MSG |
455 |
3-5-98 |
6:35 AM |
Get/Set the Workstation Broadcast Mode with Delphi
|
Author: |
WS |
|
Document ID: |
TID101509 |
|
Date: |
2/12/98 4:03 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
BRDMOD.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK |
|
Category: |
None |
Abstract
BrdMode is a Delphi 1.x/2.x/3.x application that illustrates the use of Delphi with NetWare APIs. It will display and change the broadcast state of the workstation. Broadcast messages can be disabled or enabled.
General information on how to use Delphi with the NetWare SDK can be found in the included HOW-TO.DOC file.
File Information
Self-Extracting File Name: BRDMOD.EXE
|
Files Included: |
Size |
Date |
Time |
|
BRDMOD.TXT |
(this file) |
||
|
BRDMOD16.RES |
898 |
2-12-98 |
11:01 AM |
|
BRDMOD32.DSK |
4871 |
2-12-98 |
11:01 AM |
|
BRDMOD.MSG |
327 |
2-12-98 |
11:01 AM |
|
BRDMOD16.DPR |
237 |
2-12-98 |
11:01 AM |
|
U_VARS.PAS |
1336 |
2-12-98 |
11:01 AM |
|
READ.ME |
913 |
2-12-98 |
11:01 AM |
|
MSG_U.PAS |
2430 |
2-12-98 |
11:01 AM |
|
MSG_U.DFM |
646 |
2-12-98 |
11:01 AM |
|
HOW-TO.DOC |
5748 |
2-12-98 |
11:01 AM |
|
DELPHI_U.PAS |
32988 |
2-12-98 |
11:01 AM |
|
BRDMOD32.RES |
1072 |
2-12-98 |
11:01 AM |
|
BRDMOD32.OPT |
343 |
2-12-98 |
11:01 AM |
|
BRDMOD32.DPR |
237 |
2-12-98 |
11:01 AM |
|
BRDMOD32.DOF |
1099 |
2-12-98 |
11:01 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.