CompuServe Thread

#SGI Renderer

6 messages in this thread
#186626From: Scott Polk (Polk GraphicAug 22, 1995 4:32 PM
Hi Brian, Ive got a little problem that I hope you can help with. I am the Animator for NEC America. I talked to adesk support last week about getting my sgi renderer up and asked for some configuration help. ( I believe his name was Nick) Nick was VERY helpful and suggested a couple of different configurations. The one that I decided to use was Lan Workplace for Dos. I think this will be a great solution for me with the exeption of one problem. The lwp4dos configuration ( which Nick said was one of your configurations) requires you to compile the following files. lwpnfs.c lwplock.c lwprint.c I have tried to compile these files over and over on the SGI but have been getting tons of errors. I have given up on getting them to compile. I realize that this is not a Autodesk
#186814From: Brian Rudolph [Adesk]Aug 23, 1995 11:15 AM
Scott, I am confused why you have to compile any files. I did not have to do so in order to get LWP working with the SGI. On the SGI side, I have the 3DS and License software running, the proper rpc.lockd file for my operating system, and nfs installed. On the PC side, I have the novell and lwp drivers installed in the autoexec.bat. The two machines talk to each other with no problems. Where did you see the information that you had to compile these programs? I've never seen that. -Brian
#186844From: Scott Polk (Polk GraphicAug 23, 1995 12:51 PM
Brian, I am using Lan workplace for Dos NFS client. The instructions were on page 2-7 of the manual ( Lan Workplace for Dos NFS Client users manual.) I am understanding that I will need to purchase NFS for the sgi which I was trying to avoid if possible. I think that this is probobly the problem. I am able to talk to my nt server from the indy no problem. But I am positive we have not purchased or installed NFS on the indy, is this the problem? Thanks for your help Scott
#186901From: Brian Rudolph [Adesk]Aug 23, 1995 5:43 PM
Scott 1. You _must_ get and install nfs for the SGI. It is required for your PC to communicate with the SGI. (If you are doing command line rendering only, you can skip this.) 2. The deamons that you are trying to compile, most likely require support files that are installed with the nfs package, and won't compile properly until nfs is installed. (This is just an educated guess.) 3. You really don't need the deamons anyway. When you install the nfs package, versions of those deamons are installed. The files you are trying to compile are replacements for those deamons. However, I have run the SGI renderer without replacing those deamons, so I know that they work. 4. NT works completly differently, the fact that you can talk to the NT box has little or no bearing on this problem. -Brian
#186927From: Gus GrubbaAug 23, 1995 8:18 PM
>> But I am positive we have not purchased or installed NFS on the indy, >> is this the problem? Is this the problem? You bet. If you want to use NFS in order to access the SGI (LW NFS Client) you must have something to answer on the other end of the line. Bottom line, the only way you can have this running is by installing the Network File System 5.3 (assuming you're running Irix 5.3).
#186930From: CSA/CAAug 23, 1995 8:32 PM
Scott, The Indy should have IRIX 5.3 which includes a client version of NFS. And of course any SGIs will talk to each other just fine. Kevin Krell – Computer Support Associates