Can anyone who has the message base well documented, submit the
missing proposal (or empty one)?
Can anyone who has the message base well documented, submit the missing proposal (or empty one)?
And would it make sense, for me to submit JAM also?
So it is atleast somewhere in the FTSC docs ;-)
On 2019 Feb 17 20:43:48, you wrote to All:
Can anyone who has the message base well documented, submit the missing proposal (or empty one)?
And would it make sense, for me to submit JAM also?
So it is atleast somewhere in the FTSC docs ;-)
it was discussed some time back (maybe 10-15 years?) but decided against since they are not FTN related... they are specific to message storage which can be done in any format and is not required for FTN participation...
it was discussed some time back (maybe 10-15 years?) but decided
against since they are not FTN related... they are specific to
message storage which can be done in any format and is not required
for FTN participation...
FOSSIL isn't required for FTN participation either, yet it's an FSC document. <shrug>
On 2019 Feb 18 14:16:04, you wrote to me:
it was discussed some time back (maybe 10-15 years?) but decided
against since they are not FTN related... they are specific to
message storage which can be done in any format and is not required
for FTN participation...
FOSSIL isn't required for FTN participation either, yet it's an FSC document. <shrug>
it was at one time because that was the only way to have the software be able to run on multiple platforms with widely differing serial port methodologies...
there was also a video fossil (aka VFOSSIL) used due to differing video methodologies... MSG is also documented and not required...
i actually liked the idea of having the message base formats and detailed information on how they worked in the library but... that discussion was back when odin, colin or scott were the chair... i'm fairly sure it was before scott... i don't have a problem adding them to the /reference/ library... it is
a bit late in the game, though...
17 Feb 19 20:43, Ozz Nixon wrote to All:
ON> Can anyone who has the message base well documented, submit the
ON> missing proposal (or empty one)?
It is a work in progress... FSP-1037.
Last we heard from Stas, It isn't ready yet. I've got a draft copy.
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
[...] and I know Squish is limited to 9 deep on the reply chain.
Great... I know it has been a work in progress for the past 2 years,
thus, I spoke up. I have my JAMAPI coded, now I am working on my
Squish implementation. Also have my Hudson, Goldbase, Renegade,
PCBoard implementations finished. Looking at Squish and Adept to wrap
up this month... and then stress test FMTP which each format. HMB and
GB have obvious limitations, JAM is much like PCBoard (since PCB is
older), and I know Squish is limited to 9 deep on the reply chain.
You should not bother with Adept - it has been abandoned more than 10 years.
More importantly 2/3 differing distributions have vanished.
It was only for OS/2.
Hello Vince.
20 Feb 19 16:04, you wrote to Ozz Nixon:
You should not bother with Adept - it has been abandoned more
than 10 years.
Once I have time, I have Andy Roberts' full AdeptXBBS filebase and
will put it online. He had stuff I didn't know existed.
More importantly 2/3 differing distributions have vanished.
It was only for OS/2.
Orion is still around and is open source.
But to untangle the mess that is Adept/Orion, you'd have to have a lot
of time and a deep knowledge of all things OS/2. Gatekeeper,
Adept/Orion's message tosser, is an unmitigated mess.
Orion is still around and is open source.
But to untangle the mess that is Adept/Orion, you'd have to have a lot
of time and a deep knowledge of all things OS/2. Gatekeeper,
Adept/Orion's message tosser, is an unmitigated mess.
The progress of OS/2 since then from both sides of the pond has not changed other than changes to drivers and most of that was via the
OS/2 community so I refused to remotely consider paying silly money
for a subscription for the so-called newer versions.
I and a few others offered to IBM to extract the Windows code base
from Warp 4.52 and update it for modern CPUs including 32 and 64 bit operations but they ignored us.
My attitude after such response was to migrate away from it - pity it
was a good system but just has not kept up with newer technology so my decision to more away has proven valid.
Luckily my mainframe on a stick work does NOT require the use of OS/2
and Linux works well as does a Windows platform when pushed.
document. <shrug>it was discussed some time back (maybe 10-15 years?) but decided
against since they are not FTN related... they are specific to
message storage which can be done in any format and is not
required for FTN participation...
FOSSIL isn't required for FTN participation either, yet it's an FSC
it was at one time because that was the only way to have the software be able to run on multiple platforms with widely differing serial port methodologies... there was also a video fossil (aka VFOSSIL) used due to differing video methodologies... MSG is also documented and not required...
i actually liked the idea of having the message base formats and detailed information on how they worked in the library but... that discussion was back when odin, colin or scott were the chair... i'm fairly sure it was before scott... i don't have a problem adding them to the /reference/ library... it is a bit late in the game, though...
Can anyone who has the message base well documented, submit the missing proposal (or empty one)?
And would it make sense, for me to submit JAM also?
So it is atleast somewhere in the FTSC docs ;-)
Hello Ozz!
Monday February 18 2019 12:31, you wrote to Fred Riccio:
You should not bother with Adept - it has been abandoned more than 10 years.
More importantly 2/3 differing distributions have vanished.
It was only for OS/2.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,040 |
Nodes: | 15 (0 / 15) |
Uptime: | 213:11:20 |
Calls: | 500,251 |
Calls today: | 20 |
Files: | 95,199 |
D/L today: |
5,850 files (984M bytes) |
Messages: | 464,239 |
Posted today: | 1 |