home *** CD-ROM | disk | FTP | other *** search
- 2-5
- H#: 56271 S12/SPECTRA Publishing
- 12-Jul-90 16:21:00
- Sb: GET graphics bug
- Fm: Kurt Inman (PowerBASIC) 71141,2330
- To: ALL
-
- We have confirmed an error in the PowerBASIC Reference Guide concerning the
- formula used to determine the size of an array required for a GET graphics
- statement. Internally, the current version of PowerBASIC uses the same
- incorrect formula. This frequently results in too small of a data area to hold
- the graphics image, which may cause serious side effects. Please change page
- 133 in your manual as follows:
-
- The correct formula is:
-
- # of bytes required = 4 + INT((X * BitsPerPixelPerPlane + 7) / 8) *
- Planes * Y
-
- where X is the horizontal image length, Y is the vertical image length, and
- BitsPerPixelPerPlane and Planes depend on the screen mode selected:
-
- Screen mode BitsPerPixelPerPlane Planes -----------
- -------------------- ------
- 1 2 1
- 2 1 1
- 3 1 1
- 7 1 4
- 8 1 4
- 9 1 4
- 10 1 2
- 11 1 1
- 12 1 4
-
-
- Kurt Inman PowerBASIC R&D
-
- Press <CR> for next or type CHOICES !
- H#: 56272 S12/SPECTRA Publishing
- 12-Jul-90 16:23:04
- Sb: Calling PB SUBs from ASM
- Fm: Kurt Inman (PowerBASIC) 71141,2330
- To: ALL
-
- As described on pages 290-291 of the Users Manual, PowerBASIC SUBs and
- FUNCTIONs may be called from assembler routines which are $LINKed into your
- programs. The manual fails to point out, however, that when a SUB or FUNCTION
- is called, it may alter the contents of the AX, BX, CX, DX, SI, DI, and ES
- registers. If your assembler routine expects the contents of any of these
- registers to remain constant, both before and after a PowerBASIC routine is
- called, you must save the appropriate registers before performing the call and
- restore them afterwards. Also, prior to calling a PowerBASIC routine, the DS
- register must contain the same value that it had when your assembler routine
- was invoked (PowerBASIC's main data segment).
-
-
- Kurt Inman PowerBASIC R&D
-
- Press <CR> for next or type CHOICES !
- H#: 56586 S12/SPECTRA Publishing
- 15-Jul-90 14:37:35
- Sb: #COM3/COM4
- Fm: Bob Zale: PowerBASIC R&D 76304,1303
- To: ALL
-
- Help ? ? Who is an expert on COM3 and COM4 implementations? We know that
- frequently they share IRQ3 and IRQ4 with COM1 and COM2, but that prevents
- simultaneous serial i/o on COM1/COM3 and COM2/COM4. It seems likely that some
- implementations would utilize the slave interrupt controller (IRQ9,10,etc.) to
- avoid this problem. Who has the answers? We would REALLY APPRECIATE hearing
- from you! Thanks!
- Bob Zale (PowerBASIC R&D)
-
- There is 1 Reply.
-
- Press <CR> for next or type CHOICES !
- H#: 56623 S12/SPECTRA Publishing
- 15-Jul-90 23:15:35
- Sb: #56586-COM3/COM4
- Fm: David A.J. Wedell 70215,151
- To: Bob Zale: PowerBASIC R&D 76304,1303 (X)
-
- I'm no expert, but I do know that since most I/O cards are 8-bit, they can't
- use IRQ's 9-15. However, you might consider talking with the Novell forum
- (NOVA), their NetWare 386 can communicate with LPT1-3, and COM1-4 for 7
- printers AT THE SAME TIME, and they don't use the Interrupts. I don't know if
- that helps, but it certainly dosen't hurt.
-
- David Wedell 70215,151
-
-
-
- Press <CR> for next or type CHOICES !
- H#: 56659 S12/SPECTRA Publishing
- 16-Jul-90 07:52:59
- Sb: put,get arrays
- Fm: John Gessner 71131,3256
- To: all
-
- Thanks for the help on the array corrupting while getting and putting. Here is
- a suggestion: I would like to be able to get into a multidemensional array to
- make it easier to do selective putting. For instance: I have the picture of
- the six sides of a die. It would be nice to do DIM DIE( 6 , 420 ) and then get
- each picture into a separate demension. Then it is easy to roll the die and
- PUT DIE(1), DIE(2) and so on. Without that I have to go through a small bit of
- extra code to put the right array. Just a suggestion.
-
- Press <CR> for next or type CHOICES !
- HPC Vendor B ForumHSubjects Menu
-
- Subject (# msgs)
-
- Section 12 - SPECTRA Publishing
- 1 Suggestion for PB (3)
- 2 GET graphics bug (1)
- 3 Calling PB SUBs from ASM (1)
- 4 COM3/COM4 (2)
- 5 put,get arrays (1)
- HEnter choice(s) !