Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!cscherry
From: cscherry@miavx1.acs.muohio.edu
Newsgroups: comp.windows.ms
Subject: Re: *ebios?!, argggggggh!!
Message-ID: <3850.27bf19da@miavx1.acs.muohio.edu>
Date: 18 Feb 91 05:03:38 GMT
References: <39378@cup.portal.com>
Lines: 17

In article <39378@cup.portal.com>, MJB@cup.portal.com (Martin J Brown-Jr) writes:
> I have an Everex Step 386/20 that has been running Windows 3.0
> perfectly fine since W3 came out, using a Paradise Professional
> in 800x600 mode, with 4 megs of ram.

Two things off the top of my head:
1: the *ebios isn't a file (at least that I can find) but tells the kernal 
that the system BIOS is IBM compatible (or AT&T, etc..)
the line should be the first one under [drivers] in the system.ini file
[drivers]
ebios=*ebios
you might want to check the file.

2: sounds like a bug in the new drivers.  I'd try installing the old 
drivers, and see what happens

-Chris