1024x768 Resolution in 256 colors or Higher

[fmh]

Hi

I am trying to run a GEM Program in 1024x786 by 256 colors minimum in Hatari. So far I have not been able to figure out how to do this. I am using Hatari 2.10 under Windows 7 32-bit. I setup a 68030 machine with 14MB RAM. I tried TOS 4.04 and configured a Falcon but a Falcon is not capable of this resolution. I tried EmuTOS but if I use Extended VDI at 1024x768 I get 16 colors and not 256 or higher. Is there a way to do this on Hatari?

[Xerus]

Uses a Falcon screen enhancer like Videlity, Videl Inside, Centscreen, etc.

[Faucon2001]

In falcon mode and with Videl Inside, I reach 1280x1024x256c without pb.

[dhedberg]

In falcon mode and with Videl Inside, I reach 1280x1024x256c without pb.

Yes, with Videl Inside on Hatari you're basically free to configure any resolution. I have a 1920x1200 configuration on my setup. The desktop is huge!

[lp]

How far can you push TC mode?

[Faucon2001]

For TC, 1008x1024. I believe it can go higher for vertical resolution, but 1008 in horizontal is the maximum. Anything higher will crash, but I don’t know why.

[dhedberg]

For TC, 1008x1024. I believe it can go higher for vertical resolution, but 1008 in horizontal is the maximum. Anything higher will crash, but I don’t know why.

A limitation of the Videl. Only 10-bits of the hardware register ($FF8210) used to specify the line width (in words) for the screen are used. One pixel in TrueColor is one word, highest 10-bit value is 1023.

[Cyprian]

$FF8210 is for virtual screen only and it means how much words have to be skipped between lines

[dhedberg]

$FF8210 is for virtual screen only and it means how much words have to be skipped between lines

I guess you're thinking of $FF820E (line offset). It's the register to use for specifying the number of words to skip after every display line when using a virtual screen.
$FF8210 (line width) is the number of words of the display line.

If you configure a video mode by setting the Videl registers you set $FF8210 regardless if you use a virtual screen or not, and as $FF8210 is 10-bit, it effectively restricts the actual visible line width of any screen.
If you use virtual screens you also need to set $FF820E to the number of non-displayed words (virtual/logical line = line width + line offset).

[Cyprian]

ok, never programmed VIdel.
I was sure both registers are the same:

Code: Select all

$FF820F|byte |Width of a scanline (width in words-1)               |R/W  (STe)
$FF8210|word |Width of a scanline (width in words)                 |R/W (F030)

[dhedberg]

ok, never programmed VIdel.
I was sure both registers are the same:

Code: Select all

$FF820F|byte |Width of a scanline (width in words-1)               |R/W  (STe)
$FF8210|word |Width of a scanline (width in words)                 |R/W (F030)

No, for Falcon030 video modes:

Code: Select all

$FF820E|word |Offset to next line in words (9-bit value)           |R/W (F030)
$FF8210|word |Linewidth in words                                   |R/W (F030)

For ST compatible video modes:

Code: Select all

$FF820F|byte |Width of a scanline (width in words-1)               |R/W  (STe)

Disclaimer: I've actually never programmed anything in ST compatible video modes on the Falcon030, but I assume for reasons of compatibility with the STe, $FF820E (or $FF820F as this register is only 8-bit on the STe) is then used as on a real STe.

[ThorstenOtto]

To the original question: most likely, it is the desktop that dictates your resolution. You should try to configure the video mode there, save the configuration, then reboot.

[Eero Tamminen]

Not sure whether everybody already knows this, but when investigating Videl register values, you can use Hatari debugger "info videl" command.

[lp]

I had no luck with VI2 and aranym. BlowUp030 topped out at 928 complaining about something. I was able to tweak the source code of BlowUp030 and recompiled it. Now I can get 1008x1024 in TC easily. As noted above, anything over 1008 pixels wide doesn't work. Thanks for the info guys.

[dhedberg]

Would you mind sharing the recompiled version?

[lp]

Sure, here it is. I only modified BLOWCONF.PRG. I eased the frequency restrictions since they don't really apply to an emulator. The warnings have been removed. It will throw an alert if the screen ram exceeds 2mb, just click the default button, save the config anyway.

blowupfx.zip