Date: Sun, 19 Feb 95 14:58:07 EST From: Snuffles@kew.com Subject: UUPC-Info Digest 1995 #3 To: uupc-info-digest@kew.com Message-ID: Reply-To: UUPC-Info@kew.com UUPC-Info Digest Sun, 19 Feb 95 Volume 1995: Issue 3 Today's Topics: Borland C++ and UUPC/extended (2 msgs) Bug in UUCICO V1.12m? expire not expiring? (2 msgs) inews Mail GUI interface new, improved, NNS support (2 msgs) Problem with MAIL from UUPC 1.12k question about protocol and TIN (2 msgs) UUPC for Windows question (2 msgs) To subscribe to UUPC-Info-Digest, send the command in the body of a message to listserv@kew.com: subscribe uupc-info-Digest To signoff from UUPC-Info-Digest, use "signoff" instead of "subscribe". You can also send an "index" to the listserv to get an index of back issues and other files available for retrieval. ---------------------------------------------------------------------- Date: Sat, 18 Feb 1995 12:37:05 -0500 From: Software@kew.com Subject: Borland C++ and UUPC/extended To: UUPC/Extended mailing list This mail is going to both uupc-info and uupc-announce. (A rare non-new release message to the latter, but it's important). I am in the final stages of 1.12m work, by the way, and I hope to put it out next weekend. Several things have happened in the past 18 months which are causing me to rethink my traditional use of Borland C++ for the primary compiler under DOS for UUPC/extended: 1) The Borland C++ 1.01 for OS/2 turned out to be unusable, causing me to switch to IBM C/Set++, which is derived from the old MS C OS/2 compiler, and Borland has declined to remedy the problem. (I refuse to pay for an update to a compiler which wasn't ready for prime time to begin with.) 2) Support of Windows NT has required me to buy the MS VC++ 2.0 compiler, which includes the VC++ 1.5 for Windows 3.1 and the current DOS MS C++ 8.0 compiler for free. I've bought the subscription to the compiler, so I get the next three updates for no additional chanrge as well. 4) I am no longer current on the DOS Borland C++ compiler, their current release being 4.5 and I'm back on 3.1; the reason for this of course is that 4.0 did nothing to support DOS better. 3) I have been offered an MS C based replacment for the current Borland easy win based UUCICO. 4) The financial problems at Borland International appear intractable. Basically, while I never liked MS compilers, I'm in a position now where my primary environment (OS/2) is based on an MS compiler, I only have MS support for another environment (NT), and MS may have best of breed for a third (Windows 3.x). Thus moving to MS C 8.00 for DOS seems a reasonable thing to do to reduce my workload, such as Makefile updates. Does anyone see a specific reason for me to continue support of the Borland C++ environment, or have other comments and/or questions? -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 "She really worked me over good, she was a credit to her gender She put me through some changes lord, sort of like a Waring Blender . . ." - Warren Zevon ------------------------------ Date: Sun, 19 Feb 1995 09:24:40 -0500 From: Software@kew.com Subject: Borland C++ and UUPC/extended To: UUPC/Extended mailing list On Sat, 18 Feb 95 12:46:15 -0800, "Jim Seymour" wrote: > You (Software@kew.com) said: > > Does anyone see a specific reason for me to continue support of the > > Borland C++ environment, or have other comments and/or questions? > > I don't have direct experience with it, but have you considered Watcom's > compiler? It (theoretically) supports all the platforms you need and > is can be hosted on several platforms (including OS/2). I realize this > could involve even more work and money, but if you're already in a flux, > now may be a good time to switch. (Just a thought) Ed Keith, who owns one of everything, has Watcom and is planning to try a build with it. No doubt some people would like me to switch to GNU compilers as well. Basically, however, having spent the money on the vendor compilers, so long as they work I'm prone to stick with them since their support is (sometimes unfortunetely) the best. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 Give! Support the Wonderworks Tosci's Chocolate Ice Cream Fund! ------------------------------ Date: Sat, 18 Feb 1995 07:26:30 -0500 From: Software@kew.com Subject: Bug in UUCICO V1.12m? To: UUPC/Extended mailing list On Thu, 16 Feb 1995 07:25:01 -0800, "Jeff Coffler" wrote: > Hi Guys, > > I think I found a bug in V1.12m UUCICO. I had a UUCICO that was keeping > an eye on port 540 (uupoll -r 0 -m tcp), and here's the output: > > ----- > > 32 E% uupoll -r 0 -m tcp > uupoll: UUPC/extended 1.12m (Windows 32 bit mode, 15Feb95 20:57) > Executing command: uucico -r0 -x1 -d0900 -mtcp > uucico: UUPC/extended 1.12m (Windows 32 bit mode, 15Feb95 20:57) > Monitoring port tcptty device tcp for 539 minutes until 02/16-07:03 > login: login for user foo failed, bad user id > rmsg: Timeout reading message > Executing command: uucico -r0 -x1 -d0900 -mtcp > uucico: UUPC/extended 1.12m (Windows 32 bit mode, 15Feb95 20:57) > Monitoring port tcptty device tcp for 540 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Monitoring port tcptty device tcp for 0 minutes until 02/16-07:04 > Executing command: uucico -r0 -x1 -d0900 -mtcp > uucico: UUPC/extended 1.12m (Windows 32 bit mode, 15Feb95 20:57) > Monitoring port tcptty device tcp for 540 minutes until 02/16-16:04 > > ----- > > It looks like it was sleeping until 7:04 AM. That's fine. But then look > at what happened at 7:04 AM! It did recover, but is this normal? > > Please take a look and let me know what you think, thanks! A comparison which was greater than should have been greater than or equal to. Thus, it looped for one second. Corrected in 1.12m -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 How do you make Windows faster? Throw it harder! ------------------------------ Date: Sun, 12 Feb 95 19:56:30 -0500 From: sysop@mome-raths.iac.net Subject: expire not expiring? To: UUPC/Extended mailing list It seems that expire isn't expiring all of the articles it should. Today, I ran UNPOST against the binary newsgroups, and some of the files getting decoded are at least two weeks old. I keep running out of disk space when this happens. Finally, I just ran expire -e 4. It claimed to be expiring articles older than 4 days, but when I run TIN, I'm still reading articles that were posted on the 4th. That's 8 days ago. I don't believe that it takes 8 days for these articles to reach my site. Even more bizarre, the articles have 3 or 4 February on the stamp, then it jumps to just a few days ago. In other words, it appears that the older articles are not getting expired, but just those that are somewhere in the middle. As further evidence of that, I went through my spool directory the other day and noticed that there were some jobs from this node that were still laying around. They were approx one and a half (six weeks) old. I think they went out, but UUCLEAN did not bother to clean up the debris. From what I understand, the jobs should be deleted if they are left laying around for a certain amount of time. Has anyone else experienced this? Is there another flag that I need to feed into expire? John -- Mome Raths BBS sevot yhtils eht dna ,gillirb sawT` ^. .^ (513)523-7887 ebaw eht ni elbmig dna eryg diD ( @ ) Oxford, Ohio ,sevogorob eht erew ysmim llA .ebargtuo shtar emom eht dnA ------------------------------ Date: Mon, 13 Feb 1995 08:02:54 -0500 From: uupcinfo@kew.com Subject: expire not expiring? To: UUPC/Extended mailing list On Sun, 12 Feb 95 19:56:30 -0500, sysop@mome-raths.iac.net wrote: > It seems that expire isn't expiring all of the articles it should. > Today, I ran UNPOST against the binary newsgroups, and some of > the files getting decoded are at least two weeks old. I keep > running out of disk space when this happens. Finally, I just > ran expire -e 4. It claimed to be expiring articles older > than 4 days, but when I run TIN, I'm still reading articles > that were posted on the 4th. That's 8 days ago. I don't believe > that it takes 8 days for these articles to reach my site. Even > more bizarre, the articles have 3 or 4 February on the stamp, > then it jumps to just a few days ago. In other words, it appears > that the older articles are not getting expired, but just those > that are somewhere in the middle. The test is a simpler 'older than' test. Were the files posted to multiple groups, and are these groups in your active file? > As further evidence of that, I went through my spool directory > the other day and noticed that there were some jobs from this > node that were still laying around. They were approx one and > a half (six weeks) old. I think they went out, but UUCLEAN > did not bother to clean up the debris. From what I understand, > the jobs should be deleted if they are left laying around for > a certain amount of time. The UUPC/extende uuclean does NOT clean the spool directory. You have to do that by hand with UUSTAT (run it -q, see who has old files, and then run it for those systems, and then finally run it with -k to actually kill the files.) -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 Bring back the golden days of OS/MVT release 21.6 ------------------------------ Date: Sun, 12 Feb 95 12:41:37 -0500 From: sysop@mome-raths.iac.net Subject: inews To: UUPC/Extended mailing list I'm beginning to notice that inews does not support all of the features that the unix flavor does. For example, I should be able to make some adjustments to active using inews. Also, this does not work: date | inews -c sendsys mome -n to.uuiac The above gives me an illegal option error msg. It is supposed to send off a request to the host for a copy of the host feed's sys file, which lists the groups that they are sending to you. Are there any plans to implement some of these features in the future? John -- Mome Raths BBS sevot yhtils eht dna ,gillirb sawT` ^. .^ (513)523-7887 ebaw eht ni elbmig dna eryg diD ( @ ) Oxford, Ohio ,sevogorob eht erew ysmim llA .ebargtuo shtar emom eht dnA ------------------------------ Date: Tue, 14 Feb 1995 18:58:49 -0800 From: don@reid.corvallis.or.us Subject: Mail GUI interface To: UUPC/Extended mailing list Is there a good GUI mail interface that will work with UUPC under Windows NT? I have used unix mail for a long time, but my family will find the mail program a but confusing. -- Don Reid Home: Office: e-mail don@reid.corvallis.or.us donr@cv.hp.com phone 503-754-0707 503-715-2726 address 3325 NW McKinley Dr. 1000 NE Circle Blvd. Corvallis, OR 97330 Corvallis, OR 97330 USA USA ------------------------------ Date: Sat, 11 Feb 1995 17:04:37 -0500 From: Software@kew.com Subject: new, improved, NNS support To: UUPC/Extended mailing list Per the request of Jeff Coffler (NNS author), combined with a memory shortage under DOS, I am redoing rnews processing (again). NNS processing currently (was) going through most of the normal rnews processing, which resulted in various filters being applied to it, and the news automatically being queued for remote UUCP based systems. Jeff views this as redundant to and perhaps in active conflict with NNS processing, which also performs similar processing. Since NNS can and will bypass RNEWS to directly invoke the UUX command for queuing news for the remote system, most of the RNEWS processing can be turned off. This is a reasonable request. Here's where it gets interesting for non-NNS environments, particularly DOS. I'm actually breaking RNEWS into two programs: RNEWS, which decompresses news (if not in SNEWS mode) and queues news for SNEWS, NNS, and/or NEWSRUN. If SNEWS or NNS mode is enabled, RNEWS will still queue the news for remote processing IF AND ONLY IF a SYS file already exists to control the distibution. NEWSRUN, which will actually distribute news. This includes most of the (unreleased) current function of RNEWS, but is slightly smaller because it doesn't need to know about compressed batches or SNEWS. This allows a MUCH smaller RNEWS under DOS, where I've been seeing problems with memory space for decompressing news with GZIP. It also helps RNEWS under NT using NNS, where NEWSRUN will never be run (unless you've a reason to create a SYS file for UUPC). It also allows disconnecting news back-end processing (which requires exclusive access to the HISTORY and ACTIVE files) from UUXQT processing, which helps multi-tasking systems. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 UNIX is a SPACEWAR game with a file system grafted on it. ------------------------------ Date: Tue, 14 Feb 1995 08:01:49 -0500 From: Software@kew.com Subject: new, improved, NNS support To: UUPC/Extended mailing list On Sat, 11 Feb 95 19:21:02 -0500, "Mustafa Soysal" wrote: > ... > > This allows a MUCH smaller RNEWS under DOS, where I've been seeing > > problems with memory space for decompressing news with GZIP. It also > > helps RNEWS under NT using NNS, where NEWSRUN will never be run (unless > > you've a reason to create a SYS file for UUPC). > > > > It also allows disconnecting news back-end processing (which requires > > exclusive access to the HISTORY and ACTIVE files) from UUXQT processing, > > which helps multi-tasking systems. > Any expected release date yet? > > Best Regards, No. I was originally shooting for end of January, but NT performance problems which turned into an outright bug delayed me. Also, NNS support needs to be retested. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 Days like this make me wish I was still doing drugs. ------------------------------ Date: Sun, 19 Feb 1995 09:37:53 -0500 From: Software@kew.com Subject: Problem with MAIL from UUPC 1.12k To: UUPC/Extended mailing list On Sun, 19 Feb 1995 14:55:08 +0100 (MET), "Cleto Pescia" wrote: > I am very sorry for having annoyed you with my strange "problem". I'm merely glad it is solved. > EuroCom works in the field of rehabilitation technology for blind and > low vision PC users. Among other things we have developed a special > speech friendly e-mail system which is quite popular here in Switzerland, > and now we would like to extend our solutions to Internet mail, too. > I have already received a lot of requests from blind PC users who would > like to have access to the Internet e-mail for work, and I think UUPC is > an excellent way of providing them with the tools they need, particularly > because it is a very speech friendly package. I plan to let them access our > Linux machine (the one I am writing this on) through UUPC. > But, in order to make it easy enough for the majority of our users to use > UUPC, I have to translate it into German, French and Italian (In Switzerland > we have three official national languages...). Could you please tell me > exactly where the messages to translate are? Of course, I surely will need > your assistance in getting this done, but I am ready to pay something for > that. Moreover, if you want, you could freely distribute those "translated" > versions. What do you think about that? Unfortunately, UUPC/extended is not National Language Support (NLS) enabled. The messages are, in fact, spread through each and every source file. Packages exist to extract such messages into external files, but I tend to avoid them because a) I'm personally not multi-lingual, and b) there is a lot of overhead involved. If you are willing to do the work, build new modules (you would need compilers with libraries for each language, alas, since some error messages come from the C run time libraries) and release the sources, you may feel free to do so. I'm kicking this to our general discussion list to see anyone else has some ideas. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 Give! Support the Wonderworks Tosci's Chocolate Ice Cream Fund! ------------------------------ Date: Sat, 11 Feb 95 18:27:38 -0500 From: sysop@mome-raths.iac.net Subject: question about protocol and TIN To: UUPC/Extended mailing list > > I forgot, G is the protocol with the bug? So it's safe to use the > g protocol, isn't it? > > I downloaded tin for OS/2 a file of about 175 Kb and tried to set it up. I > noticed that it is a very small program just one executable and two > textfiles. Everything seemed to work okay, but I could read the newsgroups > and I like how TIN works. Then I tried to post a message that didn't work. > On return from the editor I have to choose 'p' to post the message. Tin > then trys to start a program called postnews, but I don't have this > program. Can anyone tell me how I can make TIN to work? Thanks in advance. This has nothing to do with the afore-mentioned bug. What I did was to write a CMD file named POSTNEWS.CMD. It is based upon PNEWS.CMD that comes with UUPC. UUPC does not come with it, since POSTNEWS is a unix NNTP command, and TIN was written to work with NNTP. With this command file, though, TIN won't care. The only caveat is that you cannot cancel articles. Because I'm always sending this out, I'll put in into the mailing list this one last time. However, I will put it up for ftp at ftp.cdrom.com. I will name it tinpost.zip when I do. John =====================CUT HERE============================== /*--------------------------------------------------------------------*/ /* Program: pnews.cmd */ /* Author: Snuffles P. Bear */ /* Kendra Electronic Wonderworks */ /* P.O. Box 132 */ /* Arlington, MA 02174 */ /* */ /* Function: Quick and (very) dirty OS/2 posting program */ /* for UUPC/extended */ /*--------------------------------------------------------------------*/ /* This file modified and renamed to POSTNEWS.CMD for use with TIN */ /* for OS/2. */ /*--------------------------------------------------------------------*/ /* Note: This program doesn't support prefixed keywords in */ /* the UUPC/extended RC file, and further presumes you */ /* always want your posts saved for posterity and/or */ /* law suits. In truth, this program was a quickly */ /* hacked prototype and no more or less. */ /* */ /* Did we mention it also ALWAYS tacks on your .sig */ /* file? Or that it may not work on multiple disk */ /* systems? */ /*--------------------------------------------------------------------*/ /*--------------------------------------------------------------------*/ /* Changes Copyright (c) 1989-1994 by Kendra Electronic */ /* Wonderworks. */ /* */ /* All rights reserved except those explicitly granted by */ /* the UUPC/extended license agreement. */ /*--------------------------------------------------------------------*/ /*--------------------------------------------------------------------*/ /* RCS Information */ /*--------------------------------------------------------------------*/ /* * $Id: pnews.cmd 1.2 1994/02/13 04:56:14 ahd Exp $ * * $Log: pnews.cmd $ * Revision 1.2 1994/02/13 04:56:14 ahd * Add RCS log field * */ /* Changed to POSTNEWS.CMD by John D. Carmack to work with OS/2 TIN */ /* Notice it is mostly just taking stuff out of the original */ signal on novalue '@echo off' /* Disable OS/2 command echo */ /*--------------------------------------------------------------------*/ /* Get environment information */ /*--------------------------------------------------------------------*/ uupcusrrc = value( 'UUPCUSRRC',,'OS2ENVIRONMENT'); domain = getuupc("fromDomain", getuupc("domain")); editor = getuupc("OS2.editor",,uupcusrrc); home = getuupc("home",,uupcusrrc); mailbox = getuupc("mailbox",,uupcusrrc); name = getuupc("name",,uupcusrrc); organization = getuupc("organization","NOT!",uupcusrrc); signature = getuupc("signature","NOT!",uupcusrrc); tempdir = getuupc("TEMPDIR" ) /*--------------------------------------------------------------------*/ /* Create a posting header */ /*--------------------------------------------------------------------*/ dfile = Arg(1); say dfile /*--------------------------------------------------------------------*/ /* Save the file whether or not we post it */ /*--------------------------------------------------------------------*/ savefile = home || '\' || 'USENETPR.SPB' call lineout savefile,copies('01'x,19) call lineout savefile,'Date:' left(date('w'),3) || ',' date() time() 'LOCAL'; do while(lines(dfile)) call lineout savefile,linein(dfile) end call lineout savefile say 'Copy saved in' savefile; /*--------------------------------------------------------------------*/ /* Determine if the user really wants to post the article */ /*--------------------------------------------------------------------*/ if signature <> 'NOT!' then do; if pos( '\' , signature ) == 0 then signature = home || '\' || signature; call lineout dfile,'--'; /* Terminate body of message */ do while( lines(signature) ) call lineout dfile,linein(signature) end; call lineout dfile; /* Close the file */ end; /*--------------------------------------------------------------------*/ /* Execute the post */ /*--------------------------------------------------------------------*/ 'inews <' dfile; /*--------------------------------------------------------------------*/ /* Delete our work file and exit */ /*--------------------------------------------------------------------*/ /* call sysfiledelete dfile; */ call SysCls; exit rc; -- Mome Raths BBS Monty Python songs & skits. (513)523-7887 OS/2 programs, CDROM & new. Oxford, Ohio 12 Step & AIDS support echos. Adult pix and messages. ------------------------------ Date: Sun, 12 Feb 95 12:37:25 -0500 From: sysop@mome-raths.iac.net Subject: question about protocol and TIN To: UUPC/Extended mailing list Correction on the earlier mailing. The filename is POSTNEWS.ZIP and I put it up on ftp.cdrom.com in pub/os2/incoming last night in case anyone needs this in the future. Regards, John -- Mome Raths BBS sevot yhtils eht dna ,gillirb sawT` ^. .^ (513)523-7887 ebaw eht ni elbmig dna eryg diD ( @ ) Oxford, Ohio ,sevogorob eht erew ysmim llA .ebargtuo shtar emom eht dnA ------------------------------ Date: Tue, 14 Feb 1995 15:23:13 +0000 (GMT) From: dirkt@omico.om.org Subject: UUPC for Windows question To: UUPC/Extended mailing list Hi all! Who has set up UUPC for Windows 3.x and could give some advice? In my DOS installation I am running some batch files after UUCICO, that handle failed calls, call UUXQT etc. How can I manage to call these things automatically after the Windows executable of UUCICO has run? Thank's in advance for all replys! Dirk ------------------------------ Date: Tue, 14 Feb 1995 18:38:52 -0500 From: uupcinfo@kew.com Subject: UUPC for Windows question To: UUPC/Extended mailing list On Tue, 14 Feb 1995 15:23:13 +0000 (GMT), dirkt@omico.om.org wrote: > Who has set up UUPC for Windows 3.x and could give some advice? > > In my DOS installation I am running some batch files after UUCICO, > that handle failed calls, call UUXQT etc. UUPOLL automatically calls UUXQT. Or use the -U option in 1.12k. > How can I manage to call these things automatically after the Windows > executable of UUCICO has run? UUPOLL also has a -B to run an arbitrary command before calling out. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-641-3452 "Sorry, but support is not currently available via email." - MicroSoft.COM ------------------------------ End of UUPC-Info Digest ******************************