Troubleshooting /X BBS with Telnet

[illy5603]

This is going to be a tough one, but I want to give it one more shot while my mind is on Amiga things.

I run one of only a handful of remaining Ami-Express BBS systems via telnet on the internet. For the most part, everything works. I can get the BBS to answer on two nodes and for the most part downloads and general browsing of the BBS works.

Where I am having problems are with uploads and frequent crashing of BBS during door activation (both /X internal and 3rd party doors) as well as frequent lockups at the end of uploads (which also activate doors to grab file id out of archived files.)

I am using the latest version of telnetd.device with a Hybrid of Miami and Ami-TCP for the stack. The Ami-TCP stuff is just there for telnetd.device I believe and includes config files for the TCP/IP stack. The network card is a 3com PCMCIA card with a static IP.

There have been a lot of posts going back several years here which is how I got the BBS working in the first place, but I want it to actually work without locking up. Can anyone dig way way back and think of anything I should look at or was this just common with /X and telnet?

I had similar issues, and all seems well with this fix:

In telnetd-device.conf, make it similar to the following:

23 2 pacerate 19200 255.255.255.255

I think the pacerate 19200 is what is required for all the error correction or smoother handshaking or something....any speed above that crashes things randomly for me

[illy5603]

Originally Posted by esc

I had similar issues, and all seems well with this fix:

In telnetd-device.conf, make it similar to the following:

23 2 pacerate 19200 255.255.255.255

I think the pacerate 19200 is what is required for all the error correction or smoother handshaking or something....any speed above that crashes things randomly for me

Yeah mine is the same except I have 3 instead of 2 in the second slot, I think for nodes or something.

Hmm this is odd. I have test run Daydream successfully on my a4000 and didn't have any issues until I tried running a STDIO/CLI door and then run a daydream native door...so I took out the stdio/cli doors But other than that seems fairly stable (although can't get it to offhook properly after someone does "g"oodbye). So maybe a hardware issue? Wish I could help more.

[illy5603]

It could be hardware. I think it worked better with my other accelerator card but that one only has 8 megs and could not process large uploads correctly. Maybe I will put that one back in and try it. If I got rid of my "PC" area this would be a non issue anyway.

[TTD]

I have seen hangs on /X when it test archive(s) and if the file file_id.diz or other file was protected, inside the archive also the stripper that could cause some errors have you try running snoopdos in background?

I think it was when it was test or stripping .zip, .lha, .lzx, .rar files (.dms files was just working) mostly but is long time ago, and I was not on telnet just normal dial up modem yeah 28k8 times, I thing I had enough memory on my old a500+ with 10MB total that time, maybe some of that could be a reason.

Note: I run the board with 28 MHz 68000 cpu. supra turbo so sometime it was because it needs higher CPU types.