Telnet Client for CP/M - Beta Release

[Dave]

Hi Bill,

just had time to give it a quick try with the RESOLV.CFG file, it resolved the host name just fine - thanks a lot

regards
Dave

[acsi]

I think I am doing something wrong here as after connecting I get the first few lines of text from the BBS and then black on black until I hit enter a few times then the text displays and shortly after I get black on black again?

[Dave]

It would help to know the BBS that you are trying to use?

You could also try using something like Putty on your PC to call the BBS and show the screen output here so that we could get an idea of whether anything unusual is being displayed on the output. As the opening post in this thread says, Bill described this version as a “beta”, it is not a complete emulation of the Telnet protocol and it may be that some less common control codes are not currently implemented

[acsi]

Thanks Dave,

I did try DarkforceBBS (darkforce-bbs.dyndns.org) and then to test I tried MagnumBBS as it was show to work earlier.

Is there another I could try?

[Bill B]

Is this just the latest version, or did it happen with the previous version?

I need more information to try and determine the cause. Please will you run the program as:

Code: Select all

telnet -t -r -l telnet.log darkforce-bbs.dyndns.org

and then upload the resulting telnet.log file. I can then take a look and see what I can deduce.

Edit: Or the log for MagnumBBS if that is having the same issue.

[Dave]

Thanks Dave,

I did try DarkforceBBS (darkforce-bbs.dyndns.org) and then to test I tried MagnumBBS as it was show to work earlier.

Is there another I could try?

It's great that Bill is on the case, but your message here wasn't clear - did you mean that MagnumBBS did not work for you either?

regards
Dave

p.s., I can't ping that darkforce board from my PC, are you sure that it's working?

I looked at this page about darkforce : https://www.darkforce.org/access.html, it does say . . .

"1. Problem - I only get a blinking cursor. Solution - hit your RETURN key a few
times. Atari and Linux terminals seem to display the text correctly, asking for
the RETURN key. Some other terminals, especially under Windows, do not."

You might want to check this page for alternative boards https://www.telnetbbsguide.com/bbs/list/brief/

I only tried 1, ("a1bbs.ddns.net" and it seems to work

[acsi]

I appreciate the help guys.

Hi Dave, sorry I left :1040 off the end. It should be darkforce-bbs.dyndns.org and yes it behaves the same on all connections including magnumbbs.

Hi Bill,

I have connected and attached the log

This screen shows what I see at first after connecting. Notice the last word is truncated.

IMG_7940.jpeg (336.88 KiB) Viewed 1148 times

After selecting 1 for 80 column mode I it goes through the ansi/acsi selection which it automatically detects ansi on and then I get this

IMG_7941.jpeg (236.15 KiB) Viewed 1148 times

Then if I hit enter 6 times the screen pops back to life for a bit

IMG_7942.jpeg (391.02 KiB) Viewed 1148 times

[Bill B]

OK, I am puzzled. From the log file, all the text would appear to have been received correctly, and replaying the data through the ANSI driver (on MEMU) the screens appear to display correctly.

At the moment, the only thing I can think of is that for some reason the ANSI driver within TELNET.COM is corrupted somehow, I will consider further.

[Dave]

I have managed to log onto the DarkForce BBS

The main problem that I see is that, after the screen width selection from the menu (1 for 80 column), the system automatically detects the terminal type as ANSI and then echos every character typed, so on screen you see characters appear twice

(As I noted in an earlier message, sometime, I need to press enter a few times before the system responds and other times, it does not respond at all)

I have no problems with MagnumBBS (are you using Bill's loadfont to use the CP437 character set?)

acsi - You might want to try a different BBS too

[acsi]

acsi - You might want to try a different BBS too

Tried a couple and same sort of behaviour unfortunately. Even tried with area52 which is supposed to be ASCI.

To eliminate my MTX being the problem I swapped my MFX into another machine and the behaviour is the same.

Will look further into this tomorrow.