Path: utzoo!attcan!uunet!mcsun!inria!irisa!angelini From: angelini@irisa.fr (Pierre Antoine Angelini) Newsgroups: comp.protocols.nfs Subject: Re: Enduring PC-NFS Annoyances Message-ID: <1990Nov5.164541.20646@irisa.fr> Date: 5 Nov 90 16:45:41 GMT References: <3160@jaytee.East.Sun.COM> <1448@travis.csd.harris.com> <1990Nov04.001340.20629@naitc.naitc.com> Sender: news@irisa.fr Organization: IRISA, Rennes (Fr) Lines: 97 In article <1990Nov04.001340.20629@naitc.naitc.com> karl@bbs.naitc.com (Karl Denninger) writes: >>In article <3160@jaytee.East.Sun.COM> geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes: >>>Most of our large customers buy right-to-copy (RTC) kits, in which >>>we sell them a set of diskettes and a serialization kit. They are >>>free to use this to manufacture multiple full kits, or (more >>>commonly) to create a serialized PCNFS.SYS for each system. The >>>downside: documentation must be purchased separately. >>>some of what we're thinking about long-term, with no dates, > >That doesn't help most of us. > >You see, here's the classic problem: >1) You load PC/NFS on a machine, and give it a serial number. >2) The system crashes it's hard disk, losing the serialized copy. >....... >Solution (1) requires a huge filing cabinet, and also requires that people >not trade machines (lots of organizations move gear DAILY), while (2) also >requires record keeping on exactly which system and disk drive belongs to >who at all times. If you have several hundred users this is a REAL pain. >........... > >One of the first questions I ask is "is the package copyprotected" when I am >evaluating something that is going to be used by hundreds of people at an >organization. I agree with most of those complains. Though I'm using PCNFS for 4 years now, I would prefer a non-serialized product. PC-NFS is used by 1600 students on PC's with NO hard disk. I found a way to deal with the "Licence violation detection ...." problem, because I had to. Here's my solution for those of you wishing to use PCNFS without that serialisation problem.It requires a bit of work, it's NOT a real solution, but it works very fine. First, take out each serial number of PCNFS.SYS with a small pascal program. It's very simple, even a type on PCNFS.SYS will show that number. Then load that number into an EPROM (2716,2732,2764) . Plug that Eprom in a network board with an optional "bootprom" socket. ( I have tried it with a 3C501,3C503,NIC,WD8003EBT). Set the EPROM address correctly( C800 for me, depends on your configuration) Give to the user a PCNFS.SYS where the serial number is anything,but a correct number ( for example PCNFS.SYS from the 3.01 upgrade ). When you boot, the serial number is verified by the first NET command issued. All you have to do is to write a small program finding XXXXXXX in memory ( it's very fast, and always in the same place for my students) and replace it by the right number that you will find in the EPROM. Launch it before the first net command. Avantages: -The serial number is "machine dependant" and will stay so, even if there is a hard disk. Even if people trade,move their machine, it will work. If they crash their hard disk too. -Upgrades are simple. I moved with no problem from 2 to 3 and 3.01. -You just have to keep trace of your ethernet board. My /etc/ethers table on NIS server has a field containing the serial numbers ( just in case.....) as ethernet number and serial number are attached to the same board. Question : (To avoid that kind of "turnaround") Would it be VERY difficult to have something using "the floating license" service used on Sun workstation to "serve" PCNFS serial number ??? Disavantages: -You have to spend some time (let say 5 mn per PC) to initiate the EPROM and plug it in the network board. -You have to have an EPROM programmer and to know how to use it. A 2732 cost actually about 5$. -I hope SUN will not change anything about that in the next release, but to switch to unserialised product !!!! It's working perfectly on XT,AT,386 in a +100 PC's network for 4 years now. That's one PC-NFS default I don't have to deal with anymore. I red with interest all the complains about PC-NFS. Most of them are justified, Sun isn't doing as well as his competitors today, but I would like to thank Geoff who is caught between the hammer and the anvil. Thanks for your help, Geoff and keep on that way. I hope Sun will be able to make the PCNFS that will allow you to put your (big) stress pillbox in the trash.... By the way, any info on next release is welcome ( I just couldn't resist..) -------------------------------------------------------------------------------- Pierre Antoine ANGELINI (PAA) ## E-MAIL : angelini@irisa.fr ## IFSIC /IRISA ## Atelier Micro Universite de Rennes I Campus de beaulieu 35042 RENNES CEDEX - FRANCE --------------------------------------------------------------------------------