Nope, the gotcha is still there after boot-up has completed with R:\Temp running OK.
As soon as CHS is restarted after setting the CHS Tweaks to Force to system Temp directory
, the error: Error DBG103: DBISAM Engine Error # 11013 Access denied to table or backup file '124120'
- pops up and and CHS is without
Whilst CHS is still thus active, I go into CHS to change the Tweaks, and this error pops up again: Error DBG103: DBISAM Engine Error # 11013 Access denied to table or backup file '124120'
I then set CHS Tweaks back to Let database engine decide
and then terminate CHS and restart it. CHS then seems to start up just fine, with all settings correct as previously.This seems to be consistently repeatable.
However, CHS is definitely
"allergic" to the ImDisk
RAMdisk under this current version of Win10-64 Home
, whereas it was perfectly OK using that RAMdisk under Win10-64 Pro
I presume that the likely cause could be some vestigial Registry entry in this Home
version which remains even after fast startup
has been disabled. I shall try to research that as I'd like to know.
It might be worth identifying exactly what CHS looks at when the user sets CHS Tweaks to Force to system Temp directory
, as a good starting-point, because that's when the error is triggered - e.g., whether it checks the Registry for anything at that point.
As far as any other apps being similarly afflicted by this mysterious error, so far there's still been no sign. Pretty much everything that has to use system Temp will need to be happily using that ImDisk RAMdisk. Apart from CHS, everything else seems stable with it, so far.