Didn't found something similar to my case.
1) Recently built up everything from git and found that CC version works fine but way too slow.
Uninstalled it and installed Haxm version instead. But trying even to start command.com will lead to a blank screen and nothing else.
NTVDM.EXE is seen in task manager, but nothing happens.
If I kill the process then in Windows log I see a message HAXM cannot run CPU.
W7 x64 SP1 on i3-4150 (haswell). 16 Gb RAM.
Trying to work with FoxPro 2.5 for DOS both versions - for real mode and FoxProX with Phar Lap extender.
2) The second issue I've found - installer breaks config.nt file removing all #0D#0A characters, making it a one-line text.
I have to manually insert CR+LF before any new line (usually they begin with REM command)
3) running FoxPro for Windows (16-bit) from FoxPro for DOS with START command runs a new NTVDM.EXE with different parameters each time, but this new ntvdm.exe starts Foxpro for Windows only once.
The next attempt to start will not do anything.
If I manually kill the new instance of ntvdm.exe after finishing the FoxPro for windows, then I'm able to run the new instance again.
Didn't found something similar to my case. 1) Recently built up everything from git and found that CC version works fine but way too slow. Uninstalled it and installed Haxm version instead. But trying even to start command.com will lead to a blank screen and nothing else. NTVDM.EXE is seen in task manager, but nothing happens. If I kill the process then in Windows log I see a message HAXM cannot run CPU. W7 x64 SP1 on i3-4150 (haswell). 16 Gb RAM. Trying to work with FoxPro 2.5 for DOS both versions - for real mode and FoxProX with Phar Lap extender.
2) The second issue I've found - installer breaks config.nt file removing all #0D#0A characters, making it a one-line text. I have to manually insert CR+LF before any new line (usually they begin with REM command)
3) running FoxPro for Windows (16-bit) from FoxPro for DOS with START command runs a new NTVDM.EXE with different parameters each time, but this new ntvdm.exe starts Foxpro for Windows only once. The next attempt to start will not do anything. If I manually kill the new instance of ntvdm.exe after finishing the FoxPro for windows, then I'm able to run the new instance again.