Niakwa, Inc.

    

 


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

swiggle_small.gif (991 bytes)

Bug Report #6
for Niakwa Programming Language Release III
Report Date - March 2, 1993

This report lists known problems in Niakwa Programming Language Release III for all platforms supported, which were discovered after July 1992. This report is in addition to Bug Reports 1 through 5. This report is available on the Niakwa BBS and can be downloaded along with a Bug Report Index.

NOTES: Bugs are numbered, by Bug Report, starting with Bug 1. The following number, in parentheses, represents the internal Niakwa bug code number.

Some bugs described in this report are corrected in a revision of the NPL RunTime that is not yet available for the field.

For the latest product release available refer to the latest Niakwa Newsletter or the Niakwa BBS.

Revision 3.21.07.00 of the NPL RunTime is available as a free update for MS-Windows installations on the Niakwa BBS or upon request. Other NPL platform versions will be updated as they become available.

1. Problem: (00454)

Attempts to use raw format diskettes on a 486 IBM PS/2 Model 57 with a 2.88 MB floppy drive and Controller result in I93 errors, regardless of the format of the diskette (720K or 1.44 MB).

Solution: Under Review

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20 and greater

Platforms: DOS, Novell NetWare

2. Problem: (00453)

The RENUMBER statement does not properly renumber entries for LIST statements.

For example:

100 LIST 9000

9000 I=30

When the command RENUMBER TO 10 STEP 100 is issued, the program lists as follows:

10 LIST 9000

100 I=30

Solution: Under Review

Programs Affected: RTI

Revision Number: 3.20 and greater

Platforms: All

3. Problem: (00434)

If the user invokes the HELP processor with the DOS/Novell option during a LINPUT statement after the RunTime has been started in graphic mode (/G option), the input buffer becomes corrupted and returns to the RunTime.

The problem does not occur if the IBMFONT0.EGA file is copied in the sub-directory where the RunTime is started.

Solution: Under Review

Programs Affected: RTI, RTP

Revision Number: 3.20 and greater

Platforms: DOS, Novell NetWare

4. Problem: (00433)

If the HELP processor is invoked and immediately followed by the option CONTINUE or FAIL OPERATION, while executing a program that invokes a bright attribute, the bright attribute is lost when control is returned to the program.

Solution: Under Review

Programs Affected: RTI, RTP

Revision Number: 3.20 and greater

Platforms: DOS, Novell NetWare

5. Problem: (00432)

Under Windows on a monochrome terminal, all options offered by the HELP processor are displayed in reverse video, making it very difficult to know where the cursor is positioned.

Solution: Under Review

Programs Affected: RTI, RTP

Revision Number: 3.20 and greater

Platforms: MS-Windows

6. Problem: (00429)

Under Windows, if a $OPEN is performed to a hogged diskimage, all tasks on the workstation (NIAKWA and/or non-NIAKWA) slow down considerably.

Solution: Corrected in Revision 3.21.05.00.N or greater.

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

7. Problem: (00427)

Under Windows, attempts to set #PART to any value greater than 112 result in the error message, "Partition <#> mapped to network partition 113 number exceeds maximum".

Solution: Under review.

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

8. Problem: (00426)

Executing a LIST' with a restriction on the range of lines to be scanned results in errors in subsequent GOSUB' statements which reference DEFFN' lines outside the restricted line number range.

For example:

10 GOSUB' 1

20 LIST' (10,30)

30 GOSUB' 2

40 STOP

50 DEFFN' 1: RETURN

60 DEFFN' 2: RETURN

when executed, the following will result:

???? DEFFN' 1

- 0010

???? DEFFN' 2

- 0010

30 GOSUB' 2

ERR 237 - Undefined Marked Subroutine.

If the program is reRUN or a LIST' without a line number restrictions is performed, the DEFFN' access problem is corrected.

Solution: Corrected in Revision 4.00.05 or greater

Programs Affected: RTI, BESDK

Revision Number: 3.00 and greater

Platforms: All

9. Problem: (00425)

If the TRACE' debugging tool is turned on during a call to an external GOSUB' that has more than 16 parameters, the system may hang or otherwise behave erratically (generating A09 errors).

Solution: Corrected in Revision 3.21.04.00. or greater.

Programs Affected: RTI, BESDK

Revision Number: 3.00 and greater

Platforms: All

10. Problem: (00418)

Under Windows, if F3 is pressed after F5, while the function key bar is "in use", both function pads move. Function F3 does not generate any codes, it's only a visual problem.

Solution: Under review.

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

11. Problem: (00414)

Under Windows, when the Autosize option is on and the window is maximized, some space will still be left unused on the top-left of the Windows. This space should exist only when the windows are not maximized to avoid characters jamming against the margins. Automatic sizing calculations for maximized windows still deduct the margin amounts before computing the best results.

Solution: Under review.

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

12. Problem: (00413)

In a program that contains line numbers greater than 9999, fatal errors that occur on lines below 9999 may appear with "?" following the line number. Fatal errors that occur on lines above 9999 are displayed incorrectly (as a number containing hexadecimal digits).

Solution: Corrected in Revision 3.20.22.00 or greater.

Programs Affected: RTI, BESDK

Revision Number: 3.20 and greater

Platforms: All

13. Problem:(00412)

If -LSTFORMAT 2200 (or 2200S) is selected during a compile run, and the compiled program already exists in the specified LSTLOC diskimage, but the new version does not fit in the previously allocated area, the warning:

Program was moved to end of catalog in LSTLOC diskimage

appears, and the program is moved to the end of the catalog. However, the specified program is corrupted.

Solution: Corrected in Revision 3.20.22.00 or greater.

Programs Affected: B2C

Revision Number: 3.00 and greater

Platforms: All

14. Problem:(00411)

If -LSTFORMAT 2200 (or 2200S) is selected during a compile run, and the index of the specified LSTLOC diskimage becomes full , an error message is printed:

Fatal - (Line xxxx) Diskimage is index is full (LSTLOC).

However, the index of the LSTLOC diskimage is damaged. Files of type ?P may appear in the catalog listing and may be inaccessible.

Solution: Corrected in Revision 3.20.22.00 or greater.

Programs Affected: B2C

Revision Number: 3.00 and greater

Platforms: All

15. Problem:(00410)

Under AIX, attempts to compile from ASCII code to p-code/OBJ format result in the error message "no names found in" when the ASCII (.SRC) file is not in the current directory.

For example:

From /usr directory the following command:

b2c /usr/BASIC2C/uextrn/include/MYBOOT

generates the above error.

If the ASCII file is located in the current directory, the problem does not occur.

Solution: Under review.

Programs Affected: B2C

Revision Number: 3.20.15.07.U and greater

Platforms: IBM RS/6000 or any later "C" port platforms.

16. Problem:(00408)

If $PACK is used to pack numeric variables with large exponents (exceeds 32767), the system may hang.

For example:

10 DIM $(10)20

20 SELECT ERROR > 69

30 T0=1/0

: Q=1

40 $PACK (F=HEX(5004)) O$ FROM T0

: ERROR PRINT "ERROR"

Solution: Corrected in Revision 3.20.21.00 or greater.

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.00 and greater

Platforms: All

17. Problem: (00404)

In some very rare cases, a MOVE END on a diskimage immediately followed by a reboot of the system makes the programs and data files residing in the new allocated extent inaccessible. A LISTDCT results in error I93 - "Format error" for the files located in the newly allocated area.

NOTE: This problem was reported from the field and it could not be replicated in-house.

Work Around: After each reboot, create a dummy file using DATA SAVE DC OPEN.

Solution: Under review.

Programs Affected: RTI

Revision Number: 3.20.02.00.S and greater

Platforms: SuperDOS

18. Problem: (00403)

MOVE END, SCRATCH DISK and MOVE (of entire diskimage) operations will perform an implicit $CLOSE which will overwrite even an explicit $OPEN.

For example:

10 $OPEN/D20

20 MOVE END t/D20, =2000

will close device D20 even though an explicit $OPEN was issued. If line 20 is replaced by a DATA LOAD or DATA SAVE statement, the OPEN will still be in effect at the completion of the command in line 20.

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 2.xx and greater

Platforms: All

19. Problem: (00402)

Under Windows, if the start up option /D is used to increase the number of device entries to a value greater than 253, the following error message is generated:

Cannot allocate more file handles for /D OPTION. Recommend system.ini {Standard Option} contain ReservedMemoryLow=1 line if you want to use the /D Option. Press OK or CANCEL.

Pressing CANCEL generates a General Memory Fault error on the RTIWIN.EXE program.

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

20. Problem: (00401)

DATA statements using Niakwa characters with HEX equivalents between 00 - 1F are translated automatically to their hex codes when these characters are used in coding. This problem occurs even when $KEEPREMS=HEX(02) is used.

For example:

10 DATA "šndern nummer"

: REM data statement used in GERMANY

will list:

10 DATA HEX(156E444....)

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 2.00 or greater

Platforms: All

21. Problem: (00401)

Attempts to perform string operations using AND/OR operators between hex codes and other characters decompile incorrectly, automatically translating the characters to their equivalent hex codes.

For example:

10 DIM A$1

20 A$=HEX(00) OR "@"

will list as follows:

10 DIM A$1

20 A$=HEX(00) OR HEX(40)

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 2.00 or greater

Platforms: All

22. Problem: (00400)

Sometimes, under Windows, if more than 128K has been allocated to the workspace, execution of a CLEAR or a LOAD RUN may generate a UAE (Windows 3.0) or 'Unknown' fault (Windows 3.1).

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00 or greater

Platforms: MS-Windows

23. Problem: (00399)

Under Windows, if the printer is deselected while printing to a local printer (LPT1), data is lost.

Solution: Corrected in Revision 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N or greater

Platforms: MS-Windows

24. Problem: (00398)

Under Windows, if the printer buffer becomes full while printing to a local printer (LPT1), all Windows tasks hang until the next line is printed.

Solution: Corrected in release Rev. 3.20.21.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N or greater

Platforms: MS-Windows

25. Problem: (00370)

Attempts to execute code that contains GOSUB' and DEFFN' with more than 16 parameters, in which the last parameter is a string, may sometimes result in a RunTime stack error:

ERR 02: Value Stack Overflow

LINBLOCK Stack check failed.

Solution: Corrected in Revision 3.20.17.00 or greater

Programs Affected: RTI, RTP, B2C

Revision Number: 3.20.02.00 or greater

Platforms: All

NOTE: The code must be recompiled with Revision 3.20.17.00 or greater to correct this problem.

26. Problem: (00366)

Use of two ALL(x) statements in the same line is not detected as an error by the RunTime, but it generates erroneous code.

For example:

10 A$="1" & ALL ("2") & ALL ("3")

20 PRINT A$

will LIST as:

10 A$="1" & ALL("2")

: ELSE "3" ?

20 PRINT A$

Solution: Corrected in Revision 3.20.16.00 or greater

Programs Affected: RTI, RTP

Revision Number: 2.xx or greater

Platforms: All

27. Problem: (00365)

Use of an undefined variable in an INIT statement with multiple variables decompiles incorrectly.

For example:

10 DIM C1$(10)10

20 INIT(" ")C1$(),C3$()

If a RUN command is issued, error P55 - "Undefined variable" is correctly generated, but line 20 is displayed as follows:

20 INIT(" "C)1$(),C3$()

Solution: Corrected in Revision 3.20.16.00 or greater

Programs Affected: RTI, RTP

Revision Number: 2.xx or greater

Platforms: All

28. Problem: (00363)

If an icon from a third-party product is used to identify a minimized RunTime task, after the task has been minimized, attempts to restore or maximize the task sometimes result in UAEs (Windows 3.0) or GPEs (Windows 3.1).

Solution: Corrected in Revision 3.20.17.00.N or greater

Programs Affected: RTI, RTP

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

29. Problem: (00362)

If TRACE V output is directed to a print file, the first line of the output will display "!=" instead of the variable name.

Solution: Corrected in Revision 3.20.16.00 or greater

Programs Affected: RTI, BESDK

Revision Number: 3.00 or greater

Platforms: All

30. Problem: (00360)

Any GOSUB' issued in immediate mode generates UAEs (Windows 3.0) or GPEs (Windows 3.1).

For example:

10 DEFFN'123 (Y)

After the program is RUN, any attempt to issue a GOSUB'123 in immediate mode results in a MS-Windows error.

Solution: Corrected in Revision 3.20.17.00 or greater

Programs Affected: RTI, BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows

31. Problem: (00353)

Use of RENUMBER with a STEP value greater than 9999 can result in invalid renumbered line numbers.

Solution: Corrected in Revision 3.20.17.00 or greater

Programs Affected: RTI, BESDK

Revision Number: 3.20.02.00 or greater

Platforms: All

32. Problem: (00347)

In certain instances, when moving any Niakwa or non-Niakwa window on top of a Niakwa based window with Autosize OFF, the text in the Niakwa window appears ripped (shifted down one-half line from where the overlay window was).

Solution: Corrected in Revision 3.20.16.00 or greater

Programs Affected: RTI, RTP, BESDK

Revision Number: 3.20.11.00.N or greater

Platforms: MS-Windows

33. Problem: (00346)

On occasion, attempts to start, close, and re-start four or more windows running the Niakwa MS-Windows RunTime with External calls will result in:

Insufficient DOS memory to pass security.

Ensure there is 16k free DOS memory.

Solution: Under Review

Programs Affected: BESDK

Revision Number: 3.20.11.00.N

Platforms: MS-Windows 3.0

 

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 webmaster@niakwa.com.
Copyright © 1996-2010 Niakwa, Inc. All rights reserved.
Last updated: Thursday January 07, 2010.