Can anyone point me somewhere that will tell me what 000ffe8 in FIDO HEXconverts to?
Also, please don't point me to sbbs echo config as the values it is givinglisting with the linked nodes do not match anything in my outbound.
Which brings me to why I am posting the message here. There is adiscrepancy between the HEX value that sbbs echo config presents and the value that sbbsecho uses to create the packets. :) For example, it lists all of
the 618:250/* nodes I connect with as starting with 00fa00 yet, in theoutbound directory, all of the packets start with 0000ff.
I thought they were supposed to match so maybe I am mistaken?
Can anyone point me somewhere that will tell me what 000ffe8 in FIDO HEX converts to?
Yes, I know some smarty pants is going to say "FIDO HEX is
HEX" but the translators on the web don't know what to do with it so I don't think so. Also, please don't point me to sbbs echo config as the values it is giving listing with the linked nodes do not match anything in my outbound.
Which brings me to why I am posting the message here. There is a discrepancy between the HEX value that sbbs echo config presents and the value that sbbsecho uses to create the packets. :)
For example, it lists
all of the 618:250/* nodes I connect with as starting with 00fa00 yet, in the outbound directory, all of the packets start with 0000ff.
I thought they were supposed to match so maybe I am mistaken?
you're a digit short... there should be 8 of them... so i don't know if that's >supposed to be 0000ffe8 (0/65512) or 000ffe80 (15/65152) or 000f0fe8 (15/4072) >or something else...
it certainly should for the ?lo and ?ut files...
you are mistaken... the ?lo and ?ut files are the ones that follow the XXXXYYYY
hex format... mail bundles can also but PKTs cannot really follow this naming >convention... this is why they are listed inside the ?lo files... same with >TICs and their associated files...
It depends on the context. Which file or directory name are you referring to? And you only provided 7 digits... so are you missing something there?
EchoMail Packet filenames don't use hexadecimal encoding of the destination add
ess. Perhaps you're thinking of bundles?
Not necessarily. Here's the reference for FidoNet filenaming: http://wiki.synchro.net/ref:fidonet_files
It depends on the context. Which file or directory name are you referring to? And you only provided 7 digits... so are you missing something there?
Sorry, typo, 0000ffe8. :)
EchoMail Packet filenames don't use hexadecimal encoding of the destination add
ess. Perhaps you're thinking of bundles?
Bundles. Like, 0000ffe8.SU0 containing multiple PKT files.
Not necessarily. Here's the reference for FidoNet filenaming: http://wiki.synchro.net/ref:fidonet_files
OK, thanks!
you're a digit short... there should be 8 of them... so i don't know if
that's supposed to be 0000ffe8 (0/65512) or 000ffe80 (15/65152) or
000f0fe8 (15/4072) or something else...
It was 4 leading zeroes... 0/65512 does not really translate to anything useful. :)
it certainly should for the ?lo and ?ut files...
Unfortunately, I did not see any of them.
you are mistaken... the ?lo and ?ut files are the ones that follow the
XXXXYYYY hex format... mail bundles can also but PKTs cannot really follow
this naming convention... this is why they are listed inside the ?lo
files... same with TICs and their associated files...
It was bundles not PKTs.
It is confusing because the bundles are always named the same before
the '.' for each individual node so my assumption was that it should translate to something.
The issue is moot now. Figured out the issue and the node is getting
mail now. FWIW, all of the 0000ffe8 packets go to node 250/25.
A bundles are named with the hexadecimal *difference* between the source and de
tination net and node. So "0000" for the net means "no difference", so both the
source and destination are the same network.
The issue is moot now. Figured out the issue and the node is getting mail now. FWIW, all of the 0000ffe8 packets go to node 250/25.
excellent!
i was looking for a link to the origina BSO definitely/explanation but hadn't found anything that is easily understood... i did find this link in the wiki which is pretty straight forward regarding how bundles are named...
http://wiki.synchro.net/ref:fidonet_files
A bundles are named with the hexadecimal *difference* between the source and de
tination net and node. So "0000" for the net means "no difference", so both the
source and destination are the same network.
Similarly, then, the ffe8 in the last four of the string is the difference between the two node numbers (in this case, 1 and 25)?
Right. If you enter ffe8 into a hex calculator (e.g. https://www.rapidtables.co
/convert/number/hex-to-decimal.html) it'll report that value as -24 decimal (as
a signed 16-bit integer).
Right. If you enter ffe8 into a hex calculator (e.g. https://www.rapidtables.co
/convert/number/hex-to-decimal.html) it'll report that value as -24 decimal (as
a signed 16-bit integer).
Hmmmm, I put the whole string... 0000ffe8.... into an online hex converter and it returned mostly garbage characters. I did that before I asked here.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 20:42:46 |
| Calls: | 2,011 |
| Calls today: | 1 |
| Files: | 11,117 |
| Messages: | 944,013 |