From Newsgroup: alt.bbs.pcboard

Got my tcp fossil running for a test with PCBoard. Tried the CDC
version of zmodem, but it could not handle the speed. Then I tried PD
zmodem and that worked. 700,000 cps.

This is my set up:

a) Vintage motherboard with 1,000 MHz Athlon CPU, 256 meg RAM.

b) Windows 3.1 with QEMM97 memory manager.

c) Novell Client32 (provides TCP), with Intel E100B network card.
This was the hard part, finding a network card that works with
Client32. Cards with newer drivers, even though they claim to
support Client32, don't work. Like an SIS900. It has a driver
for Client32 that works enough to connect, but under stress it
fails. Strange but true. Stick to the drivers included with
Client32, and they work fine.

d) linux server (and firewall) to run the telnet reverse proxy
that handles inbound connections to PCBoard. The tcp fossil
I wrote connects to the proxy, which handles multiple nodes.


The only missing piece is outbound FIDOnet mail. Maybe binkd on the
linux box would work, if I could learn how to toss mail between binkd
and PCBoard. Sounds like another project ...


--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Sat, 25 Oct 2014 04:15:12 +0000, Trifle Menot
<triflemenot@protocol.invalid> wrote:

Got my tcp fossil running for a test with PCBoard. Tried the CDC
version of zmodem, but it could not handle the speed. Then I tried PD
zmodem and that worked. 700,000 cps.

This is my set up:

c) Novell Client32 (provides TCP), with Intel E100B network card.
This was the hard part, finding a network card that works with
Client32. Cards with newer drivers, even though they claim to
support Client32, don't work. Like an SIS900. It has a driver
for Client32 that works enough to connect, but under stress it
fails. Strange but true. Stick to the drivers included with
Client32, and they work fine.

Two corrections:

The CDC version of zmodem was not the problem. The problem was PCBoard ignoring the AX return value from fossil call 19h, which causes dropped characters. After fixing my tcp fossil to do write retries internally,
CDC zmodem now works.

As for the SIS900 driver with Client32, it's working now. Version 1.15
from the SIS download site. Must have been some other problem going on
when it seemed to fail before. Likely the AX return bug.

The SIS900 driver has good speed with Windows 3.1, but with Desqview it
slows down badly when copying a large file from the server. The E100B
driver does not have the problem, it gives roughly the same speed under Desqview and Windows 3.1.

Apparently some incompatibility between the SIS900 driver and Desqview.
I'll have to run Windows 3.1 on boards with an SIS900 chip.


--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Friday, October 24, 2014 9:15:13 PM UTC-7, Trifle Menot wrote:

Got my tcp fossil running for a test with PCBoard. Tried the CDC
version of zmodem, but it could not handle the speed. Then I tried PD
zmodem and that worked. 700,000 cps.

This is my set up:

a) Vintage motherboard with 1,000 MHz Athlon CPU, 256 meg RAM.

b) Windows 3.1 with QEMM97 memory manager.

c) Novell Client32 (provides TCP), with Intel E100B network card.
This was the hard part, finding a network card that works with
Client32. Cards with newer drivers, even though they claim to
support Client32, don't work. Like an SIS900. It has a driver
for Client32 that works enough to connect, but under stress it
fails. Strange but true. Stick to the drivers included with
Client32, and they work fine.

d) linux server (and firewall) to run the telnet reverse proxy
that handles inbound connections to PCBoard. The tcp fossil
I wrote connects to the proxy, which handles multiple nodes.

The only missing piece is outbound FIDOnet mail. Maybe binkd on the
linux box would work, if I could learn how to toss mail between binkd
and PCBoard. Sounds like another project ...

sounds like a easy patch fix.
can you post the pcboard fix?
--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Sat, 6 Dec 2014 17:35:00 -0800 (PST), stbenedictmission@gmail.com
wrote:

sounds like a easy patch fix.
can you post the pcboard fix?

I don't know what you want. Please describe it in more detail.


--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Friday, October 24, 2014 9:15:13 PM UTC-7, Trifle Menot wrote:

Got my tcp fossil running for a test with PCBoard. Tried the CDC
version of zmodem, but it could not handle the speed. Then I tried PD
zmodem and that worked. 700,000 cps.

This is my set up:

a) Vintage motherboard with 1,000 MHz Athlon CPU, 256 meg RAM.

b) Windows 3.1 with QEMM97 memory manager.

c) Novell Client32 (provides TCP), with Intel E100B network card.
This was the hard part, finding a network card that works with
Client32. Cards with newer drivers, even though they claim to
support Client32, don't work. Like an SIS900. It has a driver
for Client32 that works enough to connect, but under stress it
fails. Strange but true. Stick to the drivers included with
Client32, and they work fine.

d) linux server (and firewall) to run the telnet reverse proxy
that handles inbound connections to PCBoard. The tcp fossil
I wrote connects to the proxy, which handles multiple nodes.

The only missing piece is outbound FIDOnet mail. Maybe binkd on the
linux box would work, if I could learn how to toss mail between binkd
and PCBoard. Sounds like another project ...

ah, the fossil fix to pcboards fossil routines.
you said it didn't support resume?
--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Sun, 7 Dec 2014 11:43:11 -0800 (PST), corey blake
<ainewslv@gmail.com> wrote:

ah, the fossil fix to pcboards fossil routines.
you said it didn't support resume?

I wrote a fossil driver. It's a separate program, it's not a fix to the
PCBoard source. It's a TSR you load in your batch file, before calling PCBoard.

It only works with Novell Client32 TCP/IP stack. And it only connects
to my telnet reverse proxy that runs on linux.

To make it work, you need a linux box for the telnet proxy, a Netware
server for shared files, and one or more clients with DOS or Windows
3.1. So if you don't have three or more computers to run your PCBoard
setup, my tcp fossil driver won't help you.

Do you have the computers, and time, to make it all work? It's not an
easy project that can be done in a day. It will take time. Maybe weeks,
or even months.


--- Synchronet 3.17a-Linux NewsLink 1.108

From Newsgroup: alt.bbs.pcboard

On Friday, October 24, 2014 9:15:13 PM UTC-7, Trifle Menot wrote:

Got my tcp fossil running for a test with PCBoard. Tried the CDC
version of zmodem, but it could not handle the speed. Then I tried PD
zmodem and that worked. 700,000 cps.

This is my set up:

a) Vintage motherboard with 1,000 MHz Athlon CPU, 256 meg RAM.

b) Windows 3.1 with QEMM97 memory manager.

c) Novell Client32 (provides TCP), with Intel E100B network card.
This was the hard part, finding a network card that works with
Client32. Cards with newer drivers, even though they claim to
support Client32, don't work. Like an SIS900. It has a driver
for Client32 that works enough to connect, but under stress it
fails. Strange but true. Stick to the drivers included with
Client32, and they work fine.

d) linux server (and firewall) to run the telnet reverse proxy
that handles inbound connections to PCBoard. The tcp fossil
I wrote connects to the proxy, which handles multiple nodes.

The only missing piece is outbound FIDOnet mail. Maybe binkd on the
linux box would work, if I could learn how to toss mail between binkd
and PCBoard. Sounds like another project ...

ah, no.
all I have is android for pc.
--- Synchronet 3.17a-Linux NewsLink 1.108