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?
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.
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.
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)
All my nodelist networks send new files with uppercase
filenames, only tqwNet uses lowercase.
(Whereas NODELIST.### has [x] Update as diff)
(Whereas NODELIST.### has [x] Update as diff)
But, I cannot find that setting to turn OFF the "Update as
diff". Where is it?
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.
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!
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.
(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?
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.
..It *does* look like you may have discovered a bug.
Okay. Who should I report it to?
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
(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?
..It *does* look like you may have discovered a bug.
Okay. Who should I report it to?
The official destination is XPOINT echo
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.
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.
The official destination is XPOINT echo
Errrrrrrm, did I miss something ???????
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ 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? :)
"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>.
Z2PNT.### 064 Z2PNT.### Z2PNT.Z## FD-Pointliste^^^^^^^^^ ^^^^^^^^^
Did you know there's a weekly DIFF for the Z2 Pointlist:
Z2PNT_D.### Z2PNT_D.Z##
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.
The English help text doesn't make it any clearer, in fact, it clouds the issue even further <sigh>.
The official destination is XPOINT echoErrrrrrrm, did I miss something ???????
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.
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.
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
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 ³
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)
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.
"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".
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.
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? :)
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.
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.
³ [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?
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 :-/
³ 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?
Something like these might be better:
"Process DIFF files"
"Process DIFF updates"
"Enable DIFF processing"
Hmmmm, dunno, this is a tricky one.
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.
"...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"..
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.
Maybe together with my uppercase/lowercase nodelist update problem? :)
Yep.
Thank you very much!
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!
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.
³ [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.
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"
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?
"...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?
Good to see you pop in.
Been suffering from a bad case of the "Winter Blues"..
(Reply forthcoming in netmail)
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.
³ [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) .....
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 :-))
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.
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
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?
What and where is fido.txt?
The FidoNet documentation file of OpenXP :)
You can find it in /usr/local/lib/openxp/doc
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'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!
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.
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.
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 :)
What and where is fido.txt?
The FidoNet documentation file of OpenXP :)
You can find it in /usr/local/lib/openxp/doc
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.
Just to clarify the situation, I can/will update the English help text
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).
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 :-?
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.
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
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?
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,
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
:)
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?
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 versionI also registered it and I still have my licence key :)
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.
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.
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 :)
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.
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/2Nice :)
system like mine was ~20 years ago :)
Have you looked at ArcaOS?
BTW ..... I crashed a netmail to you this morning, have you seen it?
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.
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.
Nice idea, are you volunteering :-))
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 :)
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?
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.
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?
I'm asking because I tried it out with a short paragraph
and it came out looking like a dog's dinner.
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.
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.
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 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!
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.
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.
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.
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.
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 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?
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 :)
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 :)
[...]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.
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 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.
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.
What good is all that old stuff?
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".
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 am all FOR enjoying ftn tech on slightly newer machines. ;)
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
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.
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".
Was your test with DeepL?
Yes it was.
What paragraph did you test?
Here is section I.0
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?
I even have a copy of the book OS/2 2.1 Unleashed.
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 :))
Here is section I.0
Yes, very nice :)
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).
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?
Oh.. and one person is designated as managing and releasing the
final "master" copy?
Yes, there would need to be a project coordinator.
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 :)
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?
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.
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.
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.
To get started I would need to get an earlier version of
tortoisesvn that supports XP.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 54:47:55 |
| Calls: | 6,650 |
| Calls today: | 2 |
| Files: | 12,200 |
| Messages: | 5,330,629 |