cracyc

This is caused by it creating lots of gdi objects, selecting them then deleting them without deselecting first. It works fine before https://github.com/otya128/winevdm/commit/c54eb53cb71c2b850262fb6691cac1847fcbdd47 which doesn't allow deletion of selected objects....

Try renaming the path so it is at most 8.3 chars, the two periods in otvdm-v0.8.1 might be the problem. If that doesn't work will need a trace.

https://github.com/cracyc/msdos-player/tree/vt makes this work much better with full vt escapes rather than an ugly workaround. WP6 with terminal and win32 console API  WP6 with terminal and vt...

Vt support is mostly done. Buffer resizing had to be disabled as it broke output (and is the main reason why win32 console io didn't work in the terminal) and...

Which version of WP does that? 6 seems to work okay other than the file manager.

Exceptions there are supposed to land at https://github.com/mamedev/mame/blob/master/src/devices/cpu/i386/i386.cpp#L2857. The only reason it's caught there is to fix esp. OS/2, at least, requires that because it lazily allocates the stack.

The attributes in the v240 aren't hard coded in any way, it's all done by the upd7220 and the discrete hardware attached to it. The main problem is the logic...

FWIW, fuse isn't right for this because chd are block devices that can have a variety of filesystems. [qemu-nbd](https://github.com/qemu/qemu/blob/master/qemu-nbd.c) would be a better starting point.

They went even further in 24H2 by removing pretty much all the user 3.1 style compatibility code (https://github.com/otya128/winevdm/pull/1469) which should even affect nt31/win32s programs. I'd expect the basesrv vdm stuff...

This appears to be a dos program. Winevdm's dos support isn't great. Google suggests that this program controls some equipment so maybe dosbox-x would work which has physical serial port...