From owner-freebsd-questions Sat Jul 17 1:59:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from storm.digital-rain.com (storm.digital-rain.com [204.244.71.70]) by hub.freebsd.org (Postfix) with ESMTP id 9F84714BF5 for ; Sat, 17 Jul 1999 01:59:19 -0700 (PDT) (envelope-from tim@storm.digital-rain.com) Received: from agamemnon.melonville.net (dial-line60.digital-rain.com [204.244.94.60]) by storm.digital-rain.com (8.9.1/8.9.1) with SMTP id BAA08657 for ; Sat, 17 Jul 1999 01:59:16 -0700 (PDT) Message-Id: <3.0.2.32.19990717015915.0096b100@storm.digital-rain.com> X-Sender: tim@storm.digital-rain.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Sat, 17 Jul 1999 01:59:15 -0700 To: freebsd-questions@freebsd.org From: Tim Baird Subject: Re: My Printer Lost My Memory In-Reply-To: <379068B0.966DC4AF@northcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does the printcap say ???? you are limited to about 1MB spool unless you specify an mx#....... if you set mx#0 in your printcap entry, you will be limited in spool space only by the available space on your spool (var) partition...... At 04:27 AM 17/07/99 -0700, you wrote: >Hi, > >I'm running a Xerox DocuPrint P8e from my FreeBSD 2.2.7 box (flameboy). >Flameboy serves this printer to the LAN (all other systems are Win95 >OSR2 boxes) using a fairly standard Samba configuration. The printer >comes with 4mb of RAM and recently I added another 16mb to allow >scanning/printing of my wife's ink drawings for limited 'print' runs >('print' in this context is the artist's POV meaning "a copy of an >original drawing"). The problem is that the image, when printed, is only >half there. It's as if the extra 16mb of RAM was never added. > >While trying to fix this problem, I've checked file quotas (none are >set), expanding the size of the /var partition (it's 100mb now), checked >to make sure the RAM is recognized by the printer (a rigamarole >involving installation of the Xerox Windows-based driver on a notebook, >attaching the printer directly to the notebook then printing out a >'test' page where the amount of RAM is noted), as well as anything else >I can think of. Here is the current state of both the server and the >Win95 box from which I'm attempting to print: > >Server: > - 64mb system RAM > - 137mb swap > - /var is a 100mb partition with _lots_ of it free (>90mb) > - printcap description based on the "raw:" device from Samba >Printing.txt with > a line added to suppress the extra formfeed after each print job > - no file quotas set > >Win95 box: > - 64mb RAM > - 384mb swap available > >Printer driver on Win95 box: > - HP4 (the P8e can emulate anything from HPII to HP6L) > - Spooler set to EMP (I've also tried RAW and "print directly to >printer") > - RAM setting at 20mb > >Image: > - 1.4mb GIF file > - in Photoshop 4.0 this file expands to just under 5mb (probably its >true size) > - 10" x 7.x" 150dpi > - when printing from Photoshop, printer is set to 600dpi (at 300dpi, it >works fine) > >So where is the memory being lost? The printer seems to know it has 20mb >and the HP4 driver in Windows is being told 20mb. The only thing I can >think of is that there is a file size limit being imposed somewhere that >I don't see. The possible places are: > >1) somewhere deep in the Windows OS configuration >2) the Windows spooler >3) Windows networking client >4) a default file size limit imposed by the Samba server >5) a FreeBSD print spooler > >However, it's not apparent to me which of these (if any) is to blame and >so far I've been able to find no documentation to shed light on this. >Any suggestions would be very much appreciated. > >Thanks! > >-Ron Tarrant >rtarrant@northcom.net > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message