On 2019 Feb 07 17:49:30, you wrote to All:

Anyone have an updated version of the TP code from Joaquim? I found HUSKY has added a field in the first 4 bytes of the base header's reserved - for HighWaterMark for the scanner.

you should ask joho in the FD echo ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Short Books: Why People Are More Important Than Animals, by Greenpeace.
---
* Origin: (1:3634/12.73)

Hello Joacim.

10 Feb 19 14:39, you wrote to me:

Hello everybody.

Maybe you should ask him in the FD echo. Or send an email to him?

Already have - however, he's not the one going around making modifications for other people's software --- this is why I ask here. To find if there are MODs and to also in a subtle way let people know, I am collecting and merging them into a new release. You know, how Pascal developers communicate...

Ozz

--- FMail-W32 2.0.1.4
* Origin: Richmond VA (RVA) Fidonet Support (1:275/362)

Hello mark.

10 Feb 19 12:31, you wrote to me:

On 2019 Feb 07 17:49:30, you wrote to All:

Anyone have an updated version of the TP code from Joaquim? I
found HUSKY has added a field in the first 4 bytes of the base
header's reserved - for HighWaterMark for the scanner.

you should ask joho in the FD echo ;)

Snorting! I cannot believe you would say such a reply. Since, I know based upon else echo content, you have a modified MKMSGJAM. :-/


Ozz

--- FMail-W32 2.0.1.4
* Origin: Richmond VA (RVA) Fidonet Support (1:275/362)

On 2019 Feb 11 13:54:48, you wrote to me:

Anyone have an updated version of the TP code from Joaquim? I found
HUSKY has added a field in the first 4 bytes of the base header's
reserved - for HighWaterMark for the scanner.

you should ask joho in the FD echo ;)

Snorting! I cannot believe you would say such a reply. Since, I know
based upon else echo content, you have a modified MKMSGJAM. :-/

hahahaha! yes, that library was written by Mark May back in the day... my modifications to it only fixed bugs and opened some data that was inaccessible...

bugs like using only hours:minutes:00 for the time when the message base could easily store the whole hours:minutes:seconds form of time without even rounding the seconds to multiples of two... squish has this limitation because it uses the DOS file time stamp stuff which rounds the seconds... JAM doesn't have it...

another example would be certain control lines that were not being properly allowed/stored...

the biggest example may be my MSGID code but it is separate and i simply called it and then fed the results to the control line code when writing the MSGID to the message...

i never did anything with using the MKSMG106 code to read and reply to messages... i only ever generated new messages with it...

i probably should see if i can find my original MKSMG106 archive and do a diff of it against my modified code to see what i really changed in it... it wasn't much but it brought the code more into line with the RA/FD/FE implementations as well as with the JAMAPI code released by joe and company...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Never use duct tape as a major design component in any mech. system.
---
* Origin: (1:3634/12.73)

On 2019-02-12 16:15:48 +0000, mark lewis -> Ozz Nixon said:

the biggest example may be my MSGID code but it is separate and i
simply called it and then fed the results to the control line code when writing the MSGID to the message...

Could you share your MSGID logic? Does it guarantee no dupe for 3 years per echo? Instead of coding something original, I would like to "borrow" it ;-)

Ozz

--- FMail-W32 2.0.1.4
* Origin: Modern Pascal, LLC. (1:275/362.0)

On 2019 Feb 18 18:06:18, you wrote to me:

the biggest example may be my MSGID code but it is separate and i
simply called it and then fed the results to the control line code when
writing the MSGID to the message...

Could you share your MSGID logic? Does it guarantee no dupe for 3
years per echo? Instead of coding something original, I would like to "borrow" it ;-)

i am willing to do that but have a few things to consider first... however, there is a FTSC document, written by another, that provides much the same logic... a document which was written i'm guessing maybe a decade after my implementation... my implementation was written based on another older logic description given in the NET_DEV echo back in the 90s IIRC... i still have that original message around here somewhere, too... i did make a few changes to the logic but that was after seeing it in operation for a while... and yes, the code stood for at least three years before i released it to anyone else for use ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... The future belongs to those who believe in the beauty of their dreams.
---
* Origin: (1:3634/12.73)