JRD@USU.BITNET (Joe Doupnik) (02/13/90)
Eric,
Dumping graphics screens to a network printer. Ah, the joys thereof.
About the best that one can say is that Novell has found a way of making the
process as slow as physically possible, and then once in a while it manages
to lose the files altogether. Nothing seems to fit: disk access time, network
transmission rates, printer speeds, etc. It is just glacial. Queue a few of
these and things start getting lost. Yes, Novell is well aware of all this
because each site goes through the same experience. My best guess is that
each byte goes as a separate packet.
Joe D.E_DAVIES@HVRFORD.BITNET (02/13/90)
We've noticed that print screening a graphics screen (either from an EGA or a Hercules + equipped workstation) to an IBM Graphics Printer hung off the server takes about 5 times as long as print screening the same image on a non-networked machine to a local printer. We're running Adv. Netware 2.15a on a '286 server over ThinWire Ethernet cabling. The workstations are '286 machines equipped with Paradise EGA (or Hercules +) cards and WD 8003 NICs. An odd characteristic of all of this is that once one depresses the Shift & PrntScrn keys, the server's hard drive access light will flicker briefly about once every 8 seconds. The hard disk's access time is supposed to be around 18 ms and I would expect better throughput than this on our network. Any thoughts on all of this? Any buffers I could fiddle with to optimize caching or some such? The server's got 4 MB. Thanks. Eric Davies Haverford College