>>>Anybody run across this? Better yet, anybody found a solution?
>>
>>I keep all XFRX files (zlib included) in xfrx own folder as it was shipped and then use
>>
>>

>>cXFRX_Folder='C:\wherever_XFRX_is' 
>>set default to (cXFRX_Folder )
>>

>
>I somehow don't like this - if anything goes wrong, you're stuck in the wrong directory and your error handler isn't really in charge of restoring the working directory. Maybe if you used a setting object from Tom Rettig's envlib, which would restore the previous location during its .destroy()...

Well in my case this call is within the class method at the end of which default path is being restored. I just cut out here peace of code that invokes xfrx. So in terms of keeping up practices, yes absolutely; default path have to be restored, just like any other settings we commonly set and later restore. By now it should be u/stood without even saying :)