(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: New NE3200.COM from Intel
DOCUMENT ID#: FYI.A.1949
DATE: 24NOV92
PRODUCT: NetWare Btrieve NLM
PRODUCT VERSION: v5.15
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
File corruption was cited when Intel's NE3200.COM driver was used with Intel's EtherExpress 32-bit card at workstations running Btrieve applications. This driver was dated 09-03-91 and of size 19242 bytes. The exact description of the problem is as follows (per Intel):
"... a problem with the EtherExpress 32 and applications that use extended memory or memory managers (such as Microsoft Windows 3.x). Previous versions of this driver would not protect memory regions from the above mentioned applications. This could cause files that the EtherExpress 32 stored in memory to be overwritten (corrupted) if an application wrote to that address space."
SOLUTION
Intel has a new NE3200.COM driver (date: 05-04-92, size: 25967) that fixes these problems with the use of the keyword "DOUBLE BUFFER" in the NET.CFG statement. This driver is still in Beta and has not completed certification.
Also, this driver defaults to an 802.2 frame type; if a different frame type is needed, include a FRAME statement in the NET.CFG file. A sample NET.CFG file follows:
LINK DRIVER NE3200
SLOT 5
DOUBLE BUFFER
FRAME ETHERNET_802.3
PROTOCOL IPX 0 ETHERNET_802.3
PROTOCOL IPX
BIND NE3200
Note that this NET.CFG file requires the NE3200.COM driver to be in the same directory as itself.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
In the TUTORNWS.WTS file that was shipped with NetWare SQL 3.0, the Appointments table is created before the Procedures table. This causes a problem with defining a foreign key in the Appointments table that references a primary key in the Procedures table (CODE). To avoid the problem, the Procedures table must be created first.
SOLUTION
The TUTORNWS.WTS file has been updated to create the Procedures table before the Appointments table. The new tutorial file has a date/time stamp of 10-12-92 4:08pm and is 10226 bytes. It is in TBA001.ZIP available on NetWire.
The TUTORNWS.WTS file that shipped with NetWare SQL 3.0 is 10234 bytes and has date/time stamps of 1-9-92 10:24a. This should simply be replaced with the new file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Performing Create/Drop Index Operations Within a Transaction
DOCUMENT ID#: FYI.A.1129
DATE: 07DEC92
PRODUCT: NetWare SQL
PRODUCT VERSION: v3.0
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
Through NetWare SQL, if an application performs a CREATE or DROP INDEX operation on a table within a transaction after it has previously updated the same table within the same transaction, the updates will be committed when the CREATE/DROP index operation completes--the updates cannot be rolled back even though the application has not yet issued the COMMIT/ROLLBACK statement.
SOLUTION
This anomaly occurs because the NetWare SQL must temporarily disable transactions to Btrieve to perform the Btrieve CREATE/DROP INDEX operation. When this operation completes, it commits all outstanding updates to the file.
In general, applications should not mix Data Definition Language (DDL) operations and data updates within the same transaction.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Possible Conflict Between XQL and Cpi-C
DOCUMENT ID#: FYI.A.1950
DATE: 23NOV92
PRODUCT: XQL for DOS
PRODUCT VERSION: v2.01
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
IBM has a software product called Networking Services DOS (NSD), that allows mainframe to PC communication (using Cpi-C language). If the Cobol library of NSD v1.0 (CBLNSDR.LIB) is used with Novell's Cobol interface for XQL v2.01 (COBXQLM.OBJ), then the Cpi-C code does not perform its function and does not return any error codes either.
This happens regardless of whether or not the application contains any XQL code and regardless of whether or not the XQL/XQLP/XQLPO TSRs are loaded. The application simply has to link in Novell's OBJ, and the Cpi-C problem occurs.
SOLUTION
IBM found that there was a bug in their CBLNSDR.LIB file. Following is the information on the original version of this file:
Size: 5655
Date: 08-28-92
Time: 01:00 am
IBM has not released an official fix yet, but they can provide a temporary, working copy of this file to customers:
Size: 5655
Date: 11-19-92
Time: 12:58 pm
Following is the information on the COBXQLM.OBJ file:
Size: 3019
Date: 08-30-88
Time: 09:33 am
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: AIOAcquirePort - Documentation Problem
DOCUMENT ID#: FYI.A.4124
DATE: 15DEC92
PRODUCT: Network C for NLMs
PRODUCT VERSION: SDKd
SUPERSEDES: NA
SYMPTOM
Server abend
ISSUE/PROBLEM
The example in the NLM documentation for AIOAcquirePort() passes the hardwareType, boardNumber, and portNumber as integers. This could cause a server abend.
SOLUTION
The hardwareType, boardNumber and portNumber need to be passed in as pointers to integers.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MapDrive Under Windows
DOCUMENT ID#: FYI.A.4125
DATE: 15DEC92
PRODUCT: NetWare C Interface for Windows
PRODUCT VERSION: v1.3
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
The MapDrive() function under Windows can only modify a search drive. It cannot add a new search drive. The problem with search drives under Windows is caused by how Windows spawns COMMAND.COM to run DOS programs.
SOLUTION
The solution to modifying search drives is to copy the parent environment to the master environment that Windows is using.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: SaveDirectoryHandle() Does Not Save Temporary Directory Handle
DOCUMENT ID#: FYI.A.4807
DATE: 11DEC92
PRODUCT: NetWare C Interface DOS
PRODUCT VERSION: v1.20
SUPERSEDES: NA
SYMPTOM
Status 155 (BAD DIRECTORY HANDLE)
ISSUE/PROBLEM
The functionality of the SaveDirectoryHandle() API extends only to permanent directory handles. When passed a temporary directory handle, this function returns a status of 155 (BAD DIRECTORY HANDLE).
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Borland's Default open() Mode
DOCUMENT ID#: FYI.A.3860
DATE: 07DEC92
PRODUCT: NetWare C Interface DOS
PRODUCT VERSION: v1.2
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
After writing to a file with the Queue Services API, extra 0x0D (Carriage Return) characters were found in the file.
SOLUTION
The Queue Services APIs assume that the file will be open in Binary mode. For example, in SERVJOB.C module, open() is called without specifying the mode that the file should be opened. If Borland C++ 3.1 compiler is used to open the file, it defaults to text filtering. This will cause some extra characters to appear in the file. The developer can change the Borland's default open() mode by including the following lines in his code:
extern int _fmode;
_fmode = O_BINARY;
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "SPX_NOT_INSTALLED/IPX_NOT_INSTALLED" Errors Returned
When programming under Windows 3.1 using the Windows SDK v1.3, the error SPX_NOT_INSTALLED may be returned when calling the function SPXInitialize(), and IPX_NOT_INSTALLED may be returned when calling the function IPXInitialize().
SOLUTION
The appropriate release version numbers of the following files must be used:
1. IPX.COM : version 3.10 and above
- or -
IPXODI.COM : version 1.20 and above
2. VIPX.386 : version 1.13 and above
3. NWIPXSPX.DLL : version 1.31 and above
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Exiting Windows Hangs when Using WINSTART.BAT
DOCUMENT ID#: FYI.A.6101
DATE: 28DEC92
PRODUCT: Btrieve for Windows
PRODUCT VERSION: v5.10
SUPERSEDES: NA
SYMPTOM
Windows 3.1 (enhanced mode) hangs when using WINSTART.BAT
ISSUE/PROBLEM
When using WINSTART.BAT with Windows 3.1 in enhanced mode, everything works fine until Windows is exited, at which time Windows will hang. This problem happens sporadically.
SOLUTION
Do not use WINSTART.BAT; instead place all these commands in AUTOEXEC.BAT. However, when running a Windows Btrieve application, and a DOS Btrieve application in a DOS box at the same time, WINSTART.BAT must be used to load Brequest. If Brequest is loaded before Windows without using the WINSTART.BAT file, Brequest can not be loaded in a DOS box, and the DOS Btrieve application cannot be run. At this time, there is not a workaround.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Developer Can Ship Windows SDK DLLs with Application
DOCUMENT ID#: FYI.A.2946
DATE: 16DEC92
PRODUCT: NetWare C for Windows
PRODUCT VERSION: v1.3
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
Can a developer ship the Windows SDK DLLs with their application?
SOLUTION
Yes, the Windows SDK DLLs can be shipped with a developer's application. However, only the necessary DLLs should be included, not the entire set.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Return Code from AccountingInstalled API
DOCUMENT ID#: FYI.A.1951
DATE: 06JAN93
PRODUCT: NetWare C Interface DOS
PRODUCT VERSION: v1.20
SUPERSEDES: NA
SYMPTOM
NA
ISSUE/PROBLEM
The AccountingInstalled API of the NetWare C Interface-DOS v1.20 returns 0x01 if accounting is installed on the file server. This is documented, but the non-zero return code may be confused for a failure of the API (because most other APIs return 0x00 is they are successful, and non-zero return codes if they are unsuccessful). In this case, the API is successful, but it returns 0x01.
SOLUTION
Remember that for the AccountingInstalled API of the NetWare C Interface-DOS v1.20, 0x01 is a successful return code.
