You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, it seems Atari800Win PLus in full screen display modes displays incorrect colors. It looks like an uninitialized palette. It happens on two computers, both running Windows 7. Both machines have different graphic cards, so I don't think is a driver-related problem. I don't remember having this problem on Windows XP. Please has anyone else encountered a similar issue? Thank you!
The text was updated successfully, but these errors were encountered:
Yeap, many people have the same issue on Win7 and Win8. There are several workarounds, like directdraw hack (DDHack v1.0) - not working for me, patch done using "Microsoft Application Compatibility Toolkit" - not working for me.
First working is to make little batch file "Atari800Win.bat" in app dir with following content:
@echo off
cd /D %~dp0%
taskkill /f /IM explorer.exe >NUL
Atari800Win.exe
start "" explorer.exe
It kills explorer.exe before Atari800Win starts, then relaunch it after Atari800Win will end. Unfortunatelly there will be no explorer when Atari800Win.exe is running, so no access to start menu, desktop, tray bar.
Last working workaround, and best in my opinion, is to make little batch file "Atari800Win.bat" in app dir with following content:
It launches control panel screen resolution window, then minimizes it, delay for 2 seconds, and finally launches Atari800Win.exe. It seems strange, but when screen resolution is opened, there is no palette issue in full screen mode. You have to close screen resolution window by your own when Atari800Win.exe finishes (it is not handled by script).
Hi all, it seems Atari800Win PLus in full screen display modes displays incorrect colors. It looks like an uninitialized palette. It happens on two computers, both running Windows 7. Both machines have different graphic cards, so I don't think is a driver-related problem. I don't remember having this problem on Windows XP. Please has anyone else encountered a similar issue? Thank you!
The text was updated successfully, but these errors were encountered: