brian@ucsd.EDU (Brian Kantor) (03/12/89)
After a lot of poking and prodding by me and on the part of my AT&T rep, I have a somewhat more coherent picture of what's going with the WIN TCP 2.1 package under SysV-3.1 on the 3B15. IT SEEMS THAT SysV-3.1 needs to have the new 10Base5 device driver to be able to access the Network Interface [NI] device. When you install this new driver, you have to change the interrupt priority paddle on the NI board's backplane position from its current level to level 4. A suitable paddle wasn't included in the upgrade kit, so have your technician check and obtain the right paddle BEFORE you take the system down. WIN 2.1 needs the above streams driver to run. from WIN 1.1 to 2.1 we lost raw sockets, and many socket options; apparently the emphasis was on streams usage. You need to get the "virus" fixes for the ftpd daemon, and a fixed 'ftp' command or all you'll be able to ftp is zero-length files, which have a somewhat limited usefulness. However, even with the fixed version of ftpd, it seems that anonymous FTP is either disabled or broken. the WIN socket libraries are in /shlib/libshl_s.a, which means that they exist as a sharable library. The latest version of the compiler (C language development tools) that is available for the 3B15 is Issue 3.0, which doesn't do sharable libraries. Your old TCP-based code won't run under the new system. Thus, people who install the upgrade from SysV-2.1.1 to SysV-3.1 will lose all their locally-developed TCP/IP-based networking if it uses sockets. It is supposedly possible to rewrite all your applications to use the streams interface if you want it to continue working, or so I'm told. I haven't tried that; it seems like too much work to me. HOWEVER: I've also found out the following: WIN 3.0 has just become available for the 3B2. The raw sockets and socket options are supposed to be fixed in that version. [I haven't seen it yet.] The current-issue compiler for the 3B2 is Issue 4.2, which DOES do shareable libraries, so you CAN access the WIN socket compatability library. The 3B2 binaries run on the 3B15, and seem to correctly access the 10Base5 network interface device driver. [I found this out because disassembling the FTP fixes from the hotline that I'm running on the 3B15 hint that they were compiled and linked on the 3B2. I'm told that the 3B2 is the porting base for software, and that 3B15s get done afterward. Sigh.] So I guess the workaround is to do all your TCP network application development on a 3B2 and then move the binaries over to the 3B15 for use. I'm going to try this real soon now. I do have NNTP running on a 3B2 here, so there's something for me to start with. I dunno what you do if all you have is a 3B15 and no 3B2s. My guess is that the WIN 3.x and C 4.x will be available for it sometime; you may wish to consider delaying upgrading from 2.1.1 to 3.1.x if you have any of your own software that needs TCP sockets to run. I wish I had. BTW, if you've noticed that your 'errdemon' isn't running on your 3B15 under SysV-3.1, you're right. You need the fixed version. I'm told that there is a "maintenance release' SysV-3.1.1 which fixes this and a few other bugs. I don't have it yet either. - Brian