| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | bugs in pqwk |
PE> I presume the fact you decided to send me dupes today was purely PE> because of PQWK235 (where nnn = fucked), in the same way that PE> Brenton's dupes of a week ago or so were totally due to PQWK230, PE> and in neither case might the fuckwit using the fucking program PE> be in any way fucking responsible for fucking up my system? FM> I don't know whether it was PQWK235 or not, but I noticed FM> those dups fed back to me too - like reading a reply and FM> then the message to which it was replying. FM> More likely it was another of those OLX peculiarities FM> which I don't understand and Rod understands a bit of. The only time OLX will generate dupes is if you dont shut it down properly, either because of a power flick or user error like just turning the machine off without shutting OLX down. And if you reedit messages at all before they are sent, you usually see the telltale results of two messages not identical. From memory without checking all your dupes were true dupes. FM> I'd welcome any constructive suggestions to prevent this happening, Didnt happen this time, so it may have been just not exiting OLX properly one time. FM> but, like you, I don't want to spend all day configuring and FM> customising software. Which is another reason why I dont generally drop in new releases unless there is a good reason too, it makes it hard to distinguish between an unusual occurrence in what you have been using or a new wart introduced when attempting to excise an earlier one. --- 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™.