DOS Merge (arrrgh)

[Robert J. Granvin]

Seeking DOS Mergexperts.. :-)

Would someone be willing to explain a non-fatal, non-damaging DOS
Merge recurring problem?

Running DOS Merge (current release) under Uport 2.4 '286, and using
DOS 3.2 as the image, I am constantly plagued by the following message
following any DOS usage or command (while under Unix):

	fdintr: unexpected irq - state = 0, sis[0] = BC

This will manifest itself every time the machine goes down and back up
again, either by accident, crash, powerfail or graceful purposeful
shutdown.  It will also manifest itself at completely random times.
Of course, once it starts, it never stops.

The problem can be resolved by reinstalling the DOS image (either the
long (-l) or short (-s) install).  Then later on, it will start all
over again.

Since it's a completely non-damaging situation, I'd almost be happy
(At this point!) to let it continue, but in it's infinite wisdom and
mercy, it decides that these messages should be piped directly to the
console device rather than through stdout or stderr, making it a tad
more difficult to trap (grrr!).

Anyways, any hints, comments or suggestions would be _most_
appreciated.  email is preferred.  If there is enough interest, I'll
post a summary.

-- 
       Robert J. Granvin               Blessed are those that run around in
 National Information Services         circles, for they shall be known as
        rjg at nis.mn.org                 wheels.
 {amdahl,hpda}!bungia!nis!rjg