http://mamedev.emulab.it/clrmamepro/binaries/cmpro20191006.rarfixed: wrong software list rom size for roms which imply an offset of 0x00000000 as default (upcoming MAME)
added: automatic 32k path length support, no more need to use \\?\ prefixes (*)
misc: updated zip, rar and 7z dlls (4.6.7, 5.71, 1900)
misc: updated sha1 c++ class implementation to 2.1
misc: switched to Visual Studio 2019
fixed: remembering window positions on multiple / virtual screens fails
fixed: rebuilder match count for files with identical crc32 but different sha1
fixed: rebuilder removal of rebuilt files for files with identical crc32 but different sha1
fixed: detect chd clone to clone moves (aka MAME 206 vs4e to vs4eo rename)
fixed: rom count for fully missing sets included bios roms even when the bios set is available
misc: added cmpro.ini option Adv_WindowToFront = on (on / off) to handle the automatic bring window to front functionality
misc: profiler cache which reduces rescanning datfiles/settings on each profiler visit, should speed up profiler for users which have lots and lots of dats. Delete/Add/Move operations will force a refresh at the moment though
misc: limit extension removal to a max of 3 characters and no space after the .
(*) this needs of course testing. Generally, there are some remaining problems (but they were there before if you used the prefix explicitly). NTFS supports 32k path lenghts but each single folder and filename can't be bigger than 260 chars long. The problem is when it comes to directory tree walking functions when you pass a long path+filename to it. The MS library code tests this full path+filename against the 260 limit (and not just the filename and the single paths) and will fail when it shouldn't. I need to find a workaround for this. However, if you succesfully used the prefix method before, it should work for you.
(**) cmpro20191006 build contains some additional fixes for 32k UNC based paths and the scanner case test for 32k paths.
