Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 06:16:32 |
| Calls: | 12 |
| Files: | 12,929 |
| Messages: | 98,371 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
Currently, when I try to enter the game from the BBS, I get the follo error,
"Sorry, the game is currently in use. Please try again later."
Yep I had that also, look for inuse.flg in the dir, and remove it, then try, all should be good :)
believe) regional independant nodes in region 1, 2, 3 and 4. In the seen by lines I see 0/??? node numbers (I'll post an example below that I cut
folloCurrently, when I try to enter the game from the BBS, I get the
error,
"Sorry, the game is currently in use. Please try again later."
Yep I had that also, look for inuse.flg in the dir, and remove it, then try, all should be good :)
Currently, when I try to enter the game from the BBS, I get the error,
"Sorry
Everything checks out fine, so as far as I can tell there is nothing amiss with Mystic nor fsxNet.
Happy to look at anything you need.
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113
114 115
@SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131
133 134
@SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149
150 151
@SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166
167 168
@SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185
186 187
@SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100
4/100
well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133
well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:
well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:
Ah. Thanks, is there someone in the specs for this in FTN land that you can point me to the requirement? When Al or I flag this with James it would be helpful to be able to point him to it.
well, there's the problem... there must be a net on the first address
of each line... if they are all in net1, it should look like this:
Ah. Thanks,
is there someone in the specs for this in FTN land that you can point
me to the requirement? When Al or I flag this with James it would be helpful to be able to point him to it.
I took a look at another post from a node in fsxNet and indeed there
are no NET lines stated at the start of each SEEN-BY
It's the first time it seems to have been an issue for anyone/system though.
This is not an area of expertise for me but I went looking for info on the fstc.org site and found this
[snip]
There does not seem to be any reference to requiring that NET be displayed at the start of each SEEN-BY line
- perhaps I should be looking at another reference doc?
[snip]
From: nristen
To: Avon
Subj: Re: Galactic Dynasty
Date: 03/30/19 13:05
Base: FSX_GEN
@TID: Mystic BBS 1.12 A42
@MSGID: 21:1/161 2ea3e523
@REPLY: 21:1/101 5356aee7
@TZUTC: -0400
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/100
The problem as I see it is that the net needs to be specified at the beginning of each line to indicate which net the following nodes belong in. Until a new or different net is specified. The same principle is
true and used in the setup of many pieces of FTN software.
I would surmise that the Seen-By lines are not looked at as one
continuous line but as separate sequential lines. And therefor the net specification would need to be specified at the beginning of each line.
I have sought clarification in the FTSC echo in an attempt to find some
documentation that confirms this. Perhaps it's a case of some FTN
software looks for this whilst others do not?
you mean FTSC_PUBLIC, right? there is a FTSC echo but it is limited
no, the seenby lines have been done like that ever since they were introduced...