🚀 go-pugleaf

In article <2ADCB02C.21111@news.service.uci.edu>  writes:
> I'm having trouble getting pcomm to work on my (3.0) machine.
> In specific I'd like to know what the various settings in the
> pcomm.* files should be.
> 
> Please drop me a line if you've got it working.
> Thanks,
> Kurt

Ahem, I spent two days trying to get pcomm run on both an Ultrix machine and a  
NeXT (2.1) - in vain. I gave up, but as pcomm runs perfectly on an AT&T  
SYSVR3.2, I would also be interested in the 'correct' settings.

The main problem on the NeXT is that it has some of the include files for SYSV.  
Poking around a little bit I found that using -DBSD, masking the memset stuff  
in tow files (strings and inputs I think) and not using shared memory compiled  
a version that ran and alowed local processing, but as soon as I tried  
connecting to a port, the process hung and was not interruptable.

On the Ultrix machine all worked fine upto and including the communication with  
the serial port. But trying to return to local mode (CTRL-A x for example)  
failed and I had to kill the processes (pcomm and pcomm_input) to get out.

ANYBODY have the settings?

-Robert
--
Robert Frank                         tel. + (061) 321 99 67                 
Institut fuer Informatik             fax  + (061) 321 99 15                 
University of Basel, Switzerland                                            
Mittlere Strasse 142      rfc822: frank@ifi.unibas.ch (NeXT mail accepted)  
CH-4056 Basel          X400: S=frank;OU=ifi;O=unibas;P=switch;A=arcom;C=ch
                   ( if all fails try frank@urz.unibas.ch )