When FreeFixer runs into a file which it cannot open due to it being
used by another process FreeFixer tries to unlock it. It seems like the
unlocking did not work and unfortunately FreeFixer did not report which
file caused the problem in the error message.
I'll improved FreeFixer to better handle this case by making sure it
completes the Recently Modified scan and by including the full path of
the file that caused the problem in the error message. I'll start
working on it now. This bugfix will be included in FreeFixer v0.60.
Thanks
/Roger
--
You received this message because you are subscribed to the Google
Groups "FreeFixer User Forum" group. To post to this group, send email
to freefix...@googlegroups.com. To unsubscribe from this group,
send email to freefixer-for...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/freefixer-forum?hl=en.