[Prev][Next][Index][Thread]
Re: univbe/cwsdmpi conflict?
> Has anyone else had trouble running UniVBE 5.1a with executor once
> executor started using CWSDMPI.EXE for its DPMI support?
I did some simple testing on UniVBE with linear frame buffers and CWSDPMI
and it worked fine. I didn't test any page-flipping code, or many
different video cards. I have found some video BIOSes are poorly written
and use a humongous amount of stack space (over 100 words) when switching
modes, etc. If a video BIOS (or UniVBE) takes more than 128 words it
might cause some problems in CWSDPMI. I would be interested in knowing
if other people have this problem, and if so, what cards they are trying
to use (and how - what modes, etc). I can provide a test CWSDPMI to
test this theory.
References: