Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 136  |
|  Scott Little to Bj”rn Felten  |
|  File transfer using NetFoss  |
|  22 Oct 12 07:04:44  |
 [ On 2012-10-19 at 17:56:10, Bj”rn Felten wrote to All ] BF> And it works like a charm except for file transfers. Are you using an external file transfer program? Does it support/is it configured to use a FOSSIL driver? BF> Every time a file transfer is requested, my (old, outdated and BF> unsupported) BBS software tries to open a COM port that doesn't even BF> exist, or is used for other purposes, on my computer. Mostly COM1. BF> Is there a way to make NetFoss, and then my BBS program, try BF> another COM port? The NetFoss document indicate that it supports 256 BF> COM ports, but how do I make my BBS program understand this? Since everything else is working, I assume you're running NetFoss in telnet mode, not COM port mode? In telnet mode, NetFoss is supposed to let you use any COM port up to 4096 on up to 65535 nodes (including using COM1 on all your nodes concurrently). But this only works via the FOSSIL driver; if your file transfer program tries to open the port directly it'll fail. In COM port mode, you need to specify a separate COM port for each node. You can pass that from Argus with %C. Alternatively, your BBS program probably has a node-specific configuration that will pass the correct port to any doors it runs. --- I'm writing a book. I've got the page numbers done. * Origin: sysgod@sysgod.org (3:712/848) |
[ << oldest | < older | list | newer > | newest >> ]