🚀 go-pugleaf

In <1992Nov18.033044.7634@nas.nasa.gov> tweten@wilbur.nas.nasa.gov (Dave Tweten) writes:

>In article <1992Nov18.002225.3397@mksol.dseg.ti.com> mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:
>>In <1992Nov17.183627.22224@nas.nasa.gov> tweten@wilbur.nas.nasa.gov (Dave Tweten) writes:
>>
>>>I have a 486 EISA machine
>>>with an Adaptec 1740.  I couldn't get Windows 3.1 to work in enhanced
>>>mode without enabling Windows double buffering until I got Adaptec's
>>>latest fixed version of aspi4dos.sys.
>>
>>Well, you just confused the hell out of me.  The documentation with my
>>card says that you don't use ASPI4DOS.SYS when you're trying to run
>>the AHA-1740 in Enhanced Mode.  The driver you should be using is
>>called ASPIEDOS.SYS.  The ASPI4DOS.SYS is for AHA-154x boards and for
>>the AHA-174x cards running in Standard mode.
>>

>I didn't say I wanted to run my 1740 in Enhanced Mode, I said I wanted
>to run Windows 3.1 in enhanced mode (i.e. 386 enhanced mode, as
>defined on page 7 of the Windows User's Guide).  I use aspi4dos.sys
>because I want to run the 1740 in Standard Mode (for reasons of Jolitz
>Unix compatibility).

Hmmm, rereading, it wasn't real clear just WHAT you were talking about
running in enhanced mode.  

>Just a reminder - the "latest fixed version of aspi4dos.sys" is 3.0a
>(that was the point of my original posting).

Still curious.  When this new version loads, does it identify itself
as version 3.0 or as version 3.0a?  Mine identifies itself as being
Version 3.0 and works fine with Window Enhanced Mode and unbuffered.
Do they tell you what else the (a) changed?

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.