[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Problem with xaaes/nvdi+video card
Am 31.12.2009, 11:18 Uhr, schrieb Mark Nias <mintlist@mr2.net>:
just wanted to post back my findings on this, it's all a little
complicated
due to so many things being involved!
...
So you fought quite a battle!
I cannot confirm that using nvdi -> CD1_MANA does not work with
MiNT/XaAES. But it is not fun - many things don't work (redraw-issues,
some colors wrong/missing, no icons, no widgets ..). Same works ok in
aranym 8bit video. I wonder if this can be fixed at all.
But I also wonder you can't even get so far. I get 1024x768x8@78 which is
not that bad.
Tried to make a snapshot: Lonnys xaaesnap fails as well as my own one, so
the pixel-format must be something special, that would explain why the
icons are not displayed.
Speed is currently my smallest problem, at least polyline is fast enough,
it's not slower than TT-High+nvdi 4.11.
(all assuming a working mint/xaaes system)
Senario 1:
CrazyDots 2 card using original CD2 drivers
Auto app CD2_MANA.PRG redirects initial boot display to CD2 card and
allows
selection of CD2 video mode. Video drivers listed as CDDRVXXX.SYS in
ASSIGN.SYS
I run nvdi first, no slct_dev, redirect etc, just nvdi and cd_mana.
Results: Working in TOS and MINT
Problems: no NVDI acceleration so is slow, especially in 256 colours,
only
works in 640x480 under MINT. It will boot into higher resolutions but has
works in 1024x768 in MiNT/XaAES/TOS/GEM etc.
garbled display. I can see the desktop/mouse working underneath a
'skewed'
display... like when you display an image at the wrong resolution so
suspect
this is just a resolution selection problem.
I don't know much about the CD-configuration, but I think best is to
connect 2 monitors.
So in effect, no real progress, personally i'd like to see NVDI ET4000
working with XAAES properly as it's by far the best way to run a CD2
card.
Sure. This is the goal. If I can't get the NVDI-ET4000 working, I'd
suggest I send you XaAESes with 'guessed' solutions - you try and say yes
or no. Next year.
I'm sure there's no issue with NVDI itself as it works fine under mint in
many other senarios. I think it's some problem with NVDIs resolution
selection app SLCT_DEV.PRG
You cannot always blame the one or the other if something doesn't work.
Would there be any scope in someone debugging XAAES and SLCT_DEV.PRG
together?
What do you mean?
-Helmut