---------------------------------------------- Versions: 3.0/3.1 Known : Seems so A nice effect is to be reported, when you compile Sources more than once and then compare them with a Filecompare-Utility. If your free Memory has changed, the created EXE-Files will be different. As far as I see it, the two PowerBASIC Compilers save some Information about the system they were compiled on, which are of Integer/Word type and are at the Offset's &h9C/&hA0. (PB3.1) This effect can be shown as well in the PB-IDE as with PBC. Some say that PB-EXE-Files which were compiled under a PowerBASIC- Shell with PBC seem to crash more often. But even since I have been compiling all of my projects like this for two years, I can not approve to this effect. Version 3.0 of the PowerBASIC-Compiler SHELL seemed to cause other effects with big EXE- Files. The problems were solved back then by using an alternativ PBSHELL-Command. 2.7 Problems with the Mouse within the IDE ------------------------------------------- Versions: 3.0 Known : Seemingly corrected in Version 3.1 Should you work with a Mouse in the IDE, so that you can insert and cut Sorucecode easily, this could cause a partly crash when marking long texts which go past the right screen border. Furthermore the Mousecursor does not mark the text correctly. There also seem to be some problems when using the Mouse in the 80*43 /50 Mode. 2.8. The Fixup Overflow Syndrome -------------------------------- Versions: 3.0/3.1/3.2 Known : Correction demanded at PowerBASIC Inc. This is my favorite Bug, since it is actually caused by a real error in the programming of a PowerBASIC- User. The description in the Manual, as well as in the Online-Help is slightly irritating, but principally correct. Personally I would decribe the Bug like this: < new Bugdescription > PowerBASIC could not find the named Jumpaddress. A possible cause for this is a SHORT-Jump to a Label not in the valid Area for a SHORT- Jump. Please check all Jumpcommands for validity. < End > There is a small Bug in this Errormessage in both PowerBASIC Versions. But since the human mind will not really believe what is written there, the Source is compiled again (without change). The IDE crashes for doing that immediately. I will save myself a closer description of the working of the different Assemblercommands, especially the different ways of addressing in relation to the CPU. There are many Assemblerbooks out there, and they are something really needed for good programming with the Inline-Assembler anyways. 2.9. The thing with ASCII-154 after a REMARK in the Inline-Assembler -------------------------------------------------------------------- Versions: 3.0/3.1/3.2 Known : No For example there is a nice little thing that can drive you crazy when doing good commenting in the Inline-Assembler Source.It's the thing with the ASCII-154 after a REMARK (REM or ; ): Example: CLS PRINT "1" ! nop ; Ue <- (ASCII-154) PRINT "2" PowerBASIC will in this case continue the running of the program the the line with the ASCII-154 (after the REM) and then stop. The hard-on guys can trace the whole thing with the Debugger. They'll notice that in this case PowerBASIC will simply add seven ASCII-Zeros to the Code and then stops compiling. --- CrossPoint v3.11 R * Origin: Magics: PBSOUND, PBFILES (20MB), PBFAQ, PBHIVGA at: (2:2410/330.1) --------------- FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC Ref: DG300003 Date: 12/01/96 From: THOMAS GOHEL Time: 12:00am \/To: ALLE (Read 4 times) Subj: FAQ: PowerBASIC 04/16 (Bug's - Part 2) 2.10. Error 454: END FUNCTION expected --------------------------------------- Versions: 3.0/3.1/3.2 Known : No This Bug can occur when a comment in an Inline-Assemblerline contains the ASCII- 154. Please read the previous paragraph for more information. 2.11. Another REMARK-Problem with $ALIAS ---------------------------------------- Versions: 3.0/3.1/3.2 Known : No This Bug is easily described. You may not use a ':' (ASCII 58) after a REMARK when using $ALIAS, becaue PowerBASIC interprets it as an Error 462 (undefined SUB/FUNCTION). Example: $ALIAS DATA AS "_DATA" ': Fit C-Segments to PowerBASIC ^ causes Error 462 2.12. The Mistake CDWRD in the OnLine-Hilfe ------------------------------------------- Versions: 3.0 (possibly only German Version) Known : Mistake corrected in German Version 3.0? There is a small typpo in the in the OnLine-Help. Instead of 'CDWD' (the correct Command), 'CDWRD' was written. The Syntax is spelled correctly in the Manuals. Example: i??? = 1 PRINT CDWRD(i???) : 'wrong Syntax PRINT CDWD(i???) : 'correct Syntax 2.13. The Mistake CVDWRD in the OnLine-Hilfe -------------------------------------------- Versions: 3.0 (possibly only German Version) Known : Mistake corrected in German Version 3.0 beseitigt? This time the typpo is 'CVDWRD'. Correct Syntax is 'CVDWD'. The Syntax is correct in the Manuals. 2.14. Crash when pressing CTRL-C -------------------------------- Versions: 3.0 Known : Bug corrected in Version 3.0 This Bug is widely known and only occurs when you set the Compileroption $OPTION CNTLBREAK OFF while the BREAK-Flag in DOS is set to ON. (Usually it is set to OFF by MS-DOS). When you press CTRL-C under these circumstances your finished program will simply crash. You can get past this by locking the BREAK-Flag using your own PowerBASIC-FUNCTION. You can achieve this using the following routines: SHARED BreakFlag% FUNCTION BreakAus public 'Save and deactivate CTRL-BREAK Interrupt ! mov ax, &h3300 ! int &h21 ! mov BreakFlag%, dx ! mov ax, &h3301 ! mov dx, 0 ! int &h21 END FUNCTION FUNCTION BreakReset public 'Restore Control-Break-Interrupt ! mov ax, &h3301 ! mov dx, BreakFlag% ! int &h21 END FUNCTION You can find a file named CNTL.ZIP in some BBS's, it is the official BugFix. 2.15. Error when producing Output with "CONS:" and CTRL-C