1
clrmame Discussion / temp folder not used during database update
« on: 19 June 2016, 12:54 »
Hi,
I have my clrmamepro unzipped on a network share with gigabit connection.
I experience bad performance during creation/update of databases (mame64.exe --listxml), so I configured CMPro_TempFolder to point at a directory on my local hard drive.
But cmpro uses the default temp folder (which is "temp" in the cmpro program directory on the network share) during this process - at dead slow speed. Everything's fine (scanning/fixing/merging), but database updates are a pain.
Is this going to be fixed?
It would be great if I could use environment variables for path definition, such as %TEMP%.
I have my clrmamepro unzipped on a network share with gigabit connection.
I experience bad performance during creation/update of databases (mame64.exe --listxml), so I configured CMPro_TempFolder to point at a directory on my local hard drive.
But cmpro uses the default temp folder (which is "temp" in the cmpro program directory on the network share) during this process - at dead slow speed. Everything's fine (scanning/fixing/merging), but database updates are a pain.
Is this going to be fixed?
It would be great if I could use environment variables for path definition, such as %TEMP%.