Version 2 history

[19/10/2018][CRT Emudriver 2.0][CRT Tools 2.0][beta 14]

  - [Emudriver]  Removed low pixel clock limitation on HDMI outputs. This allows outputting 15 kHz through HDMI in combination with HDMI->VGA active adapters.

  - [VMMaker]    Added support for EDID emulation on digital outputs (HDMI and DVI-D). EDID emulation drop-down menu now shows outputs by type. DisplayPort still not supported.

  - [VMMaker]    Support for pixelclocks up to 6 GHz. Modeline generation now possible from 15 kHz up to 8K fulldome. Bandwidth limitations imposed by drivers still apply.

  - [VMMaker]    Fix XML processing of newer versions of MAME.

[07/03/2018][CRT Emudriver 2.0][CRT Tools 2.0][beta 13]

  - [VMMaker]    Fix composite sync for HD 5000+ cards.

[23/12/2017][CRT Emudriver 2.0][CRT Tools 2.0][beta 12]

  - [VMMaker]    Added support for composite sync.

  - [Emudriver]  New fix to allow stable support for composite sync for legacy cards (only applies to package based on Catalyst 12.6).

[24/11/2017][CRT Emudriver 2.0][CRT Tools 2.0][beta 11]

  - [Emudriver]  Disabled deflicker filter for interlaced modes. Now your interlaced modes will look perfectly sharp, with all their genuine flicker intact.

  - [VMMaker]    Fixed bug that caused CRT Emudriver not being detected under Windows XP.

  - [VMMaker]    Added new preset for 15/31 kHz dual-sync monitor.

[03/03/2017][CRT Emudriver 2.0][CRT Tools 2.0][beta 10]

  - [VMMaker]    Added option to include multiple modelines in emulated EDID. When enabled, the current modelist is added to the EDID definition (maximum of 20 modes supported). If disabled, only a 640x480 modeline will be included, as usual.

  - [VMMaker]    Fixed bug that caused newer video cards to be incorrectly detected as legacy ones.

[08/02/2016][CRT Emudriver 2.0][CRT Tools 2.0][beta 9]

  - [Emudriver]  New driver packages based on Crimson 16.2.1. Lots of new AMD GPUs & APUs supported.

  - [VMMaker]
  - [Arcade OSD] Changes to correctly apply polarities and refresh with Crimson drivers.

  - [VMMaker]    New commands available from the application's console, to allow manual management of the mode list, etc. Type "help" for details.

[01/02/2016][CRT Emudriver 2.0][CRT Tools 2.0][beta 8]

  - [Emudriver]  Fixed bug in Setup preventing the driver from getting installed depending on the location of the installation files.

[26/01/2016][CRT Emudriver 2.0][CRT Tools 2.0][beta 7]

  - [Emudriver]  Forced reset of interleave flag upon device power-up. Fixes problem with ATOM-15 flashed cards that caused a shrinked picture with progressive modes and double picture with interlaced modes.

[23/01/2016][CRT Emudriver 2.0][CRT Tools 2.0][beta 6]

  - [Emudriver]  Fixed critical bug in driver that caused the system to get frozen randomly upon display device restart.

  - [VMMaker]
  - [Arcade OSD] Correctly assign sync polarity to AMD HD 5000+ cards. Because AMD documentation is wrong, VMMaker where assigning the polarities the wrong way. This must be the direct cause of most out-of-sync issues reported till now. What happened is that GM assigned positive sync instead of negative, and vice versa. This is fixed now, but you'll need to update your crt_range definitions. By default, negative sync (0) is what should be used in most cases. Thanks to intealls for doing proper checks with an oscilloscope and R-Typer for double-checking.

  - [VMMaker]    ATI legacy: now interlaced modes are reported with full refresh (not halved) in W7+. This should solve problems with games that use a hardcoded 60 Hz refresh.

  - [VMMaker]    Better alignment of modeline generator to GroovyMAME's.

  - [Arcade OSD] Fixed Powerstrip support.

[07/01/2016][CRT Emudriver 2.0][CRT Tools 2.0][beta 5]

  - [Emudriver]  Added missing dlls for ADL library (thanks to Fonki for reporting). Issue affected HD 5xxx and newer cards. It caused VMMaker not recognizing the driver.

Thanks for doing this, Recap.

Try generic_15 instead of arcade_15. It's the most conservative preset.

Create a blank vertical.ini file, then add this line: "monitor arcade_15".

Ya está la beta 13. No hace falta actualizar el driver, basta con bajar las CRT Tools.

V e r s i o n   h i s t o r y

- v1.1 - March 2018
    - Added binaries 6.1.7600.16748, 6.1.7601.18126 (Ian Gander, Sean Skroht, Jesús García)

- v1.0 - November 2017
    - First version released.

Hi albert_c,

I don't know if you ever figured this out.

Without more information, the way I'd proceed is to use another monitor (a normal LCD or CRT PC monitor) where you have a workable picture, then use Arcade OSD to target the monitor you're going to use for emulation and force the proper resolution on it.

If the problem is you're already using a PC monitor and you get a garbled picture on it after installing the user modes, making it impossible to accomplish my suggestion above, then simply swap cables: maybe it's outputting 15 kHz to the wrong output.

I can't deduce what the scenario is from reading your post.

Hola Vlad,

quiere decir que puedo construir un cable vga a scart sacando la sincronía directamente del pin 13 del conector vga (hsync) al pin 20 del conector scart y al configurar los modos correctamente funcionaría sin más

En efecto, esa es la idea.

No es mucho más difícil que configurar el sistema para 15 kHz, pero hay más cosas que pueden fallar, en teoría, así que no es fácil conseguirlo a la primera. Por ejemplo, es conveniente haber creado ya los modos de vídeo antes de activar c-sync, porque este ajuste no funciona sobre la resolución por defecto del EDID emulado. Si no haces todo el proceso desde un monitor de apoyo te puedes encontrar con el problema de quedarte "a ciegas" a mitad.

Por cierto, espera a que saque la beta 13 que hay un fallo con c-sync y las tarjetas nuevas.

Hi MadDuke,

The VEGA graphics won't be supported by current CRT Emudriver (it's a couple of years old driver) but I'm planning to update the package as soon as I have some time.

I'm also looking forward to build one of this APU based machines. My plan is to experiment with UEFI Tool and check if it's possible to modify the embedded BIOS to output 15 kHz.

Some notes about the new composite sync feature

- Just like any other feature, composite sync support can be enabled independently for boot time (BIOS mod with ATOM-15) and for Windows (with VMMaker).

- In order to enable composite sync right from boot, you have to check the corresponding option in ATOM-15 and flash your video card with the modified BIOS. Composite sync will be applied to all available outputs, so that's something you may need to consider depending on your setup.

- Regarding Windows, first of all, an important warning: enabling composite sync may be a tricky business. Even if you know what you're doing chances are you get into a messed video state at some point of the process. Once you get everything right it should work fine forever, you just need to get there. I recommend to always work with two monitors during the process and only enable composite sync to the secondary monitor (the one you're not working with) so in case anything goes wrong you don't get an unusable display. If anything went wrong and you can't find your way around a messed display, you can boot in same mode and uninstall the driver.

- There's a new button in VMMaker's video card tab that allows you to toggle composite sync for the currently selected output.

- Again, HD 5000+ cards are easier to setup for composite sync than legacy ones. Just enable composite sync for the selected output, create the modes and you're done.

- Legacy (pre HD 5000 cards) need some extra steps in order to get correct composite sync:

    · First, to get consistent composite sync behaviour for legacy cards you must update CRT Emudriver (based on 12.6) to the new beta 12 version (this is not required for HD 5000+ cards).

    · You must set both H and V sync polarities to positive for all modes. So after enabling composite sync, you must generate and install all modes again, but first you need to go to the monitor tab to edit your selected monitor preset and modify it with the proper polarities, e.g.:

        monitor "arcade_15", "Arcade 15.7 kHz - standard resolution", "4:3"
                crt_range0 15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 1, 1, 192, 288, 448, 576

    · Finally, still in VMMaker make sure to mark "Export settings to GroovyMAME" in MAME's tab so the correct polarities are used by GroovyMAME.

- If you're using an VGA to BNC cable, remind that composite sync is ouput through the h-sync cable, so if you're using a T connector, unplug the v-sync cable.

V e r s i o n   h i s t o r y

- v1.5 - December 2017
    - Added support for composite sync.
    - Reduced BIOS hook size by 40 bytes, now only 532 bytes of blank space are required.

- v1.4 - November 2017
    - Fixed bug that caused wrong checksum correction in some cases.

- v1.3 - March 2017
    - Implemented GOP reallocation for EFI bios.

- v1.2 - September 2016
    - Detect blank space as a combination of 0x00 and 0xFF characters.
    - Reduce by 256 bytes the size required by the BIOS hook, now only 572 bytes of blank
      space are needed to patch the BIOS.
    - Fixed bug that caused wrong checksum correction in some cases.

- v1.1 - October 2014
    - Fixed critical bug that affected older Radeon cards (the X series at least).

- v1.0 - October 2014
    - First version released.

Are you using latest version of ATOM-15?


(5 replies, posted in Support)

It sounds like a bandwith limit. I believe older HDMI spec does not allow such high resolution. You used to require a dual-link dvi cable to go above 1920x1080.

It's perfectly fine to use a Nvidia card along with the ATI. It may make things easier as you can't install two different versions of Catalyst, in case this was required by your new GPU.


(5 replies, posted in Support)

Have you enabled "extended desktop" from Windows' screen setup dialog?


(5 replies, posted in Support)

It's perfectly possible. Display detection might fail if you accidentaly enabled EDID emulation at the wrong output. But I'd say that's not possible with the HD 5450 which has only one analog output. Have you tested that screen on another computer?

W i n d o w s    I n t e r l a c e    P a t c h e r    v 1 . 1    -    F o r    W i n d o w s    7 / 8 / 8 . 1 / 10


*Test Mode is required as long as patched drivers are in use. This tool patches a system kernel driver, thus Test Mode is required, otherwise your system won't boot. The only side effect of Test Mode is a watermark on the right lower corner of your desktop. Well, that, and possibly a reduced security against rootkit viruses and such. If you're using this tool you're assumed to be a competent user. DO NOT attempt to disable Test Mode manually after patching your system or you're guaranteed to end up in a BSOD loop on restart. However, it's safe to disable Test Mode once you unpatch your system.

W i n d o w s    I n t e r l a c e    P a t c h e r    v 1 . 1   d o w n l o a d

Download Windows Interlace Patcher v1.1

O v e r v i e w

Windows Interlace Patcher is an experimental tool designed to fix an issue that exists in all versions of Windows (probably since Vista) affecting interlaced video modes.

The most notable effect of this issue is applications (e.g. emulators) running at halved speed when an interlaced video mode is in use and v-sync is enabled. Another typical effect is Windows desktop animations looking choppy.

This issue doesn't affect all systems however. It seems to be dependent of your particular hardware configuration. Systems with AMD pre HD-5000 video cards are known to always suffer from this issue. On the other hand, AMD HD-5000 and newer video cards are seemingly free of problems, although there is some evidence of slowdown issues with apps that run in non-exclusive full screen mode (thus affected by desktop compositing).

Therefore, it's up to you to decide whether your system is affected and so it's worth to use this software.

There have been previous workarounds to this issue, namely:

- Using positive sync polarity (pre HD-5000 cards). This magically fixes all problems, but you need an external sync converter (e.g. UMSA), as all TV sets and most arcade monitors expect negative sync.

- Disabling desktop compositing. This fixes choppy Windows animations and slowdowns on non-exclusive full screen apps. But v-synced full screen apps are still affected.

- Using direct v-sync (i.e. frame delay) in GroovyMAME. This works but it's specific to GroovyMAME. Besides it can cause static tearing for older cards, exactly those which are affected: pre HD-5000 ones.

- Using Windows XP.

This is the first fix that attempts to cover all situations.

It's important to note that this is actually a Windows issue. It is not a bug in AMD's or anyone else's drivers. We need to patch Windows itself in order to fix it. Specifically, the culprit file is dxgmms1.sys.

This tool is not part of CRT Emudriver. It can be used with or without CRT Emudriver, and is not targeted specifically at AMD cards.

This tool doesn't fix the issue with interlaced modes being reported with a halved refresh by the operating system.

U s a g e

Windows Interlace Patcher is quite simple to use. Just launch the app, and click OK when the warning message is shown.

If your kernel version is known by the patcher, it'll show a message like this:
"Version 6.3.9600.18662 found! Do you want to patch your system?"

Click OK.

Now, in case your system is not in Test Mode yet (if you're using CRT Emudriver, it'll certainly be already enabled), you'll be prompted with a request to enable to enable "TESTSIGNING".

Click OK, reboot and you're done.

If you ever want to revert the patch, just run the installer again. It will prompt:
"Your system is already patched. Do you want to revert the patch?

Again, click OK and restart your system.

If your particular kernel version is unknown to the program, it will prompt:
"Binary version not supported."

If this was the case, please send the dxgmms1.sys file you'll find in your Windows directory (x:\windows\system32\drivers), to calamity15khz at gmail dot com. Hopefully it will be added to a future version of the program.

A c k n o w l e d g e m e n t s

Special thanks to Haynor666 from BYOAC for helping me testing this tool in lots of Windows versions.

Hola metwar,

En src\osd\modules\render\drawd3d.cpp, comenta las siguientes líneas:

        osd_printf_error("Direct3D Error: Your graphics card does not fully support non-power-of-two\n");
        success = false;

    if (caps.TextureCaps & D3DPTEXTURECAPS_POW2)
        osd_printf_error("Direct3D Error: Your graphics card does not support non-power-of-two textures.\n");
        success = false;
    if (caps.TextureCaps & D3DPTEXTURECAPS_SQUAREONLY)
        osd_printf_error("Direct3D Error: Your graphics card does not support non-square textures.\n");
        success = false;


        osd_printf_error("Direct3D Error: Your graphics card does not fully support non-power-of-two\n");
        success = false;

    if (caps.TextureCaps & D3DPTEXTURECAPS_POW2)
        osd_printf_error("Direct3D Error: Your graphics card does not support non-power-of-two textures.\n");
        success = false;
    if (caps.TextureCaps & D3DPTEXTURECAPS_SQUAREONLY)
        osd_printf_error("Direct3D Error: Your graphics card does not support non-square textures.\n");
        success = false;

Con ese cambio, compila tu propio ejecutable de MAME o busca a alguien que lo haga por ti.



(11 replies, posted in Discussion)

Have you actually installed any resolutions, specifically 320x240? Does Arcade OSD show it in its list?


(2 replies, posted in Support)

Hi 002,

Test Mode is required both for installing patched drivers and for Windows to load them afterwards.

There's no side effect caused by Test Mode aside from the ugly watermark.


(11 replies, posted in En español)

No tiene que ver. El JPAC se enciende cuando enciendes el ordenador y recibe alimentación del usb. Pierde sincronismo por un problema propio del JPAC que es bien conocido, lo verás si buscas un poco. No es que el tuyo sea defectuoso, pasa con todos. Con los originales fabricados allá por 2007 no pasaba.

Hay un "mod" que parece solucionarlo: … msg1596613

Yo acabo de hacerlo, y de momento no me ha vuelto a fallar.


(11 replies, posted in En español)

xa2er wrote:

Sí, efectivamete. Mediante un JPAC. ¿Tiene algo que ver?


Cuando pierdas la sincronía, mira el JPAC y verás seguramente que el led correspondiente está apagado. Si es así, desconecta el usb por el que se alimenta el JPAC y lo vuelves a conectar. Verás como vuelve a sincronizar.


(11 replies, posted in En español)

¿Cómo tienes conectado el monitor a la tarjeta? ¿A través de un JPAC?


(11 replies, posted in En español)

Pero, si simplemente tocas el potenciómetro Hfreq, ¿se llega a estabilizar la imagen? Hablo del Hfreq, solamente, ojo.


(11 replies, posted in En español)

Seguramente tengas que tocar ligeramente el potenciómetro Hfreq.


(9 replies, posted in En español)

xa2er wrote:

Tuvo que ser algún problema del driver probablemente...

Coño, ya me la he cargado yo :)

xa2er wrote:

Una útlima consulta. Hay forma de duplicar la salida para que del VGA salga la señal al monitor arcade, y del HDMI por ejemplo a un monitor LCD al mismo tiempo?

Sin problema. Como siempre y con cualquier tarjeta, eso se hace desde el cuadro de diálogo "Propiedades de pantalla" de Windows. Duplicas el escritorio, etc.