[Bug 15687] New: Microsoft Word 5.0 for dos displays initial menu, then hangs

http://bugs.winehq.org/show_bug.cgi?id=15687

Summary: Microsoft Word 5.0 for dos displays initial menu, then
                    hangs
           Product: Wine
           Version: 1.1.6
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dos
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

This is kind of cool.  I grabbed my wife's ancient copy
of Microsoft Word 5.0 for DOS off the shelf where it
had lain ten+ years untouched.  The app fits on a 
single 720KB floppy.  (The sha1sum of the floppy image is
8e6795facd2e3ff1db6628912c4da61a50dc402b.)  The floppy
contains just the files
capture.com  capture.doc  ega.sys  full.sty  mous8514.sys  mw.ini  semi.sty 
word.exe  word.ovl  word.pif

Running word.exe with wine does nothing useful.
Running it with wineconsole, on the other hand, puts up the main menu!
Sadly, it then seems to hang, taking no input.
The log shows
err:int:DOSVM_Int2fHandler int2f: unknown/not implemented parameters:
int2f: AX 1800, BX ff12, CX 3456, DX 0000, SI 61b7, DI 0000, DS 4009, ES 9ef8
err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters:
int10: AX fa40, BX 0000, CX 0002, DX 0440, SI 08a0, DI 62de, DS 4009, ES 4009
err:int:DOSVM_Int2fHandler int2f: unknown/not implemented parameters:
int2f: AX 1700, BX 00bc, CX 0000, DX 04d1, SI 03d4, DI 000d, DS 4009, ES f000
and then, after a minute,
err:int:TIMER_TimerProc DOS timer has been stuck for 60 seconds...

The int2f call seems to be asking DOS about the version of
WINOLDAP, see http://www.ctyme.com/intr/rb-4636.htm

To see what it's doing during the apparent hang, do +int,+int21.
This shows that it's actually checking the keyboard with int 16h.
Unfortunately, the keystrokes don't seem to be making it to the
app.

I'll attach a log showing a run where I pressed abcde ESC
and then killed the app.  You can see the six keystrokes
clearly in lines like
trace:int:DOSVM_ProcessConsole scan 1e, ascii 61
but it didn't look like the next 
trace:int:DOSVM_Int16Handler Check for Keystroke
reflected that a key was pressed.  (It's hard to eyeball; I'll
need to write a perl script to make the data pop out.)