win32 as Vas suggested is most compatible. dinput frequently has trouble with these weird software key injectors too.

Virtual keyboards aren't necessarily a problem, provided you know where they come from and the driver that provides them is working correctly. For example, my workstation has two virtual keyboards: one is provided by the Wacom tablet driver, and one is provided by the Logitech mouse driver. They're needed so that tablet or mouse inputs mapped to keyboard combinations/macros work correctly with applications and games that read keyboard(s) using RawInput or HID APIs. These two virtual keyboards don't cause a problem with MAME on my system. If you don't know where your virtual keyboards are coming from, you probably have a problem though (maybe something not uninstalled properly).

You can try changing the keyboard input module and see if it changes the behaviour - if it's really a problem with the keyboards this will likely fix it. Add "-keyboardprovider win32" to the command line (without the quotes) and see whether the behaviour changes.

Some people have reported trouble with certain sound drivers with MAME on Windows. Can you try adding "-sound none" (without the quotes) to your command line to completely disable audio output? If that changes the behaviour it could be a sound driver issue, and you can try reinstalling your sound drivers or using a different MAME sound output module (xaudio2, dsound or portaudio).

You could try running with different video modules, too - try "-video opengl" or "-video bgfx" (without the quotes) and see if anything changes. Sometimes DirectX 9 drivers are problematic, but OpenGL drivers or the DirectX 11 drivers used by BGFX work better.

yeah, there are some situations where you end up with multiple ones, although I have plugged / unplugged a lot of things into this box over the years and it's still fairly clean. I'd still look into that vjoy thing tho, I have heard of such software causing issues (and any remote desktop software etc. if you happen to be running that) a lot of them use dodgy drivers which can end up hanging

Wow, you're right, that is really weird for the keyboard. As far as the displays it is correct, I have 3 monitors and one TV for a total of 4 displays. The weird part about that is it says my primary display is #1 when my primary is actually #2 display as far as Windows 10 goes, not sure how MAME arranges them. I'll check out those leads and see if anyone else see's a problem. Thanks.

Thanks for taking a look.

Microsoft Windows [Version 10.0.17134.471]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd..

C:\Windows>cd..

C:\>cd mame202

C:\mame202>mame64.exe Scramble -verbose
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Video: Monitor 65539 = "\\.\DISPLAY2"
Video: Monitor 65541 = "\\.\DISPLAY3"
Video: Monitor 65543 = "\\.\DISPLAY4"
Direct3D: Using Direct3D 9
Physical width 1063, height 1440
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 980 Ti
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col05#7&118eb48c&0&0004#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col06#7&118eb48c&0&0005#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_00#7&3565f24e&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #3: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col04#7&118eb48c&0&0003#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #4: HID Keyboard Device (device id: \\?\HID#WmVirtualDevice#2&25d493e&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: ELECOM USB Mouse (device id: \\?\HID#VID_093A&PID_2521#6&9c61094&1&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#WmVirtualDevice#2&2b3e62a0&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: ELECOM USB Mouse (device id: \\?\HID#VID_093A&PID_2521#6&9c61094&1&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#WmVirtualDevice#2&2b3e62a0&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding joystick #0: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079b95d0-1bce-11e8-8002-444553540000)
Input: Adding joystick #1: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079b95d0-1bce-11e8-8004-444553540000)
Input: Adding joystick #2: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079bbce0-1bce-11e8-8006-444553540000)
Input: Adding joystick #3: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079be3f0-1bce-11e8-8008-444553540000)
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1045x1393
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
Region ':maincpu' created
unzip: opened archive file roms\scramble.zip
unzip: found roms\scramble.zip ECD
unzip: roms\scramble.zip has no ZIP64 ECD locator
unzip: read roms\scramble.zip central directory
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':audiocpu' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':gfx1' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':proms' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Optional shared pointer ':decrypted_opcodes' not found
Optional I/O port ':IN2_GAME9' not found
Optional I/O port ':IN2_GAME8' not found
Optional I/O port ':IN2_GAME7' not found
Optional I/O port ':IN2_GAME6' not found
Optional I/O port ':IN2_GAME5' not found
Optional I/O port ':IN2_GAME4' not found
Optional I/O port ':IN2_GAME3' not found
Optional I/O port ':IN2_GAME2' not found
Optional I/O port ':IN2_GAME1' not found
Optional I/O port ':IN2_GAME0' not found
Optional I/O port ':FAKE_SELECT' not found
Optional device ':ppi8255_2' not found
Optional device ':digitalker' not found
Optional device ':cclimber_audio:aysnd' not found
Optional device ':8910.2' not found
Optional device ':dac' not found
Optional device ':audio2' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional memory region ':palette:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':soundlatch:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Starting Scramble ':'
(missing dependencies; rescheduling)
Starting Zilog Z80 ':maincpu'
Starting Watchdog Timer ':watchdog'
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Video Screen ':screen'
Starting Speaker ':speaker'
(missing dependencies; rescheduling)
Starting Intel 8255 PPI ':ppi8255_0'
Starting Intel 8255 PPI ':ppi8255_1'
Starting Zilog Z80 ':audiocpu'
Starting Generic 8-bit latch ':soundlatch'
Starting AY-3-8910A PSG ':8910.0'
Starting AY-3-8910A PSG ':8910.1'
Starting Discrete Sound ':konami'
Starting Timer ':stars'
Starting Scramble ':'
(missing dependencies; rescheduling)
Starting Speaker ':speaker'
Starting Scramble ':'
Attempting to parse: default.cfg
Attempting to parse: scramble.cfg

Hi Haze, sorry about that, I tried to be as thorough as possible for my novice/modest MAME ability in explaining my issue. So let's see, I went to https://www.mamedev.org/release.php and downloaded a fresh mame0202b_64bit.exe at the time. I didn't overwrite another install to the same folder, it was/is fresh. I ran the .exe and it made itself it's own folder and I have tried to run it from there ever since.

I have tried having only one rom in the roms folder before but I just did it again, which for now is (Scramble). All the rest are on another drive waiting to see if I can ever fix the issue. i have tried other single roms as well. They all freeze on the initialization screen on versions 0.172 through 0.204, on versions 0.171 and below MAME works great and loads the roms. I just now tried your suggestion of unplugging all joystick controllers and MAME 0.202 still freezes. Thank you for your suggestions thus far. Any other suggestions from anyone would be greatly appreciated or instructions on how to spit out a log error file.

this kind of thing is usually caused by a user setting error, or some kind of corrupt resource. (both often caused by trying to upgrade MAME by simply copying an exe over an old one rather than extracting things properly, also badly packed 'extras' collections, although you don't state the use of anything like that)

you're not really explaining what you've tried at all, eg. if you've extracted a 100% fresh version of MAME, from mamedev.org into a clean folder, put a single game in the 'roms' folder and tried that.

you should also make sure all controllers etc. are unplugged in case it's an issue with something like that. if it's not a corrupt MAME install, it's likely a conflict with something else you have installed or plugged in.

MAME generally isn't very fussy, and your specs are 100% standard and suggest you should have no problems at all (it's not far off the machine I use for MAME development)

I'll add a partially working driver for the disk station soon. Here's a screenshot of it with no disk inserted:



Disks boot too, but the keyboard seems erratic:





It doesn't boot the disk you provided though, this is this one: ftp://ftp.informatik.uni-stuttgart.de/pub/cm/mupid/disks/mcpm.imd

There is also an alternate firmware for it at ftp://ftp.informatik.uni-stuttgart.de/pub/cm/mupid/roms/

This seems to be the Grundig FL100? Screenshot:



Maybe it expects some kind of special terminal?

Ok, I managed to dump all eproms, but the plcc 27c64 on the WDC Disk Controller and the MBL8042 chips used as keyboard controllers.

@rfka01, I'm sending you a PM.

Cheers,
Rob

But it isn't a newly supported system, so gaming the script that generates the list is misleading.

Is it really worthwhile when the machines are actually identical? I mean, there's something to be said for aliased ROM definitions when the machine config or inputs are different, but for a pure badge-engineered version, I don't think it's worth it.

I've sent a PR that adds the rest of the ROM revisions to the Olivetti M24 driver.

The emulated M24 somehow gained a second, faulty RT clock ... why does the BIOS even detect two RT clocks?



A real M24 is content with having one RT clock ...



The ROMs of the badge engineered incarnations of the M24, the AT&T PC 6300, the Xerox 6060 and the Logabax Persona 1600 are identical to the M24, retaining the Olivetti string in the ROM.

Is there a way to add an alias to access the M24 driver under another name without duplicating the ROM section? If so, I'd suggest to add at least a pc6300 alias to make the driver more familiar to US users.