> Run a game w/ the verbose option and check the display info, sometimes video drivers > don't report that correctly.. so it may be //.DISPLAY4 instead or whatever. > > Actually, try \\.\DISPLAY2 instead, per the mame.ini.
Thx!
Instead of: "mame -screen0 //.DISPLAY2" I have to use: "mame -screen0 \\.\DISPLAY2"
Strange is that \\.\DISPLAY2 is actually the primary monitor, but mame shows screen0 on the other monitor.
E:\Emu\mame>mame -verbose puckman Parsing mame.ini Parsing mame.ini Video: Monitor 00010003 = "\\.\DISPLAY1" Video: Monitor 00010001 = "\\.\DISPLAY2" (primary) Direct3D: Using Direct3D 9 Direct3D: Configuring adapter #1 = NVIDIA GeForce 8800 G Direct3D: Using dynamic textures Direct3D: YUV format = RGB Direct3D: Device created at 1200x1600 Direct3D: Max texture size = 8192x8192 DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channe RawInput: APIs detected Input: Adding Mouse #1: HID-konforme Maus Input: Adding Gun #1: HID-konforme Maus Input: Adding Kbd #1: Standardtastatur (PS/2) DirectInput: Using DirectInput 7 Input: Changing default joystick map = s8.4s8.44s8.4445 s8888888s 4s88888s6 44s888s66 444555666 444555666 444555666 44s222s66 4s22222s6 s2222222s Input: Changing default joystick map = s8.4s8.44s8.4445 s8888888s 4s88888s6 44s888s66 444555666 444555666 444555666 44s222s66 4s22222s6 s2222222s Starting Driver Device 'root' (missing dependencies; rescheduling) Starting Z80 'maincpu' Starting Video Screen 'screen' Starting Speaker 'mono' (missing dependencies; rescheduling) Starting Namco 'namco' Starting Driver Device 'root' (missing dependencies; rescheduling) Starting Speaker 'mono' Starting Driver Device 'root'
-Flynn
Edited by Flynn (11/24/10 08:23 AM)
|