swm@eyrie.img.uu.oz.au (Shane Marquis [Dent]) (03/05/91)
hi all, ummm does anyone know what happend to the next release of fsuucp and if not can anyone tell me if theyve got one of its vertions up and running and functioning correctly cos i dont know what im doing wrong, i just cant get uuxqt to work properly (everything else is fine!!!) please help im getting desperate. shane.
cambler@polyslo.CalPoly.EDU (The Squire, Phish) (03/06/91)
swm@eyrie.img.uu.oz.au (Shane Marquis [Dent]) recently informed us: >hi all, Hi shane... > ummm does anyone know what happend to the next release of fsuucp >and if not can anyone tell me if theyve got one of its vertions up and running >and functioning correctly cos i dont know what im doing wrong, i just cant >get uuxqt to work properly (everything else is fine!!!) please help im getting >desperate. This is just a general note to those who are waiting for the 1.2 release of fsuucp, which is now quite late. The reason for this is a serious bug in the transfer system that I am working on. As I have always made as clear as possible, the reason fsuucp is shareware is because I cannot devote as much time to it as I would feel necessary if I were to make it a commercial-quality product, both in functionality and support. School and work have to come first, and they have, unfortunately, both been very demanding at the same time as this bug has come about. On another note, I have received a number of requests for fsuucp recently, about half of them just a letter requesting it, and the other half disk mailers with disks, but not return mailer or postage. This leads me to believe that someone posted somewhere that I'll send it for free, but neglected to mention that I require a self-addressed stamped return mailer. If anyone has seen such a post, I'd appreciate it if they could forward me a copy. In any case, work continues, and I'm not abandoning fsuucp as the delays may indicate. I can't promise a release date at this time because the bug is still being worked on (it's a showstopper, trust me, but I have a fix in the works), but I guess no more than 3 weeks. Promises mean nothing, though, until I get a firm grip on the problem. Here is the propoganda for 1.1 release 5 for those who have no idea what I'm talking about, everyone else can hit 'n' now. :-) FSUUCP Version 1.1 release 5 is the most current version of FSUUCP. FSUUCP implements a UUCP/Usenet transfer protocol for MSDOS based machines. It comes complete with a full 7 window uucico, uuxqt with rnews and rmail capability, mail, readnews, postnews, uuq, uusnap, and news utilities like batcher and expire. Unlike other packages, FSUUCP implements these programmes as DOS commands directly. By putting the executables on your PATH, and setting an environment variable pointing to your configuration file, you can have UNIX mail and news on your MSDOS machine from the prompt, just like UNIX. To get a copy of FSUUCP: 1. Get it via anonymous FTP from polyslo.calpoly.edu. The file name will be fsuu11r5.zip. The current naming convention is fsuu[VV]r[R].zip, where VV is the version number in V.V format, and R is the release number. In this case, fsuu11r5 means version 1.1, release 5. Check occasionally on polyslo to be sure you have the latest version. 2. Mail us the $35 shareware registration and we will mail you back a disk with a registered copy. Please specify: A. 3.5" 720K B. 5.25" 1.2Meg 3. Mail us a self-addressed stamped disk mailer with either formatted 5.25" 1.2 Meg or 3.5" 720K or 1.44Meg disk. ***NO 360K DISKS!!!*** Note, do NOT use postage metres to stamp your return mailer, the post office will not accept metred mail from outside the city of origin. Please use stamps. Note the increased postage rates, please. Registered users remain registered through all major revisions, or for a full year from time of registering, whichever is longer. That is, if you register your copy of 1.1, you are still registered through 1.2, 1.3, ..., 1.x, and all releases of these versions, and you are also still registered regardless of the version for a full year. Note that if you choose method 3, you DO NOT need to send the registration until/if you decide to use FSUUCP. And, as always, any bug reports or wishlists will be addressed for future releases. ADDRESS FOR SENDING DISK: Fubar Systems FSUUCP Request 1525 Mill #6 San Luis Obispo, Ca 93401-2543 For more information, send mail to: cambler@polyslo.calpoly.edu ------------------------------------------------------------------------------- -- ++Christopher(); --- cambler@polyslo.calpoly.edu --- chris@erotica.fubarsys.com ----- FSUUCP Mailing list: fsuucp@polyslo.calpoly.edu Requests to: fsuucp-request@polyslo.calpoly.edu