ss (06/23/82)
Are there any eunice version 2 users who are also running VMS version 3? Are there any problems with this configuration, or have you any news at all about this congifuration? Thanks. Sid Shapiro -- decvax!wivax!ss -- Wang Institute -- (617)649-9731
steveg (06/24/82)
We have one site trying to run EUNICE V2.0 on VMS V3.0. The images appear to work, but the shell (csh) is not working. It is getting access violations and other problems. It seems to be related to the new rooted directories and the __DRA0: definition of sys. I tried calling Kashtan, but he is out till Monday. (His boss reported that Dave did not have any problems that he knows of). <there is a rumor that Kashtan in leaving SRI, any truth?> - steve gutfreund
salkind (06/24/82)
Some changes are required to Eunice to get it running properly under VMS 3.0. The main change, as might be expected, comes in the code dealing with process creation (fork(), vfork()). Eunice_vforkcli and eunice_vfork_image both have to be updated (and it results in a big speed up in fork() and vfork()). Unfortunately I don't have any more detailed information, as we are not yet running V3.0 on any of our VMS machines. Lou Salkind
steveg (06/27/82)
The speed up in the fork routines comes from a vastly improved VMS process creation routine. It used to take up to 1/4 second to spawn a new process. VMS was constructing the new image in a swap-file, then swapping it in. It is now done by creating a memory image in memory. It would be useful to publish the new fork routines. Untilis was asking another $200 for a new copy of EUNICE. - steve