Closed KernelFox0 closed 2 years ago
Which application are you trying to use? You can debug the application with your favourite DOS debugger to find out the reason (i.e. Turbo Debugger). Or you can use NTVDM's debugger YODA to do an instruction trace and check out the code path leading to the message. Does the application work correctly in 32bit Windows NTVDM?
Works correctly on 32-bit Windows NTVDM. The app is msd.exe. Some other apps are doing this, but not all.
MSD works on Windows 7 X64.
Also works on Win10 x64 here...
By the way, I know the new build support OLE 2.0
I check https://en.wikipedia.org/wiki/Object_Linking_and_Embedding OLE 2.0 : New features were OLE automation, drag-and-drop, in-place activation and structured storage.
But i hard to understand OLE 2.0 for CMD console. Any video for demo ??
OLE 2.0 is just for WOW32, so for 16bit Windows applications. NTVDMx64 implementation still is slow and partly buggy, so it's propably not very useful compared with otvdm/winevdm, but for the sake of completeness, it was added anyway.
No further updates on MSD.EXE issue given, issue not reproducible, assuming it has been solved, reopen ticket on further updates.
I tried to open an msdos app, and it said "Error initializing screen". What can I do?