> I'm running PRS in a 6 computer setup without much problems. > The only error I get on a regular basis is that RendW/RendD have a bug > putting arguments in the wrong field at startup sometimes. > Arjo.
OK , got it working : Turns out it was human error again (mine!) . Arjo mentioning that there were wrong arguments got me thinking . Then , I went back over the manual's example and it finally sank in . Two things : 1) Even though there is no activity in the PRS.exe DOS window PRS.exe is still showing as active as a Task Manager Process . 2) You will have to 'Run' RendD.exe or RendW.exe (as the manual says) with the correct startup arguments . The easiest way to do that is to just add the correct arguments in a "shortcut to RendW.exe"(see my wiki tutorial again for how to do that) on _ALL_ computers . So that's all it was , the default startup arguments _MUST_ be changed for PRS.exe to run . In my case my main PRS server (host5 , in the manual's example) is called "celery" . So then I would have to add that to the rendW.exe shortcuts (see att- achment) . Guess I'll have to go back to that tutorial and add that part in . Not sure how I managed to overlook it in the first place , since it is actually very critical . However , this may not solve your problems , Chris. If your firewall is down then I'm guessing it has something to do with your new 1 gig cards , somehow , unless it is an odd problem with older plugins not being up to date , as Jason mentioned . studio
rendW.exe.gif
Description: GIF image
