Ditto Lodger

Fantastic I,m giving this a good go Tuesday on my day off.

I wish i had more time to play I'm really under the pump at work.

If there is anyway i can help just PM me. webspace ftp whatever.

_________________
Have Fun!!

lodger, this is great!

A couple of suggestions...

-My pet peeve, it's hardcoded to Drive #8 (This is probably in Contiki's code, not yours, but please fix it).

-The "CONTIKI BBS LINE BUSY" message appears in the wrong Telnet session. i.e. if I connect to the BBS on one terminal window, and then telnet to the BBS again from a second window, the message appears in the first session. (the second just closes right away with nothing shown).

-Can you add a way for the "sysop" to change the port#? I guess there will eventually be a config file with board name, etc, the port# could go here.

-How about some short messages on the 64 itself, i.e. "Caller from 192.168.1.5", "Caller disconnected", etc. And/or maybe change the screen color when a caller's connected.


And finally, are you willing to share your source?

Great is indeed the right word for this

It's finally moving forward in the BBS department again...

@Lodger Thanks again.

I've downloaded your contiki-bbs.zip file from here and unzipped it, then using star-commander
extracted the files and copied then to a floppy disk via the ide64 card.

Run the network-setup file and configured the contiki.cfg file. easy.

I have it running on 58.6.118.19 from my sx-64 using a RetroReplay/RRNET cartridge.

I'll leave it running in case anyone wish's to have a look.
Simply telnet on 58.6.118.19

I noticed when i telnet in, there is no notification on the c64 screen, unlike contiki-webserver.

enjoy

_________________
Have Fun!!

I gave it a try, if I connect it just clears the screen then exits.

Pinging that IP is sporadic as well.

I have connect another c64 and 1541 floppy drive, just to check if the
c64 or drive i was using is at fault.
The c64/drive i am using now is my gaming unit and works a treat.

I'll leave it alone for a few hours see what others find.

enjoy

:edit

I can telnet in no problem, but when you do the /write command, then enter your msg and /q
the drive spins up then errors.

This is a great start.

Lodger are you using a emulator or a real c64 to test contiki-bbs.

enjoy and thanks again.

_________________
Have Fun!!

zap, I connected to your "bbs" from my PC just fine this time. Tried to "write" msg #1 (before seeing the above, oops).

Connecting from GuruTerm on my 64 didn't work as well, nothing I typed echoed back or seems to be recognized, I just got bbs> bbs> bbs> etc. when hitting Return.

I can shed some light on this problem with GuruTerm.

If you use lower case the commands work fine.
if you use upper case they do not work.

ie /write does work /WRITE does not work. etc.

The drive still errors with flashing light when writing but the command gets a responce.

enjoy

_________________
Have Fun!!

I get a connection closed:

Trying 58.6.118.19...
Connected to dsl-58-6-118-19.qld.westnet.com.au.
Escape character is '^]'.
Connection closed by foreign host.

After 2 or 3 connections it mucks up. normally after someone
attempts to write to the floppy.
I've reset it many times to keep it online.

Still it does work and it is very much a work in progress.

_________________
Have Fun!!

-------------------------------
BBS> /help
* BBS COMMANDS:
/HELP THIS SCREEN
/BOARD SELECT BOARD #
/READ READ MSG. IN BOARD
/WRITE WRITE MSG. IN BOARD
/QUIT LOGOUT
BBS> /board
* CURRENT BOARD: 1
SELECT BOARD NO.: 1
* NEW BOARD: 1
BBS> /read
MSG NO.: 1
* READING: BOARD #1, MSG. #1
-------------------------------





-------------------------------
BBS>


Nice indeed

Hello everybody,

sorry for not answering that quick, my day job is eating up on me. Thank you very much for your positive replies and your bug reports. Although I'm not new to coding C, this whole TCP/IP based stuff is new for me and you people do a good job at motivating me and keep me going, thank you for that.

Now, here are some answers to your questions:

@zap: at the moment I'm using VICE for testing my code. Also, all my testing takes place in the same (class C) subnet. In order to reproduce the problems you have encountered, I'll set up my C64 hardware + RRnet and connect it 'live' to the internet and have some checks throughout the day connecting from my office.

As for the drive blinking after reading or writing: this may happen if you write to a board for which there exists no REL file at the time of the disk access. I'll write a small configuration tool that will initialize these files and also offer TCP/IP configuration of contiki in order to make things a little more comfortable. This config tool later may also be used for adding / locking / deleting users.


@schema: PETSCII based terminal programs won't work as the binary is compiled with PETSCII translation enabled. I can compile a version without this connversion which will work with PETSCII based terminal programs. Unfortunately, this is one of the problems regarding Contiki OS, as I think that you can not switch between PETSCII -> ASCII conversion and "raw PETSCII" during runtime.

Also, the drive # is hardcoded by me at the moment (as this whole thing started off as a quick'n dirty hack), but I'll also take care of that so you people may use your 1581 drives or whatever it is you're using as drive #9 #10 or #11. As for logging connections and proper "BBS is busy" handling, I'll implement those fixes / additions within the next days and post a download URL for that version here.

EDIT: Since I have always belived in the open source concept, I'll release the source of Contiki BBS along with the next release (in fact, the whole thing is a stripped down version of the Contiki Shell plus a small change in the Telnet server code). Just give me some more time to work on that piece, cleanup the ugly looking parts of the code and add some comments. I'll try to implement all of your suggestions in the next version.

_________________
LOAD ":*",8,1
READY.
RUN

Interesting, I'll have to have a look through the source and see what can be done.



Unless Contiki does something weird to zeropage, you can just read the value of $BA for the current drive number. Maybe read it at startup and store it in a separate variable, just in case. Please don't limit it to drive #11 though, as I (and probably zap) want to try this an IDE64 which lets you configure a drive to be anything up to #30.



Thanks in advance!

Any progress for this kitten?

I only wish i could help in some way.

_________________
Have Fun!!