GEustace@massey.ac.nz (Glen Eustace) (02/23/90)
As many may have noted on the net recently, we have purchased about 70
386SX PCs which are being used to equip a Computing Laboratory. These
machines are networked to a DECStation 3100 as a File Server using
PC-NFS.
For those that have seen my questions about Russ Nelson's Freemacs editor
and PC-NFS on the above machines, you may be interested in current
progress. The suggestion was made by another on the net that the problem
could be insufficient stack in Freemacs. Russ has confirmed that the
version of Freemacs we are using does not have a Stack Segment and thus
can not be changed with EXEMOD. The Stack is 256 Bytes. This may not be
enough. We have yet to try a version of Freemacs with a larger stack,
courtesy of Russ.
Anyway another question about PC-NFS and 386 machines.
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 ?
--
-----------------------------------------------------------------------
Glen Eustace, Software Manager, Computer Centre, Massey University,
Palmerston North, New Zealand. Phone: +64 63 69099 x7440 GMT+12
E-Mail via Internet: G.Eustace@massey.ac.nz
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) (02/23/90)
Quoth GEustace@massey.ac.nz (Glen Eustace) (in <582@massey.ac.nz>): #Anyway another question about PC-NFS and 386 machines. # #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\<link-level-driver>.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.) I have encountered one obscure glitch with a third-party board driver in this configuration, but apart from this things look pretty solid. Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM) ----------- News software that enforces a four-line .signature limit is responsible for the fact that these postings just go on and on and on and seem to end in mid-
bryan@intvax.UUCP (Jon R Bryan) (02/23/90)
From article <582@massey.ac.nz>, by GEustace@massey.ac.nz (Glen Eustace): > > 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 ? > I load PCNFS.SYS and VECIE6.SYS high with no problems. I load VECIE6.SYS with option /i2 so that it uses interrupt 2. If I don't change the interrupt then Telnet won't run from Desqview reliably. It's still dangerous to push Telnet to the background. My experience has been that it crashes the machine within a minute or so, and I assume the problem is with the "keep-alive" ping from the net generating an interrupt that Desqview can't handle. Desqview doesn't like interrupts unless they're from the COM ports. -- Jon R. Bryan <=> bryan@intvax.UUCP Sandia National Laboratories Intelligent Machine Principles Division Albuquerque, New Mexico