Fault compiling error BNP0000: Unable to place file W:\nt\public\sdk\lib\i386\ntvdm.exe - exiting. about ntvdmx64 HOT 6 CLOSED

Hi ,

New Info.
When not use the patch.cmd so I compiled Ntvdm.exe

from ntvdmx64.

I should have mentioned that you need to compile it with 32bit Version of Windows, as 16bit support is mandatory for compilation. I suggest compiling it with Windows XP 32bit. I will update the readme accordingly.

from ntvdmx64.

Hi leecher1337,

For your information, I have included MVDM components in MinNT repository and all included MVDM components (including 16-bit portions) can be compiled using NTOSBE, even under 64-bit Windows.

Please consider writing patches for the MinNT repository so that people can easily build your ntvdmx64 without going through setting up a separate build VM and the hard-to-work-with obsolete OpenNT build system.

from ntvdmx64.

Hi,

I just had a quik look at https://github.com/stephanosio/MinNT/tree/master/base/mvdm and I find a lot of stuff missing, i.e. DPMI Dir? So I don't know how this is supposed to work.

from ntvdmx64.

I have added the portions referenced in your patches first. If dpmi is required as well, I can add it to the repository.

from ntvdmx64.

As I don't know anything about your MinNT Build system, I guess it is easer if you can adjust the makefiles.patch to your build environment, as you are used to it. The rest of the patches just patches the sourcecode, so I guess that they will work in both build environments.
The reason is that I want to stick to the classic build environment for my own builds, as I'm running Windows XP on all my work machines anyway (and most likely will also run it for the next 5-10 years) and I don't want to maintain 2 branches seperately.
If you want and you have time, you can just do a copy of MinNT, apply patches accordingly and maintain a MinNT branch of it? :)
The main reason for just releasing patches is the risk of getting DMCAed otherwise.

from ntvdmx64.