Developer Pointers
Articles and Tips: article
01 Jan 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)
Client SDK/Win31
16-bit DLLs from New NetWare Client
|
Author: |
WS |
|
Document ID: |
TID100635 |
|
Document revision: |
A |
|
Date: |
07/16/96 2:59 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DLL16.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
The Delphi 1.0 units contained in the NetWare SDK require access to the 16-bit DLLs. These are contained in the new NetWare Client 32, but they are not required to install the complete client. To compile/run the 16-bit Delphi applications, it is sufficient to copy the 16-bit DLLs into the Windows system directory. This file is a subset of the NetWare Client 32, containing just the new 16-bit DLLs. They may be used on 16-bit or 32-bit Windows platforms.
File Information
Self-Extracting File Name: DLL16.EXE
|
Files Included: |
Size |
Date |
Time |
|
DLL16.TXT |
(this file) |
||
|
AUDWIN16.DLL |
13299 |
1-10-96 |
7:46 PM |
|
CALWIN16.DLL |
101317 |
1-11-96 |
10:58 AM |
|
CLNWIN16.DLL |
63343 |
1-10-96 |
12:23 PM |
|
CLXWIN16.DLL |
6995 |
1-10-96 |
7:34 PM |
|
LOCWIN16.DLL |
58435 |
1-10-96 |
11:21 AM |
|
NCPWIN16.DLL |
138067 |
1-11-96 |
10:34 AM |
|
NETWIN16.DLL |
175221 |
1-10-96 |
7:11 PM |
|
PRTWIN16.DLL |
279260 |
1-26-96 |
12:10 AM |
|
README.TXT |
22404 |
1-31-96 |
11:43 AM |
NWStartQueueCapture Will GPF
|
Document ID: |
TID100540 |
|
Document revision: |
A |
|
Date: |
06/19/96 09:00 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NWCAPGPF.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
NWStartQueueCapture will GPF in Windows code if a NULL is passed into the queueName field. This is a bug in the NetWare.DRV and the API call itself. This bug will be fixed with the release of Green River.
File Information
Self-Extracting File Name: NWCAPGPF.EXE
|
Files Included: |
Size |
Date |
Time |
|
NWCAP |
300 |
06-19-96 |
09:00 AM |
|
NWCAPGPF.TXT |
(this file) |
Win95 Client Bug with Int 5C (Lock Record)
|
Author: |
WS |
|
Document ID: |
TID100943 |
|
Document revision: |
A |
|
Date: |
10/9/96 9:05 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
5CWIN95.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
The client for Win95 (Jan/Feb 96) does not handle DOS interrupt 0x5C (physical record lock) correctly. The function returns 'success,' pretending a lock was applied, but the lock request is not sent to the server, and the physical record never locked.
The problem was fixed with the new client that comes with IntranetWare (July/August 96).
File Information
Self-Extracting File Name: 5CWIN95.EXE
|
Files Included: |
Size |
Date |
Time |
|
5CWIN95.TXT |
(this file) |
NWSetDriveBase GPFs Windows with NETX
|
Author: |
RM |
|
Document ID: |
TID100657 |
|
Document revision: |
A |
|
Date: |
07/29/96 8:48 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
R001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
NWSetDriveBase will cause a GPF in CLNWIN16.DLL if NETX is being used as the shell on the workstation. The resolution to this problem is to upgrade to VLMs.
File Information
Self-Extracting File Name: R001.EXE
|
Files Included: |
Size |
Date |
Time |
|
R001.TXT |
(this file) |
||
NWD2
|
Document ID: |
TID100496 |
|
Document revision: |
A |
|
Date: |
05/01/96 11:25 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NWD21.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
Novell Windows Diagnostic 2.1 lists loaded programs and DLLs on Windows 3.1, WFWG, Windows 95, and Windows NT (only 16-bit DLLs on NT). It shows Novell version information, where module loaded from, and so on.
File Information
Self-Extracting File Name: NWD21.EXE
|
Files Included: |
Size |
Date |
Time |
|
NWD2.EXE |
463360 |
01-23-96 |
01:07 PM |
|
NWD95.DLL |
14848 |
01-22-96 |
04:20 PM |
|
NWDDLL.DLL |
32799 |
01-23-96 |
07:34 AM |
|
NWDNIOS.DLL |
25904 |
01-22-96 |
04:57 PM |
|
NWNWD.HLP |
16963 |
01-24-96 |
09:50 AM |
|
NWD21.TXT |
(this file) |
NWALaunchDSFlatBrowser Context Parameter
|
Author: |
JB |
|
Document ID: |
TID100700 |
|
Document revision: |
A |
|
Date: |
08/2/96 1:59 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSBROW.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
NWALaunchDSFlatBrowser fails to return the directory context as stated in the documentation.
Detailed Description
The documentation states that NWALaunchDSFlatBrowser returns the directory context set by the user using the dialog box. Unfortunately, due to a coding error, the parameter remains unchanged.
This has been fixed in the Green River release.
File Information
Self-Extracting File Name: DSBROW.EXE
|
Files Included: |
Size |
Date |
Time |
|
DSBROW.TXT |
(this file) |
NTSWD 1.04
|
Document ID: |
TID100495 |
|
Document revision: |
A |
|
Date: |
05/01/96 11:16 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NTSWD104.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
Novell Technical Support Windows Diagnostic 1.04 lists DLLs, programs, and VxDs that are loaded on the machine. It also shows Novell versions, where the module is loaded from, date and time, and so on.
NWD 2.0 has replaced this file, but NWD 2.0 does not show VxD information. This file is intended for use on Windows 3.1 and Windows for Workgroups.
File Information
Self-Extracting File Name: NTSWD104.EXE
|
Files Included: |
Size |
Date |
Time |
|
NTSWD.EXE |
109056 |
10-06-94 |
01:32 PM |
|
NTSWD104.TXT |
(this file) |
Server
AIO Hardware Driver Types
|
Document ID: |
TID100377 |
|
Document revision: |
A |
|
Date: |
01/19/96 10:06 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DAIO1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
Contains AIODTYPE.TXT which is a listing of all the public AIO hardware device driver types (numbers). Although these numbers are issued by Novell Labs to developers of AIO device drivers, not all the drivers listed have been certified by Novell Labs.
File Information
Self-Extracting File Name: DAIO1.EXE
|
Files Included: |
Size |
Date |
Time |
|
AIODTYPE.TXT |
5133 |
07-24-95 |
01:34 PM |
|
DAIO1.TXT |
(this file) |
Bindery Emulation Security Access
|
Document ID: |
TID100250 |
|
Document revision: |
C |
|
Date: |
01/08/96 02:30 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
BNDEMU.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
NLMs have long had connection 0 or supervisory access to the bindery. In NetWare 4.x with bindery emulation, if the bindery context is set to a directory context, an NLM may change the password of any NDS object in that context.
File Information
Self-Extracting File Name: BNDEMU.EXE
|
Files Included: |
Size |
Date |
Time |
|
BNDEMUL.TXT |
294 |
01-08-96 |
02:35 PM |
|
BNDEMU.TXT |
(this file) |
Btrieve and TCP/IP
|
Author: |
WS |
|
Document ID: |
TID101020 |
|
Document revision: |
A |
|
Date: |
11/13/96 9:21 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
BTRIP.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
Q. Can I use Btrieve clients on a NetWare server that uses IP, not IPX as the transport protocol?
A. Pervasive Software (formerly BTI) does not currently have TCP/IP requesters for Btrieve for NetWare. TCP/IP support will be available shortly. TCP/IP requesters are in beta right now. They are going to be available for only NT servers, not NetWare servers.
TCP/IP requesters are available for the 16-bit and 32-bit Windows requesters. No DOS TCP/IP support will be available.
File Information
Self-Extracting File Name: BTRIP.EXE
|
Files Included: |
Size |
Date |
Time |
|
BTRIP.TXT |
(this file) |
CLIB with Debug Symbols v4.10
|
Document ID: |
TID100382 |
|
Document revision: |
A |
|
Date: |
01/19/96 08:54 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
CLDB41.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
Contains CLIBDEB.NLM v4.10. Designed to provide application developers with debug symbols to aid in the product development/debug cycle. CLIBDEB.NLM may be slower and/or larger than the standard CLIB.NLM. CLIBDEB.NLM's intended use is as a debugging tool. It is not to be used in place of CLIB.NLM in a production environment.
File Information
Self-Extracting File Name: CLDB41.EXE
|
Files Included: |
Size |
Date |
Time |
|
CLIBDEB.NLM |
238323 |
11-02-94 |
04:15 PM |
|
CLDB41.TXT |
(this file) |
CLIB with Debug Symbols v4.01E
|
Document ID: |
TID100379 |
|
Document revision: |
A |
|
Date: |
01/19/96 09:57 AM |
|
Alert status: |
Yellow |
|
Information: |
Issue |
|
Readme for: |
CLDB4E.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
Contains CLIBDEB.NLM v4.01E. Useful to NLM application developers for the development/debug cycle. CLIBDEB.NLM may be slower and/or larger than the standard CLIB.NLM and should not be used in place of CLIB.NLM in a production environment.
File Information
Self-Extracting File Name: CLDB4E.EXE
|
Files Included: |
Size |
Date |
Time |
|
CLIBDEB.NLM |
229900 |
05-25-94 |
10:53 AM |
|
CLDB4E.TXT |
(this file) |
CLIB with Debug Symbols v3.12h
|
Document ID: |
TID100372 |
|
Document revision: |
A |
|
Date: |
01/18/96 02:36 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
CLDB3H.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
Contains CLIBDEB.NLM for NetWare 3.11, NetWare SFT 3.11, and NetWare 3.12. CLIBDEB.NLM provides application developers with debug symbols to aid in the product development/debug cycle. CLIBDEB.NLM may be slower and/or larger than the standard CLIB.NLM. CLIBDEB.NLM's intended use is as a debugging tool. It is not to be used in place of CLIB.NLM in a production environment.
File Information
Self-Extracting File Name: CLDB3H.EXE
|
Files Included: |
Size |
Date |
Time |
|
CLIBDEB.NLM |
379539 |
10-27-94 |
12:47 PM |
|
CLDB3H.TXT |
(this file) |
Retrieving Interface Information on TCP/IP
|
Author: |
EE |
|
Document ID: |
TID101059 |
|
Document revision: |
A |
|
Date: |
12/3/96 1:33 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DBSDE001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
NetWare API to retrieve interface information on TCP/IP - int IPExtendedIFInfo ( struct p_extended_if_info *info_pt ). For example, given an IP address, you can get the subnet mask and board number associated with the IP address; or given the board number, you can get IP address and subnet mask associated with the board number.
Detailed Description
For an example of using NetWare API to retrieve interface information on TCP/IP, see Figure 1.
Figure 1
int IPExtendedIFInfo( struct ip_extended_if_info *info_pt )
/* Miscellaneous constants */
#define IEX_SIGNATURE 'IEXI'
#define IEX_MAJOR_VERSION 1
#define IEX_MINOR_VERSION 0
#define IEX_VERSION ((IEX_MAJOR_VERSION << 16) | IEX_MINOR_VERSION)
#define IEX_BUFFER_SIZE sizeof( ip_extended_if_info )
#define IEX_FIRST_INTERFACE 0
/*
** Extended IP interface information block -
** Structure returned by the IPExtendedIFInfo API.
*/
typedef struct ip_extended_if_info {
unsigned long iex_signature; /* API signature */
unsigned long iex_version; /* API version */
unsigned long iex_length; /* buffer size */
unsigned long iex_flags; /* flags */
unsigned long iex_if_id; /* interface id */
unsigned long iex_timestamp; /* creation time */
ip_addr iex_local_addr; /* interface's IP address */
ip_addr iex_net_mask; /* network mask */
ip_addr iex_broadcast; /* broadcast address */
unsigned long iex_packet_mx; /* maximum outgoing packet */
unsigned long iex_packet_opt; /* optimum outgoing packet */
unsigned long iex_reasm_mx; /* maximum reassembled packet */
int iex_net_type; /* network type */
unsigned long iex_board_num; /* ODI board number */
unsigned char iex_our_snpa[ SNPA_MX ]; /* SNPA for interface */
} ip_extended_if_info;
/*
Name: IPExtendedIFInfo - return info about the next network interface
Sample Call:
info.iex_signature = IEX_SIGNATURE;
info.iex_version = IEX_VERSION;
info.iex_length = IEX_BUFFER_SIZE;
info.iex_if_id = IEX_FIRST_INTERFACE;
while (IPExtendedIFInfo( &info ) == UDP_OK) &
{ ... }
Description:
Return information about the next network interface.
The caller must provide an information buffer at least
as large as IEX_BUFFER_SIZE.
Return:
UDP_OK Success
UDPE_NORESOURCES Null pointer or insufficient buffer space
USPE_BADVERSION Illegal signature or version
UDPE_NOLOCAL No match found
*/
File Information
Self-Extracting File Name: DBSDE001.EXE
|
Files Included: |
Size |
Date |
Time |
|
DBSDE001.TXT |
(this file) |
ManageWise SDK
Additional Documentation for SNMP Functions
|
Author: |
SP |
|
Document ID: |
TID100905 |
|
Document revision: |
A |
|
Date: |
09/30/96 2:12 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MWAPIS.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
ManageWise SDK |
Abstract
SAIRegisterMIBInst routine and SAIDeregisterMIBInst are not documented in the API doc, nor in the Agent header file. This TID contains the documentation for these two functions.
Detailed Description
SAIRegisterMIBInst Routine The SAIRegisterMIBInst routine allows an NLM to register a unique instance of a particular MIB.
Syntax int SAIRegisterMIBInst (ObjInfo **mib_pp, AttrValue *inst_list, unsigned long rtag)
Parameters
|
mib_pp |
Pointer to the array of objects being registered. |
|
inst_list |
NULL-terminated linked list of AttrValue structures describing theinstance information to be associated with each object in the MIB to beregistered. |
|
rtag |
Resource tag against which this MIB will be charged. NLMsinstrumented to the NetWare SNMP Agent should use the constantSAI_MIB_RTAG (defined in the header file agent.h) when allocating aresource tag. |
Return Values
|
SAI_REGISTER_OK |
Successful. |
|
|
SAI_REGISTER_FAIL_DUP |
There's already an NLM that has registered this MIBwith the instance information described by inst_list. |
|
|
SAI_REGISTER_BAD_RTAG |
The resource passed in was not allocated usingSAI_MIB_RTAG. |
|
|
SAI_REGISTER_FAIL_GEN |
Couldn't get resources necessary to register this instanceof the MIB. |
Usage When an NLM is ready to support a specific instance of a MIB, it calls SAIRegisterMIBInst to register that specific MIB instance. A given MIB may be registered multiple times with the NetWare SNMP Agent using SAIRegisterMIBInst, but the instance information described by inst_list must be unique with each registration call.
Implementation Notes The mib_pp parameter is defined in the .c output that results from the MIB compilation.
In the SNMP 3.0 release (included in MPR 3.0), inst_list must be exactly one element long where the avb_length field of that element contains an integer defining the index to be associated with each object in the array pointed to by mib_pp. One example of this integer index would be logical board number.
Each object in the array pointed to by mib_pp should be a multiple-instance object (i.e. a table), where the first item in that object's index is an integer, usually a logical board number or equivalent. The NLM registering the MIB instance is indicating that it supports the row from each table object identified by the integer contained in inst_list.
See Also
|
AttrValue |
Structure containing an actual attribute value |
|
SAIDeregisterMIBInst |
Deregister an instance of a MIB |
SAIDeregisterMIBInst routine The SAIDeregisterMIBInst routine allows an NLM to deregister a specific instance of a particular MIB.
Example See Figure 2.
Figure 2
#include <agent.h< /* SNMP Agent definitions */<
#include <advanced.h< /* AllocateResourceTag */<
#include <process.h< /* GetNLMHandle */<
#include <rfc1317.h< /* Header file resulting from MIB compilation */<
/* --------
* Parameter LSLBoardNumber defines the instance of the RS232 MIB this
* instrumented NLM will support.
* -------- */
int registerMIB( int LSLBoardNumber )
{
unsigned long rtag;
AttrValue inst_list;
memset(&inst_list, 0, sizeof(inst_list));&
inst_list.avb_length = LSLBoardNumber;
inst_list.avb_next = NULL;
/* allocate a resource tag for the MIB we are going to register */
rtag = AllocateResourceTag((unsigned long) GetNLMHandle(),
"RS232 MIB", SAI_MIB_RTAG );
if ( rtag == NULL )
return 1;
/* register the entire MIB */
if (SAIRegisterMIBInst( RFC1317_MIB, &inst_list, rtag )&
== SAI_REGISTER_OK)
{
return(EXAMPLE_OK);
}
else
{
return(MIB_REGISTRATION_FAILED);
}
} /* end of registerMIB */
Syntax
void SAIRegisterMIBInst (ObjInfo **mib_pp, AttrValue *inst_list,)
Parameters
|
mib_pp |
Pointer to the array of objects being deregistered. |
|
inst_list |
NULL-terminated linked list of AttrValue structures describing theinstance information of the specific MIB instance to be deregistered. |
Return Values
None.
Usage
When an NLM no longer supports a specific instance of a MIB (usually when the NLM is exiting the system), the NLM calls SAIDeregisterMIBInst to deregister that specific MIB instance.
Implementation Notes
The mib_pp parameter is defined in the .c output that results from the MIB compilation.
In the SNMP 3.0 release (included in MPR 3.0), inst_list must be exactly one element long where the avb_length field of that element contains an integer identifying the MIB instance to be deregistered. One example of this integer index would be logical board number.
Each object in the array pointed to by mib_pp should be a multiple-instance object (i.e. a table), where the first item in that object's index is an integer, usually a logical board number or equivalent. The NLM deregistering the MIB instance is indicating that it no longer supports the row from each table object identified by the integer contained in inst_list.
See Also
|
AttrValue |
Structure containing an actual attribute value |
|
SAIRegisterMIBInst |
Register an instance of a MIB |
Example
/* --------
* Parameter LSLBoardNumber defines the instance
* of the RS232 MIB this instrumented NLM no
* longer supports.
* -------- */
void deregisterMIB ( int LSLBoardNumber )
{
AttrValue inst_list;
memset(&inst_list, 0, sizeof(inst_list));&
inst_list.avb_length = LSLBoardNumber;
inst_list.avb_next = NULL;
SAIDeregisterMIBInst(RFC1317_MIB,&inst_list);&
}
File Information
Self-Extracting File Name: MWAPIS.EXE
|
Files Included: |
Size |
Date |
Time |
|
MWAPIS.TXT |
(this file) |
WinSNMP and Microsoft Management System
|
Document ID: |
TID100560 |
|
Document revision: |
A |
|
Date: |
06/28/96 05:51 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
WNSNMP.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
NMS SDK |
Abstract
Discussion of WinSNMP and Microsoft Management System issues.
File Information
Self-Extracting File Name: WNSNMP.EXE
|
Files Included: |
Size |
Date |
Time |
|
WINSNMP |
1770 |
06-28-96 |
04:50 PM |
|
WNSNMP.TXT |
(this file) |
LAN Protocols
Public IPX SAP Types Listing
|
Document ID: |
TID100416 |
|
Document revision: |
A |
|
Date: |
01/30/96 10:51 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSAP1A.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
LAN Protocols |
Abstract
Contains a text file document which lists all publicly exposed IPX SAP types.
File Information
Self-Extracting File Name: DSAP1A.EXE
|
Files Included: |
Size |
Date |
Time |
|
SERVER.LST |
146926 |
01-19-96 |
12:20 PM |
|
DSAP1A.TXT |
(this file) |
Public IPX SAP Types Listing
|
Author: |
AJ |
|
Document ID: |
TID101015 |
|
Document revision: |
A |
|
Date: |
11/4/96 5:00 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSAP1B.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
LAN Protocols |
Abstract
Contains a text file document that lists all publicly exposed IPX SAP types.
File Information
Self-Extracting File Name: DSAP1B.EXE
|
Files Included: |
Size |
Date |
Time |
|
DSAP1B.TXT |
(this file) |
||
|
SERVER.LST |
153357 |
11-1-96 |
2:24 PM |
IPX Static (Well-known) Sockets
|
Document ID: |
TID100375 |
|
Document revision: |
A |
|
Date: |
01/19/96 03:27 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSOC1A.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
LAN Protocols |
Abstract
Contains file SOCKET.LST that lists the publicly exposed Well-known IPX static sockets.
File Information
Self-Extracting File Name: DSOC1A.EXE
|
Files Included: |
Size |
Date |
Time |
|
SOCKET.LST |
275825 |
01-19-96 |
12:44 PM |
|
DSOC1A.TXT |
(this file) |
Public IPX Static Socket Listing
|
Author: |
AJ |
|
Document ID: |
TID101013 |
|
Document revision: |
A |
|
Date: |
11/4/96 4:58 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSOC1B.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
LAN Protocols |
Abstract
Contains a text file document that lists all publicly exposed IPX static sockets.
File Information
Self-Extracting File Name: DSOC1B.EXE
|
Files Included: |
Size |
Date |
Time |
|
DSOC1B.TXT |
(this file) |
||
|
SOCKET.LST |
276869 |
11-1-96 |
3:13 PM |
SMS
SMS & Media Manager Newsletter: 950117
|
Document ID: |
TID100365 |
|
Document revision: |
A |
|
Date: |
01/17/96 04:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ISMS000.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
Storage Management Services & Media Manager Newsletter
January 17, 1996
This newsletter will be sent out periodically to let members of the SMS and Media Manager development community know about information that may be of special interest to them.
Current newsletter topics are:
Better Tools
Novell Labs New Testing and Certification Criteria
Technical Information Documents (TIDs)
New SMS Modules Released
File Information
Self-Extracting File Name: ISMS000.EXE
|
Files Included: |
Size |
Date |
Time |
|
README.TXT |
3351 |
01-17-96 |
04:27 PM |
|
ISMS000.TXT |
(this file) |
NetWare Peripheral Architecture (NWPA)
|
Document ID: |
TID100420 |
|
Document revision: |
A |
|
Date: |
02/06/96 12:30 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSMS000.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
Developers of SMS and/or Media Manager applications may need to know more of Novell's Device Driver Interface.
This document describes the technical requirements and procedures for building device drivers under a driver architecture known as the NetWare Peripheral Architecture, or NWPA. This document provides a description of the NWPA and the application programming interface (API) set that it provides.
Support for this specification is through Novell Labs.
File Information
Self-Extracting File Name: DSMS000.EXE
|
Files Included: |
Size |
Date |
Time |
|
ABSTRACT.TXT |
770 |
02-06-96 |
12:29 PM |
|
NWPASPEC.EVY |
882058 |
02-01-96 |
10:52 AM |
|
RDFIRST.EVY |
9977 |
01-30-96 |
08:41 AM |
|
README.1ST |
1547 |
02-06-96 |
11:38 AM |
|
DSMS000.TXT |
(this file) |
Novell Device Driver Functional Specification
|
Document ID: |
TID100421 |
|
Document revision: |
A |
|
Date: |
02/06/96 12:45 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DSMS20.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
Developers of SMS and/or Media Manager applications may need to know more of Novell's Device Driver Interface. Remember, NWPA is PREFERRED.
This document describes the technical requirements and procedures for building device drivers under a driver architecture known as the NetWare Device Driver Functional Specification, or DDFS. This document provides a description of the DDFS and the application programming interface (API) set that it provides.
Support for this specification is through Novell Labs.
File Information
Self-Extracting File Name: DSMS20.EXE
|
Files Included: |
Size |
Date |
Time |
|
ABSTRACT.TXT |
774 |
02-06-96 |
12:40 PM |
|
DDFS.EVY |
586465 |
05-23-95 |
03:52 PM |
|
README.1ST |
1539 |
02-06-96 |
11:38 AM |
|
DSMS20.TXT |
(this file) |
SMS Error or Condition Codes
|
Document ID: |
TID100503 |
|
Document revision: |
A |
|
Date: |
05/06/96 10:51 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ISMS10.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
This Envoy file contains descriptions of Condition or Error codes returned by various SMS modules. If an error is encountered, a developer should first check this file before contacting Novell Developer Support.
File Information
Self-Extracting File Name: ISMS10.EXE
|
Files Included: |
Size |
Date |
Time |
|
CCODES.EVY |
22829 |
5-06-96 |
10:38 AM |
|
ISMS10.TXT |
(this file) |
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.