Hi all - This is a new message area for the discussion of the Perl programming language. I hope you find it useful.I definitely have to re-learn perl. But on another note, you do realize
But on another note, you do realize
that according to your CONTROL.DAT, your developernet and WEN nets both share The same index numbers. (3000+)
But on another note, you do realize
that according to your CONTROL.DAT, your developernet and WEN nets bo share The same index numbers. (3000+)
No they don't. My WEN conference numbers are dynamically generated on my so they won't share the same numbers. And I don't host WEN; I just re-add WEN to my BBS the other day.
No they don't. My WEN conference numbers are dynamically generated
on my so they won't share the same numbers. And I don't host WEN; I
just re-add WEN to my BBS the other day.
Downloads your BBS's .qwk packet. unzip it into its own directory. The control.dat will have a list of all conferences and the numbers of those conferences on your BBS. Look at it, and you'll see that the conference numbers for the develoment are set at 3000 and up, as well as the wen echos are 3000 and up. Look in your message settings and see if your conference numbers for development are set to 3000+, and then check the wen to see if they're set to dynamic. If so, they'll automatically be setup to 3000+, because it's the 3rd conference set.
I double-checked my Synchronet configuration yesterday, and my DeveloperNe areas are statically set to 3000+ and my WEN areas were set to dynamic numbering.
I double-checked my Synchronet configuration yesterday, and my
DeveloperNe areas are statically set to 3000+ and my WEN areas were
set to dynamic numbering.
The WEN areas just disappeared from the control.dat file.
Hi all - This is a new message area for the discussion of the Perl programming language. I hope you find it useful.I definitely have to re-learn perl. But on another note, you do realize
But on another note, you do realize
that according to your CONTROL.DAT, your developernet and WEN nets both share The same index numbers. (3000+)
But on another note, you do realize
that according to your CONTROL.DAT, your developernet and WEN nets bo share The same index numbers. (3000+)
No they don't. My WEN conference numbers are dynamically generated on my so they won't share the same numbers. And I don't host WEN; I just re-add WEN to my BBS the other day.
No they don't. My WEN conference numbers are dynamically generated
on my so they won't share the same numbers. And I don't host WEN; I
just re-add WEN to my BBS the other day.
Downloads your BBS's .qwk packet. unzip it into its own directory. The control.dat will have a list of all conferences and the numbers of those conferences on your BBS. Look at it, and you'll see that the conference numbers for the develoment are set at 3000 and up, as well as the wen echos are 3000 and up. Look in your message settings and see if your conference numbers for development are set to 3000+, and then check the wen to see if they're set to dynamic. If so, they'll automatically be setup to 3000+, because it's the 3rd conference set.
I double-checked my Synchronet configuration yesterday, and my DeveloperNe areas are statically set to 3000+ and my WEN areas were set to dynamic numbering.
I double-checked my Synchronet configuration yesterday, and my
DeveloperNe areas are statically set to 3000+ and my WEN areas were
set to dynamic numbering.
The WEN areas just disappeared from the control.dat file.
Sysop: | Gate Keeper |
---|---|
Location: | Shelby, NC |
Users: | 745 |
Nodes: | 20 (0 / 20) |
Uptime: | 60:50:09 |
Calls: | 10,642 |
Calls today: | 8 |
Files: | 5,288 |
D/L today: |
135 files (38,976K bytes) |
Messages: | 501,020 |