dik@uva.UUCP (Casper H.S. Dik) (12/20/88)
Hi, We've recently upgraded from a borrowed KFPS-2 to our own KFPS-4. After downloading K-star and the configuration parameters, I couldn't get CAP (atis, Aufs and lwsrv) to work. I soon found out that the trouble was that we were using the new ddprange. (200-up, instead of 768-up) After deleting the at-* entries in /etc/services everything started working again. Our atalkad file must be correct, since it worked fine with the FastPath-2. Does any one know a way to make K-star use the new ddprange? (Option parameters?) Soon we are going te reorganise all our Kinetices boxes and I think it would be better if they all used the new range. We're using a KFPS 4 Rom rev 4.1 FastPath Manager II 4.1, K-star rev 5.03, CAP 5.0 and atalkad from KIP 06/88. Thanks, Casper H.S. Dik ____________________________________________________________________________ Casper H.S. Dik University of Amsterdam | dik@uva.uucp The Netherlands | ...!uunet!mcvax!uva!dik
minshall@kinetics.UUCP (Greg Minshall) (12/24/88)
From article <584@uva.UUCP>, by dik@uva.UUCP (Casper H.S. Dik): > After downloading K-star and the configuration parameters, > I couldn't get CAP (atis, Aufs and lwsrv) to work. > > I soon found out that the trouble was that we were using the new ddprange. > (200-up, instead of 768-up) > After deleting the at-* entries in /etc/services everything started > working again. > Does any one know a way to make K-star use the new ddprange? K-STAR was designed, coded, etc., before the new ddprange was announced. We could have added the new range, but didn't (for a variety of reasons). There is, currently, no way of configuring K-STAR to use the new ddprange. There is a lot of interest in using the new range. A new version of K-STAR which supports the new range will be made available sometime during the first quarter of 1989. Greg Minshall Kinetics ...!ucbvax!unisoft!kinetics!minshall (415) 947-0998