My test machine is the same that I used to compile the binaries, it may have some special configuration due to all the build tools... I will test it tomorrow in a empty window 10 install.
Are you sure you selected the debug configuration in the
debug launch drop box ? You can choose between run and debug (run is selected by default).
Could you try these steps :
- run the vasm executable (vasmm68k_mot.exe) in a dos box, just to see if it is functional
- set absolute paths in the .vscode/settings.json
- delete all the "*.o" files in the build directory
- delete the fs-uae/hd0/gencop file
- click on the build word in the bottom status bar of vscode and verify that the fs-uae/hd0/gencop file has been generated
Hope this helps,
I will try to add some error reporting in the next release to help to diagnose the configuration problems.