CompuServe Thread

#PNW network rendering

9 messages in this thread
#133971From: DE SMET EMMANUELNov 7, 1994 3:35 AM
Hello, Anyone here with experience with 3D studio r3 network rendering under Novell Personal Netware? Configuration: 1 master Pentium 90 MHz 2 slave (1 Pentium – 1 486DX266) Rendering on the master and one slave is fine. However bringing in a second slave gives problems (slave is seen in the network by the master but fails to start rendering). Also I have problems when I start network rendering when both slaves are already active. [A [A [The machines share also a Pioneer DRM604X CD-ROM changer connected to the master. I have loaded MSCDEX on the master with /S option. Any suggestions ? Thanks, Emmanuel
#134096From: Brian Rudolph [Adesk]Nov 7, 1994 2:18 PM
<< (slave is seen in the network by the master but fails to start rendering). >> When you say fails, is there anything in the network log? There should be an entry that says why the machine failed rendering. <<Also I have problems when I start network rendering when both slaves are already active.>> What kind of problems? You will have to be more specific. Do you get any error messages or notifications? Also, do the machines have unique names and numbers? -Brian
#134558From: de smet emmanuelNov 9, 1994 2:12 AM
With problems I mean that one of the 2 slaves is frozen. Hitting the ESC key in the rendering screen doesn't do anything. Only CTRL-ALT-DEL restarts the machine. There is nothing in the log file. Any suggestion?
#134641From: Brian Rudolph [Adesk]Nov 9, 1994 11:06 AM
First, I would strip the slave machines to the bare minumum. That would be FILES, BUFFERS, and your network drivers. Nothing else. Hopefully that might clear up any memory conflicts. If not, maybe you need a memory manager that will exclude the memory where your network drivers are being loaded. Also, check the system timing of the machines. Every machine needs to be time and date synced to the server every time you log in for nework rendering. <<Rendering on the master and one slave is fine.>> When you say this, can you do this with either slave, or is it one specific slave that always fails? In otherwords, out of three machines, can you always get any two running? Or only a specific two?
#135116From: DE SMET EMMANUELNov 11, 1994 5:37 AM
Of the 3 machines I can always run the master and 1 of both slaves. I think the reason is due to sharing violation. However I loaded SHARE.EXE on all machines. Thanks, Emmanuel
#135272From: Brian Rudolph [Adesk]Nov 11, 1994 2:36 PM
<,Of the 3 machines I can always run the master and 1 of both slaves. I think the reason is due to sharing violation. However I loaded SHARE.EXE on all machines.>> By chance do the two slaves have either the same name or the same ID number? Other than that, what might potentially produce this problem would be network timing issues. Make sure the salves are synced to the machine acting as the server. Or it could be a network sharing issues as you suggested. I use SHARE.EXE on a client/server network. Are there any other options for the peer-to-peer? Also, what about rights in the directory? Do the users logged on have FULL rights? Are they limited in the number of times they be logged on simultaneously? Are your network files going to the root (/) of any of the hard drivers? That's about all I can think of. -Brian
#135521From: DE SMET EMMANUELNov 12, 1994 3:22 PM
Brian Thanks to your suggestion I've found that my problems was the timing issue of the slaves vs the master. It' s nice to render on 2 Pentium 90 Mhz and 1 486+/dx266. Thanks a lot, Goodbye, Emmanuel BTW: Where do you live ? I'm living in Belgium/Europe
#136092From: Brian Rudolph [Adesk]Nov 15, 1994 2:10 AM
Glad you are up and running. Timing issues are by far the most common problem people run into with network rendering, especially on peer-to-peer sytems. -Brian
#137045From: DE SMET EMMANUELNov 19, 1994 4:44 PM
I've appreciated your help Brain, Thanks, Emmanuel