3 ms·
That's a DOS executable though, and won't run on 64-bit Windows.
by poizan42 6y ago
That's a DOS executable though, and won't run on 64-bit Windows.
- mytailorisrich 6y agoNot out of the box but with something like vDos it should.
- weinzierl 6y agoRegular com programs won't run, but I'm waiting for the day the vulnerability is discovered that let's you run a specially crafted binary because of left over code from the old com launcher. Is the com extension still recognized in 64-bit windows?
- zinekeller 6y agoNo, like really impossible on a hardware level (most 16-bit instructions are hidden on hardware level on entering 64-bit mode) and on a software level (NTVDM is separate from Windows NT from day one (since it only works on x86 hardware and not on DEC Alpha for example) and it was an optional component since Vista but only on an x86 installation though).
- poizan42 6y agoConsidering that COM programs are headerless I can't imagine any way a specially crafted binary could do anything since there is no parsing going on. The "COM loader" just hands it off to NTVDM which does not exist on 64-bit Windows (there are 3rd-party implementations though) And yes, the com extension is still recognized and will pop up a dialog telling you "This app can't run on your PC". But actually .com and .exe files are handled equivalently, so you can just rename an .exe (i.e. PE executable) to .com and it will run - that doesn't make it a COM executable though...