DOS ain't dead

Windows 10 NTVDM (Users)

posted by RayeR , CZ, 31.07.2015, 22:56
(edited by RayeR on 01.08.2015, 03:57)

Hi, I just tried to install new Win10 32-bit from current official ISO inside VM and encountered problems with running some windows and DOS programs. After you run 1st DOS program, the system ask you that NTVDM component needs to be installed. After click OK it installs (it's already on HDD, just disabled) and program runs. But I can run only *.exe programs (including DOS/DJGPP so DPMI is still there) but not *.com programs - they cause this NTVDM error: http://rayer.g6.cz/1tmp/w10d.png
On other hand I'm happy that my unsigned kernel driver installed and by tools like spipgm, cpuid and smb runs without problem (when run as admin). BTW I don't plan to upgrade to W10, I was just curious...

UPDATE:
I found that only some *.com and *.exe program cause problems. Strange that there's different behavior when the program is launched from cmd.exe - it crash and directly from explorer or shortcut on desktop or Win+R - it starts OK. I tried both cmd.exe in user and admin mode - no difference.
http://rayer.g6.cz/1tmp/w10f.png
Of course programs using VGA graphics modes are not supported in any case.

---
DOS gives me freedom to unlimited HW access.

Complete thread:

• Windows 10 NTVDM - RayeR, 31.07.2015, 22:56
  • Windows 10 NTVDM - alexfru, 01.08.2015, 09:43
    • Windows 10 NTVDM - RayeR, 03.08.2015, 15:41
      • Windows 10 NTVDM - alexfru, 04.08.2015, 06:35
        • Windows 10 NTVDM - RayeR, 04.08.2015, 18:43
          • Windows 10 NTVDM - marcov, 04.08.2015, 19:30
          • Windows 10 NTVDM - alexfru, 06.08.2015, 06:41
    • Windows 10 NTVDM - Guti, 15.08.2015, 09:14
      • Windows 10 NTVDM - Rugxulo, 16.08.2015, 04:18