Developer Pointers
Articles and Tips: article
01 Mar 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)
Novell Directory Services
Supervisor under NetWare v4.x NDS
|
Author: |
LC |
|
Document ID: |
TID100967 |
|
Document revision |
A |
|
Date: |
10/16/96 11:30 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IDSA00.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
Initial User Supervisor under NetWare v4.x NDS The user Supervisor in the world of Novell Directory Services (NDS) is an odd "creature." It is both an NDS Object and a non-object. It is a Bindery-Object. It is created as an NDS object whose rights are restricted to a specific Bindery context AND ONLY to that context. SUPERVISOR DOES NOT HAVE ADMIN RIGHTS.
File Information
Self-Extracting File Name: IDSA00.EXE
|
Files Included: |
Size |
Date |
Time |
|
IDSA00.TXT |
(this file) |
||
|
ABSTRACT.TXT |
1120 |
10-9-96 |
1:11 PM |
NWA_SNAPIN_VERSION Changed on Vol.9
|
Author: |
HW |
|
Document ID: |
TID101041 |
|
Document revision: |
A |
|
Date: |
11/20/96 8:25 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SNAPVER9.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Directory Services |
Abstract
The NWA_SNAPIN_VERSION constant has changed on SDK CD Vol.9, nwsdk\include\nwsnapin.h. This may cause problems when you build snap-in DLLs for the legacy 16-bit NWAdmin.
Detailed Description
The nwsnapin.h now declares the snap-in version to be 1.1 instead of 1.0 as it was previously. This may lead to problems, as the shipping 16-bit NWAdmin (4.10.4) checks for version 1.0 and will fail any registration attempts for snap-ins built with the new version. While this is a bug and will be fixed in a future release of the SDK CD, the short-term fix for developers targeting 16-bit platforms is to modify the relevant lines in nwsnapin.h to look like this:
/*------------------------------------------*/
/* SNAPIN Version related defines */
/*------------------------------------------*/
#define NWA_SNAPIN_VER_MAJOR 1
#ifdef N_ARCH_16
# define NWA_SNAPIN_VER_MINOR 0
#else
# define NWA_SNAPIN_VER_MINOR 1
#endif
#define NWA_SNAPIN_VER_REVISION 0
#define NWA_SNAPIN_VERSION NMake32(
NMake16(NWA_SNAPIN_VER_REVISION, 0 ) ,
NMake16(NWA_SNAPIN_VER_MINOR,NWA_SNAPIN_VER_MAJOR ))
This will ensure correct versions for all target platforms.
File Information
Self-Extracting File Name: SNAPVER9.EXE
|
Files Included: |
Size |
Date |
Time |
|
SNAPVER9.TXT |
(this file) |
DOS
NWReadQueueJobEntry2
|
Author: |
RM |
|
Document ID: |
TID100668 |
|
Document revision: |
A |
|
Date: |
07/29/96 3:29 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM001.EXE |
|
Novell product class |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
How do you get the print job information out of the NWQueueJobStruct structure in the call NWReadQueueJobEntry2?
Detailed Description
How to get the printing information from the NWQueueJobStruct
There is some confusion about how to get information out of the NWQueueJobStruct in the call NWReadQueueJobEntry2. The function call and structures involved are listed below.
Notice the NWQueueJobStruct has a field called clientRecordArea, which is 512 bytes long.
In the case of NetWare printing services, this field is used to store information about the print job in the print queue. It is stored in the format defined by the NWPS_ClientRecord structure found in NWPS_JOB.H in the Novell SDK.
NWQueueJobStruct
NWCCODE N_API NWReadQueueJobEntry2
|
(NWCONN_HANDLE |
conn, |
|
|
nuint32 |
queueID, |
|
|
nuint32 |
jobNumber, |
|
|
NWQueueJobStruct N_FAR * |
job); |
NAME NWQueueJobStruct -
Holds the information found in the queue job record. The structure is defined in nwqms.h as follows:
|
typedef struct |
||
|
{ |
||
|
nuint32 |
clientStation; |
|
|
nuint32 |
clientTask; |
|
|
nuint32 |
clientID; |
|
|
nuint32 |
targetServerID; |
|
|
nuint8 |
targetExecutionTime[6]; |
|
|
nuint8 |
jobEntryTime[6]; |
|
|
nuint32 |
jobNumber; |
|
|
nuint16 |
jobType; |
|
|
nuint16 |
jobPosition; |
|
|
nuint16 |
jobControlFlags; |
|
|
nuint8 |
jobFileName[14]; |
|
|
nuint32 |
jobFileHandle[6]; |
|
|
nuint32 |
servicingServerStation; |
|
|
nuint32 |
servicingServerTask; |
|
|
nuint32 |
servicingServerID; |
|
|
nuint8 |
jobDescription[50]; |
|
|
nuint8 |
clientRecordArea[152]; |
|
|
} NWQueueJobStruct; |
clientRecordArea -
Indicates supplementary information that can be exchanged between the queue client and the queue server. The format for this information is defined by your application.
NWPS_JOB.h
|
typedef struct { |
||
|
nuint8 |
versionNumber; |
|
|
nuint8 |
tabSize; |
|
|
nuint16 |
numberOfCopies; |
|
|
nuint16 |
printControlFlags; |
|
|
nuint16 |
maxLinesPerPage; |
|
|
nuint16 |
maxCharsPerLine; |
|
|
nuint8 |
formName[13]; |
|
|
nuint8 |
reserve[9]; |
|
|
nuint8 |
bannerNameField[13]; |
|
|
nuint8 |
bannerFileField[13]; |
|
|
nuint8 |
headerFileName[14]; |
|
|
nuint8 |
directoryPath[80]; |
|
|
} NWPS_ClientRecord; |
File Information
Self-Extracting File Name: ARM001.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM001.TXT |
(this file) |
Large memory model
|
Author: |
RM |
|
Document ID: |
TID100815 |
|
Document revision: |
A |
|
Date: |
09/6/96 5:12 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM003.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
In the NetWare SDK for the client, the memory model needs to be LARGE. The libraries have been compiled in the large model, and using small or huge models in the code generation will give unexpected or inaccurate results. This information is not in the present SDK documentation, but it will be added.
File Information
Self-Extracting File Name: ARM003.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM003.TXT |
(this file) |
Get Connections Using a File Misdocumented
|
Author: |
DD |
|
Document ID: |
TID100899 |
|
Document revision: |
A |
|
Date: |
09/27/96 3:17 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM005.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
The assembly API call Get Connections Using A File is misdocumented. The documentation should read as follows in the detailed description.
Detailed Description
Get Connections Using A File
NAME Get Connections Using A File -
This call returns all logical connections using the file specified by Directory Handle and File Path.
NetWare Server: 3.11, 4.0
Lite: None
Figure 1: Get Connections Using A File: Request Packet
|
Offset |
Request Packet Contents |
Bytes |
Remarks |
|
0 |
Request Packet Length |
2 |
Length of the request packet starting at offset two (2).The first two bytes designating the length of the packet are not included. |
|
2 |
236 (ECh) |
1 |
Subfunction code |
|
3 |
DataStream |
1 |
Contains the data stream number if thename space is Macintosh. A value of 0 isthe resource fork and a value of 1 is thedata fork. If DOS, the value is always 0. |
|
4 |
Volume Number |
1 |
Identifies the volume on which the fileexists. |
|
5 |
Directory Entry |
4 |
The Directory Entry number, indicating the file or directory path. Index to FileServer is directory tables. Must be associated with volume number. Thevalue returned from Convert Path to Directory Entry must be long swappedbefore it is placed in this field. |
|
9 |
Last Record Seen |
2 |
Last record for which information wasreturned. Set to zero (0) on the first call. |
On Entry
|
AL23 (17h) |
|
|
BX |
Number of fragments in request packet. |
|
5-fragment maximum. |
|
|
DX |
Number of fragments in reply packet. |
|
5-fragment maximum. |
|
|
CX |
Handle to valid connection table entry |
|
DS:SI |
Pointer to fragment list for request packet |
|
ES:DI |
Pointer to fragment list for reply packet |
On Exit
AH Completion Code Type. 0 indicates successful.
AL Completion Code. 0 indicates successful.
Note All other registers preserved.
Completion Codes
AH=88h DOS Requester Completion Codes (REQSTR_ERR)
|
AL |
Remarks |
|
0 |
SUCCESS: The requester has filled in the reply packet. |
|
Non-0 |
Unsuccessful. The contents of the reply packet are invalid. |
|
01h |
Invalid Connection |
|
50h |
Too Many Rep Frags |
AH=89h Server Completion Codes (SERVER_ERR)
|
AL |
Remarks |
|
0 |
Successful |
|
96h |
Server Out Of Memory |
|
C6h |
No Console Rights |
Remarks
Get Connections Using A File must be repeated until Next Request Record (returned in the reply message) is 0. There is one record for every connection using or trying to use the specified file.
Lock Type contains the following bit flags:
|
BitsStatus |
|
|
76543210 |
|
|
xxxxxxx1 |
Locked |
|
xxxxxx1x |
Open Shareable |
|
xxxxx1xx |
Logged |
|
xxxx1xxx |
Open Normal |
|
x1xxxxxx |
TTS Holding Lock |
|
1xxxxxxx |
Transaction Flag Set On This File |
Figure 2: Get Connections Using A File: Reply Packet
|
Offset |
Reply Packet Contents |
Bytes |
Remarks |
|
0 |
Next Request Record |
2 |
The value that Last Record Seen must beset to in the next call. |
|
2 |
Use Count |
2 |
Number of tasks opening or logging thefile. |
|
4 |
Open Count |
2 |
Number of tasks having the file open. |
|
6 |
Open For Read Count |
2 |
Number of logical connections having thefile open for reading. |
|
8 |
Open For Write Count |
2 |
Number of logical connections having thefile open for writing. |
|
10 |
Deny Read Count |
2 |
Number of logical connections havingdenied other connections the right to readfrom the file. |
|
12 |
Deny Write Count |
2 |
Number of logical connections havingdenied other connections the right to writeto the file. |
|
14 |
Lock Flag |
1 |
0x00 Not locked exclusively 0xFELocked by a file lock 0xFF Locked byBegin Share File Set |
|
15 |
Fork Count |
1 |
|
|
16 |
Number Of Records |
2 |
Number of records that follow. Thenumber of times the remaining fieldsrepeat. |
|
18 |
Connection Number |
2 |
Logical connection number of theworkstation using the file. |
|
20 |
Task Number |
2 |
Task number using the file. |
|
22 |
Lock Type |
1 |
See Remarks below. |
|
23 |
Access Flag |
1 |
Repeats number of record times. |
|
24 |
Lock Flag |
1 |
Repeats number of record times. |
|
Connection Number n (2), Task Number n (2), Lock Type n (1), AccessControl n (1), and Lock Flag n (1) repeat Number Of Records times. Where n isone of the connections using the file. |
File Information
Self-Extracting File Name: ARM005.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM005.TXT |
(this file) |
StartSendingPktsTimed is Misdocumented
|
Author: |
RM |
|
Document ID: |
TID100871 |
|
Document revision: |
A |
|
Date: |
09/19/96 4:37 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM006.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
There are documentation errors with the ticks parameter and the target object in the SendPacketsRequestStruct.
Detailed Description
The target should read as follows:
target
Indicates a structure of type BeginDiagnosticStruct, which, in turn, is a structure of type IPXAddress. IPXAddress is defined in NXTD.H and holds information in the following:
BYTE network[4] BYTE node[6] BYTE socket[2]
Also, the ticks that are passed into the parameter are misdocumented. It says:
ticks
(IN) Indicates the the time delay (in units of clock ticks) before starting to send packets (approximately 18 ticks per second).
It should read : Indicates the amount of time that the packets will continue to be sent (in units of clock ticks, approximately 18 ticks).
File Information
Self-Extracting File Name: ARM006.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM006.TXT |
(this file) |
NWCCLicenseConn is Misdocumented
|
Author: |
RM |
|
Document ID: |
TID100963 |
|
Document revision: |
A |
|
Date: |
10/16/96 10:59 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM008.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
NWCCLicenseConn states in the documentation:
Remarks NWCCLicenseConn causes a connection to become licensed. If necessary, the license NCP will be sent. If the specified handle is already in a licensed state, an error (NWE_HANDLE_ALREADY_LICENSED) will be returned.
The NWE_HANDLE_ALREADY_LICENSED does not get returned. In testing on WIN95 and with the VLMs, if there is already a licensed connection, then zero is returned.
Detailed Description
NWCCLicenseConn states in the documentation:
Remarks NWCCLicenseConn causes a connection to become licensed. If necessary, the license NCP will be sent. If the specified handle is already in a licensed state, an error (NWE_HANDLE_ALREADY_LICENSED) will be returned.
The NWE_HANDLE_ALREADY_LICENSED does not get returned. In testing on WIN95 and with the VLMs, if there is already a licensed connection, then zero is returned.
Here is what actually happens with the call:
Under Windows NT, it is true that we remap NWE_HANDLE_ALREADY_LICENSE to SUCCESS.
Under Windows 95, the requester does not support this function. The library simply returns 0.
Under VLMs, this function is supported and returns 0 for success.
File Information
Self-Extracting File Name: ARM008.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM008.TXT |
(this file) |
NWAdEnable Returned 89a7
|
Document ID: |
TID100530 |
|
Document revision: |
A |
|
Date: |
06/12/96 3:43 pm |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IAUDIT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
NWADEnable returned 89a7, which means invalid OS version. This is a bug in the API. The problem is fixed in release 8. This bug is in all client platforms (dos, Win16, Win32).
File Information
Self-Extracting File Name: IAUDIT.EXE
|
Files Included: |
Size |
Date |
Time |
|
IAUD.TXT |
170 |
06-12-96 |
3:42 pm |
|
IAUDIT.TXT |
(this file) |
Dos Error Code with the API Set
|
Author: |
RM |
|
Document ID: |
TID101052 |
|
Document revision: |
A |
|
Date: |
11/25/96 3:05 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM011.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
There are some NetWare APIs that will return DOS error codes. One example is NWConvertHandle, which returns a local file handle. If there are too many files open on the workstation, then an error 4 is returned. This is a DOS error 4, too many files open. So, next time you get errors 188 back from an api call, look at the DOS error codes to see if it will help you in your debugging.
File Information
Self-Extracting File Name: ARM011.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM011.TXT |
(this file) |
Bindery Context Sets for Bindery Emulation
|
Author: |
MM |
|
Document ID: |
TID101088 |
|
Document revision: |
A |
|
Date: |
01/15/97 5:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
BDEMU.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
Bindery context has to be set on a 4x server before bindery emulation programs work properly, and the 4x server must have a replica before setting the bindery context. Set bindery context command is only setting the bindery context string. Even if the set command returns a string, it does not necessarily mean that bindery context is set. To verify bindery context is set properly, type "config at the system console.
File Information
Self-Extracting File Name: BDEMU.EXE
|
Files Included: |
Size |
Date |
Time |
|
BDEMU.TXT |
(this file) |
NWPS_ATTR_NOTIFY is NWPS_Typed_Name
|
Author: |
MM |
|
Document ID: |
TID101055 |
|
Document revision: |
A |
|
Date: |
12/3/96 1:31 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INWPSNOT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
NWPSCfgGetFirstPrinterAttr - data type for NWPS_ATTR_NOTIFY should be NWPS_Typed_Name. The documentation said that the type is Typed_Name_T.
File Information
Self-Extracting File Name: INWPSNOT.EXE
|
Files Included: |
Size |
Date |
Time |
|
INWPSNOT.TXT |
(this file) |
NWInitUnicodeTables() Returns -489 (0xFE17)
|
Document ID: |
TID100555 |
|
Document revision: |
A |
|
Date: |
06/27/96 3:59 pm |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INITUCT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
NWInitUnicodeTables() returns an error code of -489 (0xFE17). This error code indicates that the Unicode Tables are already loaded. Beginning with Novell Client SDK release SDK7, the function NWCallsInit() automatically loads the Unicode Tables. A subsequent call to the NWInitUnicodeTables() will then return -489.
File Information
Self-Extracting File Name: INITUCT.EXE
|
Files Included: |
Size |
Date |
Time |
|
BOVO.TXT |
313 |
06-27-96 |
3:58 pm |
|
INITUCT.TXT |
(this file) |
Developer Guide Doc Error
|
Author: |
RM |
|
Document ID: |
TID100903 |
|
Document revision: |
A |
|
Date: |
09/27/96 4:46 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ARM007.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
The guide states NWCLearConnectionNumber is being obsoleted. It isn't.
Detailed Description
In the Cross-Platform Developers Guide in Volume 9 of the sdk, it states the following under setting connection parameters functions:
Connection Table Functions
The following functions operate on the Connection Table for either the NetWare Requester or NETX.
FunctionHeaderDescription
NWClearConnectionNumber logs out the connection associated with the specified connection number. IMPORTANT: This call is being obsoleted. Call NWCCOpenConnByName.
The IMPORTANT: notice in this table is incorrect. This function is not being obsoleted, and calling NWCCOpenConnByName does not have the same functionality.
File Information
Self-Extracting File Name: ARM007.EXE
|
Files Included: |
Size |
Date |
Time |
|
ARM007.TXT |
(this file) |
General Business
CMC Gateway Setup
|
Author: |
MA |
|
Document ID: |
TID100858 |
|
Document revision: |
A |
|
Date: |
09/16/96 3:43 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
GW5DCS01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
How to set up a CMC gateway.
Detailed Description
Information for this example:
Server: LEGAZPI - mapped to drive "L" Domain: LDOM Post Office: LPOST
Create the directory WPGATE/CMCAPI under the domain directory on your server; for example, "L:\LDOM\WPGATE\CMCAPI.
On SDK 9 (and above) go to the GRPWARE\GRPWISE\CMC_CSA directory and run INSTALL.EXE.
Choose to install the NLM server or the OS/2 server.
The "Install From: directory should default to your present location.
Enter the full path to your domain directory (L:\LDOM).
The "Install To: should default to the CMCAPI directory (L:\LDOM\WPGATE\CMCAPI).
The "CMC API Server Directory: should be the SYSTEM directory on the server for the NLMs on a NetWare server or on the local hard drive for the DLLs on an OS/2 box.
In the PUBLIC directory on your server, rename the file GWGSQ13X.DLL to GWGSQ13X.DL. This DLL may be required later, but is not at this time.
Run NWADMN3X.EXE and -
Define a gateway under the domain (by right-clicking on the domain and choosing "create), checking all properties for correct values.
The Gateway Name can be anything. I used CMCGATE.
The Gateway Home Directory needs to be CMCAPI.
The Gateway Type is CMC.
Check the box to define additional properties, or go into the objects details after the object has been created and -
Set the platform type.
Enter an Alias name, which can be anything (such as CMCAlias).
Check to see that the full UNC path to the post office is correct (\\legazpi\sys\lpost).
Click on Optional Gateway Settings and set the Directory Sync/Exchange to None.
Click on Gateway Administrators, then Add to make a user the administrator. Be generous with the administrator role here until you have the gateway running properly.
Click on Gateway-Specific Setup. If you do not have this option, see #3 above.
Click on the Launch button and, when the "Access Rules for: CMCGATE window appears (CMCGATE is my gateway from #4.A.i above), tab to "OK and press <Enter<.
Click on OK to close the window and save your work.
Your CMC gateway is now set up!
File Information
Self-Extracting File Name: GW5DCS01.EXE
|
Files Included: |
Size |
Date |
Time |
|
GW5DCS01.TXT |
(this file) |
Dynatext Can't Find Book
|
Document ID: |
TID100437 |
|
Document revision: |
B |
|
Date: |
02/23/96 3:51 am |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DYNEVY.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
Some books installed from the SDK CD-ROM cannot be opened from within the Dynatext reader, as they are in envoy document format.
Please see the attached document for a solution.
File Information
Self-Extracting File Name: DYNEVY.EXE
|
Files Included: |
Size |
Date |
Time |
|
DYNAEVY.TXT |
718 |
02-20-96 |
2:39 pm |
|
DYNEVY.TXT |
(this file) |
Dynatext Hot Link Errors O SDK 10
|
Author: |
BR |
|
Document ID: |
TID101083 |
|
Document revision: |
A |
|
Date: |
01/15/97 5:49 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IDOCROO1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
In SDK release 10, NW SDK collection, SDK Views book, there are three hot links (fingers) to the Developers Tools Reference. When selected, each of them go to the Transport Developers Guide instead. This problem will be corrected by SDK release 12.
File Information
Self-Extracting File Name: IDOCROO1.EXE
|
Files Included: |
Size |
Date |
Time |
|
IDOCROO1.TXT |
(this file) |
Problems Installing OnLine Documentation
|
Document ID: |
TID100426 |
|
Document revision: |
A |
|
Date: |
02/09/96 5:12 pm |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DYNAPROB.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
When you install the online documentation to a non-root directory of any drive, DYNATEXT.INI and SYSDOCS.CFG point to incorrect file locations. Thus, when you click on the icon labeled "Novell SDK Documentation," the following error message is returned:
Configuration Error: The collection variable is not specified in the Dynatext.ini File.
The solution is contained in the attached file.
File Information
Self-Extracting File Name: DYNAPROB.EXE
|
Files Included: |
Size |
Date |
Time |
|
DYNATEXT |
724 |
02-09-96 |
5:10 pm |
|
DYNAPROB.TXT |
(this file) |
NWDetachFromFileServer Doc. Bug
|
Author: |
DS |
|
Document ID: |
TID100669 |
|
Document revision: |
A |
|
Date: |
07/30/96 10:52 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
TIDNWD01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
NWDetachFromFileServer, an obsoleted function as of 1/1/97, incorrectly identifies NWCCCloseConn as its successor. These functions perform different tasks.
Detailed Description
NWDetachFromFileServer, an obsoleted function as of 1/1/97, incorrectly identifies NWCCCloseConn as its successor. These functions perform different tasks. NWCCCloseConn terminates a connection and frees local resources for that connection, but does not terminate the attachment to the server. The documentation should state that NWCCSysCloseConnRef, whose function more closely matches that of NWDetachFromFileServer, should be used. This will be resolved in future versions of the documentation.
File Information
Self-Extracting File Name: TIDNWD01.EXE
|
Files Included: |
Size |
Date |
Time |
|
TIDNWD01.TXT |
(this file) |
NEST
NEST 1.2 FlexOS Path Problem
|
Author: |
BT |
|
Document ID: |
TID100688 |
|
Document revision: |
A |
|
Date: |
07/31/96 2:41 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
FLEXPATH.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
A path change in the NEST SDK 1.2 was not fully implemented. FlexOS tools such as Link86 and Lib86 were formerly located in c:\NEST\FlexOS\BIN. They have been moved to c:\NEST\FlexOS in release 1.2. However, the make file was not updated to reflect the path change. Modify the file NEST\MAK\FlexOS.INC on lines 153, 156, and 341 and change "\bin\" to '\'
OLD Line 153: LIBRARIAN=$(FLEXOS_PATH)\bin\lib86 OLD Line 156: LINKER=$(FLEXOS_PATH)\bin\link86 OLD Line 341: $(FLEXOS_PATH)\bin\LINK86.EXE $(INPFILE)[inp]
File Information
Self-Extracting File Name: FLEXPATH.EXE
|
Files Included: |
Size |
Date |
Time |
|
FLEXPATH.TXT |
(this file) |
Tv_hires Not Defined in NEST for VxWorks
|
Author: |
MG |
|
Document ID: |
TID100787 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:22 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID2.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
Definition of tv_hires in Wind Rivers VxWorks header files needs to be modified to work with NEST for VxWorks.
File Information
Self-Extracting File Name: MGTID2.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID2.TXT |
(this file) |
||
|
MGTIDB.TXT |
1155 |
8-30-96 |
1:45 PM |
CLSL_GetStackECB() Returns Resources Error
|
Author: |
MG |
|
Document ID: |
TID100786 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:21 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID3.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
CLSL_GetStackECB() does not return a pointer of LOOKAHEAD structure and returns ODISTAT_OUT_OF_RESOURCES.
File Information
Self-Extracting File Name: MGTID3.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID3.TXT |
(this file) |
||
|
MGTIDC.TXT |
969 |
8-30-96 |
1:53 PM |
EPS Code Problems in NEST Client SDK Rel.1.2
|
Author: |
MG |
|
Document ID: |
TID100785 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:21 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID4.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
EPS (Embedded Print Server) code in NEST Client SDK release 1.2 does not work correctly. Update attached.
File Information
Self-Extracting File Name: MGTID4.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID4.TXT |
(this file) |
||
|
MGTIDD.TXT |
1060 |
8-30-96 |
2:09 PM |
|
NESTUPDT.ZIP |
160588 |
7-23-96 |
11:52 AM |
Developing HSM for pSOS and Motorola 68360
|
Author: |
MG |
|
Document ID: |
TID100777 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:18 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTIDL.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
OEM questions that came up during development of an HSM for the MLID to run on the Motorola 68360 processor, on pSOS op sys.
File Information
Self-Extracting File Name: MGTIDL.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTIDL.TXT |
(this file) |
||
|
TID15.TXT |
907 |
8-30-96 |
3:49 PM |
Novell Protocol Test Tool Installation
|
Author: |
MG |
|
Document ID: |
TID100778 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:19 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTIDK.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
OEM couldnt find Novell Protocol Test Tool. It had not been installed with the rest of the NEST SDK.
File Information
Self-Extracting File Name: MGTIDK.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTIDK.TXT |
(this file) |
||
|
TID14.TXT |
438 |
8-30-96 |
3:47 PM |
Hsmvxnat.c Misleading Comment in Code
|
Author: |
MG |
|
Document ID: |
TID100783 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:20 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID6.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
In \nest\stkodi\mlid\hsm\hsmvxnat.c, lines 14-30, a comment describing problems that have since been fixed in the code (before the release of NEST Client SDK release 1.2) leads OEMs to believe that there are problems that remain in the code. It really does work.
File Information
Self-Extracting File Name: MGTID6.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID6.TXT |
(this file) |
||
|
MGTIDF.TXT |
1615 |
8-30-96 |
2:32 PM |
NWDSAuditGetObjectID Output Parameters Wrong
|
Author: |
MG |
|
Document ID: |
TID100775 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:17 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
NDS tree with two 4.10 file servers both running NDS mode. NEST pserver can attach and work properly with one server, but cannot attach to queue on second file server.
Detailed Description
Print server code connects fine to first NDS file server, but cannot attach to queue server on second NDS file server due to incorrect queue ID and connHandle returned from NWDSAuditGetObjectID.
File Information
Self-Extracting File Name: MGTID1.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID1.TXT |
(this file) |
||
|
MGTIDA.TXT |
914 |
8-30-96 |
1:39 PM |
Braces Missing from Macros in Odimacro.h
|
Author: |
MG |
|
Document ID: |
TID100784 |
|
Document revision: |
A |
|
Date: |
09/3/96 8:20 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTID5.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
Braces are missing from some macros in odimacro.h and other NEST include files, causing incorrect function if STRICT_ALIGNMENT is set to OFF.
Detailed Description
Because there are braces missing in some macro definitions in odimacro.h and other NEST include files, the macro definitions work properly only if STRICT_ALIGNMENT is set to off.
File Information
Self-Extracting File Name: MGTID5.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTID5.TXT |
(this file) |
||
|
MGTIDE.TXT |
1001 |
8-30-96 |
2:28 PM |
NEST 1.2 Packet Signing Fixes - Big Endian
|
Author: |
MG |
|
Document ID: |
TID100834 |
|
Document revision: |
A |
|
Date: |
09/6/96 5:18 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTIDO.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
READ ME file for fixes to NEST 1.2 for packet signing on big endian machines.
Detailed Description
Fixes to NEST 1.2 code for packet signing on big endian machines.
File Information
Self-Extracting File Name: MGTIDO.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTIDO.TXT |
(this file) |
||
|
REQ.LOG |
3270 |
9-6-96 |
2:31 PM |
|
SIGNFIX.ZIP |
23469 |
9-5-96 |
10:06 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.