🚀 go-pugleaf

In article <WIGGINS.92Oct30201836@aelle.cs.odu.edu> wiggins@aelle.cs.odu.edu (Samuel E Wiggins) writes:
>If anyone of y'all out there know anything about EMM386 and the ways
>that it is likely to screw up, please help me out.  Sometimes when using
>my soundcard (I have a PAS-16) to play stuff out of music software, or
>even games sometimes, I get EMM386 exception errors.  Specifically, I've
>gotten excep'n errors #7 and #12, so far.  If anyone has a clue as to
>what exception errors from EMM386, could you PLEASE clue me in!!!  I 
>haven't seen these things documented anywhere I've looked.  How do they
>occur and how do I approach fixing them?  Anyone know?

Here is something I saved from a net discussion a few months ago:

---------------8<-------------------------8<---------------------------
The following is a list of Intel 80386 protected mode exception
errors and their names:

Code    Meaning
----    -------
0       Divide error
1       Debugger interrupt
2       Nonmaskable interrupt
3       Breakpoint
4       Overflow interrupt
5       Array boundary violation
6       Invalid opcode
7       Coprocessor not available
8       Double fault
9       Coprocessor segment overrun
10      Invalid task state segment
11      Segment not present
12      Stack exception
13      General protection violation
14      Page fault
16      Coprocessor error

All of this was prefaced by the comment "This error should not occur
on systems that are 100 percent IBM compatible.  Because of the
hardware-intensive nature of the EMM386 device driver, strict IBM
hardware compatability is required."

---------------------8<-------------------------8<--------------------

-- 
                                                           tsand@vipunen.hut.fi
TEX disconnects, dial again for another session.
D;+vC)?iH%"
NO.CARRIER