Subj : Re: test multiple qwk up To : Marceline Jones From : August Abolins Date : Sun Mar 07 2021 07:36:00 Hi Marceline, In a message to Mauro Veiga you wrote: MJ> Only one QWK packet can be open for reading at any time, therefore I MJ> can only see a part of a thread at any time (depending on which QWK MJ> packet I have open). By keeping the REP packets in sync whith their MJ> corresponding QWK packets, locating and viewing the original messages MJ> is easier. Sounds like something like Sempoint (which I am using to demonstrate now) or Durango, would be your solution. Sempoint saves all QWK messages for each echo in squish format. I posted a modest video from screen-capture (my first ever!) on what Sempoint looks like here: https://kolico.ca/fidonet/echos/files/sempoint.avi ,or https://kolico.ca/fidonet/echos/files/sempoint.zip MJ> For example I archive all my QWK downloads (eg. VERT0001.QWK, MJ> VERT002.QWK etc). I also archive all my REP packets (eg. MJ> VERT0001.REP, VERT0002.REP etc). So if I am viewing "VERT0002.REP", I MJ> know the originating messages must be in "VERT0002.QWK" and vice MJ> versa. Yep. Totally nuts. I encountered the same issue with following a thread or needing to refer to an earlier message. That's the reason I switched to Sempoint. Today, I find that even a better solution is to use something like OpenXP. See screenshots here: https://openxp.kolico.ca Even an NNTP solution and a reader of your choice to match your OS platform is a good option. MJ> When uploading REP packets to Synchronet, I have to do it one file at MJ> a time. I see no reason why it cannot be done by batch upload. QWK was designed to speedup online use. That is [1] visit BBS [2] read NEW messages [3] reply to NEW messages. [4] Repeat 1-2-3 at next visit. QWK is for people who do not want to refer to older messages. ..Regards, Ogg * SeM. 2.26 * Everybody remember where we parked. -- Kirk --- SBBSecho 3.13-Linux * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2) .