| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | New Problem With Warp |
I have a confusing problem with WARP v3. I wrote a program a LONG time
ago that worked fine under OS/2 v2.0 and OS/2 v2.1, but gives memory
access violation errors under WARP v3. I wrote it using the 16 bit
system calls from OS/2 v1.x. (That is the only import library I had at
the time.) However, now it fails. It is multi-threaded with a second
thread handling screen output using data supplied by the first thread.
The second thread creates a local variable on the stack and formats
screen output there. Then calls DOSWRITE to print it. Below is the
section that actually errors out.
push 1 ;screen print
push ss ;segment containing data
push dx ;offset of data in segment
push di ;length of data
push ss ;segment of receiving variable
push si ;offset of receiving variable
call doswrite ;system call
For some reason, the call to DOSWRITE won't work now.
---
* MR/2 2.0 #99 * Internet: bob.liles{at}tpl-bbs.com RIME: ->7
--- QScan v1.131b / 01-0169
* Origin: The Party Line * Memphis * 901-755-4531 (1:123/5)SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 949 712/353 623 713/888 800/1 @PATH: 123/5 4 301 3615/50 229/2 12/2442 711/409 54/54 711/808 809 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™.