Caught error "'ERROR_BAD_COMMAND'"

I note that this shouldn't happen since about 5i.4

Q: Launching an image I get: Caught error "'ERROR_BAD_COMMAND'" when logging to changes file; entry not logged. Why?

A: This appears to be due to a bad startup directory selection by Windows if the image is launched by dragging an image file onto the VW engine executable, and saving the image. The next time the image is launched, this error occurs. Once the image has been damaged in this way, there's no recovery except going back and rebuilding the image.

The solution is to never launch VisualWorks by dragging the image onto the engine on MS Windows systems. Always use shortcuts, or use the visualworks.exe and visualworks.ini mechanism, which clearly specify the execution environment.