mailto: blog -at- heyrick -dot- eu

Ohmigod, now what?

So we check our mobile (US: cellular) after lunch to see if there are any messages. Actually, for a change, yes. None other than my ANPE counsellor asking me why weren't you at work today?
Well, I tried to phone him back on the number he gave, but actually he was somewhere else about 20 miles away - what sort of wally gives you a phone number of a place he isn't at? So I tracked him down and left a message there too. Nice of him to call me back...

I'm not overly worried as the woman who will be employing me handed me a piece of paper on which she has written that I begin "8/9/08", there's a scan of it on 24th July. But, really, who screwed up this time?


BBSing in a modern world

Here I am, a young man, a crashing computer program, here is a pen, write out my name. I don't know what song that's from (Alouette don't often announce stuff like that), but I love that line!
I thought it would be a good way to introduce my latest venture. A little programme called "MiniBBS". It responds to incoming telnet connections and will, hopefully, some day, provide a BBS service with menus and message areas and a message reader/editor. There will be no filebase as this is better handled by ftp. Why not HTTP? Because that's not what going retro is all about!

My version of VisualBasic doesn't want to talk to the WinSock ActiveX thingy. Must work out what that's about. So not to be defeated by some silliness, I decided to do it the hard way. A naff mixture of WSA commands and Berkeley sockets calls. And you know what? The bloody thing actually works. And better yet, it actually works across the intranet! (well, I had to (partially?) disable the Windows Firewall, must look into configuring that properly)

Here are the RISC OS telnet clients all on the iconbar:

Connecting to the server using each terminal was pretty much like:

When a user connects, basic telnet negotiation takes place, this is basically to say "don't echo stuff". The user would then be expected to enter their name and password, but this has not been implemented yet.
The text in the examples below is not strictly correct. You see, believe it or not there is no simple way to determine if a socket is active or if it has been disconnected, so I employed a quirky little cheat. If the line rests inactive for 60 seconds, MiniBBS will make the remote terminal beep. The side effect is that if the line has been disconnected, the send() call will fail and we can detect that. If the line is still active, the terminal will beep three times, at five second intervals, before the server times-out the line. So either way, the maximum a line can be tied up for without any activity is 1m15s.
Now, those C programmers among you might be saying "What's wrong with select()?". This, for those who don't know, is a command that will report on the readability and writeability of sockets. It is exactly what I am looking for, but sadly you cannot just pass a socket handle and two integers and get it to return status. Oh no, that's far too easy. Instead it will attempt to report on all sockets. Not bad, until you discover the FD_SET macro (to set a socket in the status bitmask) looks like this:

#define FD_SET(fd, set) do { u_int __i;\
for (__i = 0; __i < ((fd_set *)(set))->fd_count ; __i++) {\
	if (((fd_set *)(set))->fd_array[__i] == (fd)) {\
if (__i == ((fd_set *)(set))->fd_count) {\
	if (((fd_set *)(set))->fd_count < FD_SETSIZE) {\
		((fd_set *)(set))->fd_array[__i] = (fd);\
		((fd_set *)(set))->fd_count++;\
} while(0)
Do we have any takers to convert that (and FD_xxx) into working VB code? No? Didn't think so...

The character codes you can see in the examples are for me typing "This is a test!" in the terminal.

Nettle v0.2010r (2001/09/16) provided an "xterm/color" terminal, but it had problems that it echoed everything - and this is with MiniBBS performing basic telnet protocol negotiation and saying "please don't local echo".

There was a picture, but it got messed up in transfer,
I'll add it in here later...

FreeTerm v1.44 (2000/12/30) provides a basic monochrome emulation of a VT102. It's a shame it isn't colour-capable as it is quite pleasing to look at. Odd quirk, it can't do ^C (so I've also made MiniBBS close a connection with ^X).

VoyTerm2 v0.90 RC1 (2002/01/16) provides a colourised VT102 emulation, and - yikes - that bold text is kinda heavy - using what looks like offset overprinting instead of brighter colours! Still, it worked well.

I had a copy of ANTterm lingering around and upon installing it I saw that it was complaining about its serial number dohickey was damaged. Well, do you seriously think I'm going to trash my room for some floppies I've not seen in a decade (and in another country!) when I can make three EQ instructions NV with !Zap? O'course not! <clicky><clicky><clicky> That's ANTterm sorted! ☺
ANTterm v0.73 (1997/07/03) claims VT220 compatibility, while looking much like an ANSI colour terminal. The font is okay. What lets the terminal down is that it is the only one to be outputting additional negotiation codes after the start-up. I might insert an additional short delay if this is an issue, but so far it only manifested with ANTterm. Oh, and while it claims to negotiate (the "[255][252][ 31]" at the start of the responses), it paid no attention to my request to not local echo.

Console telnet
The console "telnet" program supplied with XP works quite nicely, which was something of an unexpected surprise. It even negotiates, doesn't echo, behaves itself... Wow!

Believe it or not, HyperTerminal can do telnet! Well, it can if you have the XP version (v5.1 2001). When you are asked for a connection, name it, pick the phone with the atom 'cos it's a cute logo, then choose Connect using TCP/IP Winsock and you'll be asked for a host and a port. It's as simple as that.
Useful hint - the call and disconnect buttons up top will re-establish and/or disconnect the connection.

And here's the status display:

It gets more interesting when you consider one program managing several 'linetasks'. The way it was handled under RISC OS in the servers I remember looking into, namely ARCbbs and ArmBBS (though I presume RiscBBS, ArchiBoard, and NewsFlash are similar) work by having a control program that sits on the iconbar, and each BBS linetask is controlled by a separate linetask program which runs in the background. The benefits are many, as the linetask can run essentially as a state machine for everything that is happening.
Unfortunately, the drawbacks are equally numerous and important. Firstly, I would need to start writing DLLs to oversee operations and shift all of the messagebase code into C. Why? Well, what happens if user #1 deletes a message that user #2 is about to read? With a shared program, each task can be already aware of the state of the messagebase. It may be trickier if the message being deleted is actually being read at that moment (though a "message in use - try again later" error might suffice?). Secondly, in the good old days each linetask looked at a serial port. End of story. Us, working as a telnet system, have only one port to look at, and from there the connect() call will allocate us a special port number and resume looking at the telnet port - if that doesn't make a lot of sense, don't worry, that's just how it works to the port in question can remain free instead of being tied up by the first incoming connection. It isn't out of the question to have the overseeing program handle connections and fire up linetasks, but that would be a messy implementation.
And from the stand-point of efficiency, I really loathed how ARCbbs needed a ~300K linetask program for each port, with what was essentially a lot of duplicated code. That, with buffering and all the other junk (the WimpSlot per linetask being 384K, plus 288K for the overseeing program), meant that a 4Mb computer could probably run a two-line BBS. Anything else would start to get awkward (remember, 'doors' and sysop tools need memory too).

What I have in MiniBBS is a central loop that affectively looks to see:

  1. Is the line timing out?
    (if so, handle that with the beeps and the disconnect)
  2. Is there data buffered?
    (if so, read the byte)
  3. Is there data in the to-send buffer?
    (if so, send in 512 byte chunks)
The transmission is not a problem, as it works by having a big resizable string and everything to be output is appended to the string and the loop simply breaks it into ½K chunks for sending. It does this for efficiency, for I did manage to send a 68Kb string in one go at which point HyperTerm promptly died. ☺

The reception? Well, I am going to have to code the linetask arbitrator in such a way that it will 'know' what is going on at every moment, so it can handle an incoming byte, and then 'exit' back to the central loop, and may be called for a different line doing something totally different. That ought to be, um, interesting.
To be honest, the byte arbitration is not terribly quick and is totally unsuitable for cases where the user might wish, say, to drag'n'drop a pre-written message (as a text file) into the message editor. I have thought of this, and you will see the beginnings of this concept if you hold down a key. For example, holding down 'A' would report something like:
  [ 65][ 65][ 65][chunk "AAAAAAA"][ 65]
Which means that the incoming byte threshold has been exceeded to the buffer was emptied as a string, not as individual bytes. I see no reason why this would happen in the menus, so this will be a mode specific to the message editor.


MiniBBS - have a go!

It doesn't do much, but feel free to give it a whirl!

LICENCE: This is for private use only. You are not permitted to make this available for download in any way. It doesn't do much, so why would you? © 2008 Rick Murray, all rights reserved.

When you first start MiniBBS, it will ask to be configured:

Simply enter the name of your BBS, your name, and your email address. The BBS name will appear on the welcome screen.

When MiniBBS starts, it will pop up a little (and I mean little) display at the top-left of the screen. It does not force itself to the top so it can get hidden, however you can Alt-Tab it back.
It looks like this:

And if somebody connects, it will change to be:

Double-clicking the word "MiniBBS" will open the status window:

In order to log-off, you must open the status window, go to the Server menu, and choose Shutdown. This will notify any current connections that you are closing down the system, and it will shut down tidily.

Want to edit the welcome display? In MiniBBS\sysdata\login is the file "welcome.txt".
You might wonder why it contains inline VT100/ANSI codes. This is because the server defaults to VT52 mode initially, and switches to VT100/ANSI mode when it knows you are using a capable terminal; hence the in-line codes to override this.
Don't try colour codes (like "{red}" and "{bgyellow}"), they are ignored until a user logs in, and that isn't available yet!
I might change this to assume VT100/ANSI unless told otherwise. D'you think the majority of telnet clients can do at least a VT100 emulation? Email me!

Logging in? Start MiniBBS. If you are going to log in on the same computer, either enter the hostname (as in the example below) or "localhost". If nothing seems to work, enter the IP address
Leave the port at 23 (if you aren't offered, set it to 23).

To connect from a different computer, the process is the same - enter the computer's hostname (if you have a local DNS server or "hosts" file set up) or its IP address. If you have a computer on an intranet, you ought to know its IP address. That's the one that looks like "192.168.0.x" (or, less commonly, 10.0.x.x).
If you are trying to connect to a computer that is connected to the internet, particularly with dynamic IP addressing, you can determine the machine's current IP address using "netstat" or "ipconfig" on the command line of the computer concerned (refer to Windows help for details); alternatively double-click on the little two-computers icon in the system tray (bottom right, by the clock) and look for the IP address there.

If it fails when you believe it should not, then from the server, try to ping the client machine. It will look something like:

C:\>ping alyson

Pinging ALYSON [] with 32 bytes of data:

Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
You will find that probably works. Now from the client, ping the host. The bottom line will look like:
Ping statistics for
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Which indicates a failure.

What this is, most likely, is the Windows Firewall blocking unwanted incoming connections. You are, currently, on your own regarding permissions required to get MiniBBS comms to pass the firewall. As I don't have internet here, I simply switched it off for the testing!


Today's word

Today's word is experiment (ex-peh-rih-ment (US: ek-spear-ment)), which is a word meaning attempt to prove. Chemistry and Physics (or "Integrated Science" for new-fangled kids) are full of experiments. Add this to that, watch it go bang. It is also a good way to validate thoughts. If you have an idea, and devise an experiment to prove the idea is valid, then you have some tried-and-tested evidence to back up your thoughts. For example, splitting the atom - sadly tried and tested (successfully) on two Japanese cities. It is also useful for the deeper thinkers to also attempt to devise an experiment to disprove something. For example, Newton's set of rules regarding the organisation of the universe are not entirely correct, but they'll fly you to the moon and back (the maths is a lot simpler than General Relativity); but in certain situations can be completely invalidated; thus proving that while an experiment to prove something is good evidence of its reliability... the inability to come up with a way of disproving it is a far stronger piece of evidence.


Your comments:

Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺ ADDING COMMENTS DOES NOT WORK IF READING TRANSLATED VERSIONS.
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.

No comments yet...

Add a comment (v0.11) [help?] . . . try the comment feed!
Your name
Your email (optional)
Validation Are you real? Please type 57429 backwards.
Your comment
French flagSpanish flagJapanese flag
«   September 2008   »

(Felicity? Marte? Find out!)

Last 5 entries

List all b.log entries

Return to the site index



Search Rick's b.log!

PS: Don't try to be clever.
It's a simple substring match.


Last read at 21:13 on 2024/07/22.

QR code

Valid HTML 4.01 Transitional
Valid CSS
Valid RSS 2.0


© 2008 Rick Murray
This web page is licenced for your personal, private, non-commercial use only. No automated processing by advertising systems is permitted.
RIPA notice: No consent is given for interception of page transmission.


Have you noticed the watermarks on pictures?
Next entry - 2008/09/02
Return to top of page