NTVDM = Windows NT Virtual DOS Machine
(supposedly) it's for running 16-bit programs in a Dos-shell. But MapView I/II are not 16-bit programs ... I forced MVii to 32-bit build; i could be wrong because I'm just not sure about that stuff. In this case, however, it's highly unlikely - i suspect that it would be very difficult to even compile a program to 16-bit in today's age.
Also, when I run MV2, if it were 16-bit (which it isn't
) ntvdm.exe should show up in my TaskManager. It doesn't. Neither does it show up when i run PckView2, which is built with the same settings. Also, in the Help screen for PckView i twiddled-in a brief system-inspection routine that prints the build-type (release or debug), the bit-type (for lack of a better way of putting it), and the OS-interaction-type (ditto). Mine says:
release
X86
WoW64
meaning it's a release-build, 32-bit, running under WoW64
It'd be kinda nice if you could get PckView2 to run, just to check that ... but NOTE: PckView2 should not be run until *after* MapView2 runs at least once (because settings that pckview relies on are written to disk only *after* MVII runs).
> im running Win7 Home Premium 32 bit
hm. There's something called a VirtualStore in windows. I don't know much about it; it seems to be a so-called virtual space on the harddrive that Windows will write things like MapView's configuration files to if MapView is installed to a protected space. It has its problems because files are being written to places they aren't expected to be.
I mention the VirtualStore since in your 2nd screenshot i think i see "@MSITStore:C\Mapview2\MapView.chm" .... "Store" suggests to me that Windows is trying to shuffle stuff into the VirtualStore ... eg, it could be trying to make a copy of the .CHM file to the store before opening it.
Have you checked for malware recently? (personally i doubt it 'cause there'd likely be a lot else going wrong on your computer if so)
my best **guess** at this point, is that Win7 Home has extra security that aggressively clamps things into protected spaces. I suggest hunting down things like UAC (User Access Control) and Ownership properties on the Mapview directory ....... personally i obliterated as much of that stuff as I could as soon as I got Win7 64. .. i tried, i really tried to live with it but just couldn't,
edit: Another way of looking at it, why is your computer trying to open a dos-box ? o.O
edit2: it's a long shot but you could try right-click mapview.exe, Properties, Compatibility, Windows XP (Service Pack 3)