It’s rumoured not to work well, because the WAN timeouts confuse FLEET,
but look for “infleet” at ftp.qnx.com, or however that new-fangled web
QDN thing puts stuff.
Previously, Warren Peece wrote in qdn.public.qnx4:
Quick answer: TCP/IP only
Long answer: Someone was talking about encapsulating FLEET within IP. I dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for that
“Paul Russell” <> firstname.lastname@example.org> > wrote in message
news:8plq4v$p7g$> email@example.com> …
| I have to set up a link between multiple QNX networks and a central QNX
| system over TCP/IP through X.25 Routers.
| Do I have to do all messaging & transfers in TCP/IP, or is there a way to
| configure the system so that all the QNX Nodes can see each other as nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the TCP/IP
| and maybe even be able to use QNX send/receive between globally registered
| All sugestions greatly appreciated.
| > firstname.lastname@example.org
Sam Roberts (email@example.com), Cogent Real-Time Systems (www.cogent.ca)