erl@jt.dk (Erik B. Larsen) (03/06/91)
For a few weeks ago I posted an article where I wrote about some problems using Sun's PC-NFS together with Xircom's Network Adapter. My problem was, that some files would't be copied out on a mounted drive. Well, Geoff Arnold, Sun Microsystems send me a new driver (XIRCOM.SYS). I tried it, and it seems that all my problems was solved. But they didn't. The filesize = 6451 I've an INTEL 386-302 which have an 80386, 25 MHz processor. At the same time Xircom Inc. also send me a new driver, but not the same as Geoff's! (PE-PCNFS.SYS) Filesize = 7552 I also tried it, but still I've problems when I want to copy files. An example: A file on 10.785 bytes can't be copied ----"---- 21.569 ---------"----------- Please Xircom Inc. and Geoff help me! Regards Erik Bruijn Larsen Systemadministrator Jutland Telephone Company Denmark Email : erl@jt.dk ------------------------------------------------------------------------------- Remember: The Sun is always shining! -------------------------------------------------------------------------------
geoff@bodleian.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) (03/08/91)
Quoth erl@jt.dk (Erik B. Larsen) (in <787@jt.dk>): #[Problems with Xircom driver for PC-NFS, fixed, and then found #not to be fixed.] #Please Xircom Inc. and Geoff help me! A clarification is in order here. The PC-NFS driver for the Xircom Pocket Ethernet Adapter is shipped and supported by Xircom. I got into the loop on this occasion, but Sun doesn't formally suport the driver. [The fact that I originally wrote is is entirely incidental to this matter!] When I first saw, and reproduced, Erik's problem, I narrowed it down to a piece of code which I'd lifted from Xircom's driver kit, but which on reflection was probably never exercised by anyone else's driver. (It was related to transmitting underlength packets, and padding things correctly.) The machine-dependency was asociated with DMA handling in some way: however, since I don't have sources to the low-level routines from the Xircom kit I couldm't go much further. I passed the fix to Xircom, who incorporated it into their released version of a driver. That's why there are two different drivers (though I don't know why their one is so much bigger) Both drivers appeared to fix the original problem. (Ugh - that's boundary conditions for you.) Anyway Erik (and anyone else who encounters this), please follow this up with Xircom. I may take a few minutes to look at it again, and if I do I may pass on my thoughts to Xircom, but I can't make any promises. -- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM) -- ------------------------------------------------------------------------------ -- Sun Microsystems PC Distributed Systems ... -- -- ... soon to be a part of SunTech (stay tuned for details) --