| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | TinyPoint |
PE> Why not just use QWKPOINT.ZIP instead? It is an archive that PE> Alan created which tells you what software you need to be a point PE> and still use your QWK system, under MSDOS. It uses Frontdoor as PE> the front-end, which you are already doing, and some other piece PE> of software (mkqwk102) to do the pktqwk conversion. Far more PE> robust than crap like pqwk hung together by batch files. RS> That just does the same thing, change and pray without actually RS> checking that its actually working properly. Atleast with PQWK, RS> it is used daily by a number of people that I am likely to see RS> comment on problems if they find some. PE> mkqwk102 is probably in use by hundreds of Remote Access BBS's, PE> not code and pray. I never said that one was code and pray. In fact it is what I used for QWKs before I moved over here. It does however have some known problems, which fanged my arse a number of times. That appears to be a known deficiency of the RA message base rather than MKQWK itself tho. Very like Squish in many ways, very widely used, very well known to be as buggy as buggery. I far prefer to avoid the known problems Squish has with message bases too and dont plan to use it to toss into a message base on my system and produce a QWK from that either with anything. The current system I use, particularly with some overall checks added like a check that the total number of messages going into the PKT->QWK conversion matches the number coming out the other end, IMO is a much more robust way to process the PKTs into QWKs. --- PQWK202* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 690/718 711/809 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™.