There seems to be a problem with the
recent .090
OpenXP doesn't like it. :(
NL problem? Recent .090?
... que?
Yup. Nodelist problem. Had to delet
it to get my OpenXP to
resume normal operations.
Ah, soz, my head was entirely someplace
else :). What system do you need to use
OpenXP with?
OpenXP operates in Windows and Linux.
OpenXP operates in Windows and Linux.
Soz again, that's not what I meant.. You are using OpenXP with a BBS, right?
Which software are you using?
OpenXP is a standalone point messagi
program. It doesn't need
to be associated with any "bbs
software".
Ahh, gotcha. Thanks for the
clarification. I tried some offline
readers back in the day, but never got
the hang of them I guess.
There seems to be a problem with the recent .090
OpenXP doesn't like it. :(
I also removed the nodelist from OpenXP and re-added WEEDNET.090 and
it got accepted...
Do you have any more information on the problem?
Does the debuglog.txt in the .openxp directory say anything?
My debuglog.txt only tracks data per session. That means, the
next time I launch OpenXP (which I've done since then) there is
a fresh new debuglox.txt file. So, there is no record of the
problem. When I've encountered a "problem with nodelist" error
in the past in othernets, I've just learned to delete the
nodelist and install the next one manually.
Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).
When I deleted 090, I didn't reactivate the auto nodelist
update part. I'll activate 097 and see what happens next time.
Will there be another nodelist delivery next week?
Am 06.04.23 schrieb Ogg@420:2/1.10 in WEED_GENERAL:
Hallo Ogg,
My debuglog.txt only tracks data per session. That means, the
next time I launch OpenXP (which I've done since then) there is
a fresh new debuglox.txt file. So, there is no record of the
problem. When I've encountered a "problem with nodelist" error
in the past in othernets, I've just learned to delete the
nodelist and install the next one manually.
Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).
telnet://bbs.roonsbbs.hu:1212 <<=-
Since today the 097 nodelist was sent out - did it work this time?
Although I have to admit that the file should not have changed
(besides the serial changing from 090 to 097).
the problem is that the header is not updated:
097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006 : 20189
the problem is that the header is not updated:
097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006 : 20189
Hello Roon!
** On Thursday 13.04.23 - 17:02, Roon wrote to acn:
the problem is that the header is not updated:
097 contains:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number 006
: 20189
Anything after a ; is a comment, no? so, anything on that line
wouldn't matter, no?
telnet://bbs.roonsbbs.hu:1212 <<=-
Anything after a ; is a comment, no? so, anything on that line
wouldn't matter, no?
it seems that nodelist compilers are using that line.
i realized that because my Qnode/2 were not using nodelists higher than
006 and tryed to figure out why. and this was the only thing i've found.
it seems that nodelist compilers are using that line.
i realized that because my Qnode/2 were not using nodelists higher than
006 and tryed to figure out why. and this was the only thing i've found.
I could try to replace the number in that line manually. What
should it be?
Meanwhile the recent .104 nodelist causes the same error.
Both .097 and .104 have the first line the same:
;A WeedNet Nodelist for Friday, January 6, 2023 -- Day number
006 : 20189
Instead of 20189, what should that be as well?
The line for .104 would be now:
;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189
So the checksum (20189) stays the same :)
The next file, .Z11 with .111, will be sent out on friday.
The line for .104 would be now:
;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189
The line for .104 would be now:
;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189
So the checksum (20189) stays the same :)
The next file, .Z11 with .111, will be sent out on friday.
The line for .104 would be now:
;A WeedNet Nodelist for Friday, April 14, 2023 -- Day number 104 :
20189
So the checksum (20189) stays the same :)
The next file, .Z11 with .111, will be sent out on friday.
It all worked this time. But I see that you are not interested
in updating the first line. :(
I suppose it's simpler that way if there are absolutely no
changes.
It all worked this time. But I see that you are not
interested in updating the first line. :(
That's a lie! Sorry, but that's absolutely not true.
I tried changing a setting in makenl (I've set
'forcesubmit' to 1), but I have to admit that I'm
absolutely no expert in this things.
So, if you know how to setup makenl to achieve this, just
tell me how to do it.
I suppose it's simpler that way if there are absolutely no
changes.
As I wouldn't have to change my setup, it would be :) (and
I have not heard from anyone that the 'problem' caused any
problems)
But I'm open for ideas.
Sysop: | MarisaG |
---|---|
Location: | South San Francisco, CA |
Users: | 5 |
Nodes: | 10 (0 / 10) |
Uptime: | 14:28:36 |
Calls: | 123 |
Files: | 36 |
Messages: | 30,630 |