|
Re: assembly
|
Chris Hoppman
|
Feb 27, 2004 09:35 PST
|
--- Veit Kannegieser <v-@Informatik.TU-Cottbus.DE>
wrote:
| | Chris Hoppman wrote:
| | asm
mov ah,04h
mov dx,FosPort
mov bx,4f50h
int 14h <--- this part.
mov t_ax,ax
end;
|
This uses function
INT 14 - SERIAL - EXTENDED INITIALIZE
(CONVERTIBLE,PS)
AH = 04h
AL = break status
00h if break
01h if no break
BH = parity (see #00307)
BL = number of stop bits
00h one stop bit
01h two stop bits (1.5 if 5 bit word
length)
CH = word length (see #00308)
CL = bps rate (see #00309)
DX = port number
Return: AX = port status code (see #00304,#00305)
| | I was am under the assumtion you could include
|
calls
| | to bios interrupts via the asm code block.
|
Sure, but only for DOS targets. for 'real' operating
systems, you have to use filesystem like functions
(open COMx, do some control messages,..)
Usually, you would use some communication library
unit.
Veit Kannegieser
|
So, I wouldn't be able to communicate with a DOS
interrupt in asm with VP.
-Here is the libary I was working with:
http://www.bsdg.org/swag/COMM/0017.PAS.html
I was hoping to use it in vp, to communicate with a
DOS Fossil driver that controls output/input to older
software that was made in the early 90's. Which is
getting harder and harder to port to vp or a higher
level language. Was hoping to interduce some inet
features to the bbs package.
shrug.
chris
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
|
|
 |
|
