Can we please have a fixed version of refer? Our users are becoming irate, and rightly so. Will it be quicker to port the 4.3 suorce myself, and will we end up with a more robust version as a result? This is certainly our experience so far. Sorry, about the irate tone of this message, but the flaky nature of large amount of HLH-supplied clipper software is becoming a major embarrassment. On a related topic, I have been tried a few of the bugs mentioned in the clipper buglist, and we seem to have broken versions of most of the programs that are starred as "fixed at HLH". Having to try out hundreds and hundreds of scenarios to be able to request specific bits of software from you seems rather wasteful. Might it be possible for you to compile a tape of "files that have been fixed since the OTS2.2 distribution of May 1988 ----- Forwarded message # 1: Received: from harrier by gos.Ukc.AC.UK Over Ring with SMTP id aa21383; 4 May 89 12:18 BST Date: Thu, 4 May 89 12:18:53 BST From: "M.Lee" To: mg@ukc.ac.uk Subject: refer on harrier I don't know whether or not you look after the refer program. If you don't, then could you forward this message as appropriate ? By the way, do you have any idea when a new copy of roffbib will arrive ? I have found some problems in using refer on harrier. Refer 'core dumped' when the -e flag is used with -k, -l, or -S flag. They worked fine without the -e flag and there is no such problem on eagle. The message looks like ------------------------------MESSAGE BEGINS-------------------------- Job started: Wed May 3 10:29:12 BST 1989 + psroff -ms -P tma2.out + refer -e -l -p tma2.ref tma2.temp setenv PATH /usr/lib/ditroff:/usr/ucb:/usr/bin:/bin:/usr/local troff -Tlps -ms /usr/spool/batch/x160.6101909498: 19034 Memory fault - core dumped Job finished: 0.4u 1.2s 0:24 7% 8+14k 89+114io 3pf+0w  ------------------------------MESSAGE ENDS---------------------------- Munha ----- End of forwarded messages