|
Title: Cannot open file Post by: Anthony on September 21, 2011, 12:54:11 PM Applying a filter during a batch edit, I'm receiving the following message:
"Cannot open file c:\programdata\ddisoftware\qimage\{q}work4.{q}. The system cannot find the file specified My version is 2012.104 running in 64 bit Windows 7 The only thing I did differently was to "show the desktop" as Qimage was taking up the entire screen Many thanks for your help - Anthony Title: Re: Cannot open file Post by: Terry-M on September 21, 2011, 02:19:09 PM Hi Anthony,
The normal file path to saved filters is: C:\ProgramData\ddisoftware\Qimage\Filters Yours seems to have the Filter folder missing. Search for that file name to see where it is or in the editor File menu - "Open Filter Parameters form File", the correct folder should open, see if it's there. Terry Title: Re: Cannot open file Post by: Anthony on September 21, 2011, 02:34:12 PM Everything is in its right place. Unless you're aware of the problem, let's treat it as a one off. I'll post if it does it again. I don't have time to test at the moment
Title: Re: Cannot open file Post by: Terry-M on September 21, 2011, 05:10:49 PM Quote Unless you're aware of the problem I'm not aware of any QU problem in this area - could be W7 or, dare I say it, operator error :o ;DOne other thing, your file name "{q}work4.{q}" (if that is the file name) is a bit odd; a filter has an extension of .flt which is not shown. Terry Title: Re: Cannot open file Post by: admin on September 21, 2011, 06:19:58 PM That's a temporary file used by QU. Sounds like interference from antivirus software. Do you use NOD32? They're one of the biggest culprits: I know because I use NOD32. Love NOD32 but they do have a lot of options that can get you into trouble with real time scanning. Whatever you use for antimalware, try entering an exception for the c:\programdata\ddisoftware\qimage folder.
Mike Title: Re: Cannot open file Post by: Anthony on September 21, 2011, 07:27:40 PM Thanks Mike. AV is Sophos and Malware is Microsoft defender. I'll see what happens next time I pass photos through the filter. After checking, I notice that the error occurred *after* all the photos had been processed, so no harm done. I've not had this error before, although I had just upgraded to 2012.104 (in the unlikely event that that is relevant)
|