I've been assuming (correctly) that this was a known issue and I haven't 
worried too much about it, so it's taken me quite a while to get around 
to asking or looking into it at all.   Anyway I get:

"Failed to save file:

The process cannot access the file because it is being used by another 
process."

...in a self-compiled version of POV-Ray 3.6.0 for Windows which I've 
been using for a while now to avoid the spline / token_count issue.

The only entry I see on the server is this partial-thread:
http://news.povray.org/povray.beta-test/thread/%3C430daeda@news.povray.org%3E/?ttop=249422&toff=150

...in which Chris mentions it being fixed now, although that's for the 
beta.   I was just wondering if  I could find out the secret to Change 
3003 if it is indeed the same thing:

Change 3003 on 2004/07/22 by thorsten@host27
   Fixes file "saving" bug thanks to Massimo Valentini

Or is it just a matter of installing a newer version of the editor dll 
or something?

Thanks in advance!
Charles

Post a reply to this message

Charles C nous apporta ses lumieres en ce 2007/11/02 04:34:
> I've been assuming (correctly) that this was a known issue and I haven't 
> worried too much about it, so it's taken me quite a while to get around 
> to asking or looking into it at all.   Anyway I get:
> 
> "Failed to save file:
> 
> The process cannot access the file because it is being used by another 
> process."
> 
> ...in a self-compiled version of POV-Ray 3.6.0 for Windows which I've 
> been using for a while now to avoid the spline / token_count issue.
> 
> The only entry I see on the server is this partial-thread:
>
http://news.povray.org/povray.beta-test/thread/%3C430daeda@news.povray.org%3E/?ttop=249422&toff=150

> 
> 
> ...in which Chris mentions it being fixed now, although that's for the 
> beta.   I was just wondering if  I could find out the secret to Change 
> 3003 if it is indeed the same thing:
> 
> Change 3003 on 2004/07/22 by thorsten@host27
>   Fixes file "saving" bug thanks to Massimo Valentini
> 
> Or is it just a matter of installing a newer version of the editor dll 
> or something?
> 
> Thanks in advance!
> Charles
Are you on Windows Vista? Is POV-Ray installed in the "program files" folder?
If so, Vista don't let you edit/change/save files in that location.
The solution is simply to install into a different folder. Or you can redirect 
all files to a user provided alternate folder.

-- 
Alain
-------------------------------------------------
Creationism: God made all shit.

Post a reply to this message

Alain wrote:

> Are you on Windows Vista? Is POV-Ray installed in the "program files" 
> folder?
> If so, Vista don't let you edit/change/save files in that location.
> The solution is simply to install into a different folder. Or you can 
> redirect all files to a user provided alternate folder.
> 


No, sorry I should have said this is XP.  I'm well aware of the Vista 
issues though, and this is not that.  See the link.

Thanks,
Charles

Post a reply to this message

Charles C wrote:
> I've been assuming (correctly) that this was a known issue and I haven't 
> worried too much about it, so it's taken me quite a while to get around 
> to asking or looking into it at all.   Anyway I get:
> 
> "Failed to save file:
> 
> The process cannot access the file because it is being used by another 
> process."

Whenever I have received that message it was because the file was still 
open in some other application.

Try ctrl+alt+delete to see if there's something running in the 
background which may be using the file.

Sam

Post a reply to this message

> Charles C wrote:
>> I've been assuming (correctly) that this was a known issue and I 
>> haven't worried too much about it, so it's taken me quite a while to 
>> get around to asking or looking into it at all.   Anyway I get:
>>
>> "Failed to save file:
>>
>> The process cannot access the file because it is being used by another 
>> process."
> 
> Whenever I have received that message it was because the file was still 
> open in some other application.
> 
> Try ctrl+alt+delete to see if there's something running in the 
> background which may be using the file.

Or get Sysinternals Process Explorer which is a far more powerful task 
manager, it can actually tell you what files each app has open (and 
search for a filename to see *which* app has it open).

Post a reply to this message

Charles C nous apporta ses lumieres en ce 2007/11/02 18:22:
> 
> 
> Alain wrote:
> 
>> Are you on Windows Vista? Is POV-Ray installed in the "program files" 
>> folder?
>> If so, Vista don't let you edit/change/save files in that location.
>> The solution is simply to install into a different folder. Or you can 
>> redirect all files to a user provided alternate folder.
>>
> 
> 
> No, sorry I should have said this is XP.  I'm well aware of the Vista 
> issues though, and this is not that.  See the link.
> 
> Thanks,
> Charles
OK
Check if the file exist and if it's read only or system. Same with the folder 
itself.
Can you open the offending file, edit it with another application and save it back?
Is the file opened by any other application?
Do you have ownership of the file? I had some instances where files and folders 
on my system got eroneous ownership, with only one user. Some folders/files had 
been set with an owner whose name was just a bunch of random characters.
Is you drive full?

-- 
Alain
-------------------------------------------------
To the world you may be one person, but to one person you may be the world.

Post a reply to this message

Nicolas Alvarez wrote:
> Or get Sysinternals Process Explorer which is a far more powerful task 
> manager, it can actually tell you what files each app has open (and 
> search for a filename to see *which* app has it open).

This is pretty cool.  Thanks for telling me about it.  Now to run into 
the problem and see what it can tell me.  I'm pretty sure it'll tell me 
that POV-Ray is using the file but this'll show it for sure.

Charles

Post a reply to this message

Samuel Benge wrote:

> Whenever I have received that message it was because the file was still 
> open in some other application.

I'm pretty sure it's just POV-Ray.  Re-starting POV-Ray and not changing 
  anything else lets me make the change and save again.
Charles

Post a reply to this message

Alain wrote:
> OK
> Check if the file exist and if it's read only or system. Same with the 
> folder itself.
> Can you open the offending file, edit it with another application and 
> save it back?
> Is the file opened by any other application?
> Do you have ownership of the file? I had some instances where files and 
> folders on my system got eroneous ownership, with only one user. Some 
> folders/files had been set with an owner whose name was just a bunch of 
> random characters.
> Is you drive full?
> 

Thanks Alain.  This happens with any non-read-only file in my P-Scenes 
directory (which btw is not next to the installation directory) where I 
continually save and re-save as I edit and test and edit and test.  It 
seems to happen with just POV-Ray running, and maybe Windows Explorer. 
The drive has dozens of gigs left.  It's pretty reproducable when it 
happens, but it doesn't always happen.  It only happens following a 
parse-error and an attempted *minor* edit and save.

Here's a better version of the link.  Hopefully it'll work a little better:
http://news.povray.org/povray.beta-test/thread/%3C430daeda@news.povray.org%3E/?ttop=249422&toff=150

Charles

Post a reply to this message

Charles C napsal(a):
> 
> 
> Samuel Benge wrote:
> 
>> Whenever I have received that message it was because the file was 
>> still open in some other application.
> 
> I'm pretty sure it's just POV-Ray.  Re-starting POV-Ray and not changing 
>  anything else lets me make the change and save again.
> Charles
It seems to me POVray doesn't close the file handle and tries to open a 
new one. This fails because there cannot be two file handles to the same 
file if one of them is a writable one.
I've never seen the POVray code but if handle closing depends on a 
garbage collector+destructor then this is certainly wrong. In this case 
either force GC before opening a file or, if that fails, trace the 
references to it (if you don't mind debugging yourself).
You can use Sysinternals taskmanager to see if the image handle is still 
open by POVray.

Post a reply to this message