jsh@alice.att.com (Juergen Schroeter) (10/02/90)
Hi windows experts, I'm running win3 on an AT&T6386/25 WGS with 8MBytes and a VDC600 (a la Paradise 256k) video card in 800x600x16 mode. I also am running an Ariel DSP16 board with its adaptor ram set to the b000 page (the DSP16 applications need somewhat less than 32kBytes so they should not interfere with the VGA at b800). This works fine from dos. In windows, however, my applications can't write to b000 and fail. My suspicion is that win3 uses b000-b7ff for its own thing. If this is true, how can I tell win3 NOT to use b000-b7ff ?? A hint in this direction is that Quarterdeck in their latest version of qemm386 recommend to exclude that address range for qemm so not to interfere with win3 (using qemm or himem.sys does not make any difference for my applications: they fail in both cases under win3 but work fine outside win3). Short of using a different range of addresses for the DSP16 board -- which I don't want to do since I have more than 100k drivers in high mem -- is there anything I'm missing? Maybe it's a flaw of the Paradise 800x600x16 driver? Of course, I have a line in system.ini to exclude b000-b7ff for EMM..... Thanx for reading so far... Juergen Schroeter, (201) 582-7059, jsh@research.att.com