>>>>> "SU" == Sebastian Unger <[EMAIL PROTECTED]> writes:
SU> Jim Morris wrote:
>>
>> Reinhard Karcher wrote:
>>
>> > as far as I know, 4 Bit Graphics is not supported in xdos. Perhaps we'll
>> > get
>> > an answer from an expert.
Last I looked there was some limited 4 Bit graphics support,
(writes to only one plane at a time), but no full support.
>>
>> I looked into this about 6 months ago, and you have hit the nail on the
>> head. xdos does NOT support any 4-bit graphics modes. I think the guys
>> that work on xdos decided that the planar video modes would be more
>> trouble to emulate than they are worth. And having done VGA graphics
>> programming quite a bit when it came out, they are probably right.
>>
>> The only answer for now is that if you have a program that runs in a
>> 16-color graphics mode under DOS, then you need to run it use DOSEMU on
>> a console, and not under X.
SU> First of all: Thanks for the answers.
SU> Still I have two questions:
SU> 1. How is it possible, that any X program using standard X-lib calls (I
SU> suspect dosemu does this ;-) can almost crash the X-Server? Doesn't this show
SU> that there must be a bug in X as well? Should I send this to any X-related
SU> Mailing list and if yes do you know the address?
Yes. There is a bug in the X Server.
No. I don't know the address.
Yes. I've seen something similiar related to palattes and the X server
but I have not tracked.
SU> 2. On the console, VPA doesn't run either. There it isn't a problem with
SU> graphics (at least I don't think so.) But once VPA has established graphics
SU> mode and writes text to the screen all digits save 0 simply disapear. (Better
SU> are not drawn from the beginning.) VPA writes some text in another font
SU> (probably with it own routines) and there it is all just fine. However, the
SU> status display and some other information (important information) is written
SU> with the system font (and thus I suspect, by calling dos or BIOS routines)
SU> and there all characters except 1-9 don't make it to the screen.
SU> Has any body run into this before? And, even more important, has anybody any
SU> suggestions about how to fix it? (I have tried virtually all combinations of
SU> the relevant settings in dosemu.conf, but to no avail)
I don't know about this latter one at all.
ERic
