Hi, Looks like a loader problem to me. I updated the loaders end of January to be more stable, do you have the most recent loaders? https://github.com/leecher1337/ntvdmx64/commi … 79737e5f763ad7f Best regards, leecher

It just means that, if everything works so far, the "release\" subdirectory should contain all the files needed for the installation package, so chdir to the releae directory and put its contente i.e. in a .zip file and you should have a complete package containing installer and files.

I recently switched from CreateProcess() hooking propagation to injection via conhost.exe This is because CreateProcess hooks were a bit unstable with certain applications. However the loader sourcecode still supports both injection mechanisms. Seems that some stupid antivirus products mistakenly …

Hi, If you are interested in the DOS-part, you can download it from the project page. emendelson also made a build publically availabe in the issue tracker issue #7. For WOW16, this implements a cooperative multitasking scheduler, but the scheduling doesn't take place in NTVDM, but is issued to the …

I now managed to get it working on Windows 7. Additionally I wanted to work on WOW16, I got it so far that i can convert 16bit to 32bit calls, but unfortunately the 16bit appliations crash randomly mustly during startup. As there is no reproducable pattern behind it, this is pretty hard to debug. …

Yeah, it's just a proof-of-concept, that's why I just published patches and nothing more to ensure that there are no legal problems with the release itself. I guess that the DPMI stuff is fixable, it was just too frustrating to debug without yoda. It works on Windows 10 because I tested it there and …

I just wanted to announce that I managed to compile and patch Microsoft Windows NTVDM on 64bit Windows and it seems to work at least for realmode applications and even supports console graphics. This might become handy for users that want to benefit from the good console and shell integration of …

I wouldn't call this highly critical, because the file locking functions (0x5C/Int 21h) actually work like they are supposed to. Altough it's true, that I haven't implemented the 0x5D-class of DOS 3.1+ internal functions yet, they are still to be considered as "internal", therefore I guess they …

I just updated the patch a bit. It now only works for WIN32, but I saw that it had some problems with locking requests for Offsets >2GB. This seems to be the case with Microsoft Excel 5.0 for Windows 3.11 for example. Now it works correctly. I also added that the SHARE.EXE installation check returns …

I implemented a very simple locking patch. Please note that it's not thouroughly tested and I just made it to get my DOS-Application to run, but it should basically work. It's available at http://dose.0wnz.at/dosbox/ The locking.patch contains the patch (patch -p1