Peter Dell

Fix confirmed. ASMA is updated.

That's my preference from the 80s. Single user computer, so TEMP is not somewhere in the user profile, but there. Environment variables are set up like this: TEMP=C:\TEMP TMP=C:\TEMP When I trigger the diff, two .sap files are created there. But they are .SAP files, not text files,

I've added the _CRT_SECURE_NO_WARNINGS; define the project and the "unsafe" warnings are gone. But these two are still there and look valid to me: C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(2813,24): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data 1>C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(3991,10): warning C4996: 'strdup': The POSIX name for this item is deprecated. Instead, use the...

warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead.

Good solution, thanks.

fix-brk is a quick-and-dirty single-use tool for ASMA. No, I'm not going to maintain or document it. :) The I'd suggest to just remove it from the repo. Please attach the broken Rock_1.sap file for tests. See below. The root cause of your problems is that you installed a wrong perl on Windows, I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" files?

fix-brk is a quick-and-dirty single-use tool for ASMA. No, I'm not going to maintain or document it. :) The I'd suggest to just remove it from the repo. Please attach the broken Rock_1.sap file for tests. See below. The root cause of your problems is that you installed a wrong perl on Windows, I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" file?

I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" file?