---------------------------------------------------
    Versions: 3.0/3.1/3.2
    Known   : No
    This internal Variable should return the number of currently displayed
    columns on the screen. In connection with all modes that do not use
    the 40 or 80 column mode, an incorrect number will be returned. Such
    modes can be set on every VGA-Card and quite a few Tools (i. e. Disk
    Command Center) even support them!
    This little FUNCTION can solve this problem:
            DIM fixScrnCols AS BYTE
            ! mov  ah, &h0f
            ! int  &h10
            ! mov fixScrnCols, ah
    2.20. Incorrect internal Function/Variable: pbvHost
    ---------------------------------------------------
    Versions: 3.0/3.1/3.2
    Known   : No
    Bit 8 is not set under Microsoft Windows(NT) 3.x
    2.21. A little difference in the new InLine-ASM of V3.1/3.2
    ------------------------------------------------------------
    Versions: 3.1/3.2
    Known   : Correction demanded at PowerBASIC Inc.
    This is explained quickly. While PowerBASIC 3.0 accepts the following
    line of Inline-Assembler code:
            ! mov ax, &h0A000
    PowerBASIC 3.1/3.2 will not work with it, even if this feature is new
    in Version 3.1/3.2.
    2.22. The dd-Problem in PowerBASIC 3.1/3.2
    -------------------------------------------
    Versions: 3.1/3.2
    Known   : Correction demanded at PowerBASIC Inc.
    This is a quickly described Bug, because the new 32Bit &h...., &o....
    &b Commands are seen as common knowledge. PowerBASIC simply forgot the
    implementation of them in the Inline-Assembler!! You don't believe me,
    the try the following:
            ! dd &h12345678
    It still has to be cleared why the command 'dd' exists in PowerBASIC
    3.0/3.1 & 3.2 anyways. ;-)
    2.23. Undocumented internal Variables in PowerBASIC 3.0/3.1/3.2
    ---------------------------------------------------------------
    The following internal Variables already exist in PowerBASIC 3.0, but
    are not documented:
    pbvBinBase
    pbvDefSeg
    pbvHost
    pbvScrnBuff
    pbvSwitch
    pbvVTxtX1
    pbvVtxtX2
    pbvVTxtY1
    pbvVtxtY2
    The following internal Variables are not documented from Version 3.1
    on, but still exist:
    pbvRestore
    The position of the Datasegments are identical in PowerBASIC 3.0 and
    PowerBASIC 3.1/3.2.
    2.24. The PRINT-Bug in PowerBASIC 3.2
    -------------------------------------
    Known    : ????
    In Version 3.2 of PowerBASIC Variables of type DWORD are not printed
    correctly with PRINT:
    Example:
            Demo??? = 1234567890
            PRINT Demo???
    causes the following output:
    PowerBASIC 3.0/3.1: 1234567890
    PowerBASIC 3.2    : 1.234568+E
    Using PRINT USING can help here...
--- CrossPoint v3.11 R
 * Origin: PBSOUND, PBFILES (20MB), PBFAQ, PBRULES, PBHIVGA at: 
2:2410/330.1)
---------------

FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC   Ref: E1400004 Date: 01/01/97
From: THOMAS GOHEL                                          Time: 12:00am
\/To: ALLE                                                (Read 3 times)
Subj: FAQ: PowerBASIC 05/16 (Bug's - Part 3)

    2.25. The "File not found"-Error after using NAME
    -------------------------------------------------
    Versions: 3.0/3.1/3.2
    Known   : No
    There is a very strange Error in the internal PowerBASIC filehandle
    management after using the command "NAME".
    Example:
           OPEN "B",1,"DATEI1.TMP"       ' Open first file
           OPEN "B",2,"DATEI2.$$$"       ' Open
           CLOSE 2                       ' ... and close immediately
           OPEN "B",3,"DATEI3.TMP"       ' Open
           CLOSE 3                       ' ... and close immediately
           KILL "DATEI2.$$$"             ' Delete second file
           NAME "DATEI3.TMP" AS "DATEI2.$$$"
                                         ' Rename third file to second file
           CLOSE 1                       ' ... Close first file
           END
    2.26. Calculationerror when using Constants
    -------------------------------------------
    Versions: 3.0/3.1/3.2
    Known   : No
    Sometimes PowerBASIC does not calculate correctly when using
    constants. Of course there is the question why you don't insert the
    answer right away, because it is just a matter of form.
    Example:
           i% = -20-4   : %k= -20-4
           PRINT i%     , %k
    2.27. Wrong "Bit movement" with ROTATE
    --------------------------------------
    Versions: 3.0/3.1
    Known   : Error corrected in Version 3.20
    The ROTATE-Command in PowerBASIC 3.0/3.1 has a Bug when using QUAD-
    Type Varibles.
    Example:
           i&& = 1
           ROTATE RIGHT i&&, 1
           ROTATE LEFT i&&, 1
           PRINT i&&
    2.28. Overflow when using FOR/NEXT-Schleifen