Digital Man wrote to All <=-
binkit.ini and ftn_domains.ini have been deprecated and their settings moved to sbbsecho.ini.
If you are using ftn_domains.ini or binkit.ini, when you upgrade to the latest .js files from CVS, you'll need to merge your ftn_domains.ini with sbbsecho.ini. If you have a binkit.ini file, then run "jsexec binkit upgrade". This is performed for you automatically if/when you run "jsexec update".
Re: ftn_domains.ini and binkit.ini
By: Digital Man to All on Sat Mar 31 2018 12:49:55
Hi Digital Man
If you are using ftn_domains.ini or binkit.ini, when you upgrade to the latest .js files from CVS, you'll need to merge your ftn_domains.ini with sbbsecho.ini. If you have a binkit.ini file, then run "jsexec binkit upgrade". This is performed for you automatically if/when you run "jsexec update".
I have updated the latest binkit.js 2.00 and id there js that I have to update and I have ran jsexec binkit update/jsexec update and I hope it has done right , ctrl/binkit.ini.old ctrl/ip-domains.ini.old which it fine
but when I run the control panel and run force time event it says cannot open binkit.ini so made another copy ctrl/binkit.ini untill I here from you as I don't now what else to do.
binkit.ini and ftn_domains.ini have been deprecated and their settings moved to sbbsecho.ini.
This was done because:
1. there was a lot of redundancy between binkit.ini and sbbsecho.ini: e.g. each
[node:] section in sbbsecho.ini was repeated a link section in binkit.ini. 2. though SBBSecho v3 could use ftn_domains.ini (for zone->domain/outbound_dir
mapping), the file was not configurable using echocfg.
3. when supporting sysops, I had to ask for all 3 .ini files to get an idea of
their configuration settings. Now I only need to ask for one.
4. BinkIT and SBBSecho can now be fully configured without hand-editing any
.ini files and closely-related settings (e.g. packet password and session
password) are now visible near each other.
If you are using ftn_domains.ini or binkit.ini, when you upgrade to the latest .js files from CVS, you'll need to merge your ftn_domains.ini with sbbsecho.ini. If you have a binkit.ini file, then run "jsexec binkit upgrade". This is performed for you automatically if/when you run "jsexec update".
If you do *not* have a binkit.ini, but you do have an ftn_domains.ini, then you can hand-merge ftn_domains.ini into your sbbsecho.ini, like this:
Example, from ftn_domains.ini:
[fidonet]
Zones=1,2,3,4,5,6
DNSSuffix=binkp.net
[fsxnet]
Zones=21
to sbbsecho.ini (copy and paste and add the "domain:" prefixes):
[domain:fidonet]
Zones=1,2,3,4,5,6
DNSSuffix=binkp.net
[domain:fsxnet]
Zones=21
I hope you all like the improved ease-of-use.
says cannot open binkit.ini so made another copy ctrl/binkit.ini
untill I here from you as I don't now what else to do.
Sounds like you didn't didn't update exec/load/*.js?
Re: ftn_domains.ini and binkit.ini
By: Digital Man to Sneaky on Sat Mar 31 2018 16:53:49
Hi Digital Man
says cannot open binkit.ini so made another copy ctrl/binkit.ini
untill I here from you as I don't now what else to do.
Sounds like you didn't didn't update exec/load/*.js?
Okay got you,update all exec/load/*.js and now back working
thank you for that
just another question if you don't mind,
!04/1 04:08:54p Timed out receiving packet data!
On one of my link
is there a setting for this or is it just between
me and my link or internet connection.
just another question if you don't mind,
!04/1 04:08:54p Timed out receiving packet data!
On one of my link
is there a setting for this or is it just between
me and my link or internet connection.
Most likely the behavior of the remote/link's mailer isn't in-line with the binkp.js expectations, but it should still work. What
mailer/version is that link using?
Hi Digital Man
just another question if you don't mind,
!04/1 04:08:54p Timed out receiving packet data!
On one of my link
is there a setting for this or is it just between
me and my link or internet connection.
Most likely the behavior of the remote/link's mailer isn't in-line with the binkp.js expectations, but it should still work. What mailer/version is that link using?
My link has Tauris not sure of version probably the latest.
as per messages via Al, should I change [3:770/330@fidonet] to
[3:770/330] or just leave it.
Re: Re: ftn_domains.ini and binkit.ini
By: Ian Segers to Digital Man on Mon Apr 02 2018 10:45 am
My link has Tauris not sure of version probably the latest.
The mailer's version number should be reported by the remote side
during BINKP session. Like this:
Peer version: Radius/4.010/21.01.2005,13:56(Final-Release)/Win32 binkp/1.1
as per messages via Al, should I change [3:770/330@fidonet] to
[3:770/330] or just leave it.
Just leave it if its working.
Hi Digital Man
Re: Re: ftn_domains.ini and binkit.ini
By: Ian Segers to Digital Man on Mon Apr 02 2018 10:45 am
My link has Tauris not sure of version probably the latest.
The mailer's version number should be reported by the remote side during BINKP session. Like this:
Peer version: Radius/4.010/21.01.2005,13:56(Final-Release)/Win32 binkp/1.1
sorry no it doesn't, not on this link but I do see all the Peer version
on my other links, is there same were else I am meant to look sbbs.ini
logs set at debugging.
as per messages via Al, should I change [3:770/330@fidonet] to
[3:770/330] or just leave it.
Just leave it if its working.
ok, I leave it as is thank you
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495932:53:56 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,910 |