Developer Pointers
Articles and Tips: article
01 Apr 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)
How To Get NetWare User Names from RAD Tools
|
Author: |
HW |
|
Document ID: |
TID101091 |
|
Document revision: |
A |
|
Date: |
01/15/97 5:53 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
USERNAME.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
This sample shows how to obtain the name and identification of the currently logged in NetWare user from a RAD tool. The DLL is written in Visual Basic 4, but because it is an OLE server, you could also use it from Delphi just by referencing it.
This TID includes the DLL with source code and a demo project showing how to use it.
File Information
Self-Extracting File Name: USERNAME.EXE
|
Files Included: |
Size |
Date |
Time |
|
USERNAME.TXT |
(this file) |
||
|
MODMAIN.BAS |
5514 |
12-9-96 |
6:26 PM |
|
MODTESTM.BAS |
194 |
12-9-96 |
6:16 PM |
|
NAME.CLS |
7982 |
12-9-96 |
6:22 PM |
|
README.TXT |
445 |
11-20-96 |
6:04 PM |
|
TESTER.VBP |
933 |
12-9-96 |
6:27 PM |
|
USERNAME.DLL |
12800 |
11-20-96 |
5:55 PM |
|
USERNAME.VBP |
1051 |
12-9-96 |
6:26 PM |
NWDSVerifyObjectPassword
|
Author: |
SW |
|
Document ID: |
TID101104 |
|
Document revision: |
A |
|
Date: |
02/5/97 4:30 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
WVERPASS.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
This demonstrates NWDSVerifyObjectPassword in Delphi 32.
File Information
Self-Extracting File Name: WVERPASS.EXE
|
Files Included: |
Size |
Date |
Time |
|
WVERPASS.TXT |
(this file) |
||
|
MAIN.DFM |
635 |
2-3-97 |
11:04 AM |
|
MAIN.PAS |
4753 |
2-3-97 |
11:11 AM |
|
VERIFY~1.DOF |
491 |
1-31-97 |
2:17 PM |
|
VERIFY~1.DPR |
188 |
1-31-97 |
2:14 PM |
|
VERIFY~1.EXE |
186368 |
2-3-97 |
11:11 AM |
|
VERIFY~1.RES |
876 |
1-31-97 |
2:17 PM |
Address Book OCX (Delphi APP)
|
Author: |
RL |
|
Document ID: |
TID101094 |
|
Document revision: |
A |
|
Date: |
01/22/97 2:51 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
GW5XOB29.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
GroupWare |
Abstract
This sample shows how to use the Address Book OCX to place names in a drop down list box.
File Information
Self-Extracting File Name: GW5XOB29.EXE
|
Files Included: |
Size |
Date |
Time |
|
GW5XOB29.TXT |
(this file) |
||
|
ADDROCX.ZIP |
101128 |
1-16-97 |
6:14 PM |
Pre-Release Libraries
|
Author: |
AJ |
|
Document ID: |
TID101113 |
|
Document revision: |
A |
|
Date: |
02/13/97 1:26 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
PLIB4X04.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This TID lists the 13-FEB-97 pre-release builds of NLM libraries for NetWare 4.x. These files are not fully tested and should not be used in production environments. Rather, they are intended to be used by NLM developers to test applications for compatibility.
Detailed Description
This TID lists the 13-FEB-97 Pre-release builds of NLM libraries for NetWare 4.x. These files are not fully tested and should not be used in production environments. Rather, they are intended to be used by NLM developers to test applications for compatibility.
Current system time: Thursday 2-13-97 1:15:32 PM
|
Updates since PLIB4X03: |
|
|
*** AIO Updates *** |
|
|
ATM\TEST: AIO.NLM |
|
|
ATM\TEST: AIOCOMX.NLM |
|
|
ATM\TEST: AIOACI.NLM |
|
|
ATM\TEST: AIODGCX.NLM |
|
|
ATM\TEST: AIODGMEM.NLM |
|
|
ATM\TEST: AIODGXI.NLM |
|
|
ATM\TEST: AIOWNIM.NLM |
|
|
*** Modular CLIB Updates *** |
|
|
ATM\TEST: CLIB.NLM |
|
|
ATM\TEST: FPSM.NLM |
|
|
ATM\TEST: MATHLIB.NLM |
|
|
ATM\TEST: MATHLIBC.NLM |
|
|
ATM\TEST: NIT.NLM |
|
|
ATM\TEST: NLMLIB.NLM |
|
|
ATM\TEST: REQUESTR.NLM |
|
|
ATM\TEST: THREADS.NLM |
|
|
*** Cross Platform (XPLAT) Updates *** |
|
|
ATM\TEST: DSEVENT.NLM |
|
|
*** NWSNUT Updates *** |
|
|
ATM\TEST: AFTER311.NLM |
|
|
ATM\TEST: A3112.NLM |
|
|
*** Transport Updates *** |
|
|
ATM\TEST: SPXS.NLM |
|
|
ATM\TEST: TCPIP.NLM |
|
|
ATM\TEST: ADSP.NLM |
|
|
ATM\TEST: APPLETLK.NLM |
|
|
*** Novell Licensing Updates *** |
|
|
ATM\TEST: LSAPI.NLM |
|
|
ATM\TEST: NLSAPI.NLM |
|
|
*** Printing Services Updates *** |
File Information
Self-Extracting File Name: PLIB4X04.EXE
|
Files Included: |
Size |
Date |
Time |
|
PLIB4X04.TXT |
(this file) |
||
|
A3112.NLM |
15906 |
2-11-97 |
10:55 AM |
|
ADSP.NLM |
76207 |
2-12-97 |
10:25 AM |
|
AFTER311.NLM |
16127 |
2-11-97 |
10:54 AM |
|
AIO.NLM |
134169 |
2-6-97 |
12:52 PM |
|
AIOACI.NLM |
22020 |
6-8-94 |
3:14 PM |
|
AIOCOMX.NLM |
17500 |
11-28-94 |
1:11 PM |
|
AIODGCX.NLM |
99104 |
11-18-96 |
11:33 AM |
|
AIODGMEM.NLM |
1705 |
1-10-96 |
9:36 AM |
|
AIODGXI.NLM |
38707 |
11-18-96 |
12:29 PM |
|
AIOWNIM.NLM |
16136 |
5-30-95 |
11:18 AM |
|
APPLETLK.NLM |
376741 |
2-12-97 |
10:25 AM |
|
AUDNLM32.NLM |
9202 |
1-8-97 |
11:00 AM |
|
CALNLM32.NLM |
89326 |
1-8-97 |
10:43 AM |
|
CLIB.NLM |
82693 |
2-3-97 |
5:43 PM |
|
CLNNLM32.NLM |
5378 |
1-8-97 |
9:49 AM |
|
CLXNLM32.NLM |
5564 |
1-8-97 |
10:58 AM |
|
REQUESTR.NLM |
47241 |
2-3-97 |
5:56 PM |
|
SPXS.NLM |
42293 |
2-5-97 |
6:42 PM |
|
STREAMS.NLM |
63751 |
7-10-96 |
4:54 PM |
|
TCPIP.NLM |
484488 |
2-10-97 |
5:57 PM |
|
THREADS.NLM |
90029 |
2-3-97 |
5:05 PM |
|
TLI.NLM |
24751 |
1-30-95 |
9:33 AM |
|
DSAPI.NLM |
628 |
1-8-97 |
10:56 AM |
|
DSEVENT.NLM |
2116 |
2-4-97 |
8:00 AM |
|
FPSM.NLM |
16546 |
2-3-97 |
6:20 PM |
|
IPXS.NLM |
10134 |
10-20-94 |
1:53 PM |
|
LOCNLM32.NLM |
4436 |
1-8-97 |
9:46 AM |
|
LSAPI.NLM |
18364 |
1-30-97 |
11:10 AM |
|
MATHLIB.NLM |
417 |
2-4-97 |
7:48 AM |
|
MATHLIBC.NLM |
426 |
2-4-97 |
7:48 AM |
|
NCPNLM32.NLM |
104031 |
1-8-97 |
10:16 AM |
|
NETNLM32.NLM |
157108 |
1-8-97 |
10:55 AM |
|
NIT.NLM |
47860 |
2-3-97 |
6:16 PM |
|
NLMDEBUG.NLM |
29132 |
11-25-96 |
3:44 PM |
|
NLMLIB.NLM |
90960 |
2-4-97 |
7:48 AM |
|
NLSAPI.NLM |
19810 |
1-30-97 |
11:19 AM |
|
NWPSRV.NLM |
92654 |
1-9-97 |
4:15 PM |
|
NWSNUT.NLM |
58327 |
7-1-96 |
3:45 PM |
GroupWise 4.1 Simple Mapi Documentation
|
Author: |
RL |
|
Document ID: |
TID101101 |
|
Document revision: |
A |
|
Date: |
02/5/97 4:27 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
GW4XD40.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
GroupWare |
Abstract
This documentation was left out of the Vol. 10 SDK. The documentation is an Envoy (EVY) file. You will need to install the Envoy viewer from the SDK to view this document.
File Information
Self-Extracting File Name: GW4XD40.EXE
|
Files Included: |
Size |
Date |
Time |
|
GW4XD40.TXT |
(this file) |
||
|
GW41REF.EVY |
465734 |
11-14-96 |
9:57 AM |
Scan the Bindery for an Object in a Set
|
Author: |
RM |
|
Document ID: |
TID101089 |
|
Document revision: |
A |
|
Date: |
01/15/97 5:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
RISOBJ.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - DOS |
Abstract
Allows the user to scan the bindery for an object in a set.
The following APIs are used:
|
NWCCOpenConnByName |
|
|
NWIsObjectInSet |
File Information
Self-Extracting File Name: RISOBJ.EXE
|
Files Included: |
Size |
Date |
Time |
|
RISOBJ.TXT |
(this file) |
||
|
ISOBJIN.CPP |
6943 |
12-21-96 |
12:23 PM |
|
ISOBJIN.EXE |
122147 |
12-21-96 |
12:29 PM |
Copying Compressed Files
|
Author: |
JB |
|
Document ID: |
TID101103 |
|
Document revision: |
A |
|
Date: |
02/5/97 4:30 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
JFB97001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
This sample code demonstrates how to open and create compressed files and read data in compressed format.
Detailed Description
This sample code demonstrates how to open and create compressed files and read data in compressed format, allowing you to copy compressed files between file servers in compressed format.
The Name Space API is used to access files in compressed format. The function NWGetNSEntryInfo is used to obtain the source file attributes to determine whether the source file is compressed. The source file and destination are opened using NWOpenCreateNSEntry. The files must be opened in exclusive mode when attempting to open a compressed file in compressed mode. When using WIN32, the NetWare file handle returned from NWOpenCreateNSEntry has to be converted to a file handle by using the function _open_osfhandle(). The destination uncompressed file size is set by using chsize, the compressed file size is set by using NWSetCompressedFileSize.
The following functions are used:
|
NWCallsInit |
|
|
NWGetNSEntryInfo |
|
|
NWOpenCreateNSEntry |
|
|
NWParsePath |
|
|
NWSetCompressFileSize |
File Information
Self-Extracting File Name: JFB97001.EXE
|
Files Included: |
Size |
Date |
Time |
|
JFB97001.TXT |
(this file) |
||
|
COPYCOM.CPP |
6701 |
2-4-97 |
12:13 PM |
NetBasic - Console NDS Query Console Sample
|
Author: |
BA |
|
Document ID: |
TID101109 |
|
Document revision: |
A |
|
Date: |
02/11/97 4:20 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XNTBNDS2.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
This sample code is designed to run on IntranetWare or NetWare 4.11. It demonstrates how to use the WIN API set which creates a NUT looking interface on the console. It also demonstrates how to query NDS.
Detailed Description
This sample script demonstrates how to use the WIN API set which creates a NUT looking interface on the console. It also demonstrates how to query NDS.
|
Installation |
|
|
Place the script in SYS:NetBasic/User |
|
|
Execution |
|
|
From the Console do the following: |
|
|
LOAD NETBASIC |
|
|
SHELL |
|
|
LISTDS |
File Information
Self-Extracting File Name: XNTBNDS2.EXE
|
Files Included: |
Size |
Date |
Time |
|
XNTBNDS2.TXT |
(this file) |
||
|
LISTDS.BAS |
13017 |
2-3-97 |
11:31 AM |
TLI (SPX) under WinOS2
|
Author: |
JB |
|
Document ID: |
TID101090 |
|
Document revision: |
A |
|
Date: |
01/15/97 5:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
TLIWOS2.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - OS/2 |
Abstract
TBMI2 must be properly configured for TLI to work under OS/2.
Detailed Description
Under WinOS2, TBMI2 must be loaded and configured for at least 80 data ECBs in order to have TLI (t_open) initialize properly for use of SPX as protocol. This is being done by adding (or changing) a TBMI section to NET.CFG, within which an entry DATA ECB COUNT <value< must be present. Not doing so causes t_open to report error 8.
File Information
Self-Extracting File Name: TLIWOS2.EXE
|
Files Included: |
Size |
Date |
Time |
|
TLIWOS2.TXT |
(this file) |
SIDF Association's Web Page
|
Author: |
LC |
|
Document ID: |
TID101096 |
|
Document revision: |
A |
|
Date: |
01/30/97 9:05 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ISMS70.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
The System Independent Data Format Association has a Web site at http://www.sidf.org/. Please visit it.
The site has information about the current standings of the SIDF, ECMA-208, and ISO/IEC 14863 standards.
The ECMA-208 standard is also available as an HTML document. There are also links to a Microsoft Word document containing the standard as well as a PostScript version.
File Information
Self-Extracting File Name: ISMS70.EXE
|
Files Included: |
Size |
Date |
Time |
|
ISMS70.TXT |
(this file) |
Printcon Database Structure Documents
|
Author: |
KB |
|
Document ID: |
TID101114 |
|
Document revision: |
A |
|
Date: |
02/13/97 1:27 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IPRTKB1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
This Technical Information Document contains two documents, in WordPerfect format. The first describes the PrintDef database (PRINTDEF.DAT). The second, the Printcon database (PRINTCON.DAT).
Note: These databases are used by NetWare legacy printing and havebeen redesigned inNovell Distributed Print Services (NDPS).
File Information
Self-Extracting File Name: IPRTKB1.EXE
|
Files Included: |
Size |
Date |
Time |
|
IPRTKB1.TXT |
(this file) |
||
|
PCON40 |
32885 |
2-6-97 |
5:23 PM |
|
PDEF40 |
102467 |
4-12-93 |
8:58 AM |
Release of Latest SMS Modules
|
Author: |
LC |
|
Document ID: |
TID101097 |
|
Document revision: |
A |
|
Date: |
01/30/97 9:06 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
ISMS80.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
SMS |
Abstract
The latest SMS modules have passed CIT testing and are now released for end-users. They can be found in SMSUP6.EXE in NetWare OS Files (NWOSFILES) directory on CompuServe, ftp to
ftp://ftp.novell.com/pub/updates/nwos/nw411/ or
http://netwire.novell.com/ to download SMSUP6.EXE.
File Information
Self-Extracting File Name: ISMS80.EXE
|
Files Included: |
Size |
Date |
Time |
|
ISMS80.TXT |
(this file) |
NWAddTrustee in Delphi
|
Author: |
SW |
|
Document ID: |
TID101102 |
|
Document revision: |
A |
|
Date: |
02/5/97 4:28 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
WADDTRUS.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
General Business |
Abstract
Demonstrates the use of NWADDTrustee.
File Information
Self-Extracting File Name: WADDTRUS.EXE
|
Files Included: |
Size |
Date |
Time |
|
WADDTRUS.TXT |
(this file) |
||
|
ADDTRUST.DOF |
491 |
2-5-97 |
10:48 AM |
|
ADDTRUST.DPR |
186 |
2-5-97 |
10:15 AM |
|
ADDTRUST.EXE |
187904 |
2-5-97 |
4:10 PM |
|
ADDTRUST.RES |
876 |
2-5-97 |
10:48 AM |
|
MAIN.DFM |
957 |
2-5-97 |
3:46 PM |
|
MAIN.PAS |
6082 |
2-5-97 |
4:09 PM |
TOOL - RDEBUG (NetWare OS Environment)
|
Author: |
AJ |
|
Document ID: |
TID101111 |
|
Document revision: |
A |
|
Date: |
02/13/97 1:22 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XRDB1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product andversion: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This concerns pre-release of Novell's RDEBUG, a source level debugging tool for the NetWare (NLM) environment.
Detailed Description
This document describes the files included with the remote source level debugger, as well as changes for this version.
The following files are distributed with this product:
|
CLIENT32 |
||
|
RDEBUGLG.BMP |
||
|
HSEARCHR.DLL |
||
|
RDEBUG.HLP |
||
|
RDEBUG.EXE |
||
|
SERVER |
||
|
RDEBUG.NLM |
||
|
SAMPLES |
||
|
TEST3.C |
||
|
TEST.C |
||
|
TEST.SYM |
||
|
TEST.NLM |
||
|
MAKEFILE.MAK |
New Features in This Version
The debugger now supports command line parameters for NLMs loaded from the client workstation with the "load" command.
A new menu option has been added to the Configure menu, which enables the user to tell the debugger to stop on all NLM loads, or only on the NLM which is specifically loaded with the "load" command. If you ask the debugger to stop on all NLM loads, control will be returned to the RDEBUG client each time an NLM loads. If you do not check this option, control will be returned only when an NLM that has been specifically loaded (as in "load myNLM") loads.
A new invocation option "-unicode" has been added to allow processing of unicode strings.
The "threads" command has changed, now displaying all threads in the system.
The "queues" command has been replaced with the "waitingthreads" command.
A new "runqueue" command has been added
General Description
The debugger is a remote debugger. To run the debugger, an NLM called RDEBUG.NLM is required on the NetWare server and three client pieces--RDEBUG.EXE, RDEBUG.HLP, and HSEARCHR.DLL--are required on a Windows, Windows 95, or Windows NT machine.
Installing the Debugger
Copy the files in the CLIENT32 directory to a directory of your choice on the Windows client machine. Copy RDEBUG.HLP and RDEBUGLG.BMP to the same directory where you copied RDEBUG.EXE. Copy HSEARCHR.DLL to your WINDOWS\SYSTEM directory.
On Green River servers, copy RDEBUG.NLM to the SYS:SYSTEM directory of the server. (On releases after Green River, RDEBUG.NLM will not be needed on the server.)
Configure RDEBUG.EXE on the workstation as described in either the serial or Ethernet section below.
Configure RDEBUG.NLM on the server as explained in either the serial or Ethernet section below.
Run the debugger by following these steps:
Load RDEBUG.NLM on the server (LOAD RDEBUG).
Break into the NetWare internal debugger (SHIFT, SHIFT, ALT, ESC).
Invoke RDEBUG from within the internal debugger, adding such parameters as are not contained in the RDEBUG.CFG file.
On the workstation, invoke RDEBUG.EXE with appropriate parameters.
From within Rdebug on the client, set the source path to include both the directory containing source files and the directory containing the symbol file.
Load the NLM that you wish to debug from within the debugger by typing "load <nlm name>" in the debugger command window.
Using the Ethernet Interface
The Ethernet interface uses the UDP/IP transport protocol. Routing is supported by using ARP. To use the ethernet interface, you must have 2 IP addresses. One for the server and one for the workstation.
For the workstation --
You must install a TCP/IP protocol stack, WLIBSOCK.DLL, and WINSOCK.DLL. For Windows 3.1, these can be obtained from LAN Workplace for Windows. For Windows 95 or Windows NT, install the Microsoft TCP/IP protocol from the Network Control Panel.
You should then edit the properties of the program and add as a parameter to RDEBUG.EXE, the following:
|
ip <IP ADDRESS< |
where <IP ADDRESS< is the IP address of the server. For example:
|
C:\RDEBUG32\RDEBUG.EXE -ip111.222.333.444 |
For the server --
You need an NE2000 board in your machine. At the moment, this is the only Ethernet card that is supported. This card should be in addition to the LAN card that is used by your server for regular network communication. It is possible to debug using a single NE2000 in the server. In such a case however, the debugger will take over the NE2000 card and the NetWare Server will not have access to the card.
As was mentioned above, RDEBUG.NLM is invoked from the NetWare Internal Debugger. Thus, after loading RDEBUG.NLM, you should break into the Internal Debugger by pressing SHIFT, SHIFT, ALT, ESC. Then invoke Rdebug with the appropriate command line. An example would be:
|
#Rdebug NE2000 IP 111.222.333.444port=320 |
Parameter information can be obtained by typing "rdebug help" from within the NetWare Internal debugger.
If you don't want to type in the IP address every time you invoke the debugger, you can put it in a file on the DOS partition and in the boot directory. The file is named RDEBUG.CFG and should contain only one line in the file, with the following format:
|
NE2000 IP <ip address< port=<portnumber< |
for example:
|
NE2000 IP 111.222.333.444 port=320 |
Note that port is the port address of the NE2000 card you are using for the debugger.
No LAN driver should be loaded by the server for the NE2000 card that will be used by the debugger. RDEBUG.NLM contains a special NE2000 driver that will control the additional LAN card.
Using a Serial Interface
If you want to use the serial interface you must have a serial cable between the server and the workstation.
For the workstation --
The debugger defaults to COM1. However, you may override this by specifying the COM port on the command line of RDEBUG.EXE. The format is as follows:
|
port <com port< |
for example:
|
C:\RDEBUG32\RDEBUG.EXE -port COM2 |
The debugger also defaults the baud rate for Windows 3.1 to 38400 baud, and for Windows NT or Windows 95 to 57600 baud. You may override the baud rate by specifying the baud rate on the command line as follows:
|
baud <baud rate< |
The debugger supports the following baud rates:
|
300, 600, 1200, 2400, 4800, 9600, 19200, 38400,57600 |
If you specify a baud rate, but it is not one of the above, the debugger will use the default for the operating system on which it is running. The port and baud parameters need not be in any specific order.
For the server --
If you are not using COM1, you may either type the port as part of the command to invoke RDEBUG, as in
|
#RDEBUG COM2 |
or put it in the RDEBUG.CFG file. This file is on the DOS partition and in the boot directory. It should only have one line in the file, with the following format:
|
COM2 |
You do not need to specify a baud rate on the server. When the initial connection is made with the workstation, the correct baud rate will be determined. However, should you break into the NetWare Internal debugger while running RDEBUG and then wish to reconnect to the workstation, it will be necessary to specify the baud rate at which the two were connected previously. An example of this is as follows:
|
#RDEBUG BAUD 38400 |
When the workstation initially connects with the server, the negotiated baud rate will appear on the screen.
Things you need to know
|
1. |
The source code can be anywhere, but must be pointed to by thespath and/or the globalpath variables. You can set these from the menu or from the command window. |
|
2. |
The symbol file (xxx.SYM) must be in a directory pointed to by either thespath orglobal path variables, or in the directory from which you run RDEBUG.EXE. |
|
3. |
When you load your NLM from the debugger, it will load the NLM, thenproceed tothe Start Procedure of the NLM. For NLMs written to use CLIB, this will bePRELUDE.OBJ. There are no symbols for this, however, you may see line numbersand assembly code following them. You can proceed to your own code by eitherselecting one of your modules, setting a breakpoint, and clicking "go", or by typing "gotil main" (or any other function name) in the command window, which will bring youthat function. |
|
4. |
If you step into a function for which you have no source code, it will take along timeand not step in, but rather step over the line. You can step in if you are in assemblymode only (which you set by pressing the ASM button). |
|
5. |
The NLM runs only on Green River versions of NetWare. You cannot debugonNetWare 4.10, 3.12, 3.11, or anything else. This is because NetWare servers prior toGreen River did not contain support for the debugger. |
|
6. |
The concept of viewpoint is mentioned throughout the documentation, but thedefinition of a viewpoint for NetWare is currently the set of all NLMs on the serverthat have symbols for them. This may change in the future to include the concept ofthreads, processes, or processors. |
|
7. |
When the debugger starts up, it will load symbols for any NLM that iscurrently loadedon the server, provided it finds the symbol file in the startup directory, or in thedirectory pointed to by spath or global path. |
|
8. |
You can debug multiple NLMs at the same time because of the way viewpointsaredefined as described above. A current problem exists, however, that causes duplicatemodule (compilation unit) names to be thrown away. So, if you had 2 NLMs that eachhad a DOG.C file in them, and you loaded symbols for both NLMs in the modules list(the debugger modules list, not the NetWare server modules list), you would only seeone instance of DOG as a module. This would be the first one loaded. Should you stepinto any function in the DOG module for the second NLM you wouldn't be able to seesymbols or source code. |
|
9. |
Using the Watcom compiler, you must compile your code with the /hc switch(seemakefile). |
|
10. |
Using the Watcom linker, you must link with the "debug codeview" link option(seemakefile). |
|
11. |
You must run CVPACK.EXE after linking (seemakefile). |
File Information
Self-Extracting File Name: XRDB1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XRDB1.TXT |
(this file) |
||
|
RD16-105.EXE |
1646584 |
5-31-96 |
10:34 AM |
|
RD32-203.EXE |
1218650 |
5-31-96 |
10:34 AM |
|
SAMPLE.EXE |
19507 |
5-31-96 |
10:34 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.