ted@usasoc.soc.mil (Ted Nolan) (09/14/90)
Has anybody been able to make the PCNFS programmers toolkit provided by Sun on the 386is work? I was unable to find any documentation on it, but after a long struggle, when I finally got the demo program to compile, and took it to my PC with PCNFS loaded, all it would do was complain about not having a toolkit TSR loaded. I know I haven't needed a TSR to run programs other people have done that interface with PCNFS -- what am I doing wrong? Thanks, Ted Nolan ted@usasoc.soc.mil
sjg@sun0.melb.bull.oz (Simon J. Gerraty) (09/25/90)
In article <1990Sep14.140514.9163@usasoc.soc.mil>, ted@usasoc (Ted Nolan) writes: > >Has anybody been able to make the PCNFS programmers toolkit provided by >Sun on the 386is work? I was unable to find any documentation on it, >but after a long struggle, when I finally got the demo program to compile, >and took it to my PC with PCNFS loaded, all it would do was complain about >not having a toolkit TSR loaded. I know I haven't needed a TSR to run >programs other people have done that interface with PCNFS -- what am I >doing wrong? Basically forget it :-) The toolkit on the 386i is for developing PC-NFS products in/for the 386i's DOS-Windows environment. If you want to produce a PC PC-NFS executable, you need to purchase the PC-NFS Programmer's Toolkit (PC-NFS-PTK). Similarly you cannot run normal PC-NFS products in the DOS-Windows world. The idea is that you develope your new product for DOS-Windows then re-link to run in the PC-NFS world. Also, while the toolkit worked under SunOS 4.0.1 on the 386i, it no longer works under 4.0.2. Also, we found a nasty memory allocation bug in the 1.0 library (PC-NFS-PTK), that made it unsuitable for developing a product that had more than one socket in use at a time. I was developing a PC multi-session emulation package that could use telnet to access unix hosts. We ended up using the 3Com socket library for 3+Open TCP/IP, which was cheaper, and less buggy (even in the 1.0 beta version) than Sun's PC-NFS-PTK (V1.0). Of course the 3Com stuff is useless for NFS environments. If anyone can provide me with work arounds/patches for any of the above toolkit problems, I would be interested to hear. -- Simon J. Gerraty <sjg@sun0.melb.bull.oz.au> #include <disclaimer> /* imagine something *very* witty here */