Hi Chris : It's different on my machines too . I'll contact you privately .
studio > Hi Studio > > Installed a new network card, but this is not the problem as it still works > fine on this machine. > I know all my machines used to work fine with the old V4 setup, so this is a > V5 config problem of some kind. > I'm still only using PRS.exe and RenD in order to keep things simple. > One thing I have noticed is that RenD is using about 20k on the machines on > which it is working and around 4.5k on the machines that don't work. Don't > know if this means anything at all ?? > > Chris > > ----- Original Message ----- > From: "studio" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, January 12, 2007 4:19 AM > Subject: Re: Network rendering > > > > > Hi Studio, > > > I will go back to the start of your tutorial as you suggest and load the > > > correct startup arguements. > > > Failing that I will install a faster network card on one of the machines > > > that do work, and see if that's the problem. > > > Thanks again, > > > Chris > > > > Hi Chris : > > > > Yes , good idea to swap your cards and see if that's the > > problem . It sucks to have to do it but what else can you > > do ? > > > > Feel free to email me privately if it turns out to not be > > your cards . > > > > Best of luck . > > > > studio > > > > > > > > > > > > > > > > > > > > Man : > > > > > > > > I need a vacation . First of all , the sceenshot I sent last > > > > mail was not correct . It should not have been of the PRS.exe > > > > but either RendD.exe or RendW.exe (D for DOS , W for Window) . > > > > > > > > Secondly , I just read my Wiki tutorial again and all that > > > > was required was in there , right from the start . No idea > > > > how I missed that info . Guess I need glasses as well as a > > > > vacation . > > > > > > > > The problem started for me , when I launched PRS.exe and > > > > did not see anything in the DOS window , and assumed it was > > > > non-functioning . It wasn't , but was just very very quiet . > > > > > > > > Never assume . Oh well , after a year off from network > > > > rendering I guess I needed a refresher course . > > > > > > > > studio > > > > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > ---- > > > ------ > > > > > > > > > > > > No virus found in this incoming message. > > > > Checked by AVG Free Edition. > > > > Version: 7.1.410 / Virus Database: 268.16.8/621 - Release Date: > 1/9/2007 > > > > > > > > > > > > > > > > -- > > > > Internal Virus Database is out-of-date. > > > > Checked by AVG Free Edition. > > > > Version: 7.5.428 / Virus Database: 268.13.21/510 - Release Date: > > > 01/11/2006 08:00 > > > > > > > > > > > > > > > > > > > > -- > > > No virus found in this incoming message. > > > Checked by AVG Free Edition. > > > Version: 7.1.410 / Virus Database: 268.16.8/621 - Release Date: 1/9/2007 > > > > > > > > > > > > -- > > Internal Virus Database is out-of-date. > > Checked by AVG Free Edition. > > Version: 7.5.428 / Virus Database: 268.13.21/510 - Release Date: > 01/11/2006 08:00 > > > > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.410 / Virus Database: 268.16.9/623 - Release Date: 1/11/2007 > >
