@MSGID: 2:221/360 571827a5
@PID: Concord 0.01 Beta-30d OS/2 ser#cc38c58d
@TID: GE/2 1.2
@CHARSET: LATIN-1
Hi All,
I simple test with SemPoint (editor) + BW (transfer) @rbb.bbs
[1] This should be on a line/paragrph by itself.
[2] This line should *also* be on a line by itself.
../|ug
* SeM. 2.26 * Cleanliness is next to impossible.
--- Concord/2/BW 001B30d (Reg.)
* Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
SEEN-BY: 19/10 103/705 154/10 203/0 221/0 1 6 360 229/426 240/1120 5832 SEEN-BY: 280/464 5003 5555 310/31 396/45 423/120 712/848 770/1 2452/250 @PATH: 221/360 6 1 280/464
@MSGID: 2:221/360 571827a5
@PID: Concord 0.01 Beta-30d OS/2 ser#cc38c58d
@TID: GE/2 1.2
@CHARSET: LATIN-1
Hi All,
I simple test with SemPoint (editor) + BW (transfer) @rbb.bbs
[1] This should be on a line/paragrph by itself.
[2] This line should *also* be on a line by itself.
../|ug
* SeM. 2.26 * Cleanliness is next to impossible.
--- Concord/2/BW 001B30d (Reg.)
* Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
@PATH: 221/360 6 1 280/464
@MSGID: 2:221/360 571827a5
@PID: Concord 0.01 Beta-30d OS/2 ser#cc38c58d
@TID: GE/2 1.2
@CHARSET: LATIN-1
Hi All,
I simple test with SemPoint (editor) + BW (transfer) @rbb.bbs
[1] This should be on a line/paragrph by itself.
[2] This line should *also* be on a line by itself.
../|ug
* SeM. 2.26 * Cleanliness is next to impossible.
--- Concord/2/BW 001B30d (Reg.)
* Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)
SEEN-BY: 19/10 203/0 221/0 1 6 360 240/1120 280/464 5003 5555
@PATH: 221/360 6 1
@MSGID: 2:221/360 571827a5
@PID: Concord 0.01 Beta-30d OS/2 ser#cc38c58d
@TID: GE/2 1.2
@CHARSET: LATIN-1
Hi All,
No TZUTC kludge. ;-)
I simple test with SemPoint (editor) + BW (transfer) @rbb.bbs
[1] This should be on a line/paragrph by itself.
[2] This line should *also* be on a line by itself.
No TZUTC kludge. ;-)
Noted! Sadly, last SemPoint v2.26 = 12-04-1999, which seems to predate the suggestion in ftsc 4008.002 in year 2003/2005 :(
On 06/05/2019 11:31 a.m., Tommi Koivula : August Abolins wrote:the
@MSGID: 2:221/360 571827a5
@PID: Concord 0.01 Beta-30d OS/2a ser#cc38c58d
@TID: GE/2 1.2
@CHARSET: LATIN-1
Hi All,
No TZUTC kludge. ;-)
Noted! Sadly, last SemPoint v2.26 = 12-04-1999, which seems to predate
suggestion in ftsc 4008.002 in year 2003/2005 :(
I simple test with SemPoint (editor) + BW (transfer) @rbb.bbs
[1] This should be on a line/paragrph by itself.
[2] This line should *also* be on a line by itself.
Very curious, this message processed by Concord looks OK to me.
Is it possible to use a different editor with SemPoint? I wonder if that would work better or not?
Very curious, this message processed by Concord looks OK to me.
YES.. it does! :) This means that something is different is happening on your system.
Is it possible to use a different editor with SemPoint? I wonder if that
would work better or not?
I can trigger an external editor, but I really doubt that's the source of the problem. rbb.bbs handles the BW packet fine.
I can crashmail a reply BW packet for your system to you a little later.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495929:22:07 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,852 |