Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!yarra!melba.bby.oz.au!leo!pcm From: pcm@bby.oz (Paul C. McLeish) Newsgroups: comp.protocols.nfs Subject: Re: PC-NFS and 386SXs Message-ID: Date: 23 Feb 90 05:14:35 GMT References: <582@massey.ac.nz> <1615@east.East.Sun.COM> Sender: news@melba.bby.oz.au Followup-To: comp.protocols.nfs Organization: Burdett, Buckeridge and Young Ltd. Lines: 103 In-Reply-To: geoff@hinode.East.Sun.COM's message of 22 Feb 90 20:46:07 GMT In article <1615@east.East.Sun.COM> geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes: From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc.programmer Quoth GEustace@massey.ac.nz (Glen Eustace) (in <582@massey.ac.nz>): #We are playing with the Quarterdeck QEMM memory manager. It suggests #that various device drivers can be loaded high. What governs the choice #of suitable candidates. Which of the PC-NFS drivers will run correctly #when loaded high, if any ? My standard PC is an NEC Powermate Portable SX, a nice little 386SX which, though a tad slow, has the most accessible slots in the business :-) I occasionally run with QEMM386 to save space, using a CONFIG.SYS of the following form: BUFFERS = 20 SHELL=C:\COMMAND.COM /P /E:800 FILES=20 DEVICE=C:\NFS\SOCKDRV.SYS DEVICE=C:\NFS\.SYS DEVICE=\QEMM386\QEMM.SYS FRAME=NONE RAM DEVICE=\QEMM386\LOADHI.SYS C:\NFS\PCNFS.SYS /M /S /R0 /F16 DEVICE=\QEMM386\LOADHI.SYS C:\GAMES\NANSI.SYS LASTDRIVE=V Note that you cannot load the link level driver or SOCKDRV.SYS high; these bugs will be addressed in a future release of PC-NFS. (I know why the link level drivers won't work; I haven't yet worked out why SOCKDRV.SYS doesn't.) Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM) ----------- We use a various AT pc's, running Windows286, and PC-NFS. Whilst their are some limitations using this combination, we have found it to be successful. The only consistant problem occurs when copying files from the fileserver to a PC (either 286 or 386), the file is copied but with a size of 0K bytes. That is until we introduced the 386SX and PC-NFS 3.01, at the same time. Then various problems surfaced with the SX's: 1. 'COM in use', followed by 'Out of Memory' When trying to execute applications from windows this error would occur, at other times the same application would execute happily. 2. 'Insufficient Disk Space' When attempting to copy or save files to the network fileserver, this error occasionally appears. The existing problem with file copying, has also continued to plague us. Following various calls etc., we were advised that the position of the lines in the config.sys was crucial (???). Having tested some combinations, we have found that the following will work, but with limited occurences of 'Insufficient Disk Space'. Note that file copying is still very iffy, and must be done twice to ensure validity. shell=c:\command.com /p /e:200 buffers=5 FILES=20 LASTDRIVE=V DEVICE=C:\NFS\PCNFS.SYS /f32 /r10 /l0 /i0 DEVICE=C:\NFS\WD8003E.SYS /i3 /mb000 device=c:\386max.sys norom ram=b000-b200 use=b200-b800 include=c400-e000 use=f500-f900 nolow frame=e000 resetkeyb device=c:\386load.sys prgreg=1 prog=c:\desktop\dos\ansi.sys device=c:\386load.sys prgreg=2 prog=c:\desktop\drivers\mouse.sys DEVICE=c:\386load.sys prgreg=1 prog=C:\NFS\SOCKDRV.SYS device=c:\386load.sys prgreg=1 size=13840 prog=c:\desktop\drivers\smartdrv.sys 128 /a Moving the max and load requests to the top of the config.sys results in an un-useable machine, due to the errors noted previously. What gives???? Are we suffering from 386MAX, or could this be related to loading SOCKDRV.SYS high ? Should we try loading PCNFS.SYS high instead of or as well as SOCKDRV.SYS ? As you may have guessed, we are by no means expert in this area, and have become tired of the suck-it-and-see approach, so any assistance is greatly appreciated. -- ------------------------------------------------------------------------------ Paul McLeish, Burdett Buckeridge & Young Ltd, Melbourne, Australia Internet: pcm@melba.bby.oz.au non-MX: pcm%melba.bby.oz@uunet.uu.net Uucp: {uunet,mnetor,pyramid,ubc-vision,ukc,mcvax,...}!munnari!melba.bby.oz!pcm Phone: +61 3 614 8922 Fax: +61 3 614 8742 "It takes 3 pigs with dermatitis to make one packet pork scratchings" Who Dares Wins