Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!rutgers!sri-spam!mordor!lll-tis!ptsfa!ihnp4!chinet!ward
From: ward@chinet.UUCP (ward)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Scrambled DOS-to-BIOS Function Calls (a query)
Message-ID: <1244@chinet.UUCP>
Date: Mon, 29-Jun-87 14:18:28 EDT
Article-I.D.: chinet.1244
Posted: Mon Jun 29 14:18:28 1987
Date-Received: Wed, 1-Jul-87 01:32:39 EDT
References: <3455@ecsvax.UUCP>
Reply-To: ward@chinet.UUCP (Ward Christensen-)
Organization: Chinet - Public Access Unix
Lines: 22

You say that when hacking INT 10 you find that DOS doing function 2 with
an * sends a function of f1 to int 10?
  I tried your example on both DOS 2.0 and 3.2 - and found INT 10 being
called with function 9 in both cases.  I'm using the Periscope debugger,
and here's what I got:
>a   <-- assemble
42DC:0100 mov ax,200
42DC:0103 mov dx,2a
42DC:0106 int 21
42DC:0108 int 3
42DC:0109
>bi 10   <-- break when interrupt 10 executed
/E>/t #  <-- trace all interrupts
/E>gt    <-- go in trace mode
AX=092A  BX=0006  CX=0001  DX=002A  SP=0BA8  BP=0000  SI=00FD  DI=0000
DS=0526  ES=42DC  SS=00E5  CS=0526  IP=0154  FL=F206 NV UP EI PL NZ NA PE NC
 WR SS:0BA2 = 0154 0526 DFF0
0526:0154 CD10           INT    10
  The above is the register/instruction dump when the next int 10 was
executed.  As you can see, the function is 9.
  I suspect you have something "strange" in your system - a multi-tasker,
or some TSR or ??.  Try it on an autoexec-less and config-less system.