| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | ASM... |
ET> OK. For using MASM/TASM on DOS, is there any specific porting ET> functions that you need to define or do before it compiles? /Oi if you use TASM. (so TASM generates standard .OBJ-files without Borland extensions) ET> under OS/2 which is a serial communication library. The second is some ET> screen functions in my user interface, such as mouse functions, filling ET> functions, color functions, text saving and restoring functions, cursor Screen functions are pretty easy to port. First you get the address to the logical screen buffer and then you write to it instead of 0xB800:xxxx, then you call VioShowBuf() to tell OS/2 which parts of the screen you have modified. If you already support Desqview then you probably can port your routines in an hour or two. I've never tried porting mouse routines but it seems pretty simple to me. --- (2:201/274.64)* Origin: Microsoft's Motto:"We're the leaders, wait for us!" SEEN-BY: 50/99 78/0 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2808 2809 @PATH: 201/274 200 2104 109/347 18 13/25 396/1 270/101 712/515 711/808 809 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.