OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
VK2ZRG > TPK      08.01.05 13:18l 139 Lines 6570 Bytes #999 (0) @ WW
BID : 1034_VK2ZRG
Read: GUEST
Subj: MAKELIST...My version...Update
Path: DB0FHN<DB0MRW<DB0ERF<DB0FBB<DB0BI<DB0PRA<ON0RET<DB0RES<DK0WUE<7M3TJZ<
      KP4IG<IZ0AWG<VK6ISP<VK2BNR<VK2TGB<VK2IO<VK2WI
Sent: 050108/1019Z @:VK2WI.#SYD.NSW.AUS.OC #:58115 [SYDNEY] FBB7 $:1034_VK2ZRG
From: VK2ZRG@VK2WI.#SYD.NSW.AUS.OC
To  : TPK@WW

VK2ZRG/TPK 1.83d Msg #:1034  Date:08-01-05  Time:10:18Z

Hello TPK users,
         The response to my bulletin of a week ago hasn't been overwhelming.
Maybe Christmas hols have something to do with that. Thank you Frank in ZL3
land, and Brian in VK3 land for your info. (Frank, I think my SP messages got
held up.) My original bulletin is attached below.

  Anyway here is what works in the first version. Item numbers are those in
my wish list (below).

Items 1,3,6,8,9,10 work OK. `Extraneous lines' now include multiple lines in
the capture file with the same message number, and lines with message numbers
corresponding to an existing line in the *.LST file.

 The menu gives a sorted list of directory names (without an extension) under
the \LISTS directory. The menu also has a line for update of EXECAUTO.TPK

Item 8, the CONFIG file, has data for directory paths and drive letter as
       contained in TPK.CFG, as well as the type of data found in MAKELIST.TEM
       and MAKELIST.CFG.

Item 2 is OK for bulletin files and can add new headers to MSG_PRIV.LST, but
       headers in a private message list can't be tagged by TPK in the same
       way as for a BBSname.LST file. In any case, to make a private list work,
       it is necessary to add entries to RXMSG.TPK, as well as properly tag
       the new headers. As far as I can tell from MAKELIST.DOC, MAKELIST
       doesn't do this.

Item 4. Programme will not run if RXMSG.TPK exists.

Item 12 Ok for TPK 1.82/1.83. Should be OK for other TPK versions. Only OK
        for FBB 7.00 or similar. I did some work a few days ago on making it
        work of other BBS software (thanks Brian, for the info).

   I still would like more info on other header formats after the L (list)
command so that the code can tested properly. I've info on this BBS software:

   FBB 7.00i and 7.00g
   F6FBB Mailbox and Server:- F6FBB-v7.04h
   F6FBB V7.00g25 (MsDos)

Item 11
 As for a TPK style help file...well not good so far. I only get a few lines
(around five) displayed on each page with a short file called FILENAME.HLP
The longer the file, the more lines per page...very curious. Maybe it's a TPK
problem. Can anyone give me the drum on this one?

 The executable file size is 16 kb. The performance of the first version is
quite adequate for my own use. Except that it is only for FBB 7.00, it seems
that it does what MAKELIST does, as far as I can tell from MAKELIST.DOC

  It operates quite quickly. Adding a 100 headers to a *.LST file of some
620 kb length (around 7600 headers) takes about 3 seconds on a 100 MHz 586
machine.

My earlier bulletin.........

VK2ZRG/TPK 1.83d Msg #:1012  Date:01-01-05  Time:7:00Z

Hello TPK users,
             I've not yet received any replies/responses to my last bulletin
to TPK re MAKELIST.EXE, a week ago. Whether this means that nobody uses
MAKELIST.EXE or that there is no need for such a programme, I know not.
Alternatively, maybe, MAKELIST.EXE doesn't work with later versions of FBB.

   So I've decided to write my own version. I've made a flow chart for a
programme, and it looks straight forward. The only info on Roger's programme
that I have, is from MAKELIST.DOC. I can't see why there should be any problem
with extraneous lines in the capture file, and having tagged files in the list
can be accommodated too, with a bit of effort. That would allow a programme to
automatically tag files, as defined in CONFIG.TPK, for download.

   I've made a test with some dummied up files for a local BBS that doesn't
send me any unproto headers. The files allowed TPK to automatically connect
to the BBS and download some files. So the scheme works quite well.

   However I lack information as to what versions of FBB are in use around
the world nowadays. The BBS's in this neck of the woods all use FBB 7.00.
Writing my programme just for FBB 7.00 would simplify it, as would making it
only accommodate TPK 1.82 and 1.83 TPK.CFG config file. I find that TPK.CFG
for TPK 1.81 is different from the ones for 1.82/1.83.

  If you would like a copy of my programme, then I need some information from
YOU. I would like to know what version of FBB (or other software type) is in
use at your local BBS, and also, what version of TPK you are using. If you
send this info to me, then I'll send you a copy of the finished programme.
  As well as the FBB version, I would like a sample of the header list from
your local BBS, after issuing an L (list) command. If you connect to your BBS
and send LL2 (list last 2 message headers), you will get something like this.

Msg#   TSLD  Dim  To    @ BBS   From   Date/Time Title       (LC-choice: *)
5429   B$    3175 SPACE @WW     ZL2VAL 1223/1656 NASA Hacker to do time
5428   B$    2730 NEWS  @WW     M5WJF  1223/1655 Re: MAIN NEWS - 19th Dec 1/11

  Save this output by using <ALT S> in TPK, and include it in your SP message
to me. Do this, even if it looks the same as the above. This is the MOST
important piece of info that I need.

  My programme will function in much the same manner as MAKELIST, as described
in MAKELIST.DOC. (MAKELIST inserts new message headers into a TPK list file,
from an ASCII capture file.)

This is what my version will do (hopefully).

1  Have a menu to select BBS's / private mail list.
2  Work equally well for bulletins and private mail.
3  Not be bothered with extraneous lines in the capture file.
4  Not be bothered with tagged message headers in original .LST file.
5  Automatically tag files, in the added headers, for download.
6  Remove headers for deleted bulletins/messages. (K prefix).
7  Probably, remove headers older than a specified number of days.
8  Be able to use any directory names, on any disc drive. (Use a config file)
9  Make backup files for all files changed by the programme.
10 Not need a separate programme to edit EXECAUTO.TPK.
11 Probably have a help file that you can read with <ALT H> in TPK.
   (In addition to a full .DOC file.)
12 Work with any FBB version/TPK version if enough info is forthcoming.

  And, of course, it will be a proper executable programme, not some kludge
with a spreadsheet. Hi!  It will also be properly tested and bebugged too!

If I don't get enough responses to this bulletin, to make all that worthwhile,
then I'll just write a simple programme for my own use, which I won't be
giving away.

Happy New Year and Happy Cricket.

73s from Ralph VK2ZRG@VK2WI.#SYD.NSW.AUS.OC
/ack

 Taglines Version 1.00, by Colin Coker G4FCN

C Program run, C Program Crash...ReWrite in Pascal!



Read previous mail | Read next mail


 18.05.2024 19:09:08lGo back Go up