MP> I noticed the following error using watcom 10.6 and I was interested in
MP> knowing if anyone knows if its a known bug and been fixed. Also if its in 
MP> earlier versions or not.

I have Watcom 10.0, and I have the same problem as you.  Amazing how it
could have gone from 10.0 to 10.6 without anyone seeing it.  Fortunately
PDCOMM has the interrupt handler in assembler, eh?  :-)  BFN.  Paul.


MP> pop     bp
MP> pop     bx  ;should be pop sp
MP> pop     bx

Segment: _TEXT  BYTE   00000021 bytes  
 0000  50                int1c_          push    ax
 0001  51                                push    cx
 0002  52                                push    dx
 0003  53                                push    bx
 0004  54                                push    sp
 0005  55                                push    bp
 0006  56                                push    si
 0007  57                                push    di
 0008  1e                                push    ds
 0009  06                                push    es
 000a  50                                push    ax
 000b  50                                push    ax
 000c  89 e5                             mov     bp,sp
 000e  fc                                cld     
 000f  b8 00 00                          mov     ax,seg L1
 0012  8e d8                             mov     ds,ax
 0014  58                                pop     ax
 0015  58                                pop     ax
 0016  07                                pop     es
 0017  1f                                pop     ds
 0018  5f                                pop     di
 0019  5e                                pop     si
 001a  5d                                pop     bp
 001b  5b                                pop     bx
 001c  5b                                pop     bx
 001d  5a                                pop     dx
 001e  59                                pop     cx
 001f  58                                pop     ax
 0020  cf                                iret    

No disassembly errors

------------------------------------------------------------
@EOT:

---