I thought I'd box clever<g> and convert one of my existing message
areas from the proprietary AMF format to JAM.
Everything appeared fine until I exited and restarted APoint but the
area I'd converted was not showing any figures in the "Msgs" and "New" columns. After going into the area, all the messages were still there
but after going back to the area list, there were still no figures in
the "Msgs" and "New" columns. So, I converted the area back to AMF
format and now the figures are back in the "Msgs" and "New" columns.
Can anyone reproduce this?
I thought I'd box clever<g> and convert one of my existing message areas
from the proprietary AMF format to JAM.
How? Is that by the top menu option (A)reas, C(o)nvert, New Format?
I'm afraid to try it!
Everything appeared fine until I exited and restarted APoint but the
area I'd converted was not showing any figures in the "Msgs" and "New"
columns. After going into the area, all the messages were still there
but after going back to the area list, there were still no figures in
the "Msgs" and "New" columns. So, I converted the area back to AMF
format and now the figures are back in the "Msgs" and "New" columns.
Can anyone reproduce this?
Same result reproduced here.
..But there is nothing that can be done about it?
I thought I'd box clever<g> and convert one of my existing message
areas from the proprietary AMF format to JAM.
Everything appeared fine until I exited and restarted APoint..
I thought I'd box clever<g> and convert one of my existing message MF>>>> areas from the proprietary AMF format to JAM.
Everything appeared fine until I exited and restarted APoint..
I believe you were tackling a JAM format issue with Apoint back in
2003:
----[begin]----^^^^
From: Martin Foster
To: Russell Tiedt
Date: 2003-01-14 09:12:32
Subject: APoint
Yes it does BUT I'm sorry to say that it's flawed. APoint will handle
a JAM message base that APoint itself has created but if you hook up APoint to an already existing JAM message base created by another
program, it will read the message base just fine but it will not
write to it correctly. This has been a long-standing problem and I
hope the author(s) will fix it for the next release.
-!- Msged/BeOS 6.0.2
- Origin: Bitz-Box (2:250/501.2)
----[end]----
Was Apoint at 1.25 back then?
-!- Msged/BeOS 6.0.2^^^^
Wow, that brings back fond memories :-)
-!- Msged/BeOS 6.0.2^^^^
Wow, that brings back fond memories :-)
It has recently sprung back to life as Haiku:
"The open-source OS Haiku, a complete reimplementation of BeOS, is designed to start up where BeOS left off. Beta 1 of Haiku was released
in September 2018, 6 years after Alpha 4.[3]"
[3] = https://www.haiku-os.org/news/2018_09_28_haiku_r1_beta1/
Screenshots = https://www.haiku-os.org/slideshows/haiku-1
Looks impressive.
...but I digress, unless I say something like, "Are there any point programs that will run on Haiku?" :)
No there aren't but I do know for a fact that timEd was ported to BeOS
and obviously Msged. As for binkD and the husky stuff, I'm not sure
about those. If binkD and the husky stuff could be ported to BeOS and assuming they would all run on Haiku, a Point setup could be cobbled together: binkD + hpt + timEd or Msged ;)
No there aren't but I do know for a fact that timEd was ported to BeOS
and obviously Msged. As for binkD and the husky stuff, I'm not sure
about those. If binkD and the husky stuff could be ported to BeOS and
assuming they would all run on Haiku, a Point setup could be cobbled
together: binkD + hpt + timEd or Msged ;)
I got BinkD to build in Haiku R1 beta 1.
I haven't tried building Husky's HPT yet but it should be fine.
Most of the work for the BeOS port of BinkD had already been done years ago, but the build was failing for Haiku.
Here's the fix that I sent to the binkd-dev list:
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 248:42:51 |
Calls: | 2,090 |
Calls today: | 1 |
Files: | 11,141 |
Messages: | 948,974 |