bachovch@sjuphil.uucp (Jeffrey J. Bachovchin) (05/09/91)
Recently, we installed PC-NFS 3.5 on several administrative PC's on our campus ethernet. We run a Sun 4/490 (SunOS 4.1.1) as a file server for all PC-NFS users on campus. We also got the latest patch of rpc.lockd from Sun (although since we did get it yesterday, there might be a new one today :-) ). Now, we are experiencing difficulties with Quattro Pro 2.0(LAN Pack). There were no problems with 3.01, but with 3.5 and the new lockd, when one user starts QPro, everything is fine, but when the 2nd starts it, you get the error message "Can't read startup strings". This only happens when we mount the virtual drive QPro is on with the /ms option. Without the option, no problem. But, we cannot mount this drive without the /ms option. Has anyone seen this problem? Is it yet another bug for rpc.lockd? Is it a QPro problem? Is it that (this is the scary pazrt) 3.01 wasn't file locking properly? Thanks in advance, Jeff +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Jeffrey J. Bachovchin Saint Joseph's University Systems Manager 5600 City Avenue bachovch@sjuphil.sju.edu Philadelphia, PA 19131-1395 Office of Academic Computing 215/660-1524
bachovch@sjuphil.uucp (Jeffrey J. Bachovchin) (05/10/91)
In article <1991May9.150917.10389@sjuphil.uucp> bachovch@sjuphil.UUCP () writes: > >Recently, we installed PC-NFS 3.5 on several administrative PC's on our campus >ethernet. We run a Sun 4/490 (SunOS 4.1.1) as a file server for all PC-NFS users >on campus. We also got the latest patch of rpc.lockd from Sun (although since >we did get it yesterday, there might be a new one today :-) ). Now, we are >experiencing difficulties with Quattro Pro 2.0(LAN Pack). There were no >problems with 3.01, but with 3.5 and the new lockd, when one user starts QPro, >everything is fine, but when the 2nd starts it, you get the error message >"Can't read startup strings". This only happens when we mount the virtual >drive QPro is on with the /ms option. Without the option, no problem. But, we >cannot mount this drive without the /ms option. Has anyone seen this problem? >Is it yet another bug for rpc.lockd? Is it a QPro problem? Is it that (this >is the scary pazrt) 3.01 wasn't file locking properly? We have solved this problem. It seems that Quattro Pro uses DOS 3.1 sharing. By adding the DOS share command to autoexec.bat, the problem of file locking was fixed. Thanks to everyone who replied. Looks like PC-NFS 3.01 was not correctly locking files. Jeff +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Jeffrey J. Bachovchin Saint Joseph's University Systems Manager 5600 City Avenue bachovch@sjuphil.sju.edu Philadelphia, PA 19131-1395 Office of Academic Computing 215/660-1524