leecher1337

Do you have a DOS-Application available for testing?

Unfortunately, you didn't supply an application for testing, so I was unable to check. I cluttered together a vdm redirector and used DLLs in order to potentially work with Win...

Hm, I cannot reproduce the problem. I installed [FORTRAN 4.10](https://winworldpc.com/download/4863c2bf-c2a5-18c3-9a11-c3a4e284a2ef) via SETUP.EXE and compiled a demo program (DEMO.FOR) just with `FL DEMO.FOR` and it compiled without any issues on Windows...

I installed with NTVDMx64 under Windows. Unpacked all installation disks, `subst A: .`, ran installer from A: and pointed all dst. directories to c:\FORTRAN and then let it build the...

That's easy, just edit Windows\SysWOW64\config.nt and add: ``` device=%SystemRoot%\system32\ansi.sys ``` Then you can see ANSI-colors in DOS-programs. For example, you can download https://www.robvanderwoude.com/files/ansidemo.zip and then run it with ``` command...

That's how it is on Windows. If you think about it a little, you can guess why it behaves this way: command.com executes entered commands via Windows execute call. .bat...

32bit code should still work with this stupid architecture and if not, nobody would want to use it anyway. So just ignore it and ensure that you buy X86-64 CPUs...

Unfortunately, the VxD driver model is completely different than the NT driver model, there is a reason why this wasn't implemented by Microsoft into the NTVDM and there are only...

Here is an example on how to write your own VDD driver extensions to replace the VXDs: https://github.com/leecher1337/antzvdd

First step is to reverse engineer the .sys driver, then you can try to write a 64bit driver based on your reverse engineering results.