Screen debugging will switch back to the debug log in case of a crash. So yes, it would be useless in this case -- but you don't need screen debugging in a VM; all the common hypervisors support serial ports.

And please try to get a debug log. https://reactos.org/wiki/Debugging#Debu ... t_messages
Thanks.

There are operating systems written in C# and probably Java... it's just a question of how much effort you want to put into the toolchain and execution environment. There are at least three aproaches I can think of: 1. You could create/use a toolchain that will compile these languages to native code...

We can't use this code unless the author submits it to us. As-is, we don't have the right to distribute it under the GPL, nor do we have any assurance that it was written in a legal manner.

For Windows-to-Windows connections, Remote Desktop supports what you're asking using a feature called RemoteApp. You can see if that feature is supported by some Linux clients (Google comes up with at least SeamlessRDP, which sounds like what you're looking for... I didn't look into it though). If y...

If you use the same compiler, you should get the same executable (minus timestamps and such, and ReactOS bugs). Windows applications do not use syscalls directly, they instead link to system dlls (ntdll.dll contains the syscall stubs, but Win32 applications aren't usually supposed to use those NT fu...

I'm not saying to install the service pack -- but you can extract dwmapi.dll from it. I don't know if the Vista+ version of this dll will work in ROS, I'm guessing it might expect DWM... so Wine's might be safer. _except_handler4_common is a Vista+ export, so yes, ReactOS doesn't have it. msvcrt.dll...

Assuming you don't want Microsoft's version (which you could probably get through a Vista or Win7 service pack download), Wine seems to have an implementation of it -- so you could look for a Windows-targeted Wine build. That said, if your goal is to use it on ROS... it may or may not work. It's a V...

Ich habe gerade noch das liveusb-ReactOS-0.4.10-vgal.iso im Debug-Modus laufen lassen, es hängt vermutlich an der gleichen Stelle wie das bootusb-ReactOS-0.4.10-vgal.iso. Das Log-Fenster zeigt als letzten Eintrag driver/swenum.sys. Dabei muss ich es dann wohl belassen. Um mal wieder auf die eigentl...

Not true, only 6.0.0 Guest Additions don't work (you'll get a BAD_POOL_CALLER bugcheck). Anything else is a new issue.
Try to get a debug log: https://reactos.org/wiki/Debugging#Debu ... t_messages

You are free to redistribute ReactOS under the terms of its license. Which, in short, just says that if you redistribute binaries based on non-official sources, you must also make those sources available. So yes, it's completely fine to publish VM images.

The release was branched in December, so aside from back-ported fixes it is indeed code from 2018.

Now that that's clarified, you still haven't explained what you meant by "completely fix the app renderer". What exactly is broken that you'd like to see fixed? If there are no Jira tickets for those issues, it's unlikely to happen.

Does it work in Windows XP/2003? If so, it's supposed to work in ROS. You should use whatever 32 bit installer you would use on Windows.
Since it's Chromium-based, however, you may have to pass it the --no-sandbox parameter in order for it to work, per https://jira.reactos.org/browse/CORE-9272

This may simply be a problem with the mixer API used by the Sound Properties dialog. If you try to play C:\ReactOS\media\ReactOS_LogOn.wav in the built-in audio player, does it work?