Renaming files

[GJB]

If I close a file in PDF-XChange I cannot rename it through Windows (eg Explorer) as Windows says it's being used by another process. I still can't rename the file even if I close PDF-Xchange. Even without PDF-XChange running, there is still a process running and I have to kill this with the task manager ('end process tree' for PDFXCview.exe), and only then I can successfully rename the file.

Surely this should not be necessary - why doesn't PDF-XChange release the locks on the file when the file is closed.

I also find that......
- once I've killed PDF-XChange through the task manager it seems to re-start of it's own accord even if I don't open a pdf file
- pdf files are locked and cannot be renamed in Windows even if they have not been accessed by PDF-XChange (but can be renamed when PDF-XChange is killed through the task manager).

Is there a way to stop this behaviour?

Thanks

[Paul - PDF-XChange]

Hi GJB,

thanks for asking this. That is definitely not intended behaviour, it should be released when the Viewer is closed. Does this always happen or is it intermittent? Is it specific to certain files or all files?

For example if you start the Viewer after a system reboot where nothing should be running (check for PDFXCview.exe in the task manager), then without opening a file, kill or close PDFXCview.exe does it restart itself?

Note that if you have the PDF-XChange Viewer Browser addin running that will show up as PDFXCview.exe in the Task manager also.

I would also check your program files folder to see if you have multiple versions installed. You can check the properties of the instances you see in Task Manager to see if they are the same (path, date etc).

Finally, do you have "Allow multiple instances' checked in the Viewer preferences? Edit --> Preferences --> General --> Application --> Allow Multiple Instances

Regards the lock on the file - as I said, it should be released when the Viewer is closed and I suspect this is not happening because of the remaining processes you are seeing. If you are up for it you could use Process Explorer to see what has a handle on the file at the time you expect it to be unlocked: http://technet.microsoft.com/en-us/sysi ... s/bb896653

[GJB]

Mystery solved, and nothing to do with PDF-Xchange! I use FreeCommander XE as a replacement for Windows Explorer, and it has the facility to show a preview of a file within the FreeCommander window. It was using PDF-Xchange as the viewer, and so inevitably the file was locked and this stopped the renaming in FreeCommander or Windows Explorer The same happens if I make FreeCommander use Acrobat Reader. I'll need to make FreeCommander use a viewer that is read-only and so doesn't lock the file.

Thanks for your help.

[Stefan - PDF-XChange]