I have a poser scene I have been working on for animation purposes.  Suddenly though the file is corrupt or something is wrong when I render to AVI.  I do this to test the movements before going to image files.

The avi finishes rendering but when it tries to boot up the rendered avi file - usually called untitled.avi - it gives me an error message that it cannot find it.  IT's not there!!  If I open up a fresh poser scene and render to AVI this works fine - it's only broken in this one file.  The AVI file does not exist on the desktop which is where I rendered it to.  It is in fact not there

Any thoughts on what might be the offending line of code in the PZ3 file?  I can render to image files ok....

That's odd.  Typically the PZ3 contains only the name without the folder.

When I tried making an AVI to desktop, here's what the PZ3 had:

movieName Untitled.pz3 

I don't know how Poser resolves the location when it immediately calls
the Media Player.... Presumably it just gives Media Player a command line
without writing the full path anywhere.  

You might see if the PZ3 has an absolute path after the 'movieName'
keyword instead of a plain name.  I don't know if that would cause the
problem, but it seems like a place to start.

In my PZ3 it is simply the name of the saved pz3 file. So this appears referential only.  Clearly it happens after the last frame is rendered and then it tries to bring up WMP. 

I deleted all the object and props from the file and created a moving camera to animate for 30 frames and I still get the error.  The on a hunch I cleared out the sound file I was using for the talk designer. When I did that it WORKED!!  I am not sure why it was rendering earlier ok and then suddenly stopped but "Clear Sound" worked. tks

Interesting.  Maybe the folder of the sound file was being used.

P7 has an internal bug which sometimes confuses folders and files.

Are you using windows vista? I "lost " files in vista.  Actually they still exist but for some stupid protection reasons, you're not allowed to access and see  them. If so, search for vista threads to solve the problem, it has to do with user access rules. TheFixer has given some advice in the past how to solve the problem.

regards,

Bopper.