Hello!

Ever since I downloaded (or rather file requested) a nodelist for my "othernet", I get this error message after each poll:


ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Datei(en) wurde(n) nicht korrekt entpackt!  00:06 ³
³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

I have disabled the processing for the other nodelist, but it looks like something wants to "process".



../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August,

Ever since I downloaded (or rather file requested) a nodelist for my "othernet", I get this error message after each poll:

ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Datei(en) wurde(n) nicht korrekt entpackt!  00:06 ³
³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

I have disabled the processing for the other nodelist, but it looks
like something wants to "process".

Would it help if you recieved that file with a tic?

You could send a message to Filefix with ..

%resend <file> <filearea>

in the message body and Filefix will send you the file along with a .tic if the
file is found.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

** 04.04.20 - 18:14, Alan Ianson wrote to August Abolins:

ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Datei(en) wurde(n) nicht korrekt entpackt!  00:06 ³
³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

I have disabled the processing for the other nodelist, but it looks
like something wants to "process".

Would it help if you recieved that file with a tic?

I dunno. It sounds like oxp might be looking for a DIFF file, but I don't have that part enabled at all. But maybe the mere existance of FSXNET.Z94
in the /FILES directory triggers something to cause the above message.

But.. if I *just* delete the archive in the /FILES directory, oxp locks up
on the next poll. But.. if I then delete the whole FSXNET nodelist, everything works as normal.

I'd like to have the FSXNET nodelist handy (for lookups and browsing with oxp). But seems that oxp expects a DIFF file.

(Martin.. are you listening?)

Am I the only user of oxp with an othernet nodelist in addition to the standard fido one?

You could send a message to Filefix with ..

%resend <file> <filearea>

in the message body and Filefix will send you the file along with a .tic
if the file is found.

I dunno. Worth a shot.


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August,

I'd like to have the FSXNET nodelist handy (for lookups and browsing
with oxp). But seems that oxp expects a DIFF file.

Yes, it would be best to have access to the nodelist.

In all the time I've been in fsxNet I have never seen a DIFF, I don't think they produce one.

You could ask Paul Hayton the ZC of fsxNet if that is a possibility or not. I suspect he uses makenl to produce the nodelist and if so it wouldn't be hard for him to produce a DIFF also, but you would need to talk to him about that.

His node is 21:4/101.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Al,

His node is 21:4/101.

Make that 21:1/101.. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello August!

*** 04.04.20 at 22:24, August Abolins wrote to Alan Ianson:

[snip]

(Martin.. are you listening?)

I'm always listening :-))

I've freq'd a copy of FSXNET.Z94 from Alan's system, installed it in
my Linux installation of OpenXP and I cannot reproduce your problem. Everything works as expected with FSXNET.Z94 still in my 'files'
directory and not presenting me with any problems.

However, I've just noticed that the last line of FSXNET.094 comprises
one single extended ascii character which I don't think should be
there. Maybe the Windows version of OpenXP doesn't like that character
for some reason. Might I suggest that you delete that character, save
the file and then try again.

Regards,
Martin

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

Hello August!

*** 05.04.20 at 12:58, Martin Foster wrote to August Abolins:

[snip]

(Martin.. are you listening?)

I'm always listening :-))

I've freq'd a copy of FSXNET.Z94 from Alan's system, installed it in
my Linux installation of OpenXP and I cannot reproduce your problem. Everything works as expected with FSXNET.Z94 still in my 'files'
directory and not presenting me with any problems.

However, I've just noticed that the last line of FSXNET.094 comprises
one single extended ascii character which I don't think should be
there. Maybe the Windows version of OpenXP doesn't like that character
for some reason. Might I suggest that you delete that character, save
the file and then try again.

If you received this message, please disregard it and don't do
anything, as there's a problem but I don't have time to have another
look at it today, sorry :((

Regards,
Martin

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

Hello August!

*** 04.04.20 at 22:24, August Abolins wrote to Alan Ianson:

ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Datei(en) wurde(n) nicht korrekt entpackt!  00:06 ³
³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

I have disabled the processing for the other nodelist, but it looks
like something wants to "process".

Would it help if you recieved that file with a tic?

I dunno. It sounds like oxp might be looking for a DIFF file, but I
don't have that part enabled at all. But maybe the mere existance of FSXNET.Z94 in the /FILES directory triggers something to cause the above message.

But.. if I *just* delete the archive in the /FILES directory, oxp locks
up on the next poll. But.. if I then delete the whole FSXNET nodelist, everything works as normal.

I'd like to have the FSXNET nodelist handy (for lookups and browsing with oxp). But seems that oxp expects a DIFF file.

(Martin.. are you listening?)

OK, let's try this again .....

Further to my two previous ramblings, I don't get the error message
that you're getting but I do get the lockup after a poll. Actually,
it's the dreaded endless loop rather than a lockup but I digress.

I'm hoping I've fixed this with a bit of a workaround .....

Even though FSXNet don't distribute diffs, I've added some "dummy"
data in the "Update file" and "Update archive" fields: FSXNET_D.###
and FSXNET_D.Z## respectively and this appears to have fixed it. To
test my workaround, I posted a test shot in FIDOTEST and there was no
lockup after the poll. Let's hope it doesn't lockup after this poll.

Regards,
Martin

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

Hello August!

*** 05.04.20 at 14:12, Martin Foster wrote to August Abolins:

[snip]

Let's hope it doesn't lockup after this poll.

Yep, that went OK, no lockup, methinks I'll have a beer now :))

Regards,
Martin

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

Hello Martin!

** 05.04.20 - 14:12, Martin Foster wrote to August Abolins:

Further to my two previous ramblings, I don't get the error message
that you're getting but I do get the lockup after a poll. Actually,
it's the dreaded endless loop rather than a lockup but I digress.

Yes.. I noticed that the DEBUGLOG.TXT file just kept getting larger and
and larger.

I'm hoping I've fixed this with a bit of a workaround .....

Even though FSXNet don't distribute diffs, I've added some "dummy"
data in the "Update file" and "Update archive" fields: FSXNET_D.###
and FSXNET_D.Z## respectively and this appears to have fixed it.

I figured that out on my own with .087 last week. I'm running it like
this right now, and it works:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Z2PNT.### 094 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist ³
³ NODELIST.### 094 NODEDIFF.### NODEDIFF.Z## Diff Nodelist ³
³ FSXNET.### 094 FSXNET.### FSXNET.Z## Diff Nodelist ³
³ ³
³ ³
³ ³
³ ³
³ ÚÄ Configure Node/Pointlist ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³
³ ³ ³ ³
³ ³ List name FSXNET.### Number 094 ³ ³
³ ³ ³ ³
³ ³ Format of list Nodelist  ³ ³
³ ³ Zone/Address 21 ³ ³
³ ³ ³ ³
³ ³ Update file FSXNET.### ³ ³
³ ³ Update archive FSXNET.Z## ³ ³
³ ³ ³ ³
³ ³ Process by ³ ³
³ ³ ³ ³
³ ³ [x] Use internal nodelist processor ³ ³
³ ³ [ ] Delete update after processing ³ ³
³ ³ ³ ³
³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ [F2] ÄÙ ³


The previous week's .087 was set up the same way. It ran fine. But the error message that I posted here started as soon as I had a FSXNET.Z94 in
the /FILE directory after a file-request. :(

To test my workaround, I posted a test shot in FIDOTEST and there was
no lockup after the poll. Let's hope it doesn't lockup after this
poll.

Yes.. it's running fine poll after poll with the workaround.

Meanwhile, I renamed the workaround fields to this:

³ FSXNET.### 094 FSXDIFF.### FSXDIFF.Z## Diff Nodelist ³


The problem/lockup seems to start as soon as it sees another FSXNET.Z** in the /FILES dir.



../|ug

-+- OpenXP 5.0.43
+ Origin: /|ug's Point, Ont. CANADA (2:221/1.58)

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Martin!

** 05.04.20 - 12:58, Martin Foster wrote to August Abolins:

I've freq'd a copy of FSXNET.Z94 from Alan's system, installed it in
my Linux installation of OpenXP and I cannot reproduce your problem.
Everything works as expected with FSXNET.Z94 still in my 'files'
directory and not presenting me with any problems.

Hmmm.. The only way it would work for me was if I filled in the other
fields (fake diff information) *and* have the internal processor enabled.

However, I've just noticed that the last line of FSXNET.094 comprises
one single extended ascii character which I don't think should be
there. Maybe the Windows version of OpenXP doesn't like that character
for some reason. Might I suggest that you delete that character, save
the file and then try again.

Hey.. I notice that too. It renders as a "SUB" char. That's a Ctrl-Z to denote EOF?

../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Alan!

** 05.04.20 - 01:35, Alan Ianson wrote to August Abolins:

In all the time I've been in fsxNet I have never seen a DIFF, I don't
think they produce one.

It's not critical. This matter just seems specific to how oxp works.

It can "update" a nodelist (manually or automatically), but only if there
is a diff.

Otherwise, an update from an existing full nodelist to newer edition has
to be done manually.

Not many nodes even do freq. Only 3 systems do.


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Alan!

** 05.04.20 - 01:42, Alan Ianson wrote to Alan Ianson:

Hello Al,

His node is 21:4/101.

Make that 21:1/101.. :)

No problem. With an integrated nodelist, I can just look it up! <G> And
oxp can pre-fill the address for a message.

Apparently, all of these are "Paul Hayton":

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
New Zealand, New Zealand 3:57/0 -Unpublished-
South Island Net, New Zealand 3:770/0 -Unpublished- ³
Southern Hub, South Island NZ 3:770/1 -Unpublished- ³
Agency HUB Gateway, New Zealand 3:770/3 -Unpublished- ³
Agency BBS, Dunedin 3:770/100 -Unpublished- ³
North Island Net, New Zealand 3:772/0 -Unpublished- ³
Northern Hub, North Island NZ 3:772/1 -Unpublished- ³
fsxNet ZC, Dunedin NZL 21:21/0 -Unpublished- ³
fsxNet RC, Dunedin NZL 21:21/0 -Unpublished- ³
fsxNet (NET 1), Dunedin NZL 21:1/0 -Unpublished- ³
Agency HUB, Dunedin NZL 21:1/1 -Unpublished- ³
fsxNet Games + Usenet Gateway, Dune 21:1/10 -Unpublished- ³
Risa HUB, Dunedin NZL 21:1/100 -Unpublished- ³
Agency BBS, Dunedin NZL 21:1/101 -Unpublished- ³
Cryptogenic Radix BBS, Dunedin NZL 21:1/179 -Unpublished- ³ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
Status Region Node list NODELIST.094 ³
Sysop Paul Hayton ³
Flags CM,INA:agency.bbs.nz,IBN ³ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Martin!

** 05.04.20 - 12:58, Martin Foster wrote to August Abolins:

I've freq'd a copy of FSXNET.Z94 from Alan's system, installed it..

Try freq'ing it again, but this time from his Zone 21 entry.

When I try to freq to his 21: address, oxp is calling Tommi's system:


/¯Netcall
474 05.04 August Abolins @ 2:221/1.58 Netcall to 21:4/106

= 13:36:11 CONNECT
13:36:11 OPT CRAM-MD5-84b37ab53dc5aca3c66e529cf66d4aee
13:36:11 SYS RBB/2
13:36:11 ZYZ Tommi Koivula
13:36:11 LOC Lake Ylo, Finland
13:36:11 NDL IBN,CM
13:36:11 TIME Sun, 5 Apr 2020 20:36:07 +0300
13:36:11 VER binkd/1.1a-101/OS2 binkp/1.1
13:36:12 TRF 0 0
13:36:12 OPT EXTCMD GZ BZ2
13:36:12 secure
= 13:36:12 hangup
- 13:36:12 exiting

The above is using the current .094 nodelist.


BUT.. just a couple days ago when I still had the .084 version installed,
it called Alan's system OK:


499 04.04 August Abolins @ 2:221/1.58 Netcall to 21:4/106

= 20:05:32 CONNECT
20:05:33 OPT CRAM-MD5-48f0d175d4147429029d786c9fe4e9ee
20:05:33 SYS The Rusty MailBox
20:05:33 ZYZ Alan Ianson
20:05:33 LOC Penticton, BC Canada
20:05:33 NDL 115200,CM,XW,IBN
20:05:33 TIME Sat, 4 Apr 2020 17:05:29 -0700
20:05:33 VER binkd/1.1a-101/Linux binkp/1.1
20:05:33 TRF 0 0
20:05:33 OPT EXTCMD GZ BZ2
20:05:33 secure
= 20:05:33 hangup
- 20:05:33 exiting

WTF?


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hi Martin,

Ooops.. I meant to post this "proof" when I used the .087 nodelist:


1 marked messages
þ 687 04.04 August Abolins @ 2:221/1.58 Netcall to 21:4/106


To: /¯NETCALL (All)
From: August Abolins @ 2:221/1.58 (RBB, Ylojarvi)
Subject: Netcall to 21:4/106
Software: OpenXP/5.0.43 (Win32)
Date: Sa 04.04.20, 19:06
Size: 687 Bytes
--------------------------------------------------------
1 21 F1-Help
= 19:05:53 CONNECT
19:05:54 OPT CRAM-MD5-32b189fcd7136296474d0f85a2d23eee
19:05:54 SYS The Rusty MailBox
19:05:54 ZYZ Alan Ianson
19:05:54 LOC Penticton, BC Canada
19:05:54 NDL 115200,CM,XW,IBN
19:05:54 TIME Sat, 4 Apr 2020 16:05:50 -0700
19:05:54 VER binkd/1.1a-101/Linux binkp/1.1
19:05:54 TRF 752 0
19:05:54 OPT EXTCMD GZ BZ2
19:05:54 secure
* 19:05:54 Rcvd 8ea9605a.pkt, 752b
* 19:05:54 Sent 0004006A.REQ, 12b
* 19:05:54 Sent 04190553.PKT, 1252b
* 19:05:55 Rcvd FSXNET.Z94, 11310b
* 19:05:55 Rcvd resp12cf.txt, 1553b
= 19:05:55 hangup
- 19:05:55 exiting



../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Martin,

However, I've just noticed that the last line of FSXNET.094 comprises
one single extended ascii character which I don't think should be
there. Maybe the Windows version of OpenXP doesn't like that
character for some reason. Might I suggest that you delete that character, save the file and then try again.

That's a <CTRL>Z. We don't see it a lot today but at one time a number of editors would put a <CTRL>Z at the end of files they saved. It's an end of file
marker from the CP/M days.

I saw a <CTRL>Z in an old file_id.diz recently. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello August,

In all the time I've been in fsxNet I have never seen a DIFF, I
don't think they produce one.

It's not critical. This matter just seems specific to how oxp works.

It can "update" a nodelist (manually or automatically), but only if
there is a diff.

Otherwise, an update from an existing full nodelist to newer edition
has to be done manually.

I'm going to ask Paul about this. It may be simple for him to do, or not I'm not sure but I'll ask.

Not many nodes even do freq. Only 3 systems do.

I've found a simple utility to install for windows/linux binkd. I'll see if I can pass it on to a couple nodes who could use it.

It's an external SRIF utility that's needed for binkd that is not well known.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello August,

His node is 21:4/101.

Make that 21:1/101.. :)

No problem. With an integrated nodelist, I can just look it up! <G>
And oxp can pre-fill the address for a message.

Apparently, all of these are "Paul Hayton":

Yes, Paul gets around.. ;)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

** 05.04.20 - 14:05, You wrote:

I'm going to ask Paul about this. It may be simple for him to do, or not
I'm not sure but I'll ask.

OK. Thanks.

Not many nodes even do freq. Only 3 systems do.

I've found a simple utility to install for windows/linux binkd. I'll see
if I can pass it on to a couple nodes who could use it.

It's an external SRIF utility that's needed for binkd that is not well
known.

I don't know what SRIF is. Google tells me it's a somatotropin release inhibiting factor. LOL

I thought most bbs softwares (especially sychro and mystic, the majority
in fsxnet?) supported freq, built-in.



../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August,

It's an external SRIF utility that's needed for binkd that is not
well known.

I don't know what SRIF is. Google tells me it's a somatotropin
release inhibiting factor. LOL

I'm not sure what that is but I don't think that'll help us in this case. :)

Binkd and most binkp mailers don't know how to get a requested file but it does
support a Standard Request Interface File. When a file is requested we pass that info to an SRIF utility that finds the file and tells binkd where it is to
send the file to the node.

I thought most bbs softwares (especially sychro and mystic, the
majority in fsxnet?) supported freq, built-in.

I think, but I'm not certain(tm) that Synchronet's binkit mailer supports file requests although the node has to tell it how to do that with an .ini file.

We just brought up file request support with James, the Mystic author and I think he put it on the todo or maybe todo for future support when he gets some free time to look into it more.

Dial-up mailers did all this themselves and it was easy to setup. It's not hard
with binkd but you need the external utilities setup.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi! August,

On 05 Apr 20 19:53, you wrote to Alan Ianson:

It's an external SRIF utility that's needed for binkd that is not
well known.

I don't know what SRIF is. Google tells me it's a somatotropin
release inhibiting factor. LOL

It's described most recently in FSP-1040. It's so simple that even I understood it enough to design a DOS batch server method of handling FREQs in binkD, Argus & Radius.

On the client side, the result is a simple ASCII text file containing a list of
filenames, one per line, requesting either real names or majic versions as concocted by the server's sysop. To get to that point requires some voodoo, usually with a netmail editor using the FREQ attribute (most BBS editors can't)
and a compliant tosser is required to act on the 'direct'/FREQ nature of the netmail (some don't).

In realising the need for a simple text file, one can use an approriate editor to produce one. (Filename is -not- important, though the 'extension' is. I've
used current date/time for quick resolution in the past; example: "06041050.req".) I've experimented successfully on several occasions by simply letting the file languish in a *filebox* configured for a peer system, for the mailer to transmit to the server during a session achieved by some other means.

I thought most bbs softwares (especially sychro and mystic, the
majority in fsxnet?) supported freq, built-in.

Nope. Not a lot of folks took the time to study the proposal (current status still, I think; not a standard yet).

Cheers,
Paul.

... Harry's Speech: https://www.youtube.com/watch?v=A-yZNMWFqvM
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

Hello Alan!

*** 05.04.20 at 14:05, Alan Ianson wrote to August Abolins:

[snip]

Not many nodes even do freq. Only 3 systems do.

I've found a simple utility to install for windows/linux binkd.
I'll see if I can pass it on to a couple nodes who could use it.

It's an external SRIF utility that's needed for binkd that is not
well known.

Oh, that sounds very interesting and useful, is it available for f'req
from your system?

Regards,
Martin

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

Hello August!

*** 05.04.20 at 11:18, August Abolins wrote to Martin Foster:

[snip]

The problem/lockup seems to start as soon as it sees another FSXNET.Z**
in the /FILES dir.

After f'reqing another copy of FSXNET.Z94 from Alan's system and then
polling Richard, no problems arose with the existance of FSXNET.Z94
sitting in my 'files' directory.

Regards,
Martin

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

Hello August!

*** 05.04.20 at 13:44, August Abolins wrote to Martin Foster:

I've freq'd a copy of FSXNET.Z94 from Alan's system, installed it..

Try freq'ing it again, but this time from his Zone 21 entry.

OK .....

---------- 8< ----------
To: /»NETCALL (All)
From: Martin Foster @ 2:310/31.3 (fido.ricsi.priv.at, Vienna A)
Subject: Netcall to 21:4/106
Date: Mo 06.04.20, 13:38
Size: 597 Bytes
MessageID: 2:310/31.3@fidonet e32ac42c
Organiz.: Bitz-Box
Software: OpenXP/5.0.43 (Linux) (x86_64) ---------------------------------------------------------------------
= 13:38:21 CONNECT
13:38:21 OPT CRAM-MD5-a20da0674363263aeb0a8e86c99438ee
13:38:21 SYS The Rusty MailBox
13:38:21 ZYZ Alan Ianson
13:38:21 LOC Penticton, BC Canada
13:38:21 NDL 115200,CM,XW,IBN
13:38:21 TIME Mon, 6 Apr 2020 05:38:21 -0700
13:38:21 VER binkd/1.1a-101/Linux binkp/1.1
13:38:21 TRF 0 0
13:38:21 OPT EXTCMD GZ BZ2
13:38:21 non-secure
* 13:38:22 Sent 0004006A.REQ, 11b
* 13:38:22 Rcvd FSXNET.Z94, 11310b
* 13:38:22 Rcvd resp22be.txt, 1823b
= 13:38:22 hangup
- 13:38:22 exiting

-+- OpenXP 5.0.43
+ Origin: Bitz-Box - Bradford - UK (2:310/31.3)
---------- 8< ----------

..... that went perfectly.

When I try to freq to his 21: address, oxp is calling Tommi's system:

How strange ????

However, I've seen a similar problem to this before but under
different circumstances. Go to "Fido", cursor over "Crash", press <F1>
and then have a read of the "IMPORTANT NOTE" near the bottom of the
help text. I suspect that the solution to your problem may be lurking somewhere amongst that lot. Best of luck ;)

[snip]

WTF?

Yes, indeed :)

Regards,
Martin

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

Hello Martin!

** 06.04.20 - 14:05, Martin Foster wrote to August Abolins:

The problem/lockup seems to start as soon as it sees another FSXNET.Z**
in the /FILES dir.

After f'reqing another copy of FSXNET.Z94 from Alan's system and then
polling Richard, no problems arose with the existance of FSXNET.Z94
sitting in my 'files' directory.

Hmmm..

I think it may only occur after oxp processes another nodelist diff (that
is, the main fidonet one) Then meanwhile, when it sees an other-net
(full) nodelist matching one of the dummy names in the config, it goes nuclear as it searches for the "diff" that doesn't exist.

So.. I think, we must await the next delivery of the nodelist for the
primary server.


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello Martin!

** 06.04.20 - 14:07, Martin Foster wrote to August Abolins:

Try freq'ing it again, but this time from his Zone 21 entry.

OK .....

[snip]

..... that went perfectly.

I see. Thanks for showing the log entries to show that.

I just noticed and realized the following is happening.

I can duplicate a similar event *IF* the system I am freq'ing is not a "server" configured in oxp.

That is why it worked for you.

In other words, a freq/crash message connects directly to any other system
as long as it is not my primary or any other system defined in the servers config.

Interesting, no?

I am surprised that oxp is programmed to behave this way.

When I try to freq to his 21: address, oxp is calling Tommi's system:

How strange ????

However, I've seen a similar problem to this before but under
different circumstances. Go to "Fido", cursor over "Crash", press <F1>
and then have a read of the "IMPORTANT NOTE" near the bottom of the
help text. I suspect that the solution to your problem may be lurking
somewhere amongst that lot. Best of luck ;)

It that your writing in the F1 help? <G>

Meanwhile, I discovered a workaround/alternative that does NOT require mucking about with switching the primary server settings.

I'll reveal the aptly named August-Solution a lil'bit later.


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August!

*** 06.04.20 at 9:48:00, August Abolins wrote to Martin Foster:

[snip]

However, I've seen a similar problem to this before but under different
circumstances. Go to "Fido", cursor over "Crash", press <F1> and then
have a read of the "IMPORTANT NOTE" near the bottom of the help text. I
suspect that the solution to your problem may be lurking somewhere
amongst that lot. Best of luck ;)

It that your writing in the F1 help? <G>

Whatever makes you think that :-))

Meanwhile, I discovered a workaround/alternative that does NOT require mucking about with switching the primary server settings.

I'll reveal the aptly named August-Solution a lil'bit later.

Come on then, the suspense is killing :-))

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Alan!

*** 06.04.20 at 15:10:14, Alan Ianson wrote to Martin Foster:

[snip]

I have also used FREQ-U by Fred Riccio in the past with good results. I have the linux version available here as FREQ-U.ZIP and the Windows version as FU_W32.ZIP.

Grabbed both those, thank you very much :)

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Sveiks Martin!

12 Apr 20 11:23, you wrote to me:

Is that your writing in the F1 help? <G>

Whatever makes you think that :-))

Because it was good english, well done, peppered with cynicism and sarcasm.

I'll reveal the aptly named August-Solution a lil'bit later.

Come on then, the suspense is killing :-))

You got it wrong. Suspense is *thrilling*. Covid is killing.

I'll work on a proper reply to "the solution" later today.



--- GoldED+/W32-MINGW 1.1.5-b20180707
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

** 14.04.20 - 18:30, August Abolins wrote to Martin Foster:

I'll reveal the aptly named August-Solution a lil'bit later.

Come on then, the suspense is killing :-))

You got it wrong. Suspense is *thrilling*. Covid is killing.
I'll work on a proper reply to "the solution" later today.

HERE, as promised is the "August-Solution" or the workaround/alternative
that does NOT require mucking about with switching the primary server settings.

I have two servers:

[1] Tommi, fidonet = primary
[2] Alan, fsxnet

When I wanted to freq a file from [1], I never encountered an "issue"
because OXP always uses the primary

When I wanted to freq a file from [2], it would always call [1]

When I wanted to freq a files from anyone else, the freq would always work
- because those systems were NOT listed as servers.

SO.. the solution: If I want to freq a file from [2] (and avoid reconfiguring the primary server), simply do this:

(are you ready? here's the answer)

(I promise to stop goofing around and delaying the answer)

After creating the freq to [2], simply allow OXP to do a normal POLL to
the [2] server via the N A or N S commands.

Maybe a variation of the last sentence above can make its way into the OXP Help system?

This strategy would probably apply nomatter how many additional servers
are added. Simply allow OXP to POLL the server for which the freq is intended.


../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

Hello August!

*** Tuesday 14.04.20 at 21:11, August Abolins wrote to Martin Foster:

[snip]

HERE, as promised is the "August-Solution" or the workaround/alternative that does NOT require mucking about with switching the primary server settings.

I have two servers:

[1] Tommi, fidonet = primary
[2] Alan, fsxnet

When I wanted to freq a file from [1], I never encountered an "issue" because OXP always uses the primary

Yes, fine.

When I wanted to freq a file from [2], it would always call [1]

Yes, that's why I said there may be something in the help text that I
pointed you to which may have helped.

When I wanted to freq a files from anyone else, the freq would always
work - because those systems were NOT listed as servers.

Yes, fine.

SO.. the solution: If I want to freq a file from [2] (and avoid reconfiguring the primary server), simply do this:

(are you ready? here's the answer)

(I promise to stop goofing around and delaying the answer)

After creating the freq to [2], simply allow OXP to do a normal POLL to the [2] server via the N A or N S commands.

Excellent and many thanks for posting the solution :-)

Maybe a variation of the last sentence above can make its way into the
OXP Help system?

OK, I'll put it on my ever-growing ToDo list.

This strategy would probably apply nomatter how many additional servers are added. Simply allow OXP to POLL the server for which the freq is intended.

Yup, I don't see any reason why it shouldn't.

Regards,
Martin

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

Hello Martin!

** On 19.04.20 - 13:24, Martin Foster wrote to August Abolins:

This strategy would probably apply nomatter how many additional servers
are added. Simply allow OXP to POLL the server for which the freq is
intended.

Yup, I don't see any reason why it shouldn't.

Hindsight is 20/20. But the Crash behaviour wasn't what I expected. When
I created a Freq and proceeded to do a Crash, logic would tell me that I would expect the call to go to the Crash destination, just like how
regular netmail crash behaves. Instead, the freq packet was wrapped up
and sent to the Primary server.

So, the documentation needs clarity on how Freq's are an exception to the Crash rule.


../|ug

--- OpenXP 5.0.43
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

Hello August!

*** Tuesday 21.04.20 at 20:58, August Abolins wrote to Martin Foster:

[snip]

So, the documentation needs clarity on how Freq's are an exception to the Crash rule.

Noted and thanks for publishing your findings.

Regards,
Martin

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

Hello Martin!

** On 06.04.20 - 14:05, Martin Foster wrote to August Abolins:

The problem/lockup seems to start as soon as it sees another FSXNET.Z**
in the /FILES dir.

After f'reqing another copy of FSXNET.Z94 from Alan's system and then
polling Richard, no problems arose with the existance of FSXNET.Z94
sitting in my 'files' directory.

Ok. We've sorted out that the mere existence of FSXNET.ZXX does not trip
up your system, but that is probably because your sysytem is not
configured for FSXNET files?

BUT.. the following happened here, again:

ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Datei(en) wurde(n) nicht korrekt entpackt!  00:06 ³
³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

..right after the newest FSXNET.Z22 arrived.

= 14:38:34 CONNECT
14:38:35 OPT CRAM-MD5-26149de3d445d8935bb267bde82991ee
14:38:35 SYS The Rusty MailBox
14:38:35 ZYZ Alan Ianson
14:38:35 LOC Penticton, BC Canada
14:38:35 NDL 115200,CM,XW,IBN
14:38:35 TIME Thu, 30 Apr 2020 11:38:33 -0700
14:38:35 VER binkd/1.1a-104/Linux binkp/1.1
14:38:36 TRF 0 36693
14:38:36 OPT EXTCMD GZ BZ2
14:38:36 secure
* 14:38:36 Rcvd FSXNET.Z22, 11465b
* 14:38:36 Rcvd kpn6i5hi.tic, 3549b
[snip]

= 14:38:37 hangup
- 14:38:37 exiting


HOWEVER.. (get this..) OXP actually updated the nodelist! The config had
the dummy diff config file FSXNET.Z## active at that time:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Z2PNT.### 115 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
³ NODELIST.### 122 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
³ FSXNET.### 122 FSXNET.### FSXNET.Z## Diff Nodelist <====
³ micronet.### 108 MICRONET.### MICRONET.Z## Diff Nodelist

The dummy diff entry was present.

BUT, repeated N A poles would keep producing the "Datei(en) wurde(n) nicht korrekt entpackt!" message.

The only way I could stop OXP from triggering the above error message was
if I manually deleted the FSXNET.Z22 from /FILES.

Subsequent polls behaved OK. BUT, I haven't reveived my Z2PNT_D.Z22 file yet.

SO.. it looks like I have to either enable this for the FSXNET entry:

[x] Delete update after processing

OR.. run a batch program to check for and delete all FSXNET.Z* files in
the /FILES directory every time OXP starts up.

Thoughts?


../|ug

--- OpenXP 5.0.43
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

Hello August!

*** Monday 04.05.20 at 09:10, August Abolins wrote to Martin Foster:

[snip]

Anyway.. the dummy diffs are now in place:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Z2PNT.### 115 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
³ NODELIST.### 122 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
³ FSXNET.### 122 FSXNET_D.### FSXNET_D.Z## Diff Nodelist
³ micronet.### 108 MICRONET_D.# MICRONET.Z## Diff Nodelist

^^^^^^^^^^^^ ^^^^^^^^^^^^
Hmmmmm, these *might* cause problems but I could, of course, be wrong.

[snip]

We shall see what this week's files trigger.

Yes, indeed we will :)

Regards,
Martin

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

Hello Martin!

::: UPDATE ::::


** On Tuesday 05.05.20 - 20:22, Martin Foster wrote to August Abolins:

Anyway.. the dummy diffs are now in place:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Z2PNT.### 115 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
³ NODELIST.### 122 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
³ FSXNET.### 122 FSXNET_D.### FSXNET_D.Z## Diff Nodelist
³ micronet.### 108 MICRONET_D.# MICRONET.Z## Diff Nodelist

^^^^^^^^^^^^ ^^^^^^^^^^^^
Hmmmmm, these *might* cause problems but I could, of course, be wrong.

[snip]

We shall see what this week's files trigger.

Yes, indeed we will :)

Since that last post I now have this:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Z2PNT.### 136 Z2PNT_D.### Z2PNT_D.Z## Diff FD Pointlist
³ NODELIST.### 136 NODEDIFF.### NODEDIFF.Z## Diff Nodelist
³ FSXNET.### 136 FSXNET_D.### FSXNET_D.Z## Diff Nodelist
³ micronet.### 122 MICRON_D.### MICRON_D.Z## Diff Nodelist

[x] Use internal nodelist processor

[x] Import nodelist updates automatically
[x] Automatic TIC file processing


That means the last few weeks of processing have been error-free and no
lockups after a poll.

OXP seems very dependent on having no nodelist issues when at least one is configured.

FSXNET and micronet do not have DIFFs, but with the dummy-diffs configured above, I can at least keep the "Import nodelist updates automatically" enabled so that fidonet parts get done.


../|ug

--- OpenXP 5.0.43
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)