Acorn (RISC OS) Network Page
Here are some recent exchanges on comp.sys.acorn.networking:
Peer-to-peer connection question;
Using Linux as a file server for RISC OS and discussion of file types;
I would also recommend you look at Ian Jeffray's Networking Page
RiscPC SA (upgraded 600) in office, RISC OS 4.03
Relevant hardware and software:
Atomwide/ANT EtherM combi card, currently connected to UTP network.
ANT Internet Suite 1.31 (bought)
OmniClient 2.04 (from Developer CD I think)
(within OmniClient) Lan Manager/NetBEUI Client 1.83
(running within OmniClient) LanMan98 CIFS Client 1.14
AlphaNet 1.21 Web/FTP/Telnet/etc. server (bought from Chris Poole)
JetDirect 0.01 providing JetDirectFS
!Printers 1.53 printing to file; see note 3 below and screenshot.
Network section of icon bar:
Example screen shot:
1024x768 screen grab (112K) showing some typical windows etc... The screen shot is a bit arbitrary but does demonstrate the long filenames and how to set your !Printers up for the excellent JetDirectFS system. Printing to HP LaserJet printers (we've got one mono and one colour) is wonderful.
Files you might find helpful:
My current INetDbase:Hosts file listing TCP/IP host names
My current INetDbase:!InetConfg file ANT Suite config (but I starred out my password)
Notes:
1. [General] I can also connect to the regular internet using my ANT Suite dial-up connection, although I had to come up with my own connection script for panix, my provider in New York. In reality I use the ANT for modem connections infrequently because my email software of choice is Eudora Pro for Windows. Sorry about that, but Eudora is a superb piece of software. My machine automatically dials up each morning and fetches news but not email.
2. [General] The LAN side of this setup is pretty much perfect for me now; it is possible to put any Acorn files on the shared PC discs and usually run them from there if necessary although the transfer speed is not ad good as a local HD (network is 500 KB/sec, HD typically 1-2 MB/sec). I use the shared PC discs a lot for collecting scanned images.
3. [JetDirect] I found that in order for JetDirectFS to work I had to put the printers into my hosts file and refer to them by hostname; if I use the IP address directly (e.g. 192.168.1.100) it does not work.
4. [LanMan98] Connecting to local LAN shares always requires me to use both the hostname and the machine name in LanMan98. This is not quite in agreement with the manual, whih suggest that this is only needed for remote sites (they mention 'sunsite') and was almost added as an afterthought. If you look a the screen grab (linked above) you will see the notation I mean.
5. [PCPro] In case anyone used my old readme's or suggestions for Network Links and the PC card, I never use my PC cards any more because I am surrounded by very fast PCs and the LAN actually makes it easier to use them than PCPro.
6. [AlphaNet] The web server services our internal corporate web site which is a significantly enhanced version of the public site. I use password authentication for some pages (over the LAN only) and this allows me to use the web pages as documentation and technical notes on the software I write here. All that stuff is generally written in Zap on my RiscPC, although some documents reach me as MS Word and I convert them to Adobe PDF for the web site.
7. [ANT config] Until about 18 months ago I was in Italy at the University of Pisa and had my machine permanently connected to the LAN and Internet. Some aspects of the config have been carried over (most notably, the LAN host name) and I have not changed them just because it works ok, so why mess with it.
| 