Xref: utzoo comp.sources.d:1574 comp.sys.ibm.pc:9578 Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!imagine!pawl22.pawl.rpi.edu!jesup From: jesup@pawl22.pawl.rpi.edu (Randell E. Jesup) Newsgroups: comp.sources.d,comp.sys.ibm.pc Subject: Re: UUPC bugs. Message-ID: <141@imagine.PAWL.RPI.EDU> Date: 13 Dec 87 13:20:28 GMT References: <1477@swlabs.UUCP> Sender: news@imagine.PAWL.RPI.EDU Reply-To: beowulf!lunge!jesup@steinmetz.UUCP Organization: RPI Public Access Workstation Lab - Troy, NY Lines: 25 In article <1477@swlabs.UUCP> jack@swlabs.UUCP (Jack Bonn) writes: >Has anyone had success getting the UUPC package working under DOS? I >have built it and it works some of the time, but lately I have been >getting a "null pointer assignement" error. I ran lint on the source >and got 10 pages of errors! I've got it up on my Amiga, and ran into many of the same problems. Various problems include: Only working for specific configurations of the systems file, combined with specific ways of calling uupc. The real reason here is some flawed logic in the state tables in dcp.c. In particular, you shouldn't call sysend until the serial port has been opened. Once you do get it calling, you may find it ignores X.* files unless they are set up a certain way, and you never call more than one system per run. It should be made to accept X.anything instead of X.specific_host_name.*. Different UUCPs will send X.yoursite*, or X.theirsite*. Etc, etc. However, for all it's flaws, it actually does work, suprisingly. The mailer is a bit confused, but it works. // Randell Jesup Lunge Software Development // Dedicated Amiga Programmer 13 Frear Ave, Troy, NY 12180 \\// lunge!jesup@beowulf.UUCP (518) 272-2942 \/ (uunet!steinmetz!beowulf!lunge!jesup)