Only one QWK packet can be open for reading at any time, therefore I
can only see a part of a thread at any time (depending on which QWK
packet I have open). By keeping the REP packets in sync whith their corresponding QWK packets, locating and viewing the original messages
is easier.
For example I archive all my QWK downloads (eg. VERT0001.QWK,
VERT002.QWK etc). I also archive all my REP packets (eg.
VERT0001.REP, VERT0002.REP etc). So if I am viewing "VERT0002.REP", I
know the originating messages must be in "VERT0002.QWK" and vice
versa.
When uploading REP packets to Synchronet, I have to do it one file at
a time. I see no reason why it cannot be done by batch upload.
Quoting August Abolins to Marceline Jones <=-
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.
QWK was designed to speedup online use. ... QWK is for
people who do not want to refer to older messages.
Not here. :-) QWK is the best way to store and backup
old messages. I have QWK /BW packages from dead 90's
systems that I like so much to read. It would be
impossible to rescue them today.
QWK was designed to speedup online use. ... QWK is for
people who do not want to refer to older messages.
Not here. :-) QWK is the best way to store and backup
old messages. I have QWK /BW packages from dead 90's
systems that I like so much to read. It would be
impossible to rescue them today.
I commend you for maintaining a scheduled routine (your 30-day
rule) and being organized.
But why not just "toss" all those messages into something like
Squish format and use something like Sempoint (which handles
both QWK and BW in the same program automatically!) to read them
whenever you want? No more repeat unpacking and searching
required. ;)
But why not ... Squish format and use something like
Sempoint (which handles both QWK and BW in the same program
automatically!)
Seems a good way but i don't know Sempoint. Need to test
and understand. Thanks for tip.
Has many ways to store messages. I use BlueWave (and a long
retention on my system) because i like so much BlueWave
visual, style and tools. A NNTP server also is a good store
option.
Quoting August Abolins to Mauro Veiga <=-
Has many ways to store messages. I use BlueWave (and a long
retention on my system) because i like so much BlueWave
visual, style and tools. A NNTP server also is a good store
option.
I think you would like Sempoint if Windows is a suitable
environment. Its Squish system can handle upto 5000 msgs per
echo. You could delete the messages that are clearly taking up
space and have more for the ones that are keepers. AND.. you
could just as easily rename or archive the .SQL, SQD, .SQI files
as a group on a regular basis - and that wouldn't need to be
every 30 days, but maybe every 180 days.
could just as easily rename or archive the .SQL, SQD, .SQI
files as a group on a regular basis - and that wouldn't
need to be every 30 days, but maybe every 180 days.
As soon as I have time I'll test it. But the limit of
5000 messages per area is boring. It forces me to the
same work that I already have with QWK to create
several files, only bigger. I'll try.
Quoting August Abolins to Mauro Veiga <=-
As soon as I have time I'll test it. But the limit of
5000 messages per area is boring. It forces me to the
same work that I already have with QWK to create
several files, only bigger. I'll try.
Ya.. but the 5000 "limit" is a whole lot more than any one QWK
could ever carry, and you wouldn't need to unpack as many files
to do your searches.
You could store the AREANAME.SQL/SQD/SQI triplets as AREANAME-
yyyy.zip or something, and with a little batch program unpack
them as required. Sempoint has a fine built-in Search feature.
Sempoint allows changing the font, build an address book, steal tearlines... and many other OLR features.
Since Sempoint supports BW and QWK, it could be a pretty good
solution to consolidate and preserve all your message bases with
one management program.
Ya.. but the 5000 "limit" is a whole lot more than any one QWK
could ever carry..
Nope. :-) By curiosity before writing this reply, I
set my system's QWK message pointers for the year 2001
in all areas and downloaded a monster package of 28MB
as 100000 messages. Some areas with more than 20000
messages, and worked fine on BlueWave and Multimail.
It is not practical. Any search takes too long. But
it shows that the QWK/BW system has the ability to
handle with bigger data.
Quoting August Abolins to Mauro Veiga <=-
Nope. :-) By curiosity before writing this reply, I
set my system's QWK message pointers for the year 2001
in all areas and downloaded a monster package of 28MB
as 100000 messages. Some areas with more than 20000
messages, and worked fine on BlueWave and Multimail.
I stand corrected. QWK and BW's apparent unlimited capacity
seems to be pretty good then.
You could probably even just leave everything in those formats
and just use something like winrar to S)earch within the files
within the archives. I find winrar's ability to do that very
handy at times.
It is not practical. Any search takes too long. But
it shows that the QWK/BW system has the ability to
handle with bigger data.
Sempoint, for example, would provide a nicer presentation for
that whole lookup proceedure. When you find the message you
need, you are ready to steal the tagline, compose a reply, save/
print the message, copy it to another area, etc.
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
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:
Even an NNTP solution and a reader of your choice to match your OS platform is a good option.
https://kolico.ca/fidonet/echos/files/sempoint.avi ,or
https://kolico.ca/fidonet/echos/files/sempoint.zip
Those links are dead.
Maybe you should have uploaded to YouTube.
Is there a QWK and REP file merge tool ?
Today, I find that even a better solution is to use
something like OpenXP. See screenshots here:
The OpenXP documentation is in German. Therefore it is
totally useless to me.
Even an NNTP solution and a reader of your choice to match
your OS platform is a good option.
NNTP is getting too far from BBS's for me.
If I wanted SMTP/POP/NNTP then I would use Linux.
^^^^^^^^^^^^Today, I find that even a better solution is to use
something like OpenXP. See screenshots here:
The OpenXP documentation is in German. Therefore it is
totally useless to me.
If you just rely on getting the program from sourceforge, then
yes, the English helps seems to be missing. :( I had some
guidance when I got started with Openxp by a fellow who wrote an
English "Startup User Guide".
If you visit https://openxp.uk/doc/ ..look for oxpguide.pdf
If you visit https://openxp.uk/doc/ ..look for oxpguide.pdf
^^^^^^^^^^^^
Ahem :)
That document is also included in the "doc" directory of
the Windows version and in the /usr/local/lib/openxp/doc/
directory of the Linux version.
If you visit https://openxp.uk/doc/ ..look for oxpguide.pdf
^^^^^^^^^^^^
Ahem :)
Did I get something wrong?
They are here now.
https://kolico.ca/fidonet/files/sempoint.avi ,or https://kolico.ca/fidonet/files/sempoint.zip
Maybe you should have uploaded to YouTube.
Meh. Nah.
Hmmm. Wrt olr messaging, I see nntp as fine improvement when a
BBS offers it.
They are here now.
https://kolico.ca/fidonet/files/sempoint.avi ,or
https://kolico.ca/fidonet/files/sempoint.zip
FYI only the AVI file exists.
Maybe you should have uploaded to YouTube.
Meh. Nah.
Are you afraid you will only get 1 view ?
Hmmm. Wrt olr messaging, I see nntp as fine improvement when a
BBS offers it.
I might as well get a NNTP add-on for Microsoft Outlook.
___ Blue Wave/386 v2.30
I might as well get a NNTP add-on for Microsoft Outlook.
re nntp add-on for MS Outlook.. I tried it many years ago. It's
terrible. I wouldn't recommend that one to anybody.
MJ> I might as well get a NNTP add-on for Microsoft Outlook.
AA> re nntp add-on for MS Outlook.. I tried it many years ago. It's
AA> terrible. I wouldn't recommend that one to anybody.
NNTP is for Usenet. BBS puritans do not use it.
On 27.03.2021 10:34, Marceline Jones wrote:
MJ> I might as well get a NNTP add-on for Microsoft Outlook.
AA> re nntp add-on for MS Outlook.. I tried it many years ago. It's
AA> terrible. I wouldn't recommend that one to anybody.
NNTP is for Usenet. BBS puritans do not use it.
NNTP is also for fidonet. Fidonet is not BBS, and BBS is not fidonet.
'Tommi
MJ> I might as well get a NNTP add-on for Microsoft Outlook.
AA> re nntp add-on for MS Outlook.. I tried it many years ago. It's
AA> terrible. I wouldn't recommend that one to anybody.
NNTP is for Usenet. BBS puritans do not use it.
NNTP is also for fidonet. Fidonet is not BBS, and BBS is not fidonet.
No, NTTP is used to gate messages in and out of Fidonet.
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 113 |
Nodes: | 10 (0 / 10) |
Uptime: | 120:32:59 |
Calls: | 373 |
Files: | 6 |
Messages: | 110,799 |