Does anybody know if Binkleyterm can still be registered these days? I would like to register my copy but I hear it can't be done anymore. This message also kind of serves as a test message as my dial up BBS has this as an active Echomnail conference. Glad to see this stiff is still alive and kicking...Greetings to Bink users.

Cheers

Derek

--- SBBSecho 2.12-Win32
* Origin: http://realitycheckbbs.org | information is power. (1:218/700)

Hello Derek!

06 Feb 13 14:48, Derek B wrote to All:

Does anybody know if Binkleyterm can still be registered these days?
I would
like to register my copy but I hear it can't be done anymore. This message
also kind of serves as a test message as my dial up BBS has this as
an active
Echomnail conference. Glad to see this stiff is still alive and kicking...Greetings to Bink users.

Cheers

Derek

-+- SBBSecho 2.12-Win32
+ Origin: http://realitycheckbbs.org | information is power.
(1:218/700)

Bink could never be registered. The whole "unregistered" thing is just a joke.


I don't remember if Vince Perriello told me this in oerson, or if I read it in one of the docs, but he said his copy would *always* say UNREGISTERED.




From the 2.60 docs...

----- BT_User.txt begins -----
NO REGISTRATION REQUIRED
Although BinkleyTerm is Copyrighted, it is "Freely Available Software" and as a
non-commercial user you are not expected or required to register it, nor to pay
for the privilege of using it.

While a registration is only required for extreme commercial use (see LICENSE.260 in the distribution archive), the program declares to other systems
that it is "UNREGISTERED", which is quite true if you think about it, but if you prefer this message not to be displayed you can do one of the following:

1. Use the "Serial" configuration statement and pick a serial number of your own choice. Note: Do not include anything except numerals in the number.
or,
2. Edit the file ENGLISH.TXT that is in the 2.60 archive to display any alternative wording that appeals to you. After you do this you need to recompile ENGLISH.TXT to BINKLEY.LNG as described under "Modification..." in the Reference Manual.
----- BT_User.txt ends -----



----- BT_Ref.txt begins -----
Serial <number>
By default BinkleyTerm identifies itself as "UNREGISTERED".

You can include the 'Serial' statement, with a number of your choice, and the "UNREGISTERED" notices will disappear. This is OK with the authors as long as you are complying with LICENSE.260 (which basically says that unless youÆre a pretty seriously commercial situation, you are licensed free of charge).

The number should NOT include any punctuation characters.
----- BT_Ref.txt ends -----

--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hello Derek!

<On 06Feb2013 14:48 Derek B (1:218/700) wrote a message to All regarding Binkleyterm >

Does anybody know if Binkleyterm can still be registered these
days? I would like to register my copy but I hear it can't be done anymore. This message also kind of serves as a test message as my
dial up BBS has this as an active Echomnail conference. Glad to
see this stiff is still alive and kicking...Greetings to Bink
users.

Binkleyterm has always been "freeware" and the so-called Unregistered thing was, IIRC for commercial application of the software. You can, however, make it stop saying unregistered... The last line of the Binkely.cfg file put in the verb SERIAL and any number behind it. That will take care of it.

Best regards,
Marc
Telnet://bbs.sursum-corda.com

--- timEd 1.10.y2k+
* Origin: Sursum Corda! BBS SysOp Point (1:396/45.1)

Hi Fred, Sent at: 17:32

Tuesday February 19 2013 22:12, Fred Riccio wrote to Derek B:

Bink could never be registered. The whole "unregistered"
thing is just a joke.

I don't remember if Vince Perriello told me this in oerson,
or if I read it in one of the docs, but he said his copy
would *always* say UNREGISTERED.

Mine says....

---------
OK
ARQ/HST/HST/V42BIS
**EMSI_REQA77E

Address 1:342/77@fidonet Using BinkleyTerm Version 2.60A ~Stolen

Welcome!
You have Contacted (403) 242-3221

Now Press <Esc>

Checking events...

MAXIMUS v3.01
Proudly Running...
MAXIMUS Version 3.01
Copyright 1989, 1994 by Lanius Corporation. All rights reserved.

etc..

I edited the language file. :)


Kevin

--- GED+DPMI 1.1.5-
* Origin: This unit must survive! (1:342/77)

Hello All!

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

Regards,

Rick

... BBSing is irrelevent. You will be..A8,1^**7 NO CARRIER
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

There's BINKD. I haven't tried this yet but it's on my to-do list:

https://github.com/pgul/binkd

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/201)

Hello All!

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

There is. BinkleyTerm was released for dos and OS2 along with source back around 1994 (maybe windows too, I forget now). I did build BinkleyTerm on linux back around 98 or so but I am unsure if it will still build today.

A bit of experimentation will tell the tale.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

There's BINKD. I haven't tried this yet but it's on my to-do list:

https://github.com/pgul/binkd

BinkD is a little different. Binkleyterm will actually answer a phone and,
I think, the protocols used are a little different. I think that the BT protocols are a little more like what ifcico uses. I know I am able to
connect and exchange mail with ifcico running on one end, and DOS
Binkleyterm answering the telnet call on the other.


* SLMR 2.1a * Business & science walk hand in sweaty hand
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (1:2320/107)

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

There is. BinkleyTerm was released for dos and OS2 along with source back around 1994 (maybe windows too, I forget now). I did build BinkleyTerm on linu
back around 98 or so but I am unsure if it will still build today.

A bit of experimentation will tell the tale.

IIRC there was a linux distribution of it called BinkleyTerm XE. I tried
it once and don't think I got it working. I didn't try very hard, though.

The one caveat with it is that, to my knowledge, there are no linux BBS packages that will accept a hand-off from it if the connection turns out to
be a BBS caller instead of an FTN node. That is why I didn't try too hard.

With AI getting better at answer coding questions, it might not be a bad
time to revisit to see if I can at least get it to compile with more modern libraries, and maybe get it to do something similar to sexpots and route
human callers via telnet connection to the BBS.


* SLMR 2.1a * Going to Beta-Test SOON! :-)
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (1:2320/107)

BinkD is a little different. Binkleyterm will actually answer a phone and, I think, the protocols used are a little different. I think that
the BT protocols are a little more like what ifcico uses. I know I am able to connect and exchange mail with ifcico running on one end, and DOS Binkleyterm answering the telnet call on the other.

So on Linux he probably has to run Binkleyterm as a DOS program. It's doubtful that there's a Linux version, right?

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/201)

On 2026 Apr 10 07:44:44, you wrote to Dumas Walker:

BinkD is a little different. Binkleyterm will actually answer a phone
and, I think, the protocols used are a little different. I think that
the BT protocols are a little more like what ifcico uses. I know I am
able to connect and exchange mail with ifcico running on one end, and
DOS Binkleyterm answering the telnet call on the other.

So on Linux he probably has to run Binkleyterm as a DOS program. It's doubtful that there's a Linux version, right?

the sources are/were out there... i had them and compiled native linux on old redhat stuff... way back... in the '00s i think... maybe the early '10s...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Better to be occasionally cheated than perpetually suspicious.
---
* Origin: (1:3634/12.73)

Pretty sure I know the answer to this, but is there a binkleyterm for linux?

There is. BinkleyTerm was released for dos and OS2 along with source back
around 1994 (maybe windows too, I forget now). I did build BinkleyTerm on

linu

back around 98 or so but I am unsure if it will still build today.

A bit of experimentation will tell the tale.

IIRC there was a linux distribution of it called BinkleyTerm XE. I tried
it once and don't think I got it working. I didn't try very hard, though.

That was an Extended version of BinkleyTerm although I forget just what the extentions were about.

I did run it for a time and it worked well. The interface was slightly different, not in a bad way but I forget what now. I went back to the standard BinkleyTerm version just because I was used to it, and it worked well.

I was running under OS/2 in those days.

The one caveat with it is that, to my knowledge, there are no linux BBS packages that will accept a hand-off from it if the connection turns out to be a BBS caller instead of an FTN node. That is why I didn't try too hard.

I didn't know of any linux native BBS packages at the time so I never tried that.

With AI getting better at answer coding questions, it might not be a bad
time to revisit to see if I can at least get it to compile with more modern libraries, and maybe get it to do something similar to sexpots and route human callers via telnet connection to the BBS.

Never know until you try.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

So on Linux he probably has to run Binkleyterm as a DOS program. It's doubtful that there's a Linux version, right?

BinkleyTerm 2.60 was released for DOS, OS/2 and Windows, WindowsNT I suppose. There were no linux binary packages as far as I know but the source was released at the same time.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

BinkD is a little different. Binkleyterm will actually answer a phone and, I think, the protocols used are a little different. I think that the BT protocols are a little more like what ifcico uses. I know I am able to connect and exchange mail with ifcico running on one end, and DOS Binkleyterm answering the telnet call on the other.

So on Linux he probably has to run Binkleyterm as a DOS program. It's doubtful
that there's a Linux version, right?

There is... I think it is called Binkleyterm XE... but I don't think it is actively maintained so getting it to compile on a current distro might be a challenge in and of itself.

As Alan pointed out, XE was not just a linux version. There were versions
for other OSes. Since he mentioned OS/2, I hope I am not getting mixed up
with an experiment I tried while running that os. ;)


* SLMR 2.1a * This taglx^$ closed for repairs.
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (1:2320/107)

With AI getting better at answer coding questions, it might not be a bad time to revisit to see if I can at least get it to compile with more modern libraries, and maybe get it to do something similar to sexpots and route human callers via telnet connection to the BBS.

Never know until you try.

Yep. Back-burnered... for now. ;)


* SLMR 2.1a * I am a Baudaholic.
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (1:2320/107)

There is... I think it is called Binkleyterm XE... but I don't think it
is actively maintained so getting it to compile on a current distro
might be a challenge in and of itself.

It sounds cool, but yea, it would be even cooler if it could run on an up to date OS.

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/201)