bristlehog wrote:

I have turned Tandy emulation on

Does this mean machine=tandy, or tandy=on with some other machine type? Some drivers may only work with machine=tandy because they look for BIOS signatures to identify a Tandy system. What program are you using to run the drivers? DIGPAK DMKIT's MENU.EXE?

Machine was set to svga_s3. I were using PX player for tandy.adv, xp32 for a32tandy.dll and xmiplay for tandy.mdi; also I tried the games.

But you were right, setting machine to tandy made both tandy.adv and tandy.mdi work.

You were also right about BIOS signatures:

tandy.adv and tandy.mdi code (yes, they are based on same code):

1                ELSEIFDEF TANDY
2
3                mov ax,0f000h           ;search PC BIOS for string 'Tandy'
4                mov es,ax
5                mov di,0
6                mov cx,65535
7                mov al,'T'
8__search_T:     repne scasb
9                jne __not_found
10                cmp WORD PTR es:[di],'na'
11                jne __search_T
12                cmp WORD PTR es:[di+2],'yd'
13                jne __search_T
14                jmp __exit              ;found, assume Tandy sound available
15__not_found:    mov ax,0              
16
17                ENDIF        

a32tandy.dll code:

1                ELSEIFDEF TANDY
2
3                mov eax,1
4
5                ENDIF

Update: I have patched the drivers, they can be downloaded here.