LarryL wrote: Wed Feb 25, 2026 3:50 pm
the boot screen is only using the upper half of the screen and thus showing everything pretty condensed.
Thank you for reporting that
@LarryL !
I did changes a while ago to make it use the 8x8 font in the terminal regardless of screensize instead of going to the larger 8x16 font.
Now that I swapped in the w32i and official driver I noticed the same as you described.
I will revert those font-size related changes until I have something that is properly tested and working regardless of what driver is used
Today I switched of the "Cache" flag in the EmuTOS Options menu: then I was able to succesfully install NVDI. Is this normal?
To be honest I have no idea but that's really good to know.
I've only copied files directly from an old NVDI install of mine on the ST.
my w32 card (1MB, no interleave) shows pixel artefacts. Not sooo many, but very noticeable when moving windows or trying to select multiple files. Sprayed pixels following the mouse cursor. This did not go away after disabling the cache. Other cards (e.g. a non-accelerated Cirrus GD5424, as well as a standard ET4000AX) work flawlessly. Maybe its my card, but maybe its the driver? I do not know exactly when this started, but I think some SW versions ago the card worked without these artefacts
This one I don't think I have any good ideas for.
When you select ET4000.W32 in bios setup you should end up running completely unmodified Nova driver + VDI (albeit with those .PRG's loaded and started by rvnova.prg).
I don't think it's this but if you have c:\rvga.inf then double check that it says interleave = 0 under the et4000.w32 section.
Or not at all, as long as it doesn't say interleave = 1
Sometimes when my card(s) are not seated properly in a slot I can end up getting artifacts which usually follows the mouse or whatever is moving or changing (eg. some reads and/or writes ending up incorrect).
I usually ignore fastening the ISA card bracket with the screw when I'm in a session of swapping between different cards a lot for testing and have had that happen in those scenarios.
Not sure where I was going with this other than maybe bad contact could be worth investigating?
Don't know if it will say all that much but could be worth trying the same card with the SVGA driver just to see if you get the same issue regardless of driver.
Although the SVGA driver does not support hardware acceleration for W32i yet so they wont be taxing the card the same amount.
Still, if you end up seeing the same issue with both drivers then perhaps that would at least point more toward the hardware side of things?
