"Failed to open file: The operation completed successfully" (Message 1 to 3 of 3)
From: Tor Olav Kristensen
Subject: "Failed to open file: The operation completed successfully"
Date: 2 Jan 2005 09:27:49
Message: <41d804e5$1@news.povray.org>
If I close POV-Ray and then delete a file that I had open
in an edit window and then start POV-Ray again, I get the
following odd message:
"Failed to open file: The operation completed successfully"
Does this mean that POV-Ray had an intention to fail ?
=)
(POV-Ray Version 3.6.1.icl8.win32 running on Windows 2000
Professional Version 5.0.2195 Service Pack 2.)
--
Tor Olav
http://subcube.net
http://subcube.com
Tor Olav Kristensen <tor### [at] TOBEREMOVEDgmailcom> wrote:
> "Failed to open file: The operation completed successfully">> Does this mean that POV-Ray had an intention to fail ?
Heh heh, I feel a T-shirt catch-phrase coming on...
"I'm a successful failure!"
And the follow-up bumper stickers... "My child successfully failed at
<insert school of choice>"
RG
From: Mike Raiford
Subject: Re: "Failed to open file: The operation completed successfully"
Date: 4 Jan 2005 08:40:20
Message: <41da9cc4$1@news.povray.org>
Tor Olav Kristensen wrote:
> > If I close POV-Ray and then delete a file that I had open> in an edit window and then start POV-Ray again, I get the> following odd message:> > "Failed to open file: The operation completed successfully"> > Does this mean that POV-Ray had an intention to fail ?>
A simple explanation of this:
the file open function probably returned a failure code, POVRay
subsequently attempts to display an error message by going to windows to
get the message for the return of GetLastError() [which gets the error
code for the last operation]
"The operation completed successfully" is the text for error code 0 (no
error)
Either of two things happened:
A) An operation between the error-causing function occured, clearing the
last error.
B) The file open function somehow failed to set an error code.
[A] is much more likely, if a C Library function like fopen is used. it
could have accidentally reset the error code by doing some cleanup.
--
~Mike