Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!tardis.computer-science.edinburgh.ac.uk!gtoal From: gtoal@tardis.computer-science.edinburgh.ac.uk Newsgroups: comp.protocols.nfs Subject: Re: SOSS version 3.2 -- Bigger Buffers Keywords: NFS DOS SOSS TCP/IP Ethernet Message-ID: <9105180950.AA22237@ucbvax.Berkeley.EDU> Date: 18 May 91 10:00:52 GMT References: <7539@spdcc.SPDCC.COM> Sender: usenet@ucbvax.BERKELEY.EDU Organization: Unix Anarchy, Edinburgh University. Lines: 41 In article <7539@spdcc.SPDCC.COM> rbraun@spdcc.COM (Rich Braun) writes: > > SOSS Version 3.2 - An NFS server for DOS > ---------------------------------------- > > SOSS is a file server conforming to SUN Microsystems' NFS protocol > version 2. It will run on IBM-PC compatibles under Microsoft > MS-DOS, using any Ethernet interface supported by Clarkson > University's packet drivers. > > Version 3.2 has the following improvements over version 3.1: > > - I/O requests can be up to 1024 bytes long; the old limit > was 512. I recently put up the previous version of Soss on a Dos PC to talk to my Acorn Archimdes using NFS. It's a *great* product - thanks for writing it and especially thanks for distributing it with source. However, I have a problem: the archimedes isn't a Unix machine (far from it), and the mount command doesn't have the option of changing block sizes. This isn't a problem on server->client data transfers, as the client asks for an 8K packet and is turned down, with the result that in future it asks for smaller and smaller packets until it gets one that works. *But*... this doesn't work in reverse, because any time I try to copy a file from the Archimedes client to the server, the server crashes - having been sent an 8K block. I suspect that the new code with 1K blocks might do the same - is the fault at the packet-driver level rather than soss itself? I *did* try recompiling soss with a mega-large packet size (9KI think i tried) but it didn't help, although it didn't crash - gave a protocol error instead. Any suggestions? I know it's not Soss's problem, but fixing the problem in the Client nfs isn't an option :-( [One day manufacturers will give their sources out too, if they can get over their embarrassment] Graham Toal