I just noticed that viewing of ARJ archives, and FILE_ID.DIZ imports
from ARJ archives, doesn't seem to work in my installation of Mystic.
@TID: Mystic BBS 1.12 A46
@MSGID: 21:2/123 bc5182ab
@REPLY: 21:1/202 8819ac6a
@TZUTC: -0600
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 109 110 111 112 114 115
116 117
@SEEN-BY: 1/118 119 121 122 123 124 125 126 127 128 129 130 131 133 134 135 136
@SEEN-BY: 1/137 138 140 141 143 144 145 146 147 150 151 152 153 154 155 156 157
@SEEN-BY: 1/158 159 160 161 162 163 164 165 166 167 168 169 171 172 173 174 176
@SEEN-BY: 1/177 178 180 181 183 184 185 186 187 188 189 190 193 194 195 198 199
@SEEN-BY: 1/200 201 202 203 204 208 209 211 212 213 995 999 2/100 101
103 104
@SEEN-BY: 2/105 106 107 108 109 110 111 112 113 114 115 116 118 119 120 1202
@SEEN-BY: 2/123 124 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140
@SEEN-BY: 2/141 142 144 145 147 148 150 151 152 154 155 156 158 159 160 161 162
@SEEN-BY: 2/163 164 165 166 167 3/100 4/100 5/100
@PATH: 2/123 100 1/100
121
I just noticed that viewing of ARJ archives, and FILE_ID.DIZ imports from ARJ archives, doesn't seem to work in my installation of Mystic.
121
I just noticed that viewing of ARJ archives, and FILE_ID.DIZ imports
from ARJ archives, doesn't seem to work in my installation of Mystic.
Notice the 121 ...
Not sure why. I should probably update the HUBS to the latest Mystic to negate some bug that could be in a pre-alpha still running.
Not sure why. I should probably update the HUBS to the latest Mystic to negate some bug that could be in a pre-alpha still running.
@MSGID: 21:4/106.1 d3690b73
@REPLY: 21:1/101 ebb9930d
@PATH: 4/106 100 1/100
100
That might be a good idea. Do you see a number on my post?
Hub 4 has already been updated and it running the official release. I forgot to send a message stating that...
On 16 Sep 2020 at 02:15a, Al pondered and said...
@MSGID: 21:4/106.1 d3690b73
@REPLY: 21:1/101 ebb9930d
@PATH: 4/106 100 1/100
100
That might be a good idea. Do you see a number on my post?
Yep, I've abridged the quoting of kludges but 100 was on display, if it was a score then you did great!
100
That might be a good idea. Do you see a number on my post?
Yep, I've abridged the quoting of kludges but 100 was on display, if was a score then you did great!
Interestingly, I dont see the numbers.
Must be another feature of Mystic - being able to see secret scores of some kind :)
121
Re: Re: ARJ not working?
By: Avon to Al on Thu Sep 17 2020 12:13 pm
On 16 Sep 2020 at 02:15a, Al pondered and said...
@MSGID: 21:4/106.1 d3690b73
@REPLY: 21:1/101 ebb9930d
@PATH: 4/106 100 1/100
100
That might be a good idea. Do you see a number on my post?
Yep, I've abridged the quoting of kludges but 100 was onwas a score then you did great!
display, if it
Interestingly, I dont see the numbers.
My copy of the message (on this occassion came via Hub 2):
X-FTN-MSGID 21:4/106.1 d3690b73
X-FTN-REPLY 21:1/101 ebb9930d
X-FTN-PATH 4/106 100 2/100
I just looked on Hub 3 - and Hub 3 got it from 4/100, but not rogue
"100" to be seen..
Must be another feature of Mystic - being able to see secret scores
of some kind :)
..____
.. A good man dies when a boy goes wrong.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
Notice the 121 ...
Not sure why. I should probably update the HUBS to the latest Mystic to negate some bug that could be in a pre-alpha still running.
Yeah, now that you mention it have seen that on some replies I have seen but I didn't connect any dots.
Not sure why. I should probably update the HUBS to the latest Mystic to negate some bug that could be in a pre-alpha still running.
That might be a good idea. Do you see a number on my post?
SEEN-BY: 2/116 118 119 120 1202 121 123 124 126 127 128 129 130 131 132 133 >SEEN-BY: 2/135 136 137 138 139 140 141 142 144 145 147 148 150 151 152 154 155 >SEEN-BY: 2/156 158 159 160 161 162 163 164 165 166 167 3/100 4/100
PATH: 2/136 100
MSGID: 21:2/136 281ee3e5
TZUTC: -0500
134
SEEN-BY: 2/105 106 107 108 109 110 111 112 113 114 115 116 118 119 120 1202 >SEEN-BY: 2/123 124 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 >SEEN-BY: 2/141 142 144 145 147 148 150 151 152 154 155 156 158 159 160 161 162 >SEEN-BY: 2/163 164 165 166 167 3/100 4/100 5/100--- SBBSecho 3.11-Linux
PATH: 1/100 2/100
121
I've checked the ones I've spotted against the headers for each message and there seems to be a pattern. Each number would "fit in" where a node number is missing at the end of a seen-by kludge. The line also contains
a variable quantity of whitespace after the number.
eg:
[snip]
SEEN-BY: 2/116 118 119 120 1202 121 123 124 126 127 128 129 130 131 132 1 >SEEN-BY: 2/135 136 137 138 139 140 141 142 144 145 147 148 150 151 152 15 >SEEN-BY: 2/156 158 159 160 161 162 163 164 165 166 167 3/100 4/100
PATH: 2/136 100
MSGID: 21:2/136 281ee3e5
TZUTC: -0500
134
[snip]
SEEN-BY: 2/105 106 107 108 109 110 111 112 113 114 115 116 118 119 120 12 >SEEN-BY: 2/123 124 126 127 128 129 130 131 132 133 134 135 136 137 138 13 >SEEN-BY: 2/141 142 144 145 147 148 150 151 152 154 155 156 158 159 160 16 >SEEN-BY: 2/163 164 165 166 167 3/100 4/100 5/100
PATH: 1/100 2/100
121
I've checked the ones I've spotted against the headers for each message and there seems to be a pattern. Each number would "fit in" where a node number is missing at the end of a seen-by kludge. The line also contains a variable quantity of whitespace after the number.
SEEN-BY: 2/116 118 119 120 1202 121 123 124 126 127 128 129 130 131 132 133 >SEEN-BY: 2/135 136 137 138 139 140 141 142 144 145 147 148 150 151 152 154 155
Seen-by:[snip]
2/116 118 119 120 1202 121 123 124 126 127 128 129 130 131 132 133 134--- SBBSecho 3.11-Linux
I've checked the ones I've spotted against the headers for each message and >> there seems to be a pattern. Each number would "fit in" where a node number >> is missing at the end of a seen-by kludge. The line also contains a variable >> quantity of whitespace after the number.
Yep, no issues on my BBBS. No problems on my own Mystic 1.12 A46
Linux/64 also. That makes me wonder if it is a windows issue but I have
no windows to take a closer look.
Yep, no issues on my BBBS. No problems on my own Mystic 1.12 A46 Linux/64 also. That makes me wonder if it is a windows issue but I ha no windows to take a closer look.
I don't think it's Windows-dependent.
vvvvvvvvvv
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
This thread was hijacked! :)Yep, no issues on my BBBS. No problems on my own Mystic 1.12 A46 Linux/64 also. That makes me wonder if it is a windows issue but
This thread was hijacked! :)
What happened to original post this thread was asking about? Anyone answer why
ARJ is not working on Mystic?
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 90 |
Nodes: | 16 (0 / 16) |
Uptime: | 08:16:33 |
Calls: | 5,073 |
Calls today: | 5 |
Files: | 8,491 |
Messages: | 352,800 |