• Nodelist problem

    From Anna Christina Nass@2:240/5824.1 to All on Saturday, March 06, 2021 13:50:00
    Hi,

    I might have found a little problem with automatic nodeilst imports.

    One of my "othernets", tqwNet, uses lowercase filenames for nodelists.
    So, the hatched file is called eg. "tqwnet.z64" and contains the file "tqwnet.064".

    If I add the entry in FidoNet > Nodelisten > Verwaltung with TQWNET.###
    and TQWNET.Z##, the entry is added and the current suffix (057 when i
    added it) is displayed in the list.

    But every time a new nodelist is sent, it only gets stored in
    ~/.openxp/files, but isn't imported.

    Nodelists from other networks are working, but they also use uppercase filenames (archive and containing file).

    Could this be a problem with uppercase/lowercase filenames?

    Thank you!

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@1:153/757.2 to Anna Christina Nass on Saturday, March 06, 2021 12:29:02

    But every time a new nodelist is sent, it only gets stored in ~/.openxp/files, but isn't imported.

    If I recall correctly, auto-updates only work when there are DIFFs.

    A full nodelist is never auto-updated. Those have to be done manually.


    Nodelists from other networks are working, but they also use uppercase filenames (archive and containing file).

    Could the difference be that the other networks are sending you diffs?

    Could this be a problem with uppercase/lowercase filenames?

    The only network that sends me diffs is Fidonet. And I think those are all uppercase. I will have to confirm with OXP when I am back home to that machine.
    --- SBBSecho 3.13-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Sunday, March 07, 2021 11:44:00
    Am 06.03.21 schrieb August Abolins@1:153/757.2 in POINTS:

    Hallo August,

    But every time a new nodelist is sent, it only gets stored in
    ~/.openxp/files, but isn't imported.

    If I recall correctly, auto-updates only work when there are DIFFs.

    No, auto-updating as a diff is an option.
    For example, I also have the fsxNet nodelist auto-updated and there I
    don't get diffs.

    My "nodelist list" looks like this:

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste
    NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodeliste
    FSXNET.### 071 FSXNET.### FSXNET.Z## Nodeliste
    tqwnet.### 057 TQWNET.### TQWNET.Z## Nodeliste

    Only the FidoNet NODELIST.### is in diff-form, all the other nodelists are full updates.
    And Z2PNT and FSXNET do work, only tqwnet.### does not work.

    The FSXNET entry is configured like this:

    Listenname FSXNET.### Nummer 071
    Listenformat Nodeliste
    Update-Datei FSXNET.###
    Update-Archiv FSXNET.Z##
    [ ] Update als Diff einbinden

    (Whereas NODELIST.### has [x] Update as diff)

    Could this be a problem with uppercase/lowercase filenames?

    The only network that sends me diffs is Fidonet. And I think those are all uppercase. I will have to confirm with OXP when I am back home to that machine.

    Thank you.

    All my nodelist networks send new files with uppercase filenames, only
    tqwNet uses lowercase.

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Sunday, March 07, 2021 11:18:00
    Hello Anna!

    If I recall correctly, auto-updates only work when there are DIFFs.

    No, auto-updating as a diff is an option. For example, I
    also have the fsxNet nodelist auto-updated and there I
    don't get diffs.

    OH! I had understood from one of the OXP experts here that this
    part in the config:

    ÚÄ Configure Node/Pointlist ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
    ³ ³
    ³ List name FSXNET.### Number 360 ³
    ³ ³
    ³ Format of list Nodelist  ³
    ³ Zone/Address 21 ³
    ³ ³
    ³ Update file FSXNET_D.### <----- THIS field ³
    ³ Update archive FSXNET_D.Z## <----- THIS field ³
    ³ ³
    ³ Process by ³
    ³ ³
    ³ [x] Use internal nodelist processor ³
    ³ [ ] Delete update after processing ³
    ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ [F2] ÄÙ

    ..would ONLY work for nets that serve DIFFs.


    My "nodelist list" looks like this:

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodeliste
    FSXNET.### 071 FSXNET.### FSXNET.Z## Nodeliste
    tqwnet.### 057 TQWNET.### TQWNET.Z## Nodeliste

    WOW... That means that I *can* get autoupdated FSXNET nodelists!
    I will do that too! Thanks!

    My nodelist table looks like this:

    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Z2PNT.### 064 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
    ³ NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    ³ FSXNET.### 360 FSXNET_D.### FSXNET_D.Z## Diff Nodelist
    ³ micronet.### 043 XXX XXX Diff Nodelist
    ³ scinet.### 008 SCINET.### SCINET.Z## Diff Nodelist

    Which means, that I would probably encounter the lowercase
    problem with micronet and scinet too!

    I never really noticed the problem though, because I wrongly
    assumed that only DIFF-supported nodelists would update.

    I *think* I had micronet's nodelist configured like you do for
    tqwnet, but never noticed because I assumed that only DIFFs were
    required for that to work. Interesting.


    Only the FidoNet NODELIST.### is in diff-form, all the other nodelists are full updates.
    And Z2PNT and FSXNET do work, only tqwnet.### does not work.

    In that case, I *does* look like you may have discovered a bug.


    The FSXNET entry is configured like this:

    Listenname FSXNET.### Nummer 071
    Listenformat Nodeliste
    Update-Datei FSXNET.###
    Update-Archiv FSXNET.Z##
    [ ] Update als Diff einbinden

    (Whereas NODELIST.### has [x] Update as diff)

    OMG.. I did not realize there was a setting for that
    distinction! I will need to find that and adjust it for FSXNET.


    All my nodelist networks send new files with uppercase
    filenames, only tqwNet uses lowercase.

    As I said, you may have indeed found a bug!


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The point of origin --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Sunday, March 07, 2021 11:32:00
    Hello Anna Christina Nass!

    I have these accumulated for FSXNET:

    12/25/2020 02:15 AM 33,457 FSXNET.360
    01/03/2021 07:37 PM 12,016 FSXNET.Z08
    01/04/2021 05:56 PM 12,115 FSXNET.Z08.1
    01/04/2021 10:45 PM 12,102 FSXNET.Z08.2
    01/07/2021 04:32 PM 12,102 FSXNET.Z08.3
    01/07/2021 11:46 PM 12,162 FSXNET.Z08.4
    01/14/2021 08:51 AM 12,079 FSXNET.Z15
    01/21/2021 08:58 AM 12,131 FSXNET.Z22
    01/23/2021 07:26 AM 12,204 FSXNET.Z29
    01/25/2021 07:55 AM 12,231 FSXNET.Z29.1
    01/28/2021 09:20 AM 12,234 FSXNET.Z29.2
    02/01/2021 08:19 AM 12,250 FSXNET.Z36
    02/04/2021 06:34 PM 12,284 FSXNET.Z36.1
    02/08/2021 06:43 AM 12,488 FSXNET.z43
    02/12/2021 01:31 AM 12,476 FSXNET.Z43.1
    02/19/2021 07:00 AM 12,545 FSXNET.Z50
    12/17/2020 06:21 PM 11,878 FSXNET.Z53
    02/19/2021 05:34 PM 12,580 FSXNET.Z57
    12/24/2020 04:37 PM 11,960 FSXNET.Z60
    03/07/2021 06:35 AM 12,691 FSXNET.Z71

    When I made the changes to match the config that you are using,
    OXP complained the nodelist is out of sequence.

    I assume that has something to do with the setting you mention
    for fidonet NODELIST as an example:

    (Whereas NODELIST.### has [x] Update as diff)

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The point of origin --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Sunday, March 07, 2021 18:56:00
    Am 07.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    (Whereas NODELIST.### has [x] Update as diff)

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?

    I don't know how it is called in the english version, but in the german version it is called "Update als Diff einbinden" and it is the first of
    the two checkbox options below "process by".
    Have a look at the help text, maybe this makes it clearer?

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Sunday, March 07, 2021 19:00:00
    Am 07.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    OH! I had understood from one of the OXP experts here that this
    part in the config:
    [...]
    ³ Update file FSXNET_D.### <----- THIS field ³
    ³ Update archive FSXNET_D.Z## <----- THIS field ³
    [...]
    ..would ONLY work for nets that serve DIFFs.

    Nope ;)

    WOW... That means that I *can* get autoupdated FSXNET nodelists!

    Yep :)

    I will do that too! Thanks!

    I'm glad that I could help.

    My nodelist table looks like this:

    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Z2PNT.### 064 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
    ³ NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    ³ FSXNET.### 360 FSXNET_D.### FSXNET_D.Z## Diff Nodelist
    ³ micronet.### 043 XXX XXX Diff Nodelist
    ³ scinet.### 008 SCINET.### SCINET.Z## Diff Nodelist

    Which means, that I would probably encounter the lowercase
    problem with micronet and scinet too!

    maybe, yes.

    And as I see it, you have the "import as diff" option enabled on all nodelists. If you disable this option on all but the FidoNet nodelists, it should work.
    Except for the upper/lowercase problem I encountered.

    Only the FidoNet NODELIST.### is in diff-form, all the other nodelists ACN>> are full updates.
    And Z2PNT and FSXNET do work, only tqwnet.### does not work.

    In that case, I *does* look like you may have discovered a bug.

    Okay. Who should I report it to?

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@1:396/45.29 to Anna Christina Nass on Sunday, March 07, 2021 13:40:00
    Hello Anna!

    (Whereas NODELIST.### has [x] Update as diff)

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?

    I don't know how it is called in the english version, but
    in the german version it is called "Update als Diff
    einbinden" and it is the first of the two checkbox options
    below "process by". Have a look at the help text, maybe
    this makes it clearer?

    ÚÄ Configure Node/Pointlist ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
    ³ ³
    ³ List name FSXNET.### Number 071 ³
    ³ ³
    ³ Format of list Nodelist  ³
    ³ Zone/Address 21 ³
    ³ ³
    ³ Update file FSXNET.### ³
    ³ Update archive FSXNET.Z## ³
    ³ ³
    ³ Process by ³
    ³ ³
    ³ [ ] Use internal nodelist processor <--THIS! ³
    ³ [ ] Delete update after processing ³
    ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ [F2] ÄÙ

    Thank you. I found the "explanation" for that first [ ] box in
    the F1 help. Ideally, the line above should read:

    [ ] Use internal nodelist DIFF processor

    ..since that function only pertains to DIFFs.


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: (1:396/45.29)
  • From August Abolins@1:396/45.29 to Anna Christina Nass on Sunday, March 07, 2021 13:47:00
    Hello Anna!

    And as I see it, you have the "import as diff" option
    enabled on all nodelists. If you disable this option on
    all but the FidoNet nodelists, it should work. Except for
    the upper/lowercase problem I encountered.


    My table now looks like this:

    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Z2PNT.### 064 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
    ³ NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    ³ FSXNET.### 071 FSXNET.### FSXNET.Z## Nodelist
    ³ micronet.### 043 micronet.### micronet.z## Nodelist
    ³ scinet.### 008 SCINET.### SCINET.Z## Nodelist


    BUT.. I think I found a way to force the lowercase to be
    uppercase.


    ..It *does* look like you may have discovered a bug.

    Okay. Who should I report it to?

    The official destination is XPOINT echo which is the same as the
    google groups nntp group called de.comm.software.crosspoint,
    which I see that you already know about. ;) Address your
    message to Gunter.


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: (1:396/45.29)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Monday, March 08, 2021 10:51:00
    Hello Anna!

    *** Sunday 07.03.21 at 11:44, Anna Christina Nass wrote to August Abolins:

    But every time a new nodelist is sent, it only gets stored in
    ~/.openxp/files, but isn't imported.

    If I recall correctly, auto-updates only work when there are DIFFs.

    No, auto-updating as a diff is an option.

    Oh, that's interesting :)

    For example, I also have the fsxNet nodelist auto-updated and there I don't get diffs.

    My "nodelist list" looks like this:

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste
    ^^^^^^^^^ ^^^^^^^^^
    Did you know there's a weekly DIFF for the Z2 Pointlist:
    Z2PNT_D.### Z2PNT_D.Z##

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Monday, March 08, 2021 11:01:00
    Hello Anna!

    *** Sunday 07.03.21 at 18:56, Anna Christina Nass wrote to August Abolins:

    (Whereas NODELIST.### has [x] Update as diff)

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?

    I don't know how it is called in the english version,

    "Use internal nodelist processor" which I somehow get the feeling is incorrect because .....

    but in the german version it is called "Update als Diff einbinden"

    ..... literally translated that means "Include update as diff" which
    doesn't actually make sense(to me) in this context.

    and it is the first of the two checkbox options below "process by".
    Have a look at the help text, maybe this makes it clearer?

    The English help text doesn't make it any clearer, in fact, it clouds the issue even further <sigh>.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Monday, March 08, 2021 11:04:00
    Hello August!

    *** Sunday 07.03.21 at 13:47, August Abolins wrote to Anna Christina Nass:

    [snip]
    ..It *does* look like you may have discovered a bug.

    Okay. Who should I report it to?

    The official destination is XPOINT echo

    Errrrrrrm, did I miss something ???????

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Monday, March 08, 2021 12:32:00
    Am 07.03.21 schrieb August Abolins@1:396/45.29 in POINTS:

    Hallo August,

    My table now looks like this:

    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Z2PNT.### 064 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
    ³ NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    ³ FSXNET.### 071 FSXNET.### FSXNET.Z## Nodelist
    ³ micronet.### 043 micronet.### micronet.z## Nodelist
    ³ scinet.### 008 SCINET.### SCINET.Z## Nodelist

    BUT.. I think I found a way to force the lowercase to be
    uppercase.

    ...and that is? :)

    The official destination is XPOINT echo which is the same as the
    google groups nntp group called de.comm.software.crosspoint,
    which I see that you already know about. ;) Address your
    message to Gunter.

    Okay, I will do that in the next days.
    Thank you!

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Monday, March 08, 2021 07:31:00
    Hello Martin Foster!

    ** On Monday 08.03.21 - 11:04, Martin Foster wrote to August Abolins:

    The official destination is XPOINT echo

    Errrrrrrm, did I miss something ???????

    YES! :D You didn't the part right after that! ;)


    "...which is the same as the google groups nntp group
    called de.comm.software.crosspoint"

    Good to see you pop in. I was beginning to kinda worry about
    you. Did you get my latest window shot of the now broken ice-
    shelf? Actually, there's another chunk sliding down but it's
    not as omminous.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Monday, March 08, 2021 07:32:00
    Hello Anna!

    ** On Monday 08.03.21 - 12:32, you wrote to me:

    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Z2PNT.### 064 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
    ³ NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    ³ FSXNET.### 071 FSXNET.### FSXNET.Z## Nodelist
    ³ micronet.### 043 micronet.### micronet.z## Nodelist
    ³ scinet.### 008 SCINET.### SCINET.Z## Nodelist

    BUT.. I think I found a way to force the lowercase to be
    uppercase.

    ...and that is? :)

    I have to wait until the next micronet nodelist arrives. If the
    update works, I'll report my kludge fix.


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Monday, March 08, 2021 07:32:00
    Hello Martin!

    ** On Monday 08.03.21 - 11:01, you wrote to Anna:

    "Use internal nodelist processor" which I somehow get the
    feeling is incorrect because .....

    but in the german version it is called "Update als Diff
    einbinden"

    ..... literally translated that means "Include update as
    diff" which doesn't actually make sense(to me) in this
    context.

    Something like these might be better:

    "Process DIFF files"
    "Process DIFF updates"
    "Enable DIFF processing"

    and it is the first of the two checkbox options below
    "process by". Have a look at the help text, maybe this
    makes it clearer?

    The English help text doesn't make it any clearer, in fact,
    it clouds the issue even further <sigh>.

    The English help is a bit closer because it says "...to process
    the diff update".

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Monday, March 08, 2021 13:53:00
    Am 08.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste
    ^^^^^^^^^ ^^^^^^^^^
    Did you know there's a weekly DIFF for the Z2 Pointlist:
    Z2PNT_D.### Z2PNT_D.Z##

    I guess there is, but it's also working this way :)

    The diffs are not that important today compared to 20 years ago when data transfer was slow and expensive.

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Monday, March 08, 2021 13:55:00
    Am 08.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?
    I don't know how it is called in the english version,
    "Use internal nodelist processor" which I somehow get the feeling is incorrect because .....

    but in the german version it is called "Update als Diff einbinden"

    ..... literally translated that means "Include update as diff" which doesn't actually make sense(to me) in this context.

    Yep :)

    The English help text doesn't make it any clearer, in fact, it clouds the issue even further <sigh>.

    I guess that would be another point for the next update, won't it?

    Maybe together with my uppercase/lowercase nodelist update problem? :)

    Thank you!

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Monday, March 08, 2021 13:58:00
    Am 08.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    The official destination is XPOINT echo
    Errrrrrrm, did I miss something ???????

    I guess this must be the usenet echo de.comm.software.crosspoint which is gated to his uplink?

    At least it is not included in the official FidoNet echolist, neither in
    the english list nor in the german one.

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Monday, March 08, 2021 08:10:00
    Hello Anna!

    ** On Monday 08.03.21 - 13:58, you wrote to Martin Foster:

    The official destination is XPOINT echo
    Errrrrrrm, did I miss something ???????

    I guess this must be the usenet echo
    de.comm.software.crosspoint which is gated to his uplink?

    At least it is not included in the official FidoNet
    echolist, neither in the english list nor in the german
    one.

    You can get it from 2:221/1 for sure.

    I have it coming in from both FTN-method and nntp-method, both
    with OXP!

    The echo availability matter is so scattered. It's sad.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Monday, March 08, 2021 08:22:00
    Hello Anna!

    Did you know there's a weekly DIFF for the Z2 Pointlist:
    Z2PNT_D.### Z2PNT_D.Z##

    I guess there is, but it's also working this way :)

    The diffs are not that important today compared to 20
    years ago when data transfer was slow and expensive.

    But.. its fun to have OXP do the magic and build the nodelist
    with the diffs! :D

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Monday, March 08, 2021 16:33:00
    Am 08.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    The diffs are not that important today compared to 20
    years ago when data transfer was slow and expensive.

    But.. its fun to have OXP do the magic and build the nodelist
    with the diffs! :D

    That's right and I will look into it :)
    I just need to subscribe to the correct fileecho...

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Martin Foster@2:310/31.3 to August Abolins on Tuesday, March 09, 2021 08:24:00
    Hello August!

    *** Sunday 07.03.21 at 11:18, August Abolins wrote to Anna Christina Nass:

    If I recall correctly, auto-updates only work when there are DIFFs.

    No, auto-updating as a diff is an option. For example, I
    also have the fsxNet nodelist auto-updated and there I
    don't get diffs.

    OH! I had understood from one of the OXP experts here

    Oh, I wonder who that was :-/

    that this part in the config:

    ÚÄ Configure Node/Pointlist ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
    ³ ³
    ³ List name FSXNET.### Number 360 ³
    ³ ³
    ³ Format of list Nodelist  ³
    ³ Zone/Address 21 ³
    ³ ³
    ³ Update file FSXNET_D.### <----- THIS field ³
    ³ Update archive FSXNET_D.Z## <----- THIS field ³
    ³ ³
    ³ Process by ³
    ³ ³
    ³ [x] Use internal nodelist processor ³
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    It would appear that whoever did the original translation of this got it
    all wrong and it's taken ~20 years for folks to notice it!

    I'll correct it for the next release but I'm struggling to find the right words. Perhaps "Update with diff" or "Use diff to update" or maybe
    something else?

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tuesday, March 09, 2021 08:34:00
    Hello Anna!

    *** Sunday 07.03.21 at 11:44, Anna Christina Nass wrote to August Abolins:

    But every time a new nodelist is sent, it only gets stored in
    ~/.openxp/files, but isn't imported.

    If I recall correctly, auto-updates only work when there are DIFFs.

    No, auto-updating as a diff is an option.
    For example, I also have the fsxNet nodelist auto-updated and there I don't get diffs.

    My "nodelist list" looks like this:

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodeliste
    FSXNET.### 071 FSXNET.### FSXNET.Z## Nodeliste
    tqwnet.### 057 TQWNET.### TQWNET.Z## Nodeliste

    Only the FidoNet NODELIST.### is in diff-form, all the other nodelists are full updates.
    And Z2PNT and FSXNET do work, only tqwnet.### does not work.

    The FSXNET entry is configured like this:

    Listenname FSXNET.### Nummer 071
    Listenformat Nodeliste
    Update-Datei FSXNET.###
    Update-Archiv FSXNET.Z##
    [ ] Update als Diff einbinden

    (Whereas NODELIST.### has [x] Update as diff)

    After carefully reading through this thread several times, I'm assuming
    that OpenXP is capable of updating a nodelist with the next *nodelist* in
    the sequence *providing* "Update als Diff einbinden" is disabled. Is my assumption correct?

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Tuesday, March 09, 2021 09:00:00
    Hello August!

    *** Monday 08.03.21 at 07:31, August Abolins wrote to Martin Foster:

    The official destination is XPOINT echo

    Errrrrrrm, did I miss something ???????

    YES! :D You didn't the part right after that! ;)

    "...which is the same as the google groups nntp group
    called de.comm.software.crosspoint"

    That newsgroup has been gated via the Usenet<->Fido gateway at 2:240/2188
    for more years than I care to remember :)

    Good to see you pop in.

    Been suffering from a bad case of the "Winter Blues" which resulted in a
    lack of motivation to do most anything :((

    I was beginning to kinda worry about you.

    Awwwww, how sweet :-)))

    Did you get my latest window shot of the now broken ice-shelf?
    Actually, there's another chunk sliding down but it's not as
    omminous.

    Yes, got it thanks, along with all the others.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Tuesday, March 09, 2021 09:09:00
    Hello August!

    *** Monday 08.03.21 at 07:32, August Abolins wrote to Martin Foster:

    "Use internal nodelist processor" which I somehow get the
    feeling is incorrect because .....

    but in the german version it is called "Update als Diff
    einbinden"

    ..... literally translated that means "Include update as
    diff" which doesn't actually make sense(to me) in this
    context.

    Something like these might be better:

    "Process DIFF files"
    "Process DIFF updates"
    "Enable DIFF processing"

    Hmmmm, dunno, this is a tricky one.

    and it is the first of the two checkbox options below
    "process by". Have a look at the help text, maybe this
    makes it clearer?

    The English help text doesn't make it any clearer, in fact,
    it clouds the issue even further <sigh>.

    The English help is a bit closer because it says "...to process
    the diff update".

    Yes but it says "OpenXP will call its own nodelist processor to process
    the diff update". Well yes, it will, but that doesn't describe the true purpose of this particular option.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tuesday, March 09, 2021 09:11:00
    Hello Anna!

    *** Monday 08.03.21 at 13:53, Anna Christina Nass wrote to Martin Foster:

    Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste
    ^^^^^^^^^ ^^^^^^^^^
    Did you know there's a weekly DIFF for the Z2 Pointlist:
    Z2PNT_D.### Z2PNT_D.Z##

    I guess there is, but it's also working this way :)

    OK, fine, just thought I'd mention it :)

    The diffs are not that important today compared to 20 years ago when
    data transfer was slow and expensive.

    Yes, that's true.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tuesday, March 09, 2021 09:13:00
    Hello Anna!

    *** Monday 08.03.21 at 13:55, Anna Christina Nass wrote to Martin Foster:

    But, I cannot find that setting to turn OFF the "Update as
    diff". Where is it?
    I don't know how it is called in the english version,
    "Use internal nodelist processor" which I somehow get the feeling is
    incorrect because .....

    but in the german version it is called "Update als Diff einbinden"

    ..... literally translated that means "Include update as diff" which
    doesn't actually make sense(to me) in this context.

    Yep :)

    The English help text doesn't make it any clearer, in fact, it clouds
    the issue even further <sigh>.

    I guess that would be another point for the next update, won't it?

    Yes, it would :)

    Maybe together with my uppercase/lowercase nodelist update problem? :)

    Yep.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tuesday, March 09, 2021 09:21:00
    Hello Anna!

    *** Monday 08.03.21 at 13:58, Anna Christina Nass wrote to Martin Foster:

    The official destination is XPOINT echo
    Errrrrrrm, did I miss something ???????

    I guess this must be the usenet echo de.comm.software.crosspoint which
    is gated to his uplink?

    Yes it is, see my earlier post about this :)

    At least it is not included in the official FidoNet echolist, neither in the english list nor in the german one.

    I can't speak for the German echolist but DE.COMM.SOFTWARE.CROSSPOINT(note UPPERCASE) is not listed in the English "elist" either and quite rightly
    so.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Tuesday, March 09, 2021 11:57:00
    Am 09.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    The English help text doesn't make it any clearer, in fact, it clouds MF>>> the issue even further <sigh>.
    I guess that would be another point for the next update, won't it?
    Yes, it would :)

    Maybe together with my uppercase/lowercase nodelist update problem? :)
    Yep.

    Thank you very much!

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Tuesday, March 09, 2021 12:00:00
    Am 09.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    ³ [x] Use internal nodelist processor ³
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    It would appear that whoever did the original translation of this got it all wrong and it's taken ~20 years for folks to notice it!

    I'll correct it for the next release but I'm struggling to find the right words. Perhaps "Update with diff" or "Use diff to update" or maybe something else?

    "Updatefile is a diff" would be a short description - and tells the most important thing that this switch selects (diff / no diff).

    And in the help file it could be made more clear that an internal
    processor merges the diff.

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Tuesday, March 09, 2021 07:57:00
    Hello Martin!

    ** On Tuesday 09.03.21 - 08:24, you wrote to me:

    No, auto-updating as a diff is an option. For example, I
    also have the fsxNet nodelist auto-updated and there I
    don't get diffs.

    OH! I had understood from one of the OXP experts here

    Oh, I wonder who that was :-/

    <LOL>

    ³ Process by ³
    ³ ³
    ³ [x] Use internal nodelist processor ³
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


    It would appear that whoever did the original translation
    of this got it all wrong and it's taken ~20 years for folks
    to notice it!

    Probably because very few English users were using OXP?
    Considering that Z2PNT is documents a large community of users,
    I would assume that point-use is still a very Euro-thing.


    I'll correct it for the next release but I'm struggling to
    find the right words. Perhaps "Update with diff" or "Use
    diff to update" or maybe something else?

    I would suggest one of my earlier suggestions, including this
    one:

    "Enable DIFF processing"


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Tuesday, March 09, 2021 08:01:00
    Hello Martin!

    ** On Tuesday 09.03.21 - 09:09, you wrote to me:

    Something like these might be better:

    "Process DIFF files"
    "Process DIFF updates"
    "Enable DIFF processing"

    Hmmmm, dunno, this is a tricky one.

    How so? That's exactly what that setting "enables". When the
    DIFF arives, OXP processes the DIFF.


    The English help is a bit closer because it says "...to
    process the diff update".

    Yes but it says "OpenXP will call its own nodelist
    processor to process the diff update". Well yes, it will,
    but that doesn't describe the true purpose of this
    particular option.

    Huh? Isn't the "true purpose" to tell OXP that it is OK to
    kickstart the nodelist updates when a new DIFF arrives?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Tuesday, March 09, 2021 08:09:00
    Hello Martin!

    ** On Tuesday 09.03.21 - 09:00, you wrote to me:

    "...which is the same as the google groups nntp group
    called de.comm.software.crosspoint"

    That newsgroup has been gated via the Usenet<->Fido gateway
    at 2:240/2188 for more years than I care to remember :)

    What is the FTN group called over there?

    This is one of the things about echomail that seems lacking..
    the use of echonames in a consistent manner, and/or an automated
    way to know which system carries what.

    Good to see you pop in.

    Been suffering from a bad case of the "Winter Blues"..

    (Reply forthcoming in netmail)

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@1:396/45.29 to Anna Christina Nass on Tuesday, March 09, 2021 20:13:00
    Hello Anna!

    ** On Monday 08.03.21 - 07:32, August Abolins wrote to Anna Christina Nass:

    BUT.. I think I found a way to force the lowercase to be
    uppercase.

    ...and that is? :)

    I have to wait until the next micronet nodelist arrives. If the
    update works, I'll report my kludge fix.


    The micronet.zip arrived:

    = 19:51:45 CONNECT
    19:51:46 OPT CRAM-MD5-e688113534e23d2fcc6454bd08c5c2ee
    19:51:46 SYS Alterant MailHub
    19:51:46 ZYZ Deon George
    19:51:46 LOC Parkdale, VIC AU
    19:51:46 NDL 115200,TCP,BINKP
    19:51:46 TIME Wed, 10 Mar 2021 11:51:45 +1100
    19:51:46 VER binkd/1.1a-111/Linux binkp/1.1
    19:51:47 TRF 0 66596
    19:51:47 OPT EXTCMD GZ BZ2
    19:51:47 secure
    * 19:51:47 Rcvd 480c3800.we0, 3465b
    * 19:51:47 Rcvd mininfo.zip, 20160b
    * 19:51:48 Rcvd 13cbzwt3.tic, 947b
    * 19:51:48 Rcvd micronet.zip, 9545b
    ^^^^^^^^^^^^

    ..but the nodelist update did NOT happen.

    Therefore, mostly likely there *is* a problem discerning
    lowercase filenames for the arrivals.


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Thursday, March 11, 2021 01:14:00
    Hello Anna!

    ** On Tuesday 09.03.21 - 11:57, Anna Christina Nass wrote to Martin Foster:

    Maybe together with my uppercase/lowercase nodelist update problem? :)
    Yep.

    Thank you very much!

    My nodelist config looks like this:

    NODELIST.### 064 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
    FSXNET.### 071 FSXNET.### FSXNET.Z## Nodelist
    MICRONET.### 064 MICRONET.### MICRONET.Z## Nodelist
    scinet.### 071 SCINET.### SCINET.Z## Nodelist


    The SCINET nodelist arrived:

    = 01:05:34 CONNECT
    01:05:34 OPT CRAM-MD5-02545922718bd6baa5792979d0c681ee
    01:05:34 SYS Northern Realms
    01:05:34 ZYZ Warpslide
    01:05:34 LOC Binbrook, Ontario, Canada
    01:05:34 NDL 115200,TCP,BINKP
    01:05:34 TIME Thu, 11 Mar 2021 01:05:33 -0500
    01:05:34 VER binkd/1.1a-112/Win32 binkp/1.1
    01:05:34 TRF 0 8394
    01:05:34 OPT EXTCMD GZ BZ2
    01:05:34 secure
    * 01:05:34 Rcvd SCINET.Z71, 6048b
    * 01:05:34 Rcvd AB06TQ00.TIC, 2346b
    = 01:05:34 hangup
    - 01:05:34 exiting

    But the lowercase "scinet.071" file inside the archive did not
    process.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Thursday, March 11, 2021 09:46:00
    Hello Anna!

    *** Tuesday 09.03.21 at 11:57, Anna Christina Nass wrote to Martin Foster:

    The English help text doesn't make it any clearer, in fact, it clouds
    the issue even further <sigh>.
    I guess that would be another point for the next update, won't it?
    Yes, it would :)

    Maybe together with my uppercase/lowercase nodelist update problem? :)
    Yep.

    Thank you very much!

    Just to clarify the situation, I can/will update the English help text but only Gunter can make any necessary code changes because I'm not a
    programmer. So, once we've figured this case sensitivity problem out, you will need to report our findings in the Usenet support newsgroup so that Gunter will see it.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Thursday, March 11, 2021 10:43:00
    Hello Anna!

    *** Saturday 06.03.21 at 13:50, Anna Christina Nass wrote to All:

    I might have found a little problem with automatic nodeilst imports.

    One of my "othernets", tqwNet, uses lowercase filenames for nodelists. So, the hatched file is called eg. "tqwnet.z64" and contains the file "tqwnet.064".

    If I add the entry in FidoNet > Nodelisten > Verwaltung with TQWNET.### and TQWNET.Z##, the entry is added and the current suffix (057 when i added it) is displayed in the list.

    But every time a new nodelist is sent, it only gets stored in ~/.openxp/files, but isn't imported.

    What happens if you manually extract "tqwnet.064" from the archive, rename
    it to "TQWNET.064", repack it as "TQWNET.Z64" and then try a manual
    nodelist update by going to Fido -> Nodelisten -> Update einbinden and navigating your way to TQWNET.Z64

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Thursday, March 11, 2021 10:51:00
    Hello Anna!

    *** Tuesday 09.03.21 at 12:00, Anna Christina Nass wrote to Martin Foster:

    ³ [x] Use internal nodelist processor ³
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    It would appear that whoever did the original translation of this got it
    all wrong and it's taken ~20 years for folks to notice it!

    I'll correct it for the next release but I'm struggling to find the
    right words. Perhaps "Update with diff" or "Use diff to update" or maybe
    something else?

    "Updatefile is a diff" would be a short description - and tells the most important thing that this switch selects (diff / no diff).

    Yes, that's a good possibility :)

    And in the help file it could be made more clear that an internal processor merges the diff.

    So, with the option enabled, the internal nodelist processor merges the
    diff with the existing nodelist, whereas with the option disabled, the existing nodelist is overwritten by the new full nodelist. Am I
    understanding this correctly?

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 11, 2021 10:53:00
    Hello August!

    *** Tuesday 09.03.21 at 07:57, August Abolins wrote to Martin Foster:

    [snip]
    I'll correct it for the next release but I'm struggling to
    find the right words. Perhaps "Update with diff" or "Use
    diff to update" or maybe something else?

    I would suggest one of my earlier suggestions, including this
    one:

    "Enable DIFF processing"

    OK, I'm still thinking about this as I don't seem to be able to get my
    brain into gear just now :-/

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 11, 2021 11:10:00
    Hello August!

    *** Tuesday 09.03.21 at 08:01, August Abolins wrote to Martin Foster:

    [snip]
    The English help is a bit closer because it says "...to
    process the diff update".

    Yes but it says "OpenXP will call its own nodelist
    processor to process the diff update". Well yes, it will,
    but that doesn't describe the true purpose of this
    particular option.

    Huh? Isn't the "true purpose" to tell OXP that it is OK to
    kickstart the nodelist updates when a new DIFF arrives?

    Ahbut that's only half the story, it says nothing about the hitherto
    unknown fact that a nodelist can be updated(overwritten) with a new full nodelist. The way I see it is that the true purpose is that a nodelist can
    be updated either by using a diff or by using a full nodelist, depending
    on whether the switch is on or off.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 11, 2021 11:12:00
    Hello August!

    *** Tuesday 09.03.21 at 08:09, August Abolins wrote to Martin Foster:

    "...which is the same as the google groups nntp group
    called de.comm.software.crosspoint"

    That newsgroup has been gated via the Usenet<->Fido gateway
    at 2:240/2188 for more years than I care to remember :)

    What is the FTN group called over there?

    Same as the Usenet newsgroup but in UPPERCASE.

    [snip]
    Good to see you pop in.

    Been suffering from a bad case of the "Winter Blues"..

    (Reply forthcoming in netmail)

    Got it thanks and will reply in due course :)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Thursday, March 11, 2021 07:10:00
    Hello Martin!

    ** On Thursday 11.03.21 - 11:10, you wrote to me:

    Huh? Isn't the "true purpose" to tell OXP that it is OK
    to kickstart the nodelist updates when a new DIFF arrives?

    Ahbut that's only half the story, it says nothing about the
    hitherto unknown fact that a nodelist can be
    updated(overwritten) with a new full nodelist. The way I
    see it is that the true purpose is that a nodelist can be
    updated either by using a diff or by using a full nodelist,
    depending on whether the switch is on or off.

    AH! I like *that* explanation. Put *that* in the Helps. ;)

    I had no idea that oxp could utilize incoming "full" nodelists
    and update the config that way. I thought the updates only
    pertained to diffs if/when they arrived. And otherwise if the
    diff setting was disabled, I thought that NOTHING would happen
    with the incoming files - and require manual processing.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Thursday, March 11, 2021 12:19:00
    Hello Anna!

    *** Thursday 11.03.21 at 10:51, Martin Foster wrote to Anna Christina Nass:

    ³ [x] Use internal nodelist processor ³
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    It would appear that whoever did the original translation of this got
    it all wrong and it's taken ~20 years for folks to notice it!

    I'll correct it for the next release but I'm struggling to find the
    right words. Perhaps "Update with diff" or "Use diff to update" or
    maybe something else?

    "Updatefile is a diff" would be a short description - and tells the
    most important thing that this switch selects (diff / no diff).

    Yes, that's a good possibility :)

    And in the help file it could be made more clear that an internal
    processor merges the diff.

    So, with the option enabled, the internal nodelist processor merges the diff with the existing nodelist, whereas with the option disabled, the existing nodelist is overwritten by the new full nodelist. Am I understanding this correctly?

    I've just come across this in fido.txt(sec 3.1) .....

    ---------- 8< ----------
    Grundsätzlich gibt es zwei mögliche Formen von Node- und Pointlisten-Updates: Komplettupdates, bei denen die alte Liste durch
    eine neue ersetzt wird, oder Diff-Updates, bei denen aus der alten
    Liste und einer Differenzdatei die neue Liste erzeugt wird. Um
    welche Art von Update es sich jeweils handelt, teilen Sie XP in der Nodelisten-Konfiguration (/Fido/Nodelisten/Verwalten, Option "Edit")
    mit dem Schalter "Update als Diff einbinden" mit. Bei den Updates
    zur Haupt-Nodeliste und zur Region-24-Pointliste handelt es sich
    immer um Diff-Dateien.
    ---------- 8< ----------

    With the aid of Goggle Translate and my own limited knowledge of German,
    I've come up with the following translation .....

    ---------- 8< ----------
    There are basically two possible forms of Node and Point list
    updates: Complete updates in which the old list is replaced with a
    new one, or diff updates where a new list is generated by merging a
    difference file into the old list. Depending on what kind of update
    it is, this can be configured in Fido -> Nodelists -> Config -> Edit
    by use of the "Include update as diff" button. The main nodelist and
    the Region 24 pointlist always use diff files.
    ---------- 8< ----------

    So, the information was there all the time.
    Please feel free to correct my translation if necessary :-))

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Thursday, March 11, 2021 09:13:00
    Hello Martin!

    I've just come across this in fido.txt(sec 3.1) .....

    With the aid of Goggle Translate and my own limited
    knowledge of German, I've come up with the following
    translation .....

    ---------- 8< ----------
    There are basically two possible forms of Node and Point list updates: Complete updates in which the old list is replaced with a
    new one, or diff updates where a new list is generated by merging a difference file into the old list. Depending on what kind of update
    it is, this can be configured in Fido -> Nodelists -> Config -> Edit
    by use of the "Include update as diff" button. The main nodelist and
    the Region 24 pointlist always use diff files.
    ---------- 8< ----------

    So, the information was there all the time.
    Please feel free to correct my translation if necessary :-))

    What and where is fido.txt?

    Anyway.. the news is exciting. Remember the issues I was
    reporting regarding nodelist updating? Originally, my problem
    was the matching of the right Zone-version of the nodelist with
    the DIFFs. But I had a "feeling" that I ought to be able to
    just get OpenXp to do a direct replacement of the whole thing
    (without the diff processing) I mean.. it just seemed silly NOT
    to be able to do that!

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Thursday, March 11, 2021 15:05:00
    Am 11.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    Just to clarify the situation, I can/will update the English help text but only Gunter can make any necessary code changes because I'm not a programmer. So, once we've figured this case sensitivity problem out, you will need to report our findings in the Usenet support newsgroup so that Gunter will see it.

    Okay, I will do that.

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Thursday, March 11, 2021 15:09:00
    Am 11.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    What happens if you manually extract "tqwnet.064" from the archive, rename it to "TQWNET.064", repack it as "TQWNET.Z64" and then try a manual nodelist update by going to Fido -> Nodelisten -> Update einbinden and navigating your way to TQWNET.Z64

    I tried it with "tqwnet.z64", without any change, there it does not work.
    But when using TQWNET.Z71, which included TQWNET.071 (that I renamed as suggested) it did work and now it shows day 071 in Fido > Nodelisten > Verwalten.

    Regards,
    Anna


    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Thursday, March 11, 2021 15:10:00
    Am 11.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    So, with the option enabled, the internal nodelist processor merges the diff with the existing nodelist, whereas with the option disabled, the existing nodelist is overwritten by the new full nodelist. Am I understanding this correctly?

    That's at least what I'm understanding, yes.
    I just don't know what will happen if the new file is a diff and the
    checkbox is not ticked :)

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Thursday, March 11, 2021 15:50:00
    Am 11.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    What and where is fido.txt?

    The FidoNet documentation file of OpenXP :)
    You can find it in /usr/local/lib/openxp/doc

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Thursday, March 11, 2021 10:25:00
    Hello Anna!

    The FidoNet documentation file of OpenXP :)
    You can find it in /usr/local/lib/openxp/doc

    Oh THAT! It's in a different location on my Windows version,
    but I know that one. I never thought of bothering to translate
    that.

    Perhaps there should be a fido-eng.txt version of that with the kit/distribution.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Friday, March 12, 2021 09:09:00
    Hello August!

    *** Thursday 11.03.21 at 07:10, August Abolins wrote to Martin Foster:

    Huh? Isn't the "true purpose" to tell OXP that it is OK
    to kickstart the nodelist updates when a new DIFF arrives?

    Ahbut that's only half the story, it says nothing about the
    hitherto unknown fact that a nodelist can be
    updated(overwritten) with a new full nodelist. The way I
    see it is that the true purpose is that a nodelist can be
    updated either by using a diff or by using a full nodelist,
    depending on whether the switch is on or off.

    AH! I like *that* explanation. Put *that* in the Helps. ;)

    Hopefully, I'll be tackling this later today :)

    I had no idea that oxp could utilize incoming "full" nodelists and
    update the config that way.

    Neither had I and we have Anna to thank for pointing this out.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Friday, March 12, 2021 09:25:00
    Hello August!

    *** Thursday 11.03.21 at 09:13, August Abolins wrote to Martin Foster:

    I've just come across this in fido.txt(sec 3.1) .....

    With the aid of Goggle Translate and my own limited
    knowledge of German, I've come up with the following
    translation .....

    ---------- 8< ----------
    There are basically two possible forms of Node and Point list
    updates: Complete updates in which the old list is replaced with a
    new one, or diff updates where a new list is generated by merging a
    difference file into the old list. Depending on what kind of update
    it is, this can be configured in Fido -> Nodelists -> Config -> Edit
    by use of the "Include update as diff" button. The main nodelist and
    the Region 24 pointlist always use diff files.
    ---------- 8< ----------

    So, the information was there all the time.
    Please feel free to correct my translation if necessary :-))

    What and where is fido.txt?

    It's the German documentation for the Fido Point system and it's in the
    "doc" directory.

    Anyway.. the news is exciting.

    Yes, it's what I would call a little gem :)

    Remember the issues I was reporting regarding nodelist updating?

    Will I ever forget =8}

    Originally, my problem was the matching of the right Zone-version of
    the nodelist with the DIFFs.

    Yes.

    But I had a "feeling" that I ought to be able to just get OpenXp to
    do a direct replacement of the whole thing (without the diff
    processing) I mean.. it just seemed silly NOT to be able to do that!

    Yep, agreed.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 09:26:00
    Hello Anna!

    *** Thursday 11.03.21 at 15:05, Anna Christina Nass wrote to Martin Foster:

    Just to clarify the situation, I can/will update the English help text
    but only Gunter can make any necessary code changes because I'm not a
    programmer. So, once we've figured this case sensitivity problem out,
    you will need to report our findings in the Usenet support newsgroup so
    that Gunter will see it.

    Okay, I will do that.

    Seen it and thanks for posting the report.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 09:27:00
    Hello Anna!

    *** Thursday 11.03.21 at 15:09, Anna Christina Nass wrote to Martin Foster:

    What happens if you manually extract "tqwnet.064" from the archive,
    rename it to "TQWNET.064", repack it as "TQWNET.Z64" and then try a
    manual nodelist update by going to Fido -> Nodelisten -> Update
    einbinden and navigating your way to TQWNET.Z64

    I tried it with "tqwnet.z64", without any change, there it does not
    work. But when using TQWNET.Z71, which included TQWNET.071 (that I renamed as suggested) it did work and now it shows day 071 in Fido > Nodelisten > Verwalten.

    Ah, so that proves it *is* a case sensitivity issue.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 09:28:00
    Hello Anna!

    *** Thursday 11.03.21 at 15:10, Anna Christina Nass wrote to Martin Foster:

    So, with the option enabled, the internal nodelist processor merges the
    diff with the existing nodelist, whereas with the option disabled, the
    existing nodelist is overwritten by the new full nodelist. Am I
    understanding this correctly?

    That's at least what I'm understanding, yes.

    OK, thanks for that.

    I just don't know what will happen if the new file is a diff and the checkbox is not ticked :)

    There's one way to find out :)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 09:30:00
    Hello Anna!

    *** Thursday 11.03.21 at 15:50, Anna Christina Nass wrote to August Abolins:

    What and where is fido.txt?

    The FidoNet documentation file of OpenXP :)
    You can find it in /usr/local/lib/openxp/doc

    Yes, that's where it is in the Linux version and it can be found in the
    "doc" directory in the Windows version.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Friday, March 12, 2021 09:33:00
    Hello August!

    *** Thursday 11.03.21 at 10:25, August Abolins wrote to Anna Christina Nass:

    The FidoNet documentation file of OpenXP :)
    You can find it in /usr/local/lib/openxp/doc

    Oh THAT! It's in a different location on my Windows version,
    but I know that one. I never thought of bothering to translate
    that.

    Perhaps there should be a fido-eng.txt version of that with the kit/distribution.

    Yes, there most definitely should be an English version BUT who's going to
    do the translation :-?

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 11:47:00
    Hello Anna!

    *** Thursday 11.03.21 at 09:46, Martin Foster wrote to Anna Christina Nass:

    [snip]
    Just to clarify the situation, I can/will update the English help text

    Done for the next release.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Friday, March 12, 2021 11:50:00
    Hello Anna!

    *** Tuesday 09.03.21 at 12:00, Anna Christina Nass wrote to Martin Foster:

    [snip]
    I'll correct it for the next release but I'm struggling to find the
    right words. Perhaps "Update with diff" or "Use diff to update" or maybe
    something else?

    "Updatefile is a diff" would be a short description - and tells the most important thing that this switch selects (diff / no diff).

    Corrected for the next release.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Friday, March 12, 2021 08:06:00
    Hello Martin!

    Perhaps there should be a fido-eng.txt version of that
    with the kit/distribution.

    Yes, there most definitely should be an English version BUT
    who's going to do the translation :-?

    Google translate! :D It's better than nothing.

    Too bad it has a char limit each time. But maybe the task can be
    split between 3 or more people here doing responsible for
    different sections?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Friday, March 12, 2021 11:55:00
    Am 12.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    Just to clarify the situation, I can/will update the English help text MF>>> but only Gunter can make any necessary code changes because I'm not a MF>>> programmer. So, once we've figured this case sensitivity problem out, MF>>> you will need to report our findings in the Usenet support newsgroup so MF>>> that Gunter will see it.
    Okay, I will do that.
    Seen it and thanks for posting the report.

    I'm happy that I could help :)

    I already liked the original XP back in the late 90s, when I had the registered version for my FidoNet point running on DOS and OS/2 and it's great that it is still around and even available for Linux :)

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Friday, March 12, 2021 17:44:00
    Hello Martin!

    ** On Thursday 11.03.21 - 10:43, Martin wrote to Anna:

    What happens if you manually extract "tqwnet.064" from the
    archive, rename it to "TQWNET.064", repack it as
    "TQWNET.Z64" and then try a manual nodelist update by going
    to Fido -> Nodelisten -> Update einbinden and navigating
    your way to TQWNET.Z64

    I just tried this with renaming micronet.zip, renamed it to
    MICRONET.Z71, and renamed the micronet.071 file inside to
    MICRONET.071, performed the Fido/Nodelist/Update.. navigated to
    MICRONET.Z71 and it worked.

    But does the archived file need to be uppercase ..or just the
    file inside the archive?


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 14, 2021 08:32:00
    Hello August!

    *** Friday 12.03.21 at 08:06, August Abolins wrote to Martin Foster:

    Perhaps there should be a fido-eng.txt version of that
    with the kit/distribution.

    Yes, there most definitely should be an English version BUT
    who's going to do the translation :-?

    Google translate!

    Just for a laugh, I fed it with a 7 line paragraph and it spewed out what
    I can only describe as a dog's dinner :(

    :D It's better than nothing.

    Many many many years ago, I had some translation software but it got
    "lost" somewhere. I don't remember the name of it but I do recall it did a reasonable job and it also had the power to learn.

    Too bad it has a char limit each time. But maybe the task can be
    split between 3 or more people here doing responsible for
    different sections?

    Nice idea, are you volunteering :-))

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Sunday, March 14, 2021 08:44:00
    Hello Anna!

    *** Friday 12.03.21 at 11:55, Anna Christina Nass wrote to Martin Foster:

    Just to clarify the situation, I can/will update the English help text
    but only Gunter can make any necessary code changes because I'm not a
    programmer. So, once we've figured this case sensitivity problem out,
    you will need to report our findings in the Usenet support newsgroup
    so that Gunter will see it.
    Okay, I will do that.
    Seen it and thanks for posting the report.

    I'm happy that I could help :)

    I already liked the original XP back in the late 90s,

    I first came across it in 1994 when I was a Node and was immediately
    hooked on it, even though it was in German only.

    when I had the registered version

    I also registered it and I still have my licence key :)

    for my FidoNet point running on DOS and OS/2

    Yep, same here apart from I was running it in SysOp Mode which allowed me
    to use my Node number instead of a Point number.

    and it's great that it is still around and even available for Linux
    :)

    Yes and it would be even better if there was an OS/2 version but unfortunately, that's unlikely to happen.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 14, 2021 08:48:00
    Hello August!

    *** Friday 12.03.21 at 17:44, August Abolins wrote to Martin Foster:

    What happens if you manually extract "tqwnet.064" from the
    archive, rename it to "TQWNET.064", repack it as
    "TQWNET.Z64" and then try a manual nodelist update by going
    to Fido -> Nodelisten -> Update einbinden and navigating
    your way to TQWNET.Z64

    I just tried this with renaming micronet.zip, renamed it to
    MICRONET.Z71, and renamed the micronet.071 file inside to
    MICRONET.071, performed the Fido/Nodelist/Update.. navigated to MICRONET.Z71 and it worked.

    Excellent!

    But does the archived file need to be uppercase ..or just the
    file inside the archive?

    As I don't have any "othernet" nodelists to play about with, I'm sorry but
    I don't know.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Sunday, March 14, 2021 12:12:00
    Am 14.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    I already liked the original XP back in the late 90s,
    I first came across it in 1994 when I was a Node and was immediately
    hooked on it, even though it was in German only.

    :)

    when I had the registered version
    I also registered it and I still have my licence key :)

    I think mine is printed on a paper somewhere... :)

    and it's great that it is still around and even available for Linux
    :)

    Yes and it would be even better if there was an OS/2 version but unfortunately, that's unlikely to happen.

    Isn't one of the other XPs (FreeXP, XP/2 ?) available for OS/2?

    I have an old Pentium 233 here where I want to rebuild an old OS/2 system like mine was ~20 years ago :)

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Sunday, March 14, 2021 08:56:00
    Hello Martin!

    ** On Sunday 14.03.21 - 08:44, you wrote to Anna Christina Nass:

    for my FidoNet point running on DOS and OS/2

    Yep, same here apart from I was running it in SysOp Mode
    which allowed me to use my Node number instead of a Point
    number.

    I was wondering about that and thought what good is sysop mode
    if it only works with files locally and not publically.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Tuesday, March 16, 2021 09:11:00
    Hello Anna!

    *** Sunday 14.03.21 at 12:12, Anna Christina Nass wrote to Martin Foster:

    [snip]
    Yes and it would be even better if there was an OS/2 version but
    unfortunately, that's unlikely to happen.

    Isn't one of the other XPs (FreeXP, XP/2 ?) available for OS/2?

    Not that I'm aware of but I have a slight recollection of the XPý
    developers saying that they were considering an OS/2 version but I don't recall it ever happening.

    I have an old Pentium 233 here where I want to rebuild an old OS/2
    system like mine was ~20 years ago :)

    Nice :)

    Have you looked at ArcaOS?

    BTW ..... I crashed a netmail to you this morning, have you seen it?

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Tuesday, March 16, 2021 09:22:00
    Hello August!

    *** Sunday 14.03.21 at 08:56, August Abolins wrote to Martin Foster:

    for my FidoNet point running on DOS and OS/2

    Yep, same here apart from I was running it in SysOp Mode
    which allowed me to use my Node number instead of a Point
    number.

    I was wondering about that and thought what good is sysop mode
    if it only works with files locally and not publically.

    Ah well, there ya go :)

    The way it works is, that instead of polling the BossNode for mail, OpenXP creates a mail packet/bundle in whatever directory has been assigned as
    the "outbound". It's then up to the Node to transfer the mail packet/
    bundle to their secure inbound in their mailer setup and then run their tosser to pack mail for uplinks/downlinks.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Tuesday, March 16, 2021 12:03:00
    Am 16.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    Isn't one of the other XPs (FreeXP, XP/2 ?) available for OS/2?
    Not that I'm aware of but I have a slight recollection of the XPý developers saying that they were considering an OS/2 version but I don't recall it ever happening.

    Ah okay. I just thought that I've read something like that.

    I have an old Pentium 233 here where I want to rebuild an old OS/2
    system like mine was ~20 years ago :)
    Nice :)
    Have you looked at ArcaOS?

    Not in detail, as it is a commercial program and I hesitate to invest that much money in this project.
    And I still have original OS/2 versions (2, 3, 4) here that work "good enough" for that :)

    BTW ..... I crashed a netmail to you this morning, have you seen it?

    As it arrived in my BBS and not at my point - I've just read (and
    answered) it :)

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Tuesday, March 16, 2021 09:21:00
    Hello Martin!

    ** On Tuesday 16.03.21 - 09:22, Martin wrote to August:

    The way it works is, that instead of polling the BossNode
    for mail, OpenXP creates a mail packet/bundle in whatever
    directory has been assigned as the "outbound". It's then up
    to the Node to transfer the mail packet/ bundle to their
    secure inbound in their mailer setup and then run their
    tosser to pack mail for uplinks/downlinks.

    I suppose that might have been practical when binkd wasn't a
    built-in feature of the program?

    Even so, it's almost a shame that oxp can't be configured to
    operate as a standalone "sysop/nodelisted" node. All the
    capability is there.
    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Tuesday, March 16, 2021 18:15:00
    Hello Martin!

    ** On Sunday 14.03.21 - 08:32, you wrote to me:

    Many many many years ago, I had some translation software
    but it got "lost" somewhere. I don't remember the name of
    it but I do recall it did a reasonable job and it also had
    the power to learn.

    I think Grammarly works the same way. It "learns" (or rather,
    retains) the corrections you make and then remembers them the
    next time a word or set of words are used in context.

    I found another online translator. Here is the TOC using DeepL:

    I Basics

    1.1 FidoNet - structure and addressing
    1.2 Point in FidoNet
    1.3 The nodelist(s)


    II Installation and operation

    2.1 Installation and configuration
    2.2 Network call
    2.3 Ordering and managing areas (boards, echoes)
    2.4 Board groups: Umlauts, Origins, Re^n and size limit
    2.5 Writing and polling under different AKAs
    2.6 Sending and receiving files
    2.7 Addressing Internet gateways
    2.8 Sysop mode (diskpoll)


    III Node lists

    3.1 Managing node and point lists
    3.2 Crash mails
    3.3 File Requests
    3.4 Call charge counter for crashes and requests
    3.5 Crash/Request by Timing List and AutoSend


    IV Technical Documentation

    4.1 The NDIFF node list editor
    4.2 The message converter ZFIDO
    4.3 The call log file XPFIDO.LOG
    4.4 The Fido mailer XP-FM
    4.5 The yuppie converter YUP2PKT


    Appendix

    A. Files in the CrossPoint/Fido package
    B XP-ToolNET
    C. Glossary
    D. Known problems
    E. CrossPoint/Fido - Version History

    "Translated with www.DeepL.com/Translator (free version)"

    Do you see anything amiss above?

    DeepL will allow 5000 chars per translation.


    Nice idea, are you volunteering :-))

    I would suggest that we can split the effort between several of
    us OpenXP users, post the translation results in the XPOINT echo
    and tweek where necessary to produce the final result.

    The fido.txt file is about 133,400 chars. That would be about 27
    chunks of txt (or visits) to DeepL at a time. We could assign
    three people to do 10 x 5000 char chunks at a time.

    We could assign a couple of weeks to critique the translation
    result for each section.

    Many hands make light work! ;)

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to Anna Christina Nass on Thursday, March 18, 2021 11:18:00
    Hello Anna!

    *** Tuesday 16.03.21 at 12:03, Anna Christina Nass wrote to Martin Foster:

    [snip]
    Have you looked at ArcaOS?

    Not in detail, as it is a commercial program and I hesitate to invest that much money in this project.

    Very wise choice because I bought a licence 3 years ago which turned out
    to be a HUGE mistake. After messing around with the simplest of things for many weeks and getting virtually nowhere, I came to the conclusion that
    I'd paid them for the privelege of being an alpha tester!! Quite simply
    put, it wasn't fit for purpose.

    With the help of their support guys, it took ~10 days to get it to
    actually boot. USB support was terrible. DOS-OS/2 sessions didn't work. Win-OS/2 sessions didn't work. The included version of Firefox was ancient and took forever to load. Those are just some of the things that spring to mind off the top of my head. My licence has long since expired and I've
    not read anything anywhere that makes me want to rush out and buy another licence.

    And I still have original OS/2 versions (2, 3, 4) here that work "good enough" for that :)

    I had Warp3 but it went in the bin long ago(13 floppies!) =8)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 18, 2021 11:21:00
    Hello August!

    *** Tuesday 16.03.21 at 09:21, August Abolins wrote to Martin Foster:

    The way it works is, that instead of polling the BossNode
    for mail, OpenXP creates a mail packet/bundle in whatever
    directory has been assigned as the "outbound". It's then up
    to the Node to transfer the mail packet/ bundle to their
    secure inbound in their mailer setup and then run their
    tosser to pack mail for uplinks/downlinks.

    I suppose that might have been practical when binkd wasn't a
    built-in feature of the program?

    Not really because the whole idea of SysOp Mode is to allow a Node to use OpenXP as a message reader/editor AND to use their Node address instead of the more usual Point address.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 18, 2021 11:44:00
    Hello August!

    *** Tuesday 16.03.21 at 18:15, August Abolins wrote to Martin Foster:

    Many many many years ago, I had some translation software
    but it got "lost" somewhere. I don't remember the name of
    it but I do recall it did a reasonable job and it also had
    the power to learn.

    I think Grammarly works the same way. It "learns" (or rather,
    retains) the corrections you make and then remembers them the
    next time a word or set of words are used in context.

    I found another online translator. Here is the TOC using DeepL:

    I Basics

    1.1 FidoNet - structure and addressing
    1.2 Point in FidoNet
    1.3 The nodelist(s)


    II Installation and operation

    2.1 Installation and configuration
    2.2 Network call
    2.3 Ordering and managing areas (boards, echoes)
    2.4 Board groups: Umlauts, Origins, Re^n and size limit
    2.5 Writing and polling under different AKAs
    2.6 Sending and receiving files
    2.7 Addressing Internet gateways
    2.8 Sysop mode (diskpoll)


    III Node lists

    3.1 Managing node and point lists
    3.2 Crash mails
    3.3 File Requests
    3.4 Call charge counter for crashes and requests
    3.5 Crash/Request by Timing List and AutoSend


    IV Technical Documentation

    4.1 The NDIFF node list editor
    4.2 The message converter ZFIDO
    4.3 The call log file XPFIDO.LOG
    4.4 The Fido mailer XP-FM
    4.5 The yuppie converter YUP2PKT


    Appendix

    A. Files in the CrossPoint/Fido package
    B XP-ToolNET
    C. Glossary
    D. Known problems
    E. CrossPoint/Fido - Version History

    "Translated with www.DeepL.com/Translator (free version)"

    Do you see anything amiss above?

    Nope, that's an excellent job. Is that exactly as it came out or did you
    do a bit of tickling up?

    I'm asking because I tried it out with a short paragraph and it came out looking like a dog's dinner.

    DeepL will allow 5000 chars per translation.

    Nice idea, are you volunteering :-))

    I would suggest that we can split the effort between several of
    us OpenXP users, post the translation results in the XPOINT echo
    and tweek where necessary to produce the final result.

    I would NOT advise using the XPOINT echo for that purpose as it's actually
    a gated *German* newsgroup. Some sort of versioning system, such as git or svn, would be a far better way of handling it IMO.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Thursday, March 18, 2021 08:41:00
    Hello Martin!

    ** On Thursday 18.03.21 - 11:44, you wrote to me:

    I found another online translator. Here is the TOC using DeepL:

    I Basics

    1.1 FidoNet - structure and addressing
    1.2 Point in FidoNet
    1.3 The nodelist(s)

    [...]

    "Translated with www.DeepL.com/Translator (free version)"
    Do you see anything amiss above?

    Nope, that's an excellent job. Is that exactly as it came
    out or did you do a bit of tickling up?

    That's the exact result, with indenting. Mind you, since the
    original had indenting and added spacing, the proper spacing in
    the restul was noticeable after a cut'n'paste into Notpad or
    this wider editor space.

    I'm asking because I tried it out with a short paragraph
    and it came out looking like a dog's dinner.

    Was your test with DeepL?

    I would suggest that we can split the effort..

    I would NOT advise using the XPOINT echo for that purpose
    as it's actually a gated *German* newsgroup. Some sort of
    versioning system, such as git or svn, would be a far
    better way of handling it IMO.

    Yeh, I guess the "de." part in "de.comm.software.crosspoint"
    would be a clue. :/ But the rest of the name is english. I
    mean, it's not like it's "komm.software.kreuzungspunkt" :D

    Personaly, I like the idea of managing a translation discussion
    with OXP, the product underdiscussion itself. The built in
    search and threading would make it easy to follow a development.

    Someone posted a samples of usage of the ftsc documentation in
    git. https://github.com/zoomosis/ftsc There, it looks pretty straightforward to make editing changes right on the spot and
    watch the progress.

    I just learned about TortoiseSVN, since it support Windows. It
    looks like a fine tool for managing doc changes.

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Thursday, March 18, 2021 21:34:00
    Hello Martin!

    Not really because the whole idea of SysOp Mode is to allow
    a Node to use OpenXP as a message reader/editor AND to use
    their Node address instead of the more usual Point address.

    Calling it sysop mode seems like a degrade, when I would think
    that sysop mode would be something greater.

    So, sysop mode scales down the functionality of OpenXp to being
    just a reader/editor, while providing a full node (z:nnn.fff)
    identity.

    I was just thinking that if OpenXP can operate as a full node
    locally, then why not have the ability to operate that node live
    and connect with other nodes since it can do the connections and
    transfers as a point.


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Friday, March 19, 2021 09:31:00
    Am 18.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I was just thinking that if OpenXP can operate as a full node
    locally, then why not have the ability to operate that node live
    and connect with other nodes since it can do the connections and
    transfers as a point.

    I think this would imply that there is some kind of "binkd" running in the background to accept incoming connections while OpenXP is still running.
    That would need a new base for OXP because at the moment, it isn't a multithreading application :)

    So my guess would be that this could be accomlished by using another binkp daemon which could send/receive packages. OXP then uses the incoming/
    outgoing directories.

    Could that work?

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Martin Foster on Friday, March 19, 2021 10:06:00
    Hello Martin!

    ** On Sunday 14.03.21 - 08:48, you wrote to me:

    I just tried this with renaming micronet.zip, renamed it
    to MICRONET.Z71, and renamed the micronet.071 file inside
    to MICRONET.071, performed the Fido/Nodelist/Update..
    navigated to MICRONET.Z71 and it worked.

    Excellent!

    Yes and no. :(

    I just found out that micronet only delivers its weekly nodelist
    packed in micronet.zip.

    So.. I am hoping the following adjustment in NODELIST.CFG will
    work when .078 comes down the line:

    Listfile=MICRONET.###
    Number=78
    UpdateFile=micronet.###
    UpdateArchive=micronet.zip <=== all lowercase, too.

    The zip file is delivered in lowercase, and the .### file inside
    is lowercase too.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From August Abolins@1:396/45.29 to Martin Foster on Friday, March 19, 2021 17:59:00
    Hello Martin!

    So.. I am hoping the following adjustment in NODELIST.CFG will
    work when .078 comes down the line:

    Listfile=MICRONET.###
    Number=78
    UpdateFile=micronet.###
    UpdateArchive=micronet.zip <=== all lowercase, too.

    The zip file is delivered in lowercase, and the .### file inside
    is lowercase too.

    My bad.

    The nodelist arrived:

    = 08:18:06 CONNECT
    * 08:18:07 Rcvd c5140e87.pkt, 752b
    * 08:18:08 Rcvd 54235800.fr0, 15985b
    * 08:18:08 Rcvd mininfo.zip, 8444b
    * 08:18:08 Rcvd 13ct94r3.tic, 948b
    * 08:18:08 Rcvd micronet.zip, 8839b
    * 08:18:08 Rcvd 13ct94r7.tic, 942b
    = 08:18:09 hangup
    - 08:18:09 exiting

    ..but the above CFG settings failed. THEN, I noticed that the
    archive .zip is sent lowercase, and the nodelist inside is
    uppercase. So, the following adjustment:

    Listfile=MICRONET.###
    Number=78
    UpdateFile=MICRONET.### <==== changed to all UPPERCASE UpdateArchive=micronet.zip

    ..worked the next time I restarted OpenXP.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 21, 2021 09:12:00
    Hello August!

    *** Thursday 18.03.21 at 21:34, August Abolins wrote to Martin Foster:

    Not really because the whole idea of SysOp Mode is to allow
    a Node to use OpenXP as a message reader/editor AND to use
    their Node address instead of the more usual Point address.

    Calling it sysop mode seems like a degrade,

    ISTM more like an enhancement :)

    when I would think that sysop mode would be something greater.

    Such as?

    So, sysop mode scales down the functionality of OpenXp to being
    just a reader/editor, while providing a full node (z:nnn.fff)
    identity.

    I suppose it does but over the many years I used CrossPoint in SysOp Mode,
    I never perceived it as being "scaled down" and I certainly never thought
    of it as being just a reader/editor.

    I was just thinking that if OpenXP can operate as a full node
    locally, then why not have the ability to operate that node live
    and connect with other nodes since it can do the connections and
    transfers as a point.

    Yeah, that would be very nice and something which I often thought about in the past but methinks that's not going to happen.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 21, 2021 09:16:00
    Hello August!

    *** Friday 19.03.21 at 10:06, August Abolins wrote to Martin Foster:

    I just tried this with renaming micronet.zip, renamed it
    to MICRONET.Z71, and renamed the micronet.071 file inside
    to MICRONET.071, performed the Fido/Nodelist/Update..
    navigated to MICRONET.Z71 and it worked.

    Excellent!

    Yes and no. :(

    I just found out that micronet only delivers its weekly nodelist
    packed in micronet.zip.

    That sucks! :((

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 21, 2021 09:18:00
    Hello August!

    *** Friday 19.03.21 at 17:59, August Abolins wrote to Martin Foster:

    So.. I am hoping the following adjustment in NODELIST.CFG will
    work when .078 comes down the line:

    Listfile=MICRONET.###
    Number=78
    UpdateFile=micronet.###
    UpdateArchive=micronet.zip <=== all lowercase, too.

    The zip file is delivered in lowercase, and the .### file inside
    is lowercase too.

    My bad.

    The nodelist arrived:

    = 08:18:06 CONNECT
    * 08:18:07 Rcvd c5140e87.pkt, 752b
    * 08:18:08 Rcvd 54235800.fr0, 15985b
    * 08:18:08 Rcvd mininfo.zip, 8444b
    * 08:18:08 Rcvd 13ct94r3.tic, 948b
    * 08:18:08 Rcvd micronet.zip, 8839b
    * 08:18:08 Rcvd 13ct94r7.tic, 942b
    = 08:18:09 hangup
    - 08:18:09 exiting

    ..but the above CFG settings failed. THEN, I noticed that the
    archive .zip is sent lowercase, and the nodelist inside is
    uppercase.

    That also sucks! :((

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Sunday, March 21, 2021 09:22:00
    Hello August!

    *** Thursday 18.03.21 at 08:41, August Abolins wrote to Martin Foster:

    I found another online translator. Here is the TOC using DeepL:

    I Basics

    1.1 FidoNet - structure and addressing
    1.2 Point in FidoNet
    1.3 The nodelist(s)

    [...]

    "Translated with www.DeepL.com/Translator (free version)"
    Do you see anything amiss above?

    Nope, that's an excellent job. Is that exactly as it came
    out or did you do a bit of tickling up?

    That's the exact result, with indenting. Mind you, since the
    original had indenting and added spacing, the proper spacing in
    the restul was noticeable after a cut'n'paste into Notpad or
    this wider editor space.

    I'm asking because I tried it out with a short paragraph
    and it came out looking like a dog's dinner.

    Was your test with DeepL?

    Yes it was.

    [snip]
    I just learned about TortoiseSVN, since it support Windows. It
    looks like a fine tool for managing doc changes.

    Yes, it's an excellent piece of software and it's free :)

    There's also SmartSVN but it's commercial but once the 30-day trial period ends, it switches into "Lite" mode and can be used for as long as is required. Windows, Linux and macOS versions are available from .....

    https://www.smartsvn.com/

    I've used the Linux version for many years and have found that "Lite" mode more than meets my needs.

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?

    The master copy of the document would be held in the remote svn repository and all changes to the document would be done in the users' own local
    working copy of the document. All changes to the users' working copy of
    the document would then be commited by each user to the master copy in the remote svn repository. That's simplifying it a bit but you should get the jist of how it works :)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Sunday, March 21, 2021 10:03:00
    Hello Martin!

    ** On Sunday 21.03.21 - 09:22, you wrote to me:

    Was your test with DeepL?

    Yes it was.

    What paragraph did you test? Here is section I.0

    I Basics
    =======================================================


    Actually, CrossPoint was once conceived as a pure Z-net
    pointing software designed, and in fact it was supposed
    to remain that way. Well, as you you can see that it did
    not stay that way - since version a large number of
    different networks since version 2.0, and the Fido part
    takes the biggest space. This is mainly due to Burkard
    Schoof, who has constantly provided me with new ideas
    and comments on the Fido implementation.

    The FidoNet is the oldest and largest of all mailbox
    networks and can therefore be and can therefore offer
    the most special features. Because of the number of
    special Fido features, I have decided to decided to
    summarize all FidoNet related things in this text. in
    this text. It should and can replace the manual, but
    serves only as a supplement and a quick as a quick start
    guide for Fido. To understand the CrossPoint concept you
    should at least read the basic chapters of the manual.
    read.

    The Fido part of CrossPoint is covered by the same
    shareware license conditions as for the rest of the
    program. For more details can be found in LIZENZ.TXT.
    As for the manual also for this text, may be published
    in mailbox networks with reference to the source.
    mailbox networks.

    So, let's finally get to the main thing - the use of
    CrossPoint in FidoNet. If you already have experience
    with other Fido point software and have a profound
    knowledge of Fido technology, you can you can proceed
    directly with the installation in chapter 2.1. As a Fido
    new user you should at least briefly skim part 1 of this
    text, because I will assume you know the concepts and
    terms explained there. as known.

    In case of problems you can reach the team in the known
    support echoes (see manual, chapter 1.3).

    Peter Mandrella,
    September 1992 - September 1995
    (revised by the OpenXP team in March 2000)


    --4 PS: Fido and FidoNet are registered trademarks of Tom
    Jennings and Fido Software.

    --4 PPS: I would like to thank Burkard Schoof, Max Raabe and Michael
    Heydekamp for their valuable cooperation.


    I added my own wrapping to fit better in this echo.

    I don't see too many problems above at all. Minor clean up is
    to be expected.


    [snip]
    I just learned about TortoiseSVN, since it support
    Windows. It looks like a fine tool for managing doc
    changes.

    Yes, it's an excellent piece of software and it's free :)

    So.. if we were to engage in this project, we would need to
    settle on using the same svn program I suppose.


    https://www.smartsvn.com/

    I've used the Linux version for many years and have found
    that "Lite" mode more than meets my needs.

    I'm game to try that one since you're already using it.

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?

    The master copy of the document would be held in the remote
    svn repository and all changes to the document would be
    done in the users' own local working copy of the document.
    All changes to the users' working copy of the document
    would then be commited by each user to the master copy in
    the remote svn repository. That's simplifying it a bit but
    you should get the jist of how it works :)

    Oh.. and one person is designated as managing and releasing the
    final "master" copy?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to Martin Foster on Monday, March 22, 2021 10:53:00
    Am 18.03.21 schrieb Martin Foster@2:310/31.3 in POINTS:

    Hallo Martin,

    Have you looked at ArcaOS?
    Not in detail, as it is a commercial program and I hesitate to
    invest that much money in this project.

    Very wise choice because I bought a licence 3 years ago which turned
    out to be a HUGE mistake. After messing around with the simplest of
    things for many weeks and getting virtually nowhere, I came to the conclusion that I'd paid them for the privelege of being an alpha
    tester!! Quite simply put, it wasn't fit for purpose.
    [...]

    Okay, thank you for the warning.
    I really will stick to my original OS/2 versions :)

    And I still have original OS/2 versions (2, 3, 4) here that work "good ACN>> enough" for that :)

    I had Warp3 but it went in the bin long ago(13 floppies!) =8)

    I have a small collection:
    OS/2 1.3, 2.0, 2.1, 2.11 (all on Floppies)
    OS/2 Warp 3, Warp 3 Connect, Warp 4 (CDs)

    I bought them "used" some ~15 years ago :)

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Monday, March 22, 2021 09:56:00
    Hello Anna Christina Nass!

    ** On Monday 22.03.21 - 10:53, Anna Christina Nass wrote to Martin Foster:

    I had Warp3 but it went in the bin long ago(13 floppies!) =8)

    I have a small collection:
    OS/2 1.3, 2.0, 2.1, 2.11 (all on Floppies)
    OS/2 Warp 3, Warp 3 Connect, Warp 4 (CDs)

    I started with 2.0 (beta tester) ..free discs!

    But then I purchased 2.1 and went to 2.11 (yes.. floppies
    indeed!) Then, purchased Warp 3. I never reached the Connect
    version.

    Now, sadly, all that software and their respective media must go
    to the landfill.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Tuesday, March 23, 2021 10:06:00
    Am 22.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I started with 2.0 (beta tester) ..free discs!

    ;-)

    That reminds me that I bought the March '95 beta of Windows95 in a
    computer shop.
    It also came on (copied... so I don't know if it was legal at all)
    floppies.

    But then I purchased 2.1 and went to 2.11 (yes.. floppies
    indeed!) Then, purchased Warp 3. I never reached the Connect
    version.

    Now, sadly, all that software and their respective media must go
    to the landfill.

    Why is it a "must"?

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Tuesday, March 23, 2021 08:59:00
    Hello Anna!

    Now, sadly, all that software and their respective media must go
    to the landfill.

    Why is it a "must"?

    I don't see the point in listing all the retro stuff on ebay for
    example and hoping to sell. Listing, pricing, packaging
    requires a lot of extra time to manage and organize.

    I even have a copy of the book OS/2 2.1 Unleashed. I see a
    listing on ebay for $11 + $25 s/h. I have a sealed box of Lotus
    Smartsuite 1.1 for OS/2. OH so much more!

    At this point I think it would be better that if I touch any of
    that stuff again it would be for the last time - out the door -
    and be done with it. To sort it, price it, watch for bids and
    offers requires far too much time and extra organized space.

    What good is all that old stuff?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Tuesday, March 23, 2021 18:35:00
    Am 23.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I don't see the point in listing all the retro stuff on ebay for
    example and hoping to sell.
    [...]
    What good is all that old stuff?

    Well, that's an interesting question, especially in a FidoNet echo :)

    There are some people who would like to have some of the stuff that you mentioned (I, eg. would be interested in the SmartSuite, but preferably in German).

    If you don't want to invest much time and effort, why not just put the
    stuff in a box, make some photos and put it in a forum or an echo (like CLASSIC_COMPUTING) and say "for free, to pick up".

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Daniel Path@2:371/52 to Anna Christina Nass on Tuesday, March 23, 2021 19:21:12
    Hello Anna.

    23 Mar 21 18:35, you wrote to August Abolins:

    Am 23.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I don't see the point in listing all the retro stuff on ebay for
    example and hoping to sell.
    [...]
    What good is all that old stuff?

    Well, that's an interesting question, especially in a FidoNet echo :)

    :)) touche!

    There are some people who would like to have some of the stuff that
    you mentioned (I, eg. would be interested in the SmartSuite, but preferably in German).

    If you don't want to invest much time and effort, why not just put the stuff in a box, make some photos and put it in a forum or an echo
    (like CLASSIC_COMPUTING) and say "for free, to pick up".

    +1.

    --
    Daniel

    --- GoldED+/EMX 1.1.4.7
    * Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)
  • From August Abolins@2:221/1.58 to Anna Christina Nass on Tuesday, March 23, 2021 18:08:00
    Hello Anna!

    What good is all that old stuff?

    Well, that's an interesting question, especially in a
    FidoNet echo :)

    I am all FOR enjoying ftn tech on slightly newer machines. ;)
    There is no way that I would want to fire-up an old AT PC and do
    the same thing sitting in front of a CRT screen. As you know,
    fido echos can be admirably enjoyed with linux pcs too.

    Some fidonet echos are even accessible via the Telegram app for
    all platforms - platforms that did not exist back in the day.

    There are some people who would like to have some of the
    stuff that you mentioned (I, eg. would be interested in
    the SmartSuite, but preferably in German).

    Wouldn't there be an option in the menus to set the language of
    preference? WARNING: 12MB RAM minimum required! LOL

    https://susepaste.org/70764990

    If you don't want to invest much time and effort, why not
    just put the stuff in a box, make some photos and put it
    in a forum or an echo (like CLASSIC_COMPUTING) and say
    "for free, to pick up".

    I thought of that very thing. I already mentioned a handful of
    gear about a year ago in appropriate echos where some people
    were discussing parts would hang out. But no takers.

    Maybe it's worth repeating. Apparently fidonet has a cforsale
    echo too.

    Taking photos of the stuff is definitely a good idea.

    There is a local shop in town that operates as a donation-based
    thrift store and helps to raise funds for the local hospice. The
    shop has a man-cave area that is filled with tools and gear of
    all kinds. Not sure about computer parts and software.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Anna Christina Nass@2:240/5824.1 to August Abolins on Wednesday, March 24, 2021 11:21:00
    Am 23.03.21 schrieb August Abolins@2:221/1.58 in POINTS:

    Hallo August,

    I am all FOR enjoying ftn tech on slightly newer machines. ;)

    I'm also using my modern computers for BBSing, but in general Fido & Co.
    is a kind of retro technology, I guess.

    Some fidonet echos are even accessible via the Telegram app for
    all platforms - platforms that did not exist back in the day.

    Yeah, I'm not very happy about that, as Telegram has some kind of "bad
    smell" (at least) here in Germany because of many right-wing and covidiot chatgroups there.
    Besides, for me as a "classic" FTN user, the Telegram messages don't "look nice" in terms of formatting, subject etc.
    But that's just my personal point of view.

    There are some people who would like to have some of the
    stuff that you mentioned (I, eg. would be interested in
    the SmartSuite, but preferably in German).

    Wouldn't there be an option in the menus to set the language of
    preference?

    That depends on the software. Often there is a "english only" version and sometimes the programs are multilingual - but this takes up more space on
    the hard disk...

    WARNING: 12MB RAM minimum required! LOL
    https://susepaste.org/70764990

    Very nice :) :)

    [giving away old stuff]
    I thought of that very thing. I already mentioned a handful of
    gear about a year ago in appropriate echos where some people
    were discussing parts would hang out. But no takers.

    Maybe it's worth repeating. Apparently fidonet has a cforsale
    echo too.

    I hope it works!

    Taking photos of the stuff is definitely a good idea.

    There is a local shop in town that operates as a donation-based
    thrift store and helps to raise funds for the local hospice. The
    shop has a man-cave area that is filled with tools and gear of
    all kinds. Not sure about computer parts and software.

    It's worth a try, I think.

    Have a nice day!

    Regards,
    Anna

    --- OpenXP 5.0.49
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Mauro Veiga@4:801/194.2 to Anna Christina Nass on Wednesday, March 24, 2021 10:41:37
    Quoting Anna Christina Nass to August Abolins <=-

    I don't see the point in listing all the retro stuff on ebay for
    example and hoping to sell.
    [...]
    What good is all that old stuff?

    Well, that's an interesting question, especially in a FidoNet echo :)

    There are some people who would like to have some of the stuff that
    you mentioned (I, eg. would be interested in the SmartSuite, but preferably in German).

    If you don't want to invest much time and effort, why not just put the stuff in a box, make some photos and put it in a forum or an echo
    (like CLASSIC_COMPUTING) and say "for free, to pick up".

    I love old stuff.
    At moment i'm using a 1997 point software. I love this things. :-)


    []s ³
    ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ * ÄÄÄÄÄÄÄÄÄÄÄÄÄ
    ³ Mauro R. Veiga - abutre.no-ip.org:2323 ³
    ÄÄÄÄijÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ


    MeSSaGe SiTTeR 1.00 - Full Version
    Live Long and Prosper

    ... BlueWave - More than a program, it's a lifestyle.
    --- Indigo/DOS 0.01+Blue Wave/DOS
    * Origin: Point do Pardal - Brasil * (4:801/194.2)
  • From Martin Foster@2:310/31.3 to August Abolins on Wednesday, March 24, 2021 13:55:00
    Hello August!

    *** Sunday 21.03.21 at 10:03, August Abolins wrote to Martin Foster:

    Was your test with DeepL?

    Yes it was.

    What paragraph did you test?

    I don't remember now but the major issue was one of formatting.

    Here is section I.0

    Yes, very nice :)

    [snip
    I added my own wrapping to fit better in this echo.

    OK.

    I don't see too many problems above at all. Minor clean up is
    to be expected.

    Yup.

    [snip]
    I just learned about TortoiseSVN, since it support
    Windows. It looks like a fine tool for managing doc
    changes.

    Yes, it's an excellent piece of software and it's free :)

    So.. if we were to engage in this project, we would need to
    settle on using the same svn program I suppose.

    No, not at all, each user would be free to use whatever svn client they chose, even the commandline version of svn would do. In fact, that may
    well be easier for the new svn user because it's only really necessary to learn 3 basic commands(checkout, update and commit).

    https://www.smartsvn.com/

    I've used the Linux version for many years and have found
    that "Lite" mode more than meets my needs.

    I'm game to try that one since you're already using it.

    I wouldn't really recommend SmartSVN if you're new to version control, I
    feel that TortoiseSVN would be the better choice. The only reason I use SmartSVN is because there isn't a Linux version of TortoiseSVN.

    However, I don't see the point of trying it out just yet because I haven't seen any volunteers step forward and therefore, there's no repository to
    try it out on.

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?

    The master copy of the document would be held in the remote
    svn repository and all changes to the document would be
    done in the users' own local working copy of the document.
    All changes to the users' working copy of the document
    would then be commited by each user to the master copy in
    the remote svn repository. That's simplifying it a bit but
    you should get the jist of how it works :)

    Oh.. and one person is designated as managing and releasing the
    final "master" copy?

    Yes, there would need to be a project coordinator.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Wednesday, March 24, 2021 13:59:00
    Hello August!

    *** Tuesday 23.03.21 at 08:59, August Abolins wrote to Anna Christina Nass:

    [snip]
    I even have a copy of the book OS/2 2.1 Unleashed.

    Oh, I have a copy of OS/2 Warp Unleashed - DeLuxe Edition, which I bought
    off eBay many years ago :))

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@1:153/757.2 to Martin Foster on Wednesday, March 24, 2021 10:15:47
    I even have a copy of the book OS/2 2.1 Unleashed.

    Oh, I have a copy of OS/2 Warp Unleashed - DeLuxe Edition, which I bought off eBay many years ago :))

    ebay was not available for me back then. All my OS/2 stuff was *new* from brick-n-mortar places.

    I think I have the Warp Unleashed too.
    --- SBBSecho 3.14-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From August Abolins@1:396/45.29 to Martin Foster on Wednesday, March 24, 2021 21:15:00
    Hello Martin!

    ** On Wednesday 24.03.21 - 13:55, you wrote to me:

    Here is section I.0

    Yes, very nice :)

    Except for a couple of words that duplicated, I thought the
    result was pretty good too!

    So.. if we were to engage in this project, we would need to
    settle on using the same svn program I suppose.

    No, not at all, each user would be free to use whatever svn client they chose, even the commandline version of svn would do. In fact, that may well be easier for the new svn user because it's only really necessary to learn 3 basic commands(checkout, update and commit).

    Hmmm. I installed tortoisesvn on my win7 DT pc but nothing
    seemed to load. I got a message saying "Read the manual!" :/

    I wouldn't really recommend SmartSVN if you're new to version control, I feel that TortoiseSVN would be the better choice. The only reason I use SmartSVN is because there isn't a Linux version of TortoiseSVN.

    The latest tortoisesvn versions don't support XP. But apparently
    I can fetch an older version.

    However, I don't see the point of trying it out just yet because I
    haven't seen any volunteers step forward and therefore, there's no repository to try it out on.

    But I could use some practice first, with your help - and
    experiment with the paragraphs in section I for starters.

    What minimum # of people do you envision should participate in
    the translation project? DeepL can work with 5000 chars at a
    time. The fido.tx file is about 133K chars. That would make it
    about 26 or 30 files in the depository?

    From the sounds of it, svn is something I should have been using
    all along especially for the invoices that I sometimes need to
    modify and keep track of what was changed.

    Apparently tortoisesvn "integrates" into windows explorer (the
    file management display) but I can't seem to figure out how to
    get started with anything.

    But I suppose we would need a webbased versioning
    system, not a local one for participants/editors?

    Oh.. and one person is designated as managing and releasing the
    final "master" copy?

    Yes, there would need to be a project coordinator.
    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From August Abolins@1:396/45.29 to Martin Foster on Wednesday, March 24, 2021 21:19:00
    Hello Martin!

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?

    The master copy of the document would be held in the remote svn
    repository and all changes to the document would be done in the users'
    own local working copy of the document. All changes to the users' working copy of the document would then be commited by each user to the master copy in the remote svn repository. That's simplifying it a bit but you should get the jist of how it works :)

    It sounds amazing! I am anxious to try it. But like I wrote
    earlier, I wasn't able to kick-start anything to work on.

    If the master is to be on a server, how does that work with
    tortoisesvn? Tortoisesvn seems to be a local program that works
    with one's own files only.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 25, 2021 11:31:00
    Hello August!

    *** Wednesday 24.03.21 at 21:15, August Abolins wrote to Martin Foster:

    [snip]
    However, I don't see the point of trying it out just yet because I
    haven't seen any volunteers step forward and therefore, there's no
    repository to try it out on.

    But I could use some practice first, with your help -

    Gulp! =8}

    and experiment with the paragraphs in section I for starters.

    Nice idea but experimenting with other folks' repositories is a NO-NO.

    What minimum # of people do you envision should participate in the translation project? DeepL can work with 5000 chars at a time. The fido.tx file is about 133K chars.

    That's a good question which I can't really answer but I would guess at probably two.

    That would make it about 26 or 30 files in the depository?

    No it wouldn't, there would only be one file in the repository.

    From the sounds of it, svn is something I should have been using
    all along especially for the invoices that I sometimes need to
    modify and keep track of what was changed.

    Apparently tortoisesvn "integrates" into windows explorer (the
    file management display) but I can't seem to figure out how to
    get started with anything.

    Right-Clicking on the Desktop would be a good place to start and then
    click on "SVN Checkout" but without a repository URL, that's as far as you could go.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, March 25, 2021 11:38:00
    Hello August!

    *** Wednesday 24.03.21 at 21:19, August Abolins wrote to Martin Foster:

    But I suppose we would need a webbased versioning system, not a
    local one for participants/editors?

    The master copy of the document would be held in the remote svn
    repository and all changes to the document would be done in the users'
    own local working copy of the document. All changes to the users'
    working copy of the document would then be commited by each user to the
    master copy in the remote svn repository. That's simplifying it a bit
    but you should get the jist of how it works :)

    It sounds amazing! I am anxious to try it. But like I wrote
    earlier, I wasn't able to kick-start anything to work on.

    If the master is to be on a server, how does that work with
    tortoisesvn? Tortoisesvn seems to be a local program that works
    with one's own files only.

    Once any changes have been completed in the user's working copy, those changes would be merged into the remote master copy by using TortoiseSVN
    to commit the changes.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Monday, March 29, 2021 20:11:00
    Hello Martin Foster!

    ** On Thursday 25.03.21 - 11:31, Martin Foster wrote to August Abolins:

    and experiment with the paragraphs in section I for starters.

    Nice idea but experimenting with other folks' repositories is a NO-NO.

    Huh? The translation hasn't even started (except for the first
    para in section I)

    What minimum # of people do you envision should participate in the
    translation project? DeepL can work with 5000 chars at a time. The
    fido.tx file is about 133K chars.

    That's a good question which I can't really answer but I would guess at probably two.

    OK! But you said there had to be more people involved. Now you
    say only two - how 'bout you and I? :D

    That would make it about 26 or 30 files in the depository?

    No it wouldn't, there would only be one file in the repository.

    I think it would be much easier to monitor translations if the
    project proceeded subsectio by subsection. The whole 150K char
    document would be a nightmare to monitor progress. The editing
    work and approval amongst the team would be easier from to
    bottom in an orderly sequence.

    Apparently tortoisesvn "integrates" into windows explorer (the
    file management display) but I can't seem to figure out how to
    get started with anything.

    Right-Clicking on the Desktop would be a good place to start and then click on "SVN Checkout" but without a repository URL, that's as far as
    you could go.

    I watched a few tortoisesvn YT videos. Most of them were
    terrible - the host moving the mouse all over the place and NOT
    explaining WHY and WHERE he was moving the mouse. Literally it
    was "go here, then here, to get that, oops.. I mean here, and
    then this.." ARGHHHH!

    To get started I would need to get an earlier version of
    tortoisesvn that supports XP.

    The only other thing I don't understand and is HOW and WHERE is
    the "repository" hosted so that the files are availble to other
    editors interested in the project?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Thursday, April 01, 2021 11:19:00
    Hello August!

    *** Monday 29.03.21 at 20:11, August Abolins wrote to Martin Foster:

    [snip]
    To get started I would need to get an earlier version of
    tortoisesvn that supports XP.

    Going by the research I did yesterday, WinXP support was dropped in
    v1.9.x, so you would probably need to grab a copy of v1.8.12, which you
    can get from here .....

    https://sourceforge.net/projects/tortoisesvn/files/1.8.12/Application/

    I've replied to the rest of your missive by netmail :)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)