MARCH 1992 VOLUME 4 NUMBER 3

INDEX

• MAD'S COLUMN
• ARTICLES
• SPECIAL PRODUCT SUPPLEMENT
• TECHNICAL INSIGHTS
• NIBBLES AND BITS
• PATCH LISTINGS
• NOVELL EDUCATION
• FUN & FACTS QUIZ
• CONTACTING NOVELL
• ACKNOWLEDGEMENTS

MAD'S COLUMN

As you will very quickly notice, in this issue of Bullets,we have included a four-page technical marketing supplement.

This supplement provides our existing database programmers a quick look at the new functionality that is available in NWSQL v.3.0, as well as the enhancements and features added to version 6.0 of Btrieve. For those of you that are not currently using our database tools, we hope that these new features will entice you, too.

The excitement here at Novell Austin increased as NetWare SQL v3.0 neared completion and the scheduled release date inched closer and closer. The level of activity and teamwork also increased as each department prepared for the release. For the past three months, we have been involved in intensified in-house technical classes and presentations, marketing reseller seminars, software engineer training and long hours of coding and testing.

These activities have demonstrated our entire site's commitment to the success of NetWare SQL v3.0. All of our efforts will be worth it if you, the Novell developer, are satisfied with the final product. Let us know what you think!

Happy_Programming!

Mad Poarch
Director
Developer Support/Service

ARTICLES:

Capturing with the NetWare Print Services

This article describes how to use the various NetWare Print Services APIs to control capturing of printed output and redirect it to a print queue or file on a NetWare file server. The code examples in this article are excerpts from a program called CAPIT. C, which reproduces much of the functionality of CAPTURE.EXE. Because of space limitations, the entire source code for CAPIT.EXE cannot be printed in this publication. Both the source code and the executable itself are available in Novell's CompuServe forum, NetWire (see details at end of article).

The CAPTURE.EXE program included with NetWare provides some additional capabilities over CAPIT.EXE. For example, it can retrieve default capture flags defined by PRINTCON in the file, PRINTCON.DAT. The format of the information in PRINTCON.DAT is proprietary to Novell and is subject to change without notice. If you need a mechanism to store or retrieve these default values, you should develop your own. This article will demonstrate how to "carry-forward" existing capture flags.

CAPIT.EXE uses "default" capture functions whenever they are available. This design simplifies the code for choosing the local printer to which printer output will be directed. These functions act on the printer port being captured, which is set by the function SetDefaultLocalPrinter(). There are also "specific" functions that act upon a specified local printer on each call. These functions are similar to their "default" counterparts, but include an extra parameter specifying the local printer.

The Capturing Process

1. End any existing capture
2. Set the capture print queue
3. Set the capture flags
4. Start the capture

Ending Existing Captures

FIGURE 1: Resetting capture flags to default values

SetDefaultLocalPrinter(localPrinterToCaptureTo);
  GetDefaultCaptureFlags(&setCaptureFlags);
  retCode = GetLPTCaptureStatus(&serverNumber);
  if (retCode == 0)  // Reset flags if not now captured
  {
setCaptureFlags.status = 0x00;
setCaptureFlags.flags = 0x00;
setCaptureFlags.tabSize = 0x08;
setCaptureFlags.serverPrinter = 0x00;
setCaptureFlags.numberOfCopies = 0x01;
setCaptureFlags.formType = 0x00;
setCaptureFlags.localLPTDevice = 0x00;
setCaptureFlags.flushCaptureOnDeviceClose = FALSE;
setCaptureFlags.flushCaptureTimeoutCount = 0x00;
setCaptureFlags.maxLines = 66;
setCaptureFlags.maxChars = 132;
setCaptureFlags.formName[0] = NULL;
setCaptureFlags.LPTCaptureFlag = FALSE;
setCaptureFlags.fileCaptureFlag = FALSE;
setCaptureFlags.printQueueFlag = FALSE;
setCaptureFlags.printQueueID = 0x00;
  }

End of Figure 1

The documentation for SetDefaultCaptureFlags() and SetSpecificCaptureFlags() incorrectly states that the parameter passed to each function should be a pointer to a structure of type, SET_CAPTURE_FLAGS. Although the function's prototype expects this type of pointer, additional flags in the CAPTURE_FLAGS structure are required. These functions should be passed the same structure that is passed to the appropriate GET functions, and cast to the expected structure. For example:

This is why the code required to get and clear the flags (shown in Figure 1) uses setCaptureFlags. The functions to set the flags require the entire structure as defined by CAPTURE_FLAGS, not the shortened version defined by SET_CAPTURE_FLAGS.

Capturing to a File or Print Queue

     specifyCaptureFile(directoryHandle, path);

FIGURE 2: Calls necessary to capture to print queue

  SetPreferredConnectionID(printServerConnectionID);
  retCode = GetBinderyObjectID(queueName,
 OT_PRINT_QUEUE,
 &queueID);
  if (retCode != 0)
  {
   // Queue may not exist on server   handle the error
  }
  setCaptureFlags.LPTCaptureFlag = FALSE;
  retCode = SetCapturePrintQueue(localPrinterToCaptureTo,
   printServerConnectionID,
   queueID);

End of Figure 2

Setting Capture Flags

FIGURE 3: Flags field of CAPTURE_FLAGS structure

Flag Definition
----------------------------------------------------------
0x01 Undefined

0x02 Undefined

0x04 If set, jobs get printed if workstation loses connection during capture

0x08 If set, form feeds will not be sent at the end of each job

0x10 If set, the user is notified when the job has printed

0x20 Undefined

0x40 If set, tabs are converted to spaces

0x80 If set, a banner page is printed before the print job

End of Figure 3

The printerSetupBuffer and printerResetBuffer fields are used for placing printer controls before and after a print job. They are far pointers to the buffers created by the NetWare shell. The first word (not byte) in each buffer defines the size of the buffer. The second word defines the length of the printer control (how many bytes to send to the printer). The remaining bytes are sent to the printer.

The size of these buffers is determined by the PRINT HEADER= and PRINT TAIL= parameters inside the shell.cfg or net.cfg file. If these parameters are not set within these files, default sizes are used: 64 bytes for the printerSetupBuffer and 16 bytes for the printerResetBuffer.

Unless you need to modify the values inside these buffers, you only need to know how to treat the pointers to the buffers under various versions of the shell. With versions of NetWare shell before v3.00, the address of the buffers was returned long-swapped (i.e. in "hi-lo" or non-Intel format), but with v3.00 and above, the addresses are no longer swapped (they are returned in lo-hi, or Intel-readable, format).

The NetWare C Interface for DOS (v1.2 and earlier) swapped these bytes to compensate for the swapping performed with pre-v3.00 shells, but the interface does not check for the shell version before doing so. Therefore, if your application is running under shell versions 3.00 and above you must swap these values. Swapping can be performed with the code displayed in Figure 4.

FIGURE 4: Calls needed to manage differences between v2.x & v3.x shells

retCode = GetNetWareShellVersion(&majorVersion,
   &minorVersion,
   &revisionLevel);
if (retCode == 0)
{
  printf("Shell version too old\n");
  exit(1);
}
if (majorVersion > 2)
{
  setCaptureFlags.printerSetupBuffer =
   (char far *)LongSwap((long)setCaptureFlags.printerSetupBuffer);
  setCaptureFlags.printerResetBuffer =
   (char far *)LongSwap((long)setCaptureFlags.printerResetBuffer);
}

End of Figure 4

The only remaining step is to start the capture, either with StartLPTCapture() or StartSpecificLPTCapture().

Capturing data intended for a printer and redirecting it to a file or print queue is a fairly simple matter. A few situations require special handling, but once these are resolved, applications that are not NetWare-Aware can be made to print to NetWare print servers or files. An alternative to capturing printer output is to write data directly to NetWare print queues.

The source code to CAPIT.EXE and the executable can be downloaded from NetWire (NOVLIB section, LIB 14, under filename CAPITx.ZIP, where "x" is the revision number if any). If you have additional questions on capturing with the NetWare Print Services, or if you need technical assistance, please contact the Developer Support Group at Novell Austin (See "Contacting Novell Austin" at the end of this issue).

SPECIAL PRODUCT SUPPLEMENT:

NetWare SQL New & Enhanced Features

Even a novice database administrator will be able to install and use NetWare SQL v3.0 due to the new, simple Install utility We have improved the performance of many join and fetch functions at the NetWare SQL level and enhanced loading of large files. The documentation has been reorganized to better accommodate different expertise in the SQL level functions or relational primitives. Convenient quick reference cards provide easy access to SQL statements and status codes.

Cursor Stability, the ability to lock the page containing the record to which the cursor is currently pointing, has been added. Cursor stability ensures that the data each user reads remains stable, while still allowing other users access to other pages within the same data files. The cursor stability isolation level generally permits greater concurrency for all users on a network by limiting the number of records each user locks at any one time. This allows other network users to access more pages of the data file.

Btrieve Enhancements

Referential Integrity (RI) constraints ensure that cross references between tables are always valid. A Database Administrator can define RI restrictions with SQL statements. NetWare SQL enforces these constraints across all applications at the Btrieve level. Since these RI restrictions are enforced at the data dictionary level, developers are freed from having to include RI restrictions directly in their applications.

Online Backup or continuous operations allows users to backup the database currently in use at any time without closing the files. Online backup is implemented with a NetWare SQL utility which opens the original file in a read only mode. Btrieve backs up a "snapshot" of the file and creates a "Delta" file for operations occurring during the backup process. After turning off the backup utility, Btrieve issues a "commit" transaction.

New caching algorithms have been developed to provide hashing search methods for improved access, concurrent sharing of a single cache, and persistence of the cache across operations. The speed of building and loading supplemental indexes for large data files has been improved with merge sorts.

Page Allocation Tables (PATs) contain information about the file, such as file size and page size, as well as information about other current pages. PATs represent a departure from Btrieve's previous pre-imaging method. Btrieve's previous pre-imaging is the process of storing the image of a file page before a record on the page is updated. In the alternative, PATs are updates to the page or pages written into unused or "recycled" pages in the Btrieve file. During the commit, the PAT is updated to reflect any activity. This enhances performance because a pre-imaging file does not need to be maintained.

Because of the shift to PATs, a "roll-back" command is no longer necessary. The user is working with a "virtual" copy of the file. The file is always valid and internally consistent except during a controlled commit period.

Passive Control allows applications to expect the update or delete operation to complete successfully. Rather than requiring an application to lock a record before updating it, Btrieve returns a "conflict" status at update time if an application attempts to update a record that has been changed since the application last read it. Passive control supports updates of one record at a time outside of a transaction.

Passive control allows a single user application to run on the network without implementing locking. However, passive control is most effective when an application is operating in a lightly utilized network environment or on files in which the data is fairly static.

Packaging and Upgrades

The NetWare SQL Developer's Kit will be offered concurrently (as a separate product) with the release of NetWare SQL v3.0. The developer's kit documents the NetWare SQL APIs and SQL statements. It also provides a comprehensive overview for new NetWare SQL developers who start writing applications for NetWare SQL. The language interfaces and embedded SQL preprocessor for DOS and libraries for OS/2 are a part of the kit.

Upgrades are offered from NetWare SQL 386 2.11 (NLM) and NetWare SQL 2.11 (VAP) for a limited time.

For more information about NetWare SQL v3.0, contact your local Novell reseller, or call 1-800-477-9139 (FAX 512-345-9509). Customers outside the USA, please contact your local Novell office or call 512-795-8094.

TECHNICAL INSIGHTS:

CLib API Update: GetVolumeNumber( ) (Network C for NLMs v2.0b)

Source:

int volNumber = 0xFFFFFFFF;

GetVolumeNumber("SYS", &volNumber);

printf("0x%X\n", volNumber);

Output:

0xFFFFFF00

Patches for 3270 LAN Workstation for DOS (3270 LAN Workstation for DOS v2.0)

• Cursor movement problems on Printer Control Panel.
• "No Resources Available" when WSLAN is configured for multiple gateways.
• Incompatible keyboard BIOS problem with new IBM PS/2 model 35 and 40.

Internals of the XQL Data Segment (XQL for DOS v2.11)

FIGURE 5: Makeup of 64K XQL data segment

BYTES     DESCRIPTION
------------------------------------------------------
13856     XQL's global data
  980     Memory allocated to hold info about active dictionary
  539     Current Session data structure
  867     Current View data structure
 1400     Join List data structures
 2267     Data buffer (allocated at load-time) used for swapping data structures to disk
 2062     Memory used for extended Btrieve operations
  896     Dictionary position blocks
  817     Misc. key buffer, currency addresses, etc.
------------------------------------------------------
23684     This is the fixed size of data that resides in XQL's 64K data segment.  There is 41852
bytes of data left for the load-time parameters.  Space will be allocated in the data segment for
the /w, /t and /b parameters as follows:

          w  Fetch buffer.  w = value in /w: parameter

          t * 130    Trans. processing. t = value in /t: parameter.

           Defaults to 12.

          b * 1024   Heap buffer.  b = value in /b: parameter
------------------------------------------------------
65536     If this number is exceeded XQL will display an "insufficient memory" error and fail to
load.

End of Figure 5

xql /t:12 /v:8 /w:8000 /b:32 /e

  23684
   (12 * 130)
   8000
+ (32 * 1024)
-------------
  66012

Reducing the /t parameter to eight will enable XQL to load.

xql /t:8 /v:8 /w:8000 /b:32 /e

  23684
    (8 * 130)
   8000
+ (32 * 1024)
-------------
  65492

SPXEstablishConnection( ) Uses "bp" Register (NetWare System Calls for DOS v1.0)

This requirement is undocumented in the current NetWare System Calls manual.

MapDrive & Search Drives (NetWare C Interface for DOS v1.2)

FIGURE 6: Deleting mapped search drive with MapDrive function

GetSearchDriveVector(vectorBuffer);
for(i=0;i<16;i++)
if(vectorBuffer[i] == driveLetter - 'A') break;
 if(i == 16) i=0;
   else i++;   /* Search Drives are  */
/* relative to 1, not 0.   */
cCode=MapDrive(connectionID,  /* Server Connection ID    */
NO_BASE_DRIVE, /* No Relative drv Mapping */
"",  /* No Path Required   */
DRIVE_DELETE,  /* Delete This Drive  */
i,   /* Number Of Search Drive  */
&driveLetter); /* Drive To Be Deleted*/

End of Figure 6

PUBLIC User in Xtrieve PLUS v4.10 (Xtrieve Plus v4.10)

PUBLIC functions like a group (as in NetWare, where there can be individual users and groups). The Master user can assign rights to PUBLIC. Then, as individual users are added, the Master user does not need to redefined each users rights individually; users can be assigned the rights that have been given to PUBLIC (this design is similar to security equivalences in NetWare).

GetBinderyObjectDiskSpaceLeft( ) Problem (NetWare C Interface for DOS v1.20)

Calling GlobalAlloc( ) from Windows DLLs (Network C for Windows v1.22)

• GMEM_DDESHARE
• GMEM_FIXED
• GMEM_NOT_BANKED

ScanDirEntry Sequence Number (NetWare C Interface for DOS v1.2)

Key Position & Create Operation (Btrieve (all versions))

The Key Position must be set to a value between one and the specified record length. This requirement also applies with BUTIL -CREATE operations and any application that performs a Btrieve Create (14) operation.

CLib Rename API & Directories on NetWare 2.x Servers (Network C for NLMs v2.0b)

Btrieve Pascal Examples (Btrieve for DOS v5.10a)

For instance, the Btrieve Create example in Appendix D results in a status 25 (Create I/O Error), a status 27 (Invalid Key Position) or possibly other errors if used in a Turbo Pascal program. The following changes should be made in order for the Btrieve Create example program to function properly:

1. The key specification must include a four-byte "Not used" field. In the sample program, this field is declared as "NOT_USED : string[4];" which is actually a five-byte field. This will cause a status 27 to be returned on the Btrieve Create call. Change this variable to "NOT_USED : ARRAY [1..4] OF char;"
2. Similarly, the file specification includes a four-byte "Not used" field, as well as a two-byte "Reserved" field. The sample program declares the fields as "NOT_USED : string[4];" and "RESERVED : string[2];" respectively. These may also produce a status 27 on the Btrieve Create call. Change the data type of these fields to ARRAY [1..x] OF char.
3. The KeyBuffer parameter passed on the Btrieve Create call must contain the name of the file to be created. The example uses a variable declared as: "FILE_NAME : string[17];" and then calls Btrieve with this variable as the key buffer (fifth) parameter. When Btrieve reads FILE_NAME, it reads the length byte first, which usually is not a legal character for a DOS file name, and a status 25 will be returned.

   STATUS := BTRV (B_CREATE,
    POS_BLK,
    DATA_BUF,
    DATA_LEN,
    FILE_NAME[1],
    0);

FIGURE 7: Excerpt from Pascal Get First example in Btrieve manual

  type
    EMP_REC = record
 case integer of
 1: (NAME : string(20);
AGE  : string(2);
HIRE_DATE : string(6));
 2: (ENTIRE    : string(28));
    end;
  var
    DATA_BUF : EMP_REC;
    ...
  begin
    ...
    STATUS := BTRV(B_GET_FIRST, POS_BLK, DATA_BUF.ENTIRE,
    DATA_LEN, KEY_BUF, 2);

End of Figure 7

  type
    EMP_REC = record
 NAME : string[20];
 AGE  : string[2];
 HIRE_DATE : string[6]
    end;
...

STATUS := BTRV( B_GET_FIRST,
 POS_BLK,
 DATA_BUF, {Use "DATA_BUF" as 3rd parameter}
 DATA_LEN,
 KEY_BUF,
 2);

End of Figure 8

Preventing NLMs from Unloading (Network C for NLMs SDK v2.0b)

1. Specify the CHECK option in your LNK file, giving it the name of a function that will be called on an unload attempt. The prompt from the loader will expect a "Yes/No" response. Forcing a "No" response and an "n" will prevent the NLM from unloading. For example:

        option check=NWNoUnload
   

2. Insert the routine listed in Figure 9 into your code. This routine will "push" characters to the console screen using "ungetch" ("n").
3. The routine in Figure 9 prevents NLMs from unloading, so you must provide an alternate method. Register a command processor using the RegisterConsoleCommand API.

FIGURE 9: Routine to prevent NLMs from unloading

#include 
#include 
#include 

int   NWNoUnload()
{
 LONG   OldScrID = GetCurrentScreen();
 LONG   NewScrID = CreateScreen("System Console",0);

 if( OldScrID != NewScrID) SetCurrentScreen(NewScrID);
 ungetch('n');
 if( OldScrID != NewScrID) SetCurrentScreen(OldScrID);

 return 1;   // ask NetWare to send a warning message
}

End of Figure 9

NetWare System Calls Clarification (NetWare System Calls v1.0)

Stack Corruption on Paths Larger than 255 Bytes (Network C for NLMs SDK v2.0b)

WLINK & Redefining Imported Symbols (Network C for NLMs SDK v2.0b)

IPXGetInternetworkAddress API Problem (Network C for Windows v1.22)

EMSNETX Bug (EMSNETX v3.22)

CLib Addition Error (Network C for NLMs SDK v2.0b)

NIBBLES AND BITS

Fast Answers to Common Questions

NetWare C Interface for DOS v1.2

A - There is no API to execute the login script.

NETX v3.22

A - Borland's Make utility has an option (-S) that allows you to swap the make utility out of memory while it compiles or links. Errors occur when the Make utility tries to reload itself into memory. Borland's C++ Compiler v3.0 does not include a BCCX file and functions correctly. Earlier shells seem to work properly; the problem seems to only occur when you use BCCX v2.0 with netx v3.22.

Network C for NLMs v2.0b

A - If you install Network C for NLMs according to Novell's installation defaults, the installation process places these tutorial examples in \WATCOM\NOVX\CS.

Q - When I use the AIOCOMX driver at high speeds, it frequently loses characters. What should I do?

A - The COMX driver does not guarantee that all characters will be received, because the LAN and disk drivers disable interrupts for too long. Drivers like the ARTIC driver and the WNIM driver will produce better results since they have their own CPU on the board.

NetWare C Interface for Windows v1.22

A - Make sure that NETWARE.DRV is in the search path, or is located in the directory from which Windows is running. When Windows cannot find NETWARE.DRV, it returns the error message that it cannot find NETWARE.DLL.

Q - When using the DLLs provided with the NetWare C Interface for Windows SDK v1.22, what is maximum packet size that NetWare supports under Windows Standard mode?

A - The maximum packet size is 512 bytes, including the header.

DR DOS v6.0

A - A number of patches have been released for DR DOS v6.0 and can be acquired in several ways:

1. From the Digital Research CompuServe forum, DRFORUM.
2. Directly from Digital Research by calling 408-646-6464.
3. From Digital Research by faxing your request to 408-649-8209.

NetWare OS/2 Developer's Kit v1.3a

A - You will need the DOSNP TSR that is provided with the NetWare OS/2 SDK and the specific libraries that are also available with that SDK.

Q - The Named Pipe status codes are not defined in the DOS Named Pipe headers in the NetWare OS/2 SDK v1.3. How can I check the status of a pipe without reading the data?

A - When you issue a DosPeekNamePipe API call while writing a DOS Named Pipe application, you will notice that some of the status return codes are not defined, and that they generate compiler warnings. The status codes describe the status of the Named Pipe. In the NetWare OS/2 SDK, there is also a NMPIPE header file under the WINNP directory for Windows and Named Pipes. If you need to use this API call, copy over the predefined status codes to the DOS NMPIPE header file.

Btrieve

A - You can download this file from NetWire (NOVLIB, LIB1, filename: UPPER.ZIP).

Q - How can I define a C long integer as a key in Btrieve, when there is no long data type?

A - To define a C long integer in Btrieve, specify the key as an integer with a length of four bytes.

PATCH LISTINGS

NetWare Btrieve (VAP, NLM) v5.15 Patches

• 51. (BTRIEVE.NLM) This patch corrects the following situation involving two workstations: the first workstation performs an Update (3) operation, but a status 80 (Conflict error) is returned because a second workstation updated the record after the first workstation read the record. If the first workstation then performs a Get Position (22) operation before rereading the record, an erroneous status 8 (Invalid Positioning) is returned. This patch allows the Get Position operation to succeed.
• 52. (BTRIEVE.NLM) When you build a supplemental index, server utilization goes to 100% and any other stations making Btrieve calls "time out," receiving status 95 (Session No Longer Valid) errors. This patch corrects the situation by decreasing the time slice used by Btrieve while sorting the keys.

NetWare SQL/XQL v2.11 Patches

• 67. NWSQL (NLM) This patch fixes a side-effect of patch #59 which could cause extraneous information to be returned in the bDataBuf parameter of xDDIndex. This situation only occurs if the Btrieve Stat (15) operation fails for option one of xDDIndex.

  This situation will cause the workstation to hang when you use Xtrieve PLUS to "SHOW" a file definition and the data file does not exist in the directory specified by the XTRPATH variable.

• 68. NWSQL (NLM) The patch disables use of Btrieve extended filter operations when NetWare SQL is able to perform optimization based on indexed reads. In the case of a restriction which provides values for a segmented index, NetWare SQL can retrieve the records more quickly than a Btrieve filtered operation. The Btrieve filter operation will only optimize on the first segment of the index.
• 69. NWSQL (NLM) This patch prevents server problems when you execute a non-stored statement after you execute (in succession) a stored statement containing a UNION which returns records and a stored statement containing a UNION which does not return any records.

Xtrieve PLUS for DOS v4.10 Patches

1.   In XQL, if you have a BOOLEAN field, and you specify an EDIT mask of "-NO,"
how would the value "false" be represented?

A. NO

B. (blank space)

C. FALSE
2.   In XQL, if you have a BOOLEAN field, and you specify an EDIT mask of "-NO," how
would the value "true" be represented?

A. Yes

B. (blank space)

C. TRUE
3.   In XQL, what environment variable tells XQLI where the dictionaries are located?

A. XQLIDD

B. XQLIDDF

C. XQLIDICT
4.   What status code does Btrieve return when there is a CREATE I/O ERROR?

A. 2

B. 14

C. 25
5.   When using data compression in Btrieve, can the record be of variable length?

A. Yes

B. No
6.   In Xtrieve PLUS, what is the key sequence used to chain command files?

A. Alt-F8

B. Shift-F6

C. Shift-F7
7.   Name the three queues within the Netware Operating System.

A. Print Server Queue, Object IDs Queue, and Supervisor's Queue

B. Job Queue, Print Queue, Users Queue

C. Run Queue, Sleep Queue, Semaphore Queue
8.   What is the maximum size of an SPX packet in OS/2?

A. 576 bytes

B. 534 bytes

C. 540 bytes
9.   What .OBJ file initializes all the CLIB.NLM data structures?

A. Startup.OBJ

B. Prelude.OBJ

C. Init.OBJ
10.  In the NetWare 2.x environment, what two files make up the bindery?

A. Net$Bind.Sys and Net$Prop.Sys

B. Net$Bind.Sys and Net$Obj.Sys

C. Net$Bind.Sys and Net$Bval.Sys
11.  What option in WDISASM will generate the .ASM format from a .OBJ file?

A. /a

B. /asm

C. /80x86
FUN & FACTS ANSWERS
1.     A
2.   B
3.   A
4.   C
5.   A
6.   C
7.   C
8.   A
9.   B
10.  C
11.  A