filipetolhuizen wrote:I suppose the message is due to another program which runs when you try to run 16 bits applications.
A separate program? I expect it's some internal Windows thing buried in the kernel.
A quick Google search turns up a page in Windows Internals:
https://books.google.ca/books?id=w65CAwAAQBAJ … 20ntvdm&f=false
You could go and try to patch the kernel or insert some sort of hook, I suppose, but in the end it would probably be easier (and safer) just to make a separate launcher for starting every .exe file.
filipetolhuizen wrote:If so, replacing this program with wowexec or something else like WINE could be possible?
There have been threads here before about running WINE on Windows; at this point I doubt it's ever going to happen (unless it's something like WINE running in Linux running in DOSBox). Besides, WINE's ability to run 16-bit Windows code relies on some unique trickery exclusive to the Linux kernel, and even those tricks are starting to get phased out (or so I understand).