Search options (Page 5 of 11)

Interesting. May I ask you to try to install a newer Catalyst version (non-CRT Emudriver), or even better, a recent Crimson package?

No.

It is only convenient so you can see the boot process properly. J-PAC will allow your monitor to synchronize without flashing your card but you'll get a split screen.

Nice job Pakoman! Just wanted to make some comments.

With regards to EDID emulation, as far as I know CRU uses EDID overrides, which is a feature of Windows. On the other hand VMMaker uses EDID emulation, an ATI specific feature. EDID emulation operates on a somewhat lower level than EDID overrides, because it's the driver what reports a fake monitor, so from Windows standpoint it's just another monitor, it basically can't tell the difference.

The link from Nvidia that buttersoft posted shows there's an equivalent method that works for Nvidia Quadros. The thing is the method VMMaker uses for EDID emulation is only supposed to work for AMD Firepros, but VMMaker uses a hack to make it available for all AMD cards. Maybe the same could be done for Nvidia. (It's really funny how these companies copy each other. These workstation cards are sold at unjustifiably expensive prices and some of their features are just functionality being capped by the driver on the lower-end models).

With regards to stock ATI driver, I can confirm it won't accept more than 10 custom modes and nothing below 640x480 (this is not a pixel clock limitation that could be patched, rather than that it's a crude "if x < 640 or y < 480 then " check hardcoded in the driver that CRT Emudriver explicitely removes). One could try to use the registry to add the modes instead of using the API in order to bypass the check, but then, again, GM wouldn't be able to udpate the video timings afterwards because the check would be applied then. Believe me when I say that I exhausted all these possibilities when developing GM for 5000+ cards last year. Sadly there was no option but to use a patched driver.

Now on the other hand, adding the modes to an emulated EDID, even if read only,  is an interesting alternative, specially for super resolutions. The check I mentioned doesn't apply to those modes (this could be different for Nvidia).

I have to say I never liked the EDID approach because its read-only-ness takes us a decade back into the past. Our quest is custom video, rather than a boring "15-kHz output". However, that said, I have to confess I often miss the possibility of outputting even a single custom video mode from an average laptop, even if I had to configure it manuallyover and over. So I understand here's where this method could shine.

Not a bug.

Check this article:

"Due to technical constraints in Win7, boot is always displayed in our recommended minimum resolution – 1024×768, regardless of the system’s native resolution."

However, because Windows 7 boot screen was hardcoded to run on 1024x768, when the OS doesn't find this VESA mode available it automatically falls back on the old Vista 640x480 boot screen. Thanks to Microsoft forseeing this circumstance we can enjoy a full boot sequence at 15 kHz.

Sorry I missed this one.

Your card is supported, as long as it is detected by the installer. It's only that there's a typo in the .inf file corresponding with the name of your card, so the commercial name is not properly read, that's all. It's just a name that has no meaning for the system, one could write "Radeon 7870 XT" or "Genghis Khan" in there, no difference.

Hola Carlos,

Te pido disculpas por la tardanza en contestar.

En mis pruebas, no he conseguido sacar sincronismos compuestos con un método de que funcione de manera general, por lo que no añadí esa opción a VMMaker.

Probablemente, esa clave de registro funcionaba en versiones anteriores del driver, o para modelos anteriores de gráficas, de ahí que Winmodelines la incorporase.

Si tienes un cable con circuito para mezclar sincronismos, pienso que siempre será mejor opción que hacerlo desde software, ya que te garantiza que funcione en todas las situaciones (por ejemplo, durante el arranque si usas ATOM-15).

I can't see any reason why exiting MAME would make the desktop look different than before. Can you make sure the resolution is the same before and after? Please try this by launching MAME from command line, not from HS.

Sounds like you're using a dated version of VMMaker. MAME XML format changes with time and you need updated tools. Check this.

You can create a "backup" of your modelines with the "Export video modes" option in the "Video card" tab. But I can't guarantee the stuff you created with other tools will be preserved (it probably will). Anyway it's a terrible idea to use Powerstrip with the CRT Emudriver & GM combo.

The preset I provided is safe. As I've explained dozens of times, CRT monitors have no maximum vertical resolution, what they have is a maximum horizontal frequency. As long as you keep Hfreq within the monitor work range, it's safe:

crt_range5 34001-38000, 40-100, 1.000, 3.200, 2.200, 0.020, 0.106, 0.607, 0, 0, 576, 768, 0, 0

For vector games, I'd say GM already goes for the higher possible resolution achievable from the given monitor preset.

Hi u-man,

The way the D9800 preset is defined, makes it obvious that nothing above 600p can be generated from it:

monitor "d9800", "Wells Gardner D9800", "4:3"
        crt_range0 15250-18000, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 0, 0, 224, 288, 448, 576
        crt_range1 18001-19000, 40-80, 2.187, 4.688, 6.719, 0.140, 0.191, 0.950, 0, 0, 288, 320, 0, 0
        crt_range2 20501-29000, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 0, 0, 320, 384, 0, 0
        crt_range3 29001-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 0, 0, 384, 480, 0, 0
        crt_range4 32001-34000, 40-80, 0.636, 3.813, 1.906, 0.020, 0.106, 0.607, 0, 0, 480, 576, 0, 0
        crt_range5 34001-38000, 40-80, 1.000, 3.200, 2.200, 0.020, 0.106, 0.607, 0, 0, 576, 600, 0, 0

The solution to your problem is quite straight-forward. Just extend the existing preset to reach 768p.

monitor "nec-3pg", "NEC 3PG", "4:3"
        crt_range0 15250-18000, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 0, 0, 224, 288, 448, 576
        crt_range1 18001-19000, 40-80, 2.187, 4.688, 6.719, 0.140, 0.191, 0.950, 0, 0, 288, 320, 0, 0
        crt_range2 20501-29000, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 0, 0, 320, 384, 0, 0
        crt_range3 29001-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 0, 0, 384, 480, 0, 0
        crt_range4 32001-34000, 40-80, 0.636, 3.813, 1.906, 0.020, 0.106, 0.607, 0, 0, 480, 576, 0, 0
        crt_range5 34001-38000, 40-80, 1.000, 3.200, 2.200, 0.020, 0.106, 0.607, 0, 0, 576, 768, 0, 0

(In the "Monitor settings" tab, press "Edit monitor presets", then paste the text above. Save and exit. Now a new "NEC 3PG" preset will be available from the drop-down menu).

You can use the sliders on the right panel to analyze each of the 6 ranges, e.g. see how vertical resolution limits the achievable vertical refresh for a certain range, etc.

Cuando dices que has modificado el dotclock de esos modos, creo deducir que el problema real es que la frecuencia horizontal era demasiado alta, de manera que al bajar el dotclock, indirectamente has bajado dicha frecuencia, y así ya te funcionan. Si esto es así, el procedimiento lógico es crear un nuevo preset de monitor, a partir del que hayas usado, modificando únicamente la frecuencia horizontal máxima (Hfreq-Max) para limitarla a un valor más bajo. Por ejemplo:

crt_range0 15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576 (arcade_15 original)

crt_range0 15625-15900, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576 (arcade_15 modificado)

También puedes lograr lo que creo que estabas intentando, esto es: que VMMaker tome modelines "a pelo". Para ello tienes que usar el botón de importar modos, y tienes que preparar un archivo de texto con la lista de modelines que quieras instalar. En ese archivo de texto puedes incluir los modelines previamente modificados con ArcadeOSD. Cuando usamos este procedimiento, lo que hacemos es puentear el generador de modelines de VMMaker.

Por aclarar un poco el asunto, VMMaker permite dos formas de introducir modos de vídeo:

- Desde la pestaña "User modes", donde seleccionamos un archivo con modos de vídeo (por defecto "user_modes.ini"). Estos modos de vídeo serán generados como modelines por VMMaker, a partir del preset de monitor que tengamos activo.

- Desde la pestaña "Video card", botón "Import modes", donde seleccionamos un archivo de texto con modelines. Estos modelines son incorporados a la tabla de modos del programa sin pasar por el generador de modelines.

Finalmente, GM se pasa todo esto "por el forro", y vuelve a calcular sus propios modelines, ignorando cualquier ajuste que se haga con Arcade OSD. Si queremos forzar un modeline precalculado o modificado por nosotros, hay usar la opción -modeline, introduciéndola en un archivo .ini para el juego o driver concreto.

Ferix lo que hizo fue desproteger la bios de la ArcadeVGA. El driver de monitor del que hablas me suena que era un .inf que había por ahí. La emulación de EDID que te comentaba yo actúa a un nivel más interno, Windows te reconoce el monitor arcade como cualquier otro monitor normal. Se me pasó decir que todo esto sólo funciona a partir de Windows 7.

Dios mío, esa versión de MAME tiene 12 añacos.

En Dosbox puedes configurar la resolución que tu quieras. Yo lo tenía así y me iba perfectamente con los drivers modificados. Ahora no recuerdo los detalles.