Niakwa, Inc.



What's News
NPL Products
NPL Support
NPL Downloads
System Integration
swiggle_small.gif (991 bytes)

swiggle_small.gif (991 bytes)

Bug  Global Report Index
For Niakwa Programming Language
Report Date - June 15, 1999

This report lists known problems in the Niakwa Programming Language, Releases III , IV, and V, for all platforms supported, which were discovered after December 1, 1990. This report is in addition to Bug Reports 1 through 13. This report is available on the web site at and can be downloaded along with a Bug Report Index.


  • The following is an index of all currently known bugs existing in the Niakwa Programming Language. This index will be continuously updated as corrections and new bugs become known.
  • Some bugs described in this report are corrected in a revision of the NPL RunTime that is not yet available for the field. Developers should be aware that Revision 3.xx bug correction may never be released to the field, and are published here for informational purposes only. All bug corrections noted in these releases have also been applied to NPL Release V (either the current version or future releases).
  • Detailed descriptions of particular bugs and all relevant information can be found by referring to the Bug Report number specified under the Report # /Bug # column of this report. (all Bug Reports are also available at

NOTE: Bugs which have been corrected display the RunTime revision number in which the correction took place. For details on the current field release revision of each platform, refer to the current issue of Niakwa News, the copy available on the Niakwa web site, or contact Niakwa.

Index Updated on July 17, 2008

5/1$RELEASE TERMINAL associated with pseudo-ports under SuperDOS.3.00
5/2Information about the no of sectors used when a programs that, when saved, end in byte 256 of a sector.3.20
5/3The DOS ERRORLEVEL code returned from rti/rtp when run with either /U or /M startup options is incorrect.
5/4In seldom situations, attempts to raise decimal bases to a calculated exponent produces a result of
5/5$CLOSE command directed to a DOS standard handle will not work properly.
5/6For 68000 versions the value generated by #GOLDKEY is sometimes greater than 65535.
5/7$SHELL can cause strange effects if comspec is set to drive A and is not on drive A.
5/8If a series of $DEMO scripts are used, the first script is left in open mode.
5/9Under Windows, at high baud rates (9600 & 4800), using the 2227 drivers, the information buffer is corrupted.
5/10MOD operation with numbers greater than HEX(1E14) produces erroneous results.
5/11$GIO(hex-digits[,arg2]) [arg3] can cause b2c to generate spurious warnings. Error only in b2c.
5/12LISTV issued will list twice variables present in line number where a MAT operation is.
5/13Bytes 25 and 29 of $PSTAT contain null characters.
5/14Use of "t3" instead of "T3" for tab specifications in $DEMO script generates UAE.
5/15Byte 6 of $MACHINE is not supported under MS-Windows and it contains corrupted information.
5/16Cannot exit 2 background partitions started incorrectly with the same partition number.
5/17Under SuperDOS, Exception Error 13 at 0150:0E32, when in the HELP screen, the DIAG option is selected and the PROCEED options.
6/1Raw format diskettes used on IBM PS/2's with 2.88 MB floppy drives and controllers causes I93 errors.
6/2The RENUMBER statement does not renumber entries for LIST statements.
6/3Invoking the HELP processor and the DOS/Novell option during a LINPUT statement with the RunTime in graphics mode corrupts the input buffer.
6/4Use of the HELP processor, followed by a CONTINUE or FAIL OPERATION, causes the bright attribute to be lost Refer to if it was invoked. Report #6
6/5Cursor cannot be seen on a monochrome monitor under MS-Windows because all HELP processor options are in reverse video3.21.11.00
6/6Using $OPEN under MS-Windows on a hogged diskimage significantly slows other Windows' tasks.
6/7Setting #PART to a value greater than 112 in MS-Windows causes a partition number error.
6/8Executing a LIST' statement with a restricted range of lines to scan causes errors in GOSUB' statements referencing DEFFN' lines outside of that range.
6/9Using TRACE' during an external GOSUB' call which has more than 16 parameters causes the system to hang or otherwise behave erratically.
6/10If F3 is pressed after F5 while the Windows function is "in use", both function pads move. Visual problem.
6/11When the Autosize option is on, unused space exists above and to the left of maximized windows.
6/12Messages generated by fatal errors in programs with line numbers above 9999 may display line numbers incorrectly, with "?" or hexadecimal digits.
6/13Program code can be corrupted if it is compiled with the -LSTFORMAT 2200 (or 2200S) option and the program code is moved to the end of the specified diskimage.
6/14If -LSTFORMAT 2200 (or 2200S) is selected during a a compile and the index of the LSTLOC diskimage becomes full, an index full message is printed, "the index has been damaged".
6/15Under AIX, attempts to compile from ASCII code to p-code/OBJ format result in an error message. A work around is available.
6/16If $PACK attempts to pack numeric variables with very large exponents, the system may hang.
6/17After a MOVE END on a diskimage and an immeadiate reboot, program/data files in the newly allocated extent may become inaccessible and produce a format error. This is limited to SuperDOS and was not replicated in-house.
6/18MOVE END, SCRATCH DISK, and MOVE (of an entire diskimage) operations will perform an implicit $CLOSE that will overwrite explicit $OPENs.
6/19Under MS-Windows, if the startup option /D is used to increase the number of device entries to a value greater than 253, a General Memory Fault error can occur.
6/20Niakwa characters with HEX equivalents between 00-1F, contained in DATA statements, are translated automatically to their hex codes when used in coding.
6/21String operations using AND/OR operators between hex codes and other characters will cause characters to be translated to their equivalent hex codes.
6/22Under MS-Windows, execution of a CLEAR or a LOAD RUN may generate a UAE or "Unknown" fault, if more than 128K has been allocated to the workspace.
6/23Under MS-Windows, if the printer is deselected while printing to a local printer, data is lost.
6/24Under MS-Windows, if the print buffer becomes full while printing to a local printer, all the Windows tasks hang until a next line is printed.
6/25Executing code containing GOSUB's and DEFFN's with more than 16 parameters, with a string as the last parameter, may result in a RunTime stack error.
6/26Use of two ALL(x) statements in the same line is not detected as an error by the RunTime, but generates erroneous code.
6/27Use of an undefined variable in an INIT statement with multiple variables will decompile incorrectly.
6/28If a third-party product's icon is used to identify a minimized RunTime task, attempts to restore or maximize the task, once minimized, result in a UAE or GPE.
6/29If TRACE V output is directed to a print file, the first line of the output will display "!=" instead of the variable name.
6/30Under Windows, any GOSUB' issued in immeadiate mode generates UAEs or GPEs.
6/31Use of RENUMBER with a STEP value greater than 9999 can result in invalid renumbered line numbers.
6/32When moving windows on top of a Niakwa-based window with Autosize OFF, the text in the Niakwa window appears ripped and shifted down.
6/33Attempts to start, close, and restart four or more windows running Niakwa RunTimes with external calls will result in a memory error message.
7/1If RENUMBER is used with a large STEP value that generates line numbers greater than the new line numbers over the supported limit are corrupted. No error message (P33) is generated.
7/2If GOSUB or GOSUB' are performed from an IF THEN statement, the information displayed by a LIST STACK command is incorrect.
7/3Attempts to write a HEX(0D) using a $GIO command Not A Bug results in an extra HEX(0A) being generated. Refer to Report #7
7/4A MAT MOVE operation with a starting byte within each element of the receiver array, causes the operation to decompile incorrectly.
7/5Under MS-Windows, setting bytes 29 and 30 of $OPTIONS does not not result in the remapping of available colors for video attribute replacement.
7/6NPL applications, under MS-Windows, that use external libraries (.DLL's) that specify FIXED memory allocation, may fail to pass NPL security.
7/7Program's that contain GOSUB's in the range of 0-255 may crash, if a GOSUB' in the range of 255 or higher is executed first.
7/8The NIAKWA_RUNTIME environment variable is ignored on RunTimes that were upgraded from NPL Revision 3.00 to 3.20 (ie; 3.20 RunTime's that were tied to the 3.00 security).
7/9Wang 2236 graphics mode problem, when switching back and forth between a foreground and background partition.  SuperDOS only.
7/10NPL Revision 3.20 security problem on non-dedicated file servers.
7/11NPL execution problems on VESA local bus systems.
7/12Cancelling a $DEMO script under RTP exits the RunTime incorrectly. Problem does not occur with RTI.
7/13The 386/DOS-Extender RunTime does not pas ONCE A DAY security correctly.
7/14A negative value on the length parameter of a PRINT AT statement causes a P34 error. This is inconsistent with the Wang 2200 syntax.
8/1Read only attempts to a Diskimage may hang the system after a READ DC command.
8/2Problem with printing in landscape mode under Windows.
8/3LIST V addressed to a variable used multiple times in a LIMITS statement will only display 1 variable reference. See BR #8
8/4Under 386/DOS Extender problem with PRINT SCREEN
8/5Problem with color selection after drawing a box under UNIX.
8/6Problem with external routines under MS-Windows and the SetTimer API call.
8/7Attempt to compile form p-code to p-code with REMS off with ling lines are not handled properly.
8/8Release IV problem scanning long identifiers with a space or underline between the @ or the _ in constants or global variables.
8/9The compiler generates an incorrect argument type for string fields if the field name is specified indirectly using a constant string-variable.
8/10Problem with generation of bad p-code with $NAMEOF and FIELDFORMAT functions.
8/11Increased time in doing a LIST PUBLIC when the amount of public items is large.
8/12Memory allocation problem with external DEFFN's.
8/13Problem changing colors under Windows with the 64K palette.
8/14Under DEC/VMS, when running a program in the background (Work around garbage can be picked up by the LINPUT statement refer to Bug Report # 8
8/15Under DEC/VMS, problem with the "PRINTER CONTROL" utility under HELP.
9/1Problem with scrambled protected modules with LIST PUBLIC [DEFFN/FUNCTION/PROCEDURE].
9/2CONTINUE RETURN or CONTINUE NEXT halts after first executed return form a FUNCTION or PROCEDURE.
9/3Problems with external libraries containing DEFFN' externals with more than 16 parameters.
9/4Allocation of work space using 386/DOS-Extender under Release IV.
9/5Programs with DATA or ERROR statements that are SAVED while resolved, produce output that is different than the output produced by the B2C compiler.
9/6RunTime hanging problems with /Dx parameter under the Release IV using the 386/DOS-Extender if x is greater than 16 and the value of mod(x,8)=5.
9/7Under Release IV, problem with $OBJECT with Release III syntax if a bulit-in function word is encountered in a $PACK or DATA SAVE statement.
9/8A01 - Memory Overflow Errors can occur when there is a large amount of free memory in the workspace, when DEFFN' values over 255 are used.
9/9Problems when a passing security with a Release IV MS-DOS RunTime from a workstation attached to a Novell Netware network with a Revision 3.20 Runtime installed and the security on the network has been passed by the Supervisor.
9/10If the only Release IV features used are LINS in a LIST V or TRACE V range, the program may be saved incorrectly, with a label indicating they do not require Release IV to load.
9/11A memory fault can occur if a program is halted in a library module, and a LOAD RUN statement is executed.
9/12If NPL_SECURITY is set to a lower case drive letter it is ignored.
9/13Problems with ONCE-A-DAY security with Novell Netware 4.0 and 3.11 if the VLM drivers are used.
9/14Problems with detecting a Novell Netware network when Refer to using VLM drivers on a workstation. TN #63 &66
9/15Windows RTP does not recognize finger print with Refer to Novell's VLM drivers. TN #66
9/16Under MS-Windows, the BrightBackground parameter does not work.
9/17If an END SWITCH does not follow a CASE statement, the wrong error displays.
9/18Under protected mode O/Ss, the CONVERT statement may generate memory faults.
9/19Problems with SELECT PRINT address when evaluating a function in immediate mode.
9/20Memory faults with forced exits do to program modification while in a callback from an externallibrary.
9/21Compiling from the 2200 atomized code fromat with -LISTFORMAT .SRC or .LST produces output files with corruped program line numbers.
9/22The statement SELECT #x Dxx used without a slash ("/") may generate errors.
9/23If memory is extremely low (SPACEF < 32 bytes) a RUN command may cause the system to hang or generate bizarre behavior.
9/24Wrong statement is highlighted when error messages for unresolved  FUNCTION/PROCEDURE/DEFFN' /FORWARD declarations4.00.24.00
9/25A large value for the numeric variable used in the ON <val> GOTO statement causes Abonormal Protection termination for the RunTime.
9/26Attempts to load a program containing LINs from a "raw" diskette will generate a D88 error.
9/27A LISTDIM * statement of an array variable does not list all the elements and some of the last elements containing blanks show corrupted information instead.
9/28Problems executing programs with no Release IV eatures, but using a Release III RunTime that passed security with a Release IV Gold Key.
9/29The END statement does not close files as documented.
9/30A LOAD statement executed when the RUN module has an /EXIT procedure may fail to delete the indicated program line range.
9/31Problems with GOTO or GOSUB statment-labels that do not exist.
9/32On the RS/6000, attempts to switch to background partition, ($RELEASE TERMINAL TO <part#> hang the terminal under the C (csh) shell or Korn shell (ksh).
9/33Problems with LINs with LIST STACK DIM4.00.26.00
9/34Problem with FOR/NEXT loops pending when a RETURN or RETURN ERROR exits from a FUNCTION or PROCEDURE4.00.26.00
9/35Problems with the return value of a string FUNCTION sometimes being treated as a modifiable variable.
9/36Under MS-Windows, attempts to press function keys using the Function bar (SF Keys from Option) hang the system when a polling form of KEYIN statement is used.under review
9/37Due to LIN support, some statemens that were previously valid, now generate syntax errors4.00.28.00
9/38Error X75 is not recognized as a recoverable error in INPUT statements.
10/1List 9999 lists all subsequent line numbers, without pause.
10/2Attempts to use a string function as a STR argument results in an error 529.
10/3On 386 versions, if a progrm has a arunaway recursive loop memory faults may occur.4/10.16.00
10/4Use of the /D option with any value over 16 produces an immediate memory fault.
10/5If the HEX(02) bit of byte 42 of $OPTIONS is set, edit mode line insert (CTRL/F1) no longer works, (ALT/0 does work).
10/6The extended form of $SOURCE does not generate a proper p-code label on the file.
10/7Using a variable larger that 64K as the reciever for a $GIO statement results in a memory protection fault.
10/8Execution of a RETURN CLEAR ALL statement inside a FUNCTION/PROCEDURE body causes a /POINTER variable to become corrupted
10/9Applications that have a tight loop within a polling KEYIN loop cause the pointer to switch to an hourglass and remain an hourglass , even outside of the NPL window
10/10The keyboard buffer is not cleared before executing the application boot program.
10/11After the cursor had been turned off using HEX(06), using HEX(05) or HEX(02050F) does not always turn it on again. Open
10/12LOADDCT Afilename@ produces a syntax error. A space is required before the AT@ eliminating the ADC@ makes it work without spaces.
10/13Attempts to open more than 66 files with DATA SAVED DC OPEN causes the terminal to hang
10/14CTRL+R (recall LIN=s) does not work if the LIN is in the middle of the line.
10/15The EDIT OPTIONS Utilityunder the NPL Utilities shows the second page bytes 47 and 48 with no description4.00.34.00
10/16The following code decompiles incorrectly:    10 IF X=Y THEN $DEMO,V4$=@ A

10/15 . 4.00.34

10/16     4.00.33


10/17 An X70 error is generated properly, but when it is used in conjunction with the RESTORE command, it corrupts the line number specified by the RESTORE. 4.00.30

10/18 LIST T AGOSUB@ may report extra occurances of GOSUBs. 4.00.23

10/19 Attempts to save a program that contains long lines generates an error 242. Open

10/20 Under the 386/DOS-Extender the perimeter color does not work. 4.00.33

10/21 If the HELPscreen is invoked after 132 character mode has been established, the 132 character mode is no longer active when the HELP screen terminates. 4.00.33

10/22 The DEMO box loses text if its bottom line is on 23 of the screen. 4.00.30

10/23 RETURN ERROR(x) values from a callback routine cannot be detected by the calling library. 4.10.18

10/24 On 32-bit platforms, the error codes returned by external functions are incorrect if the return value is larger than 255.  4.10.18

10/25 If RTI halts in immediate mode, with a user-generated error that is not in ERRORMSG.HLP, no additional error messages are displayed. 4.10.17

10/26 $OPTIONS byte 48, HEX(02) bit does not work for printers other than LPT1, LPT2, and LPT3. 4.10.17

10/27 DATA LOAD BM and DATA SAVE BM requests for more that 64K if data directed to raw diskettes, fail with error I98. 4.10.17

10/28 LIST STACK may crash RTI, if called when many FUNCTION or PROCEDURE calls are pending.  4.10.16

10/29 If the first arg-3 of a $GIO involves a function call, an address fault mey occur. 4.10.16

10/30 Multi-user RTIWINs may fault at startup if no Novell NetWare or NIAKNETB is detected.  4.10.16

10/31 The decompiler may corrupt indirect calls to GOSUB functions which use an indirect name argument. 4.10.14

10/32 Following an overlay which causes an INCLUDE module to be discarded, a recoverable error that should be caught by an ERROR statement is not caught thereby causing the program to halt. 4.10.14

10/33 RESET sets the STEP # range of all INCLUDEd modules to 0,9999. 4.10.14

10/34 $CLOSE statement leaves status flag set, which can cause a LOAD statement in a subsequently called FUNCTION to fail. 4.10.14

10/35 Passing security as a SUPERVISOR does not properly set the Novell NetWare Network-Wide Once-A-Day flag, unless the prompt to mount your Gold Key is displayed when passing as SUPERVISOR. 4.10.12

10/36 If compiling a program requires relocation to the end of the DISKIMAGE, BS2 hangs or behaves unpredictably. 4.10.18

10/37 If an external DEFFN= function returns a recoverable error, NPL does not clear the RETURN information for the external GOSUB= from the stack. 4.10.08

10/38 The CLEAR command resets SPACEW to a value that does not include the memory used by surviving modules. 4.00.33

10/39 A LIST V statement reports spurious variable references if it has a restricted line number range. 4.00.33

10/40 $FORMAT DISK directed to a non-existent file does not generate an error. 4.00.30

10/41 Access to network files on non-Novell NetWare networks may result in read-only or other inappropriate access capabilities. 4.00.27

10/42 Core dump (or hang/fault) occurs if -OBJFORMAT SCRAMBLED option is selected. 4.00.30

10/43 A LOAD statement executed when the RUN mode has a /EXIT procedure may fail to delete the indicated (or default) program line range, or may get a protection fault on protected mode operating systems. 4.00.28

10/44 If GOTO a statement-label or a GOSUB statement-label references a label that does not exist, the error diagnostic line highlights the following statement on the line. 4.00.28

11/1 Using new $BOXTABLE mode 2, box colors on inverse video areas use the background color instead of text color. 4.20.11

11/2 If a small amount of data is written to a write-protected media, the write protect error does not occur on the DATASAVE statement and a subsequent close using $DEVICE= will cause a memory fault. 4.20.11

11/3 B2C cannot compile pcode programs with $DECLARE, #INSTALL or #INSTALLID syntax in them. 4.20.11

11/4 If $OPTIONS byte 47 is set to HEX(01), (no polling for HALT key) even polling KEYIN statements do not check the windows queue. 4.20.06

11/5 If a program contains LIST statements with line numbers in them, a RENUMBER command that will cause the line numbers to change will usually result in a memory fault. 4.20.04

11/6 Access to Araw@ diskettes either does not work at all or works very slowly 4.20.02

11/7 When running the MS-DOS or 386/DOS-Extender version in a DOS box under MS-Windows, repeated use of the AFail@ option in an AAbort/Retry/Ignore@ help screen can hang MS-Windows. 4.20.02

11/8 Under rare circumstances, the output p-code generated by the compiler is incorrect. It is difficult to predict when the problem will occur except that it will not occur for small (less than 32 sectors) modules 4.20.02

11/9 Speed when printing to local parallel printers is much slower than on previous releases. 4.20.02

11/10 If $OPTIONS byte 43 is set to HEX(01), NPL hogs the Windows interface while printer class files are $OPENed. This should only occur when disk class files are $OPENed. 4.20.02

11/11 The NPLSYS.BS2 SOURCE I/O functions will not decompile a program with a revision label of 1.01. 4.10.31

11/12 If a PROCEDURE / FUNCTION declares a local variable and a static variable with the same name is defined in the module while the program is HALTed after the procedure calls a DEFFN= located outside the body of the PROCEDURE / FUNCTION, then immediate mode references to that variable name are resolved to the local variable, instead of to the module static variable. 4.10.31

11/13 The syntax RETURN(STR(A$())), incorrectly decompiles as RETURN(A$()). The produced code is not equivalent, since it is reserved for (future) function types that return array values. 4.10.29

11/14 RunTime fails to detect a recoverable D81 error if only a single sector is available in the diskimage. 4.20.11

11/15 Under Windows 3.11, configured with Novell=s VLM version of NETWARE.DRV, NPL incorrectly detects a, @Novell Network is running but no NETWARE.DRV is configured in SYSTEM.INI@. The problem occurs on workstations unattached from a network with single user RunTimes installed .4.20.10

11/16 Under Windows95, the browse and SF key bars open in the upper left corner of the desktop. Any attempt to move either window causes an immediate shift of focus back to the NPL Window, making it impossible to move either. 4.20.10

11/17 In a Novell or NetBIOS environment, when a $OPEN / $CLOSE is directed to a local print class device, an unexpected increase of packets are sent to the network when none should be sent. Open

11/18 The RESTORE pointer is not set properly when, an overlay containing new DATA statements is performed, or an INCLUDEd module in the root is deresolved on the overlay. 4.10.29

11/19 RTI386 is substantially slower than RTI when executing polling KEYINs. 4.10.27

11/20 The -p option does not work, with Preboot, or from the command line. 4.10.24

11/21 If a PROCEDURE / FUNCTION declares a local variable and a static variable with the same name is defined in the module while the program is HALTed after the procedure calls a DEFFN= located outside the body of the PROCEDURE / FUNCTION, then immeditate mode references to that variable name are resolved to the local variable, instead of to the module static variable.  4.10.31

11/13 The syntax RETURN(STR(A$())), incorrectly decompiles as RETURN(A$()). 4.10.29

11/14 RunTime fails to detect a recoverable D81 error if only a single sector is available in the diskimage 4.20.11

11/15 Under Windows 3.11, cinfigured with Novell=s VLM version of NETWARE.DRV, NPL incorrectly detects a ANovell Network is running but no NETWARE.DRV is configured in SYSTEM.INI@. The problem occurs on workstations unattached from a network with single user RunTimes installed. 4.20.10

11/16 Under Windows95, the brows and SF key bars open in the upper left corner of the desktop. Any attempt to move either window causes an immediat shipt of focus back to the NPL Window, Making it impossible to move either. 4.20.10

11/17 In a Novell or NetBIOS environment, when a $OPEN / $CLOSE is directed to a local print class device, an unexpected increase of packets are sent to the network when none should be sent. Open

11/18 The RESTORE pointer is not set properly when:  An Overlay containing new DATA statements is performed.  An INCLUDEd module in the root is deresolved on the overlay.  4.10.29

11/19 RTI386 is substantially slower than RTI when executing polling KEYINs. 4.10.27

11/20 The -p option does not work, with Preboot, or from the command line. 4.10.24

11/21 A program line containing a DATA statement with more than 9 elements is destroyed, as shown when attempting to list or edit the line.

11/22 NPL fails to detect ABASIC2C_ID=xx@ when set in a stand alone configuration. 4.10.18

11/23 NPL fails with a P48 error when the PRINT option is selected from the HELP screen. 4.10.18

11/24 ($IF ON /001,xxx) branches regardless of a keystroke at startup, if debug is on. 4.10.18

11/25 A callback to NPL during a $BREAK statement is disabled, it should not be. In addition, a HALT key pressed during a $BREAK is not detected immediately and should be. 4.10.25

11/26 Pressing SFkeys (including TAB = SF=126) when the current program module containing GOSUB= references to the same function, but no DEFFN= definitions for the referenced function can result in garbage being displayed as if there were a marked function key literal, i.e. DEFFN= 126 "Lots of garbage@. 4.10.25

11/27 If SELECT LOG is enabled, a KEYIN statement can cause the RunTime to fault. 4.10.25

11/28 If an INPUT SCREEN or PRINT SCREEN specifies line and rows values such that line+rows = 25, this should be flagged as a range error. It is not. 4.10.26

11/29 When accessing communications ports with MXE=Y option, if the first statement directed to the device is not a $OPEN, access to the file will return incorrect information and can result in address faults and crashes. 4.10.25

11/30 If an INPUT statement containing arguments involving FUNCTION calls is exited via a special function key, when the DEFFN= function RETURNs, the INPUT statement doe not restart from the beginning. The program can get errors, hang, or crash the operating system. 4.10.25

11/31 If a program has a PUBLIC section containing INCLUDE statements, scoping rules for USES statements may not apply. 4.10.25

11/32 Applications that INCLUDE many modules within their own PUBLIC section may be unable to reference named PUBLIC sections with a USES statement. 4.10.25

11/33 If a line function ( e.g. DEF FNA(X) ) within a FUNCTION or PROCEDURE body uses a dummy variable which is also passed to the function as a /POINTER parameter, evaluating the function can hang or crash RTI. 4.10.25

11/34 If the number of open files is extended with a SELECT #nn statement, the extension area could be deleted before the /EXIT procedure was run, resulting in an invalid file number error. 4.10.24

11/35 Compiling expressions which use functions can result in incorrect expression evaluation order. A numeric function followed by numeric operators is executed as if in parentheses, even where it is not. 4.10.24

11/36 If the Debug Window is shut down while immediate mode commands are in progress, a fault can occur. 4.10.24

11/37 DATA SAVE DC CLOSE #x statement leaves flag set that can cause a subsequent LOAD executed in a PROCEDURE or FUNCTION to fail. 4.10.24

11/38 /EXIT procedures may not run to completion if RTIWIN is shut down with the >Close= system menu option or by a general windows shutdown. 4.10.24

11/39 External libraries that use floating point and do not have an RTPEXT_SHAREABLE function occasionally crash with a kernel GPF. 4.10.23

11/40 If a LIST function pauses with a --MORE-- prompt, and a $DEMO script is active to supply the (-RETURN-) key, the LIST will not continue properly ( or the program may hang). 4.10.23

11/41 If a LIST option with a restricted line number range is entered or executed immediately before a program SAVE or RESAVE operation, the SAVEd program may have an invalid p-code label and may not load if the program uses Release IV syntax. 4.10.23

11/42 Some versions of NETX.EXE (esp 3.31) do not report locking errors correctly to RTI, this can result in I98 errors, especially if the HEX(01) bit in $OPTIONS byte 39 is set. 4.10.22

11/43 When using true boxes on a W2236 terminal, the interior on BOX displays, displayed during $DEMO scripts, may contain pieces of previously existing boxes. 4.10.22

11/44 Unstructured exits (e.g. LOAD T, LOAD RUN, CLEAR, $END) from an automatically invoked /EXIT procedure crash the RunTime or behave erratically. 4.10.22

11/45 If a program HALTs or STOPs while in an automatically executing /EXIT procedure, when the program is CONTINUEd, an address fault occurs when it completes the PROCEDURE. 4.10.22

11/46 Hardware interrupts can corrupt the stack if RTI is executing a critical code section during a program overlay. This is most likely to occur when the PC is used as a server ( non-dedicated Novell or peer-to-peer) under heavy interrupt load. 4.10.21

11/47 An indirect specification of a string function requires a >$= in the alpha-var used for the name. ( It should not be required.) 4.10.21

11/48 A LIST D after a LIST > that referenced named DEFFN=s did not properly show referenced lines ( with a >-= preceding the line number). 4.10.20

11/49 If a program is HALTed while automatically executing the /MAIN procedure of an INCLUDE module, the >Warning - RUN statement is incomplete= message should appear, as it does for STOP statements, but doesn=t. 4.00.20

11/50 Stepping through a program SAVE or RESAVE statement results in an improperly saved program. .4.10.20


blank.gif (841 bytes)

Niakwa, Basic-2C and NPL are trademarks of Niakwa, Inc. All other products mentioned are registered trademarks or trademarks of their respective companies.

Questions or problems regarding this web site should be directed to
Copyright 1996-2010 Niakwa, Inc. All rights reserved.
Last updated: Thursday January 07, 2010.