devio.exe itself should run fine even on Windows NT 3.51, unless I have made some mistake very recently. But I don't think so because I cannot remember having even tried to build it with VC++ 2013. But depends.exe would show you exactly what is requiring something that your OS doesn't have.
Yep , that's the reason why I posted here and cited the *something else* as possible culprit, though I don't use often devio.exe, every time I used it (for simpler tests) it always worked .
The point is that IF I used a stupider, already much more bloated later Windows OS, I would already have the stupid .Net (possibly 4.0 version) installed and then I would use the IMDISK with discutils.dll (or whatever other stupid .Net facility it would provide), but our good friend erwan.l offered this thing here as a native alternative to the .Net bloat, seemingly without checking if it worked at all, natively.
As you might be well aware I am a self-declared, grumpy, old, bastard, and when I download something described as "native", I expect and demand that it should §@ç#ing work out-of-the-box, or at least provide the list of what (the heck) it needs in order to work or state how it is (say) targeted only to Vista or 7 or later and won't work on XP or on XP SP3 only.
And yes I know that XP is out of extended support, and that I should get a later Windows OS or at least upgrade to SP3, but this isn't going to happen any soon.
No prob about the msvc .dll (though it is a nuisance and makes very little sense) as it is easy to add it, while the GetLogicalProcessorInformation is a show stopper (at least for me) until some good soul will recompile (if possible at all) the libvmdk.dll (which BTW is now on github https://github.com/libyal/libvmdk) without these stupid dependencies.