#PAR errors
3 messages in this thread
Hi Gus:
I have several questions regarding some peculiarities of the PAR I have been
noticing since ver 1.5. Intermittantly, when I launch parinit/pardrv I get an
error message that states:
Super 8 Timed Out, waiting for Ack
Last Micro Code Command ===> 56
If I rerun my PAR start batch file it usually comes up ok the second time.
What does this error mean?
Second, I have been unable to get parout to work properly. It usually runs for
10% of the frames of the rendering and then it just refuses to dump anymore to
my PAR. Additionally, the frames dumped to the PAR are corrupted. I have
learned to select No to delete files because when I choose yes. I render a
whole animation and find out that the finished animation is both corrupted and
incomplete and I have no files to do the transfer manually. If I network
render in the traditional sense I can transfer my TGA's to the PAR in the end
with no problem using BLF240 and QF23.
Third, Par Control doesn't see my PAR files after I switch directories in the
PAR (project names.) I'll see them the first time I launch but if I switch to
a new proj name there are no files. If I go back to the original project name
those files are now gone. If I exit par control and restart the files are
still gone. If I exit 3ds and relaunch my par init and then 3ds I can
initially see the files again.
Hopefully, with the above info, you can give me some idea as to what is going
wrong. FYI: I usually run my par drive with nothing stored on it and the
whole drive is usually available for new renderings.
It sounds like you've got some problems with the PAR board. The "Super 8 Timed
Out" message is given out by the PARINIT program while loading the microcode
from your computer up to the PAR (Super 8 is the CPU used in the PAR). I don't
know what that error (56) means. You'd be better off asking the DPS folks. The
fact you're getting corrupted frames make this case even stronger. I have not
seen any of the problems you mentioned while using the other PAR utilities.
Check with the DPS folks about the error "56" and let's take it from there.
Gus
Thanks, Gus for the info. I'll follow up with Brick next time we chat. For
now I have reseated the PAR board and IDE cables and the error has temporarily
disappeared. Maybe it was just some oxidation build up on the mechanical
connections. I'll be starting another rendering soon so maybe this error was
related to the other IPAS problems.
Thanks again,
Don