| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | That Areafix user... |
BV> Hmmm....This only happens if I have stoped the "Mail Run" for BV> whatever reason (or your system was busy) and I create more mail BV> before trying to connect again. I've done this before without any BV> problems although I have had a few "unexplainable" things happen with BV> PQWK201 (or is it 202 now). The "strange" things have happened so BV> infrequently that I haven't even been able to work out what is BV> happening. As for the appending of the packets, that is done with BV> PKTJOIN if it is needed. It has worked in the past ? - Strange.... PE> Ok, so that's why you append packets. Well if you use PKTJOIN to PE> append packets, that should be all that is required. It's only PE> happened the once so far (that I know of), so we'll just play it by PE> ear. I never ever do that with outgoing PKTs and have never seen that symptom. But as you recall, I have twice seen a glitch with incoming PKTs being combined to eventually produce a QWK which crashes OLX in a most spectacular fashion. Just processing each of the archive files containing PKTs separately does produce an acceptible QWK. And Hamish has seen one of those too. So maybe we are indeed seeing a blemish with PKTJOIN, as yet unclear just what it is about a particular pair of PKTs which triggers it. --- PQWK202* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.