Pov seems to try and create a temp file on the root drive which is causing a
problem for us.  If we give a user write access to the root of the drive the
render works.  When they do not have write access the render will not
complete.

How do you change the location where this temp file is being created.

Post a reply to this message

"Brian" <bri### [at] chiefarchitectcom> wrote in message 
news:web.46168c053403448a4f02351a0@news.povray.org...
> Pov seems to try and create a temp file on the root drive which is causing 
> a
> problem for us.  If we give a user write access to the root of the drive 
> the
> render works.  When they do not have write access the render will not
> complete.
>
> How do you change the location where this temp file is being created.

I don't recall but I don't think that POV creates a temp file in the manner 
that you may be thinking .... I may be wrong but what I think is happening 
is that if you or your users are trying to render the example files that 
come up the first time you use POV the restricted account is unable to write 
the output file (bmp, png etc) that is produced when you render the examples 
that are included in the application directory. There are a couple of ways 
to get around this .... I'll mention a couple and perhaps others my offer 
ideas that I've overlooked.

1) copy or save some of the example files to the user accounts home 
directory as POV tries to write an image file to the current directory.
2) use the -f command line switch to keep from producing an output file.
3) use the shared directories area if more than one person needs to 
write/read example files
4) use the command line directive Output_File_Name="C:\Some Path 
Name\filename.bmp .... png .... tif"

Hope this helps

Jim

Post a reply to this message

It does not seem to be a problem with creating the output file.  I used the
-f switch and still got the same results.  The problem seems to be with
reading the texture image files.  Here is a copy of the error that I
receive when I try and create the raytrace.

Possible Parse Error: jpeglib: Failed to create temporary file

It does not seem to matter where the textures are located, I always get this
error.  The only thing that seems to resolve this it to give the user write
access to the root of the C drive.  This is what leads me to believe that
there  is a temporary file being written there during raytrace process.

Post a reply to this message

"Brian" <bri### [at] chiefarchitectcom> wrote in message 
news:web.461a652f3b750ee14f02351a0@news.povray.org...
> It does not seem to be a problem with creating the output file.  I used 
> the
> -f switch and still got the same results.  The problem seems to be with
> reading the texture image files.  Here is a copy of the error that I
> receive when I try and create the raytrace.
>
> Possible Parse Error: jpeglib: Failed to create temporary file

hmmmm .... sorry that didn't help.
>
> It does not seem to matter where the textures are located, I always get 
> this
> error.  The only thing that seems to resolve this it to give the user 
> write
> access to the root of the C drive.  This is what leads me to believe that
> there  is a temporary file being written there during raytrace process.

I tried to run pov from a restricted account on my xp system and it stopped 
me as well .... I tried ALL the ideas I floated in my last responce and they 
all worked for me so I'm at a loss to offer anything else .... perhaps you 
have a corrupt installation or a problem with your system.

Maybe other readers of this new group might have some insights????

Jim

Post a reply to this message

Jim Holsenback wrote:
> I tried to run pov from a restricted account on my xp system and it stopped 
> me as well .... I tried ALL the ideas I floated in my last responce and they 
> all worked for me so I'm at a loss to offer anything else .... perhaps you 
> have a corrupt installation or a problem with your system.

Can you run it using something like filemon (www.sysinternals.com; they have
been borg'd by Microsoft but the utility ought to still be out there) and
find out what exactly it is failing on?

Note that by default it does write to pvengine.ini, however a failure to do
so should not cause the program to fail to operate. If it does then I will of
course fix it.

-- Chris

Post a reply to this message

"Brian" <bri### [at] chiefarchitectcom> wrote in message 
news:web.461a652f3b750ee14f02351a0@news.povray.org...
> It does not seem to be a problem with creating the output file.  I used 
> the
> -f switch and still got the same results.  The problem seems to be with
> reading the texture image files.  Here is a copy of the error that I
> receive when I try and create the raytrace.
>
> Possible Parse Error: jpeglib: Failed to create temporary file
>
> It does not seem to matter where the textures are located, I always get 
> this
> error.  The only thing that seems to resolve this it to give the user 
> write
> access to the root of the C drive.  This is what leads me to believe that
> there  is a temporary file being written there during raytrace process.
>
>
Did you have a look at section 1.2.7  I/O Restrictions of the documentation?

My setup is:

allow read/restrict write
permit read/write in current directory
disable starting other programs

I do most if not all my raytracing from an account that has admin 
privileges, but I have several restricted accounts that pov runs just fine 
with those settings .... so as Chris offered perhaps a bit more 
troubleshooting might be in order to determine what exactly is failing.

Jim

Post a reply to this message

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
>
> Can you run it using something like filemon (www.sysinternals.com; they have
> been borg'd by Microsoft but the utility ought to still be out there) and
> find out what exactly it is failing on?
>
> Note that by default it does write to pvengine.ini, however a failure to do
> so should not cause the program to fail to operate. If it does then I will of
> course fix it.
>
> -- Chris

Filemon seems to reveal a clue as to what the problem may be.  It seems that
when POV processes some of our jpeg image files it writes temp files to the
root of the c drive.  The name of these files look something like this
t7k.1, t7k.2, t7k.3....and so on.  The name and number of files is slightly
different for each image that causes this problem.

This only happens on certain images and not all.  One theory that we have
here is that these jpegs were created in a older jpeg format, since
these files that we are failing on were probably created 5-7 years ago.
The reason we think this, is that if we resave these files in paint shop the
problem goes away.

Doesn't look like we can attach files here or I would attach one of the
problem jpegs.  If you would like to send me an email I would be happy to
send you one of these files.

Thanks Again
Brian

Post a reply to this message

Brian wrote:
> This only happens on certain images and not all.  One theory that we have
> here is that these jpegs were created in a older jpeg format,

Perhaps they're interlaced?

-- 
   Darren New / San Diego, CA, USA (PST)
     His kernel fu is strong.
     He studied at the Shao Linux Temple.

Post a reply to this message

Brian wrote:
> Filemon seems to reveal a clue as to what the problem may be.  It seems that
> when POV processes some of our jpeg image files it writes temp files to the
> root of the c drive.  The name of these files look something like this
> t7k.1, t7k.2, t7k.3....and so on.  The name and number of files is slightly
> different for each image that causes this problem.
> 
> This only happens on certain images and not all.  One theory that we have
> here is that these jpegs were created in a older jpeg format, since
> these files that we are failing on were probably created 5-7 years ago.
> The reason we think this, is that if we resave these files in paint shop the
> problem goes away.
> 
> Doesn't look like we can attach files here or I would attach one of the
> problem jpegs.  If you would like to send me an email I would be happy to
> send you one of these files.

hmmm, this is interesting. please post one of the original files that cause
this issue to povray.binaries.images and let me know (here) when it's up.

thanks,

-- Chris

Post a reply to this message

> hmmm, this is interesting. please post one of the original files that cause
> this issue to povray.binaries.images and let me know (here) when it's up.
>
> thanks,
>
> -- Chris


Images are posted at povray.binaries.images.

-Brian

Post a reply to this message