From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9710150352.AA13081@clio.rice.edu>
Subject: Re: cwsdpmi r4 beta
To: djgpp-workers AT delorie DOT com
Date: Tue, 14 Oct 1997 22:52:00 -0600 (CDT)
In-Reply-To: <199710150148.OAA14993@teleng1.tait.co.nz.gatekeeper.tait.co.nz> from "Bill Currie" at Oct 15, 97 02:52:01 pm
Content-Type: text
Precedence: bulk

> How would I go about testing [VDS]? I don't think I have any 16 bit dma 
> devices at home, and 8 bit dma doesn't seem to work above 1 M (You'ld 
> think it would on an AT, the page registers didn't HAVE to stay 4 
> bit), or am I missing something?.

Testing is one of the issues.  I want a test program which uses many of 
the features, be able to test it on W95, make sure the test program
seems sound, then make sure it does the right things with the CWSDPMI
implementation.  I have a sound card which supports 16bit DMA, but
I am really too busy to spend much time on the testing.

For example, VDS on W95 seems to always return a 63.5K length DMA transfer
buffer - we ought to do the same (we currently return 16K or 32K).  So
my obsession with getting it right may delay getting it officially into
a release.  With my primary platform anymore (NT) not even supporting
VDS, I'll probably do more supervising than doing...

Then the real question comes up ... should the effort be put into MWDPMI
instead?  I actually think so, since the compiler is much higher quality
and more available to everyone wanting to hack...