End of problems
Harry Sideras
*Hi Louis*, on 12 Apr 98 you wrote: ...respect, brethren
l>
l> It looks like my problem is solved. I finally simply deleted
l> Cache.dns in the Sting folder and replaced the corrupted Route.tab
l> file by a "new" one. Next I started Sting, then Newsie online, got
l> some messages/mail and logged out again. Surprise, surprise, Sting had
l> created a new Cache.dns, this time with the names of my own ISP, and
l> Route.tab was still OK!!!
If you'd kept the same title to your messages I wouldn't have lost the thread
and made all those other replies. Glad you're fixed up...
l> In the meantime, I upgraded to Newsie 0.88, and the only problem I'm
l> still having is sending postings: my editor saves a file that I'm
l> calling POST0000.TXT or whatever, then I quit the editor, next Newsie
l> creates just another file, but I found again that when I don't save
l> in my external editor, Newsie only sends out a posting with the
l> header lines. (Hence the "empty posting" before. I find this a messy
l> way to handle things. Or maybe I just got everything wrong here :-)
You know, I've never completely understood Newsie's online messaging. I've
never managed it successfully yet... %^{|
# Regards, Harry Sideras - UK Association of Atari User Groups #
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*
# sidc...@cix.compulink.co.uk # 90:102/14...@nest.ftn #
* hsid...@mettav.demon.co.uk * 100:1011/14...@turbonet.ftn *
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The Tavern BBS Gateway 300-33600 V42Bis MNP 2-5 24 Hours |
| **> 44-(0)181-364-8268 <** |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Louis Holleman
On 16 Apr 98 05:53:50, Harry Sideras wrote:
>
>If you'd kept the same title to your messages I wouldn't have lost the thread
>and made all those other replies. Glad you're fixed up...
>
Hi Harry,
well, you've seen I got the problem solved. THAT problem that is. Others have
told me how to handle my own mail and postings and I got that under control too.
Ya' know, I've been using a mailer system for years (Semper/LED) but this stuff
is a complete new learning process :-)
>
>You know, I've never completely understood Newsie's online messaging. I've
>never managed it successfully yet... %^{|
>
What buggers me now is I can't see my own postings back here. I saw a few ones,
but I'm pretty sure all postings of the last 2 days have somewhere gone down
the drain - at least I haven't seen them in this NG. I do it like it should be
done but heck, it just looks like Fido, where there's always The BLack Hole
lurking around...
Strange thing is: everything in Mail goes well now, but I simply miss a lot of
postings I did. So far I didn't always check after writing them (offline)
whether there were POSTxxxx files and a PBX file, but I'm gonna check this for
a while, also the logfile. Pity the logfile only exists on the last session...
In the meantime I have no further problems with Newsie, like I said, it's that
old learning process again and I do like some features, once I got them sorted
out :-)
CU NeXT msg
Louis
---------------------------------
| Louis Holleman |
| E-mail: lo...@holleman.demon.nl |
| http://www.holleman.demon.nl |
---------------------------------
--
Neil Roughley
Louis Holleman wrote:
> Strange thing is: everything in Mail goes well now, but I simply miss a
> lot of postings I did. So far I didn't always check after writing them
> (offline) whether there were POSTxxxx files and a PBX file, but I'm
> gonna check this for a while, also the logfile. Pity the logfile only
> exists on the last session...
Make backups of your postxxxx.txt files and the post.pbx file before the
articles are posted. This way if something goes wrong you can quickly
start over again (this is what I used to do). But after the articles are
posted (or appear to be), check NEWSie's log to see what went on with the
news server. Summon the log via the drop-down menu just after doing a
post. If you quit NEWSie and re-run it, the log will be zeroed. If you
forgot to check the log and have already exited, view the log on your
desktop.
If a post appears to be sent OK but you don't get a copy of it back, then
chances are something went wrong and the log will tell you what. With
server errors, NEWSie behaves as if nothing went wrong: the modem lights
flicker, a prompt says it's sending, and the postxxxx.txt and post.pbx
files end up deleted -- all the while the server may have rejected
everything sent to it. Since being connected to the 'net, I've had four
different news server errors occur, all of which NEWSie had no idea were
going on at the time. But that's what the log is for.
<< Neil >>
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Neil Roughley | http://www.excelprinters.com/tos.htm
roug...@HORMEL.unix.dsoe.com | remove uppercase spamblock to reply
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Pascal Ricard
Hello,
in article <892709257.13651....@news.demon.nl>
Louis Holleman wrote:
> Ya' know, I've been using a mailer system for years (Semper/LED) but this stuff
> is a complete new learning process :-)
Do you know you can still use Led as your offline news/mail reader ?
You will need then net2net or FiST for import/export and something like
NEWSwatch/POPwatch (or even Nos) for sending/fetching. Easy, isn't it ? ;-)
--
Pascal, surfing the web on his Falcon...
Derryck Croker
On 16 Apr 1998 06:47:37, Louis Holleman wrote:
>On 16 Apr 98 05:53:50, Harry Sideras wrote:
>>
>>If you'd kept the same title to your messages I wouldn't have lost the thread
>well, you've seen I got the problem solved. THAT problem that is. Others have
>told me how to handle my own mail and postings and I got that under control too.
>Ya' know, I've been using a mailer system for years (Semper/LED) but this stuff
>is a complete new learning process :-)
Right, it's a whole new ballgame.
>What buggers me now is I can't see my own postings back here. I saw a few ones,
>but I'm pretty sure all postings of the last 2 days have somewhere gone down
>the drain - at least I haven't seen them in this NG. I do it like it should be
Hmm, I usually get my own postings shown in the same session.
>done but heck, it just looks like Fido, where there's always The BLack Hole
>lurking around...
Sounds a bit more serious than that!
>Strange thing is: everything in Mail goes well now, but I simply miss a lot of
>postings I did. So far I didn't always check after writing them (offline)
>whether there were POSTxxxx files and a PBX file, but I'm gonna check this for
You can do that easily enough by checking in the outbox menu item.
>a while, also the logfile. Pity the logfile only exists on the last session...
Yes. I think that it might be better if the log was added to rather than
being rewritten (perhaps with a user-configurable size), would be far more
useful.
Rgds, Derryck
Peter Rottengatter
In article <892709257.13651....@news.demon.nl>,
You're doing strange things with news articles ! For instance you truncate
Reference lines, like this one taken from a header of a message of yours :
> References: <2864_h...@mettav.demon.co.R.E.M.O.V.E.T.O.R.
It's obvious that "E.P.L.Y.uk (Harry Sideras)" is missing, which destroys
all the news threading. Have you possibly set your editor to auto-reformat
your text ? Header lines that are long must not be wrapped !!!
John, I think NEWSie should be modified to include certain NEWS header tags
*after* the message has been edited. This should especially include the
Reference line, as there is no reason why a user should be allowed to edit
it.
Cheers Peter
--
---------------------------------------------------------------------
Peter Rottengatter pe...@pallas.amp.uni-hannover.de
http://www.stud.uni-hannover.de/~perot
---------------------------------------------------------------------
Michael Grove
On 20 Apr 1998 10:13:43, Peter Rottengatter wrote:
>In article <892709257.13651....@news.demon.nl>,
> lo...@holleman.demon.nl (Louis Holleman) writes:
>> On 16 Apr 98 05:53:50, Harry Sideras wrote:
>
>You're doing strange things with news articles ! For instance you truncate
>Reference lines, like this one taken from a header of a message of yours :
>
>> References: <2864_h...@mettav.demon.co.R.E.M.O.V.E.T.O.R.
>
>It's obvious that "E.P.L.Y.uk (Harry Sideras)" is missing, which destroys
>all the news threading. Have you possibly set your editor to auto-reformat
>your text ? Header lines that are long must not be wrapped !!!
>
>John, I think NEWSie should be modified to include certain NEWS header tags
>*after* the message has been edited. This should especially include the
>Reference line, as there is no reason why a user should be allowed to edit
>it.
>
>
>Cheers Peter
I notice that when trying to post to groups such as
xxx.xxxxxxxx.xxxxxxxx.xxxxxxx.xxxxxx, that Newsie dosen't insert the
proper newsgroup, so I assume posting to one with that length of a
name is not possible. The last bit of the group is lost, and some
random characters are inserted.
Mike
Neil Roughley
Peter Rottengatter wrote:
> John, I think NEWSie should be modified to include certain NEWS header
> tags *after* the message has been edited. This should especially
> include the Reference line, as there is no reason why a user should be
> allowed to edit it.
The truncation is caused by NEWSie's 50-character limit on message IDs.
FireNews doesn't have this limit, but like NEWSie it only uses the
references from the *first* line, so some manual interaction in an editor
has to be done to 'fix' things. But FireNews does one thing differently:
it quotes all the article's headers when the editor is summoned, so
instead of digging around trying to reconstruct things, the complete
references are already there (ready for pasting).
Louis Holleman
On 20 Apr 1998 10:00:05, Peter Rottengatter wrote:
>> So if I'm getting this right, when starting up don't put any Cache.dns in
your
>> Sting folder because if this doesn't contain the right names, it may screw up
>> things.
>
>Hmm, not quite likely.
>
>> Peter, may I suggest you leave out any Cache.dns files in any future package?
>> These are simply created as needed and this way future users could avoid
lotsa
>> problems.
>> >> In the meantime, I upgraded to Newsie 0.88, and the only problem I'm
>Can you truely and honestly rule out that the problem was fixed by the
>NEWSie upgrade and not by deleting CACHE.DNS ?
>
>
Hi Peter (and glad you're back here)
First of, it had nothing to do with the earlier versions of Newsie. I started
out with 0.82, then I got 0.86 and a little later I grabbed 0.88 from John's
site. With all versions the problem existed. It wasn't after I installed 0.88
when I found out (thanks to the FAQ and the hyp) that these two files Cache.dns
and Route.tab got screwed as soon as Newsie was hooked into the system. At
first I thought Newsie was the problem, but later (and I still tend to hang on
to this theory now) I figured out it isn't Newsie. Let's sum it up here:
Sting reads a file Route.tab for the routing. It also reads Cache.dns for the
server's names, right? You provide a Cache.dns with (probably) your own used
names. So Sting starts, finds addresses and a routing table and says: OK, let's
do it. So far so good, Sting pings fine.
Next I start up Newsie, but Newsie says: hey man, those addresses are wrong,
they should be "whatever". Newsie works OK, and in the meantime or just later,
I don't know, Sting wants to write the new addresses into Cache.dns but fails
to do so, instead it corrupts the Route.tab and the Cache.dns. After that it
simply won't ping any longer to the host. So you have to reboot and if you
haven't found out about the corruption, it finds no decent route any longer and
won't ping any longer.
Like I said, simply deleting Cache.dns did solve the problem: first Sting
displays "Cache load failed" but what the h..., next Newsie passes the right
names to Sting for the Cache.dns, Sting writes a decent file and doesn't screw
up Route.tab in the meantime. This problem turned up here and AFAIK with other
people too, but not with just anybody... It's probably depending on what's in
your system. I have been thinking of Liberty/Freedom straight from the
beginning, that's why I mentioned it in my set-up.
Right now this stuff runs decently for about a week, I admit I had to learn
once again how to handle new programs :-) but I've come to grips with them and
I have no longer big problems. Only problems left are sometimes Newsie screwing
me with postings and E-mail, so right now I'm steadily checking the log whether
things go right or wrong.
I still believe it's best for just anybody NOT to put the Cache.dns in Sting's
folder at the start, because Sting will write the file itself once it's got the
right names for it. Therefore I once more ask: delete this file from the
archives... it MAY prevent lotsa problems.
I will visit your site soon and get the latest stuff for Sting etc.
Finally, I know you call Freedom a "Schweineprogramm", it may be one, but the
rotten thing is: Freedom is my replacement to Selectric and I simply won't let
it go easily... I got simply hooked to it... :-) It really must screw me up on
a permanent basis before I throw it back into the can!
BTW: again, this posting went down the drain, it was sent off but the log
showed "malformed header" so I think it got nowhere. For this I make copies of
the POSTxxxx and POST.PBX files, so now I just send it again by simply creating
a NEW posting, trying to keep up with the thread and pasting in the POSTxxxx
file into this new msg in my editor. That works. I figure Newsie sometimes
cant't handle the given address, hence the "malformed header" message.
This is the final bug that's bothering me with Newsie, and it might originate
from this Freedom/Liberty duo but I'll have to check it more thoroughly...
For now it's a pain in the neck, all this double handling of postings and e-
mail...
So if this msg turns up twice, don't blame me... :-)
Neil Roughley
Louis Holleman wrote:
> BTW: again, this posting went down the drain, it was sent off but
> the log showed "malformed header" so I think it got nowhere.
I suspect the "malformed header" error has something to do with the
header references. The next time you do a follow-up, keep an eye out for
how long the references line is and how it's formatted. That is, if it's
so long that it scrolls off your editor's screen, then go to the very end
of the line and make sure nothing is truncated. Some editors have limits
on how long a line can be (STeno, for instance, had problems). You might
find that follow-ups to a busy thread (i.e. lots of references on one
line) is the source of the problem. Obviously this post (yours) was sent
OK, but I noticed you had to do a *new* post (no references line was
present). Whether your references line is too long or improperly
formatted, I would keep my eye on it to see if a pattern exists (my money
would be on improperly formatted). For posts that "don't make it", view
the manual backups you made of them -- check spacing, line-ends,
truncation, or anything else that a news server might be finicky about.
Louis Holleman
On 21 Apr 1998 20:07:28, Neil Roughley wrote:
> Louis Holleman wrote:
>
>> BTW: again, this posting went down the drain, it was sent off but
>> the log showed "malformed header" so I think it got nowhere.
>
>I suspect the "malformed header" error has something to do with the
>header references. The next time you do a follow-up, keep an eye out for
>how long the references line is and how it's formatted. That is, if it's
>so long that it scrolls off your editor's screen, then go to the very end
>of the line and make sure nothing is truncated. Some editors have limits
>on how long a line can be (STeno, for instance, had problems). You might
>find that follow-ups to a busy thread (i.e. lots of references on one
>line) is the source of the problem. Obviously this post (yours) was sent
>OK, but I noticed you had to do a *new* post (no references line was
>present). Whether your references line is too long or improperly
>formatted, I would keep my eye on it to see if a pattern exists (my money
>would be on improperly formatted). For posts that "don't make it", view
>the manual backups you made of them -- check spacing, line-ends,
>truncation, or anything else that a news server might be finicky about.
>
><< Neil >>
>
you simply GOT it! I know my QED is set to break lines at 80 chars. So I just
turned that off, now I've got to put returns in on the lines, but let's see
if this goes OK now.
I remember seeing this reference line on two lines in that posting I did
before, where I put in those headers from the "follow up postings"...
OK, this also means I have to keep an eye on my own lines of writing, don't
go beyond 80 chars.
Tks for the advice,
John Whalley
on Tue 21-04-98 09:54 Louis Holleman wrote:
>On 20 Apr 1998 10:00:05, Peter Rottengatter wrote:
>>> So if I'm getting this right, when starting up don't put any Cache.dns in
>your
>>> Sting folder because if this doesn't contain the right names, it may screw up
>>> things.
>>
>>Hmm, not quite likely.
>>
>>> Peter, may I suggest you leave out any Cache.dns files in any future package?
>>> These are simply created as needed and this way future users could avoid
>lotsa
>>> problems.
>>> >> In the meantime, I upgraded to Newsie 0.88, and the only problem I'm
>still >
>>Can you truely and honestly rule out that the problem was fixed by the
>>NEWSie upgrade and not by deleting CACHE.DNS ?
>>
>>
>Hi Peter (and glad you're back here)
>
>First of, it had nothing to do with the earlier versions of Newsie. I started
>out with 0.82, then I got 0.86 and a little later I grabbed 0.88 from John's
>site. With all versions the problem existed. It wasn't after I installed 0.88
>when I found out (thanks to the FAQ and the hyp) that these two files Cache.dns
>and Route.tab got screwed as soon as Newsie was hooked into the system.
<mega snip>
I think you just made the main point here. Judging from the
discussions in here, it's happened with several versions of Newsie and
the files get messed up as soon as Newsie is hooked into the system.
People who don't use Newsie (eg me, apart from *very* occasional
testing to see how it's getting on) don't have the problem. QED...
AIUI (and Peter will doubtless correct/elucidate if I'm wrong)
cache.dns is just what you'd think from the name: it's a cache for DNS
lookups. So the contents as supplied are largely irrelevant as it's
refreshed on a regular basis. If you check the file date/time stamp
you'll see it's updated each time you use STinG: mine currently shows
host names for the machines I connected to at last login if I view it
in STguide. This is used for all clients: I use POPwatch and NEWSwatch
for mail and news collection, plus AFTP, CAB, Finger, TVT102 and the
network time setter. None of them messes up cache.dns or route.tab.
BTW route.tab is only *read* by STinG (mine is still unchanged/
untouched since last August) - something has to *write* to the disk to
mangle it.
<crosses fingers that the whole thing doesn't fall apart now...>
TTFN
John
--
John Whalley
Please substitute john for news when replying by email:
Mail to ne...@whalley.demon.co.uk will be killed!
Peter Rottengatter
In article <893152472.22253...@news.demon.nl>,
lo...@holleman.demon.nl (Louis Holleman) writes:
> Next I start up Newsie, but Newsie says: hey man, those addresses are wrong,
> they should be "whatever".
No. NEWSie has no direct access to these names. NEWSie has no way whatsoever
to find out which names are cached (i.e. in CACHE.DNS).
> Newsie works OK, and in the meantime or just later,
> I don't know, Sting wants to write the new addresses into Cache.dns but fails
> to do so, instead it corrupts the Route.tab and the Cache.dns.
Since ROUTE.TAB is never accessed after bootup, this corruption can only
occur by corrupted internal GEMDOS data. For that, it's accidental that it
hits GEMDOS, it can well hit STinG or even NEWSie itself. So you cannot
deduce anything from irregular behaviour *after* this bug has struck.
The only important point is that the bug does not strike if NEWSie is not
started. Nobody has seen it happen without NEWSie. That should say enough.
> people too, but not with just anybody... It's probably depending on what's in
> your system. I have been thinking of Liberty/Freedom straight from the
> beginning, that's why I mentioned it in my set-up.
Although possible, I rather doubt that it involves third party software.
I also doubt that the bug is really gone. That's the treacherous thing
about pointers going wild : It may effect memory that is rarely or even
never used, and that hides the bug very effectively, until much much later
when some minor change in the overall configuration makes the pointer go
to and corrupt some important data, and the bug becomes obvious. Makes you
think your software is fine since it worked all the time - wrong.
So I definitely think there is still data corrupted in your system, just
it does not corrupt those structures anymore that led GEMDOS to corrupt
ROUTE.TAB and CACHE.DNS. Maybe it corrupted some other program instead
that you have on your hard disk and which you haven't touched in a while.
This is not to scare you, but is the reality with all machines that do not
implement efficient memory protection.
Peter Rottengatter
In article <893191472.29610...@news.demon.nl>,
lo...@holleman.demon.nl (Louis Holleman) writes:
> you simply GOT it! I know my QED is set to break lines at 80 chars. So I just
> turned that off, now I've got to put returns in on the lines, but let's see
> if this goes OK now.
> I remember seeing this reference line on two lines in that posting I did
> before, where I put in those headers from the "follow up postings"...
>
> OK, this also means I have to keep an eye on my own lines of writing, don't
> go beyond 80 chars.
This is basically the background for my suggestion the other day that John
should include certain header parts *after* the article has been edited.
There is no need to ever edit the References: line, and it only can cause
trouble if either the editor (by "formatting") or the user mingles with it.
Louis Holleman
you'd better said: "Cheer up!"...
Good lawd once more, and I have said "I'm sorry having called Newsie a
screwball"...
Well, for one thing: I'm definitely NOT going to try again to let Newsie
eventually corrupt more data by figuring out what's going to happen when I put
in again the original Cache.dns file... NO WAY!!!
Heck, this scares me... and once more I learned something. BTW, will this
possible corruption go beyond my C-partition where Newsie and Sting are? I've
got 2 HD's, altogether 8 partitions with a total of 1.7 Gb hooked up to my TT!
I figure there's more people now reading with bleak cheeks (Hi, Petter!)...
And finally, there's one more yelling to go:
JOHN, try to fix this problem ASAP!!!!!
Harry Sideras
*Hi Louis*, on 16 Apr 98 you wrote: ...respect, brethren
l>
l> On 16 Apr 98 05:53:50, Harry Sideras wrote:
>> If you'd kept the same title to your messages I wouldn't have lost
l> Well, you've seen I got the problem solved. THAT problem that is.
I knew I spoke too soon B^{)
l> Ya' know, I've been using a mailer system for years (Semper/LED) but
l> this stuff is a complete new learning process :-)
IKWYM. Much like the situation with Semper/LED, this Internet connectivity
subject seems to be a secret that no-one wants to divulge. It's a voyage of
discovery rather than anything more straightforward...
l> What buggers me now is I can't see my own postings back here. I saw a
l> few ones, but I'm pretty sure all postings of the last 2 days have
l> somewhere gone down the drain - at least I haven't seen them in this
l> NG.
My problem too tbh... that's why I don't do my messaging with the IP
connection.
l> So far I didn't always check after writing them (offline) whether
l> there were POSTxxxx files and a PBX file, but I'm gonna check this
l> for a while
Wise move.
l> ...also the logfile. Pity the logfile only exists on the last
l> session...
That's a good point. IOSMail's method of keeping the logfiles trimmed to a
configurable numer of kilobytes is just what I need with Newsie too. I can
handle that!
l> In the meantime I have no further problems with Newsie, like I said,
l> it's that old learning process again and I do like some features,
l> once I got them sorted out :-)
Me too.
Regards,
Harry
Peter Rottengatter
In article <893322169.14922....@news.demon.nl>,
lo...@holleman.demon.nl (Louis Holleman) writes:
> Well, for one thing: I'm definitely NOT going to try again to let Newsie
> eventually corrupt more data by figuring out what's going to happen when I put
> in again the original Cache.dns file... NO WAY!!!
Neither would I if that happened on my machine.
> Heck, this scares me... and once more I learned something. BTW, will this
> possible corruption go beyond my C-partition where Newsie and Sting are? I've
It all depends on which structures inside GEMDOS are effected, but this is
very well possible ! So running a filesystem check on each of your partitions
is a good idea.
> And finally, there's one more yelling to go:
>
> JOHN, try to fix this problem ASAP!!!!!
Such a bug can be very difficult to find, and you can help John a lot by doing
systematic tests (on a backed up partition with all other partitions disabled.
They are safe if you disable them such that you cannot access them from your
applications, i.e. if they do not show up in a fileselector etc. How to disable
them depends on you hard disk driver.) to find out which part of NEWSie causes
the corruption.
Shiuming Lai
On 25 Apr 1998 22:56:29, Peter Rottengatter wrote:
>In article <893322169.14922....@news.demon.nl>,
> lo...@holleman.demon.nl (Louis Holleman) writes:
>> Heck, this scares me... and once more I learned something. BTW, will this
>> possible corruption go beyond my C-partition where Newsie and Sting are? I've
>
>It all depends on which structures inside GEMDOS are effected, but this is
>very well possible ! So running a filesystem check on each of your partitions
>is a good idea.
Aha, I presume this is the same problem I'm having. A lot of file
attachments sent to me decode without any apparent problem but when
I extract them I get CRC errors all over the place. A check with
Diamond Edge revealed hundreds of lost clusters and in my experience
the problem does not spread beyond the partition where Newsie is
installed (for a while I thought I had a corrupt partition so moved
it but the problem followed). I have to regularly fix disk errors
in between using Newsie (haven't tried the latest version yet). It's
a pain, but I just thought, if you're getting CRC errors when
decompressing archives in your mail box, try copying the actual
mail (look where your mail is, lots of MAILnnnn.TXT (where n is an
integer) files and you'll recognise file attachments because they
are much larger than the rest) to a healthy partition and use the
TTP programs to extract. It would seem the corruption problems
arise from the action of old mail being deleted and when you extract
an attachment within Newsie somehow the system is blindly dumping
data and not skipping bad sectors (hence CRC errors when you try to
decompress?) You get the idea...
>> And finally, there's one more yelling to go:
>>
>> JOHN, try to fix this problem ASAP!!!!!
He's aware of the problem but be patient, the man is making a
pretty cool (and complex) piece of software for free, don't
expect miracles!
S.Lai
---------------------------------------------------
e-mail: la...@zetnet.co.uk
la...@cs.man.ac.uk
shiu...@cyberstrider.org
shiu...@mayway.demon.co.uk
WWW: http://www.users.zetnet.co.uk/lais
http://www2.cs.man.ac.uk/~lais
http://www.shiuming.cyberstrider.org
http://www.mayway.demon.co.uk
---------------------------------------------------
Roger Cain
On 8 May 1998 05:45:28 , Charles Silver wrote:
>Not sure how NEWSie decides which to use, UUD
>or MUNPACK.
UUD = UUE Decode
MUNPACK = Mime Unpack.
----------------------------------------------------------------
Roger Cain, Manchester, UK NeST:90:100/103
TT 6Mb/MagiC 5/NVDI 4
________________________________________________________________
Guy Harrison
On 8 May 1998 05:45:28 GMT, csi...@Puke.On.Spammers.com (Charles
Silver) wrote:
>I had a few problems a while back with this and the culprit was UUD.TTP.
Hmm. I wonder if this is the UUD that comes with UUE and the source
code for both? Someone call it from a command shell with no arguments
and see what it spouts out in the way of "usage". There should be a
debug mode so someone could write a dummy UUD which (a) prints out the
arguments passed to it then (b) invokes the original UUD (renamed to
something else) but with debugging enabled.