CompuServe Thread

#Network Rendering on NT

2 messages in this thread
#131929From: MARK H. HOUSEROct 28, 1994 8:30 PM
Brian, Did you get it work under NT 3.1, or just NT 3.5? i.e. I've got 20 machines running MS-DOS rendering, all sharing the x: drive (NT 3.5). Aside from syncing the clocks to the server and running SHARE, is there anything else special to do on the MS-DOS side? I tried for about 3 months to get it working and never could. I had machines re-rendering the same frames, and some would just kick out of the queue and sit idle. I appreciate your feedback, Robb Rinard
#132188From: Brian Rudolph [Adesk]Oct 30, 1994 3:10 PM
<<Did you get it work under NT 3.1, or just NT 3.5?>> This was NT 3.1, and about 2-1/2 months ago. << I've got 20 machines running MS-DOS rendering, all sharing the x: drive (NT 3.5). Aside from syncing the clocks to the server and running SHARE, is there anything else special to do on the MS-DOS side?>> As I recall, that's all I did. On my side, it was relatively a no brainer. We had someone running NT server, I said can you give me rights to the drive so that I can write the control files, he did, and it worked. There were no hassles on my end, but I was not the one who installed the NT software. I don't think he did anything special, but I am not absolutely sure. <<I tried for about 3 months to get it working and never could. I had machines re-rendering the same frames, and some would just kick out of the queue and sit idle.>> Now, I never had it working in a production environment, I just had it working. I was testing to see if it was feasible at all. I think the project I rendered was BOUNCE.3DS, so It's not like I was taxing the system. It is possible I could have run into problems if I was working with it extensively. I just wanted to see if it was possible. If you got it this far, I would say that it was working, you just need to experiment with tweaking the network communication parameters. -Brian