🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: adobe.psprinter.windows
18 messages
18 total messages Started by Rob Hecker. Wed, 17 Jul 2002 18:22
Adding printer memory postscript problem
#1302
Author: Rob Hecker.
Date: Wed, 17 Jul 2002 18:22
11 lines
1819 bytes
After adding 16 MB of memory to an HP Laserjet 2100TN, the printer will no longer print complex Illustrator 10 documents, which it would print before adding the memory. 

The 2100TN is a Postscript 2 emulation, non-color, 1200dpi, letter size, parallel port connection. It comes with 8 MB memory. I am using the most current printer driver, the correct PPD, and have updated the driver to recognize the added memory. A printer test page reports the correct amount of memory. OS is W2K SP2. System memory is 512 MB. 

With the added memory, the printer prints InDesign 2 and other documents as expected. It also prints simple documents from Illustrator 10. Before adding the additional 16 MB of memory, it took one hour to print a complex Illustrator document (no raster elements, but numerous patterns). After adding the memory, the job simply fails with an unspecified error after 4 minutes. 

The whole idea of adding the additional memory was to cut down on printing time. 

Any thoughts? 

Rob
Re: Adding printer memory postscript problem
#1303
Author: Aandi Inston
Date: Wed, 17 Jul 2002 20:27
4 lines
932 bytes
What do you mean by an "unspecified error"?  Is the printer set up to
print an error sheet on failure?

Aandi Inston
Re: Adding printer memory postscript problem
#1304
Author: Rob Hecker.
Date: Wed, 17 Jul 2002 22:26
9 lines
1141 bytes
Aandi, 

In the driver "Send Postscript Error handler" is checked, but no report is printed. 

The error message I get is simply: "There was an error printing to the document "first.ai" to LPT1:" 

Thanks for your inquiry. I appreciate any ideas you have on this. 

Rob
Re: Adding printer memory postscript problem
#1305
Author: Dov Isaacs
Date: Thu, 18 Jul 2002 04:47
3 lines
1003 bytes
Since this is a printer that uses HP's "emulation" of PostScript, why not ask their tech support people for some help on this? Might be a known bug in their "emulation" with relationship to their memory management schemes. This is really not an Adobe issue. 

- Dov
Re: Adding printer memory postscript problem
#1307
Author: Rob Hecker.
Date: Thu, 18 Jul 2002 13:10
9 lines
1517 bytes
Dov, 

You are right that this is more of an HP issue, however tech support from HP costs $2.50/minute with no guarantee that they can solve the problem. I've been through all the material they provide on the web. Also, it's only a complex Adobe illustrator document that is likely to cause problems. I've spoken before with printer manufacturer tech support people who didn't know what postscript was. 

There is a lot of knowledge and experience on the Adobe Forums, so I felt it would be worthwhile asking here.  

I may yet have to call HP. I just hate spending $20 for the memory and $50 finding out that that there is a bug in the emulation software. Ouch! 

Rob
Re: Adding printer memory postscript problem
#1308
Author: pleader
Date: Thu, 18 Jul 2002 15:02
4 lines
991 bytes
If your recently installed memory is branded HP, then it is extremely unlikely that you have to pay for the support incident. 

Regards, 
Victor Lee.
Re: Adding printer memory postscript problem
#1311
Author: Rob Hecker.
Date: Thu, 18 Jul 2002 20:43
7 lines
1106 bytes
Victor, 

The HP brand memory cost $200. The Viking memory made for the HP cost $8 ($20 with tax and shipping). so I didn't go with the HP. 

I don't believe the Viking memory is at fault, as it is properly recognized, has the same specs, and the problem is only with files that spool 80+ megs. 

Rob
Re: Adding printer memory postscript problem
#1312
Author: Dov Isaacs
Date: Fri, 19 Jul 2002 02:53
7 lines
1826 bytes
Rob, 

I guess that what I am trying to say as kindly as possible is that if you chose a non-Adobe PostScript implementation for whatever reason, you really should be bringing that problem back to its source. Adobe stands behind Adobe PostScript. For emulations, you should go to whatever resources the "cloner" may (or may not) provide. 

Adobe Illustrator 10 generates its own PostScript and only uses the PostScript driver as a conduit for sending that PostScript to the printer. Illustrator 10 is NOT aware of how much memory is in the printer; it generates the exact same PostScript, regardless of how much memory is installed in the device interpreting that PostScript. Assuming that you printed to the device both times (with original memory and with additional memory) with identical settings from the Illustrator print dialog and failure occurs with more memory installed, the strongest evidence exists for a problem in the printer firmware. And only HP can help you there! 

- Dov
Re: Adding printer memory postscript problem
#1318
Author: Rob Hecker.
Date: Fri, 19 Jul 2002 11:46
5 lines
860 bytes
Dov, 

Thanks, I hear you. I'll take this up with HP now. 

Rob
Re: Adding printer memory postscript problem
#1323
Author: Aandi Inston
Date: Fri, 19 Jul 2002 12:22
6 lines
1147 bytes
I've found one area where InDesign 2.0 creates dodgy PostScript; it
will fail if internaldict is not defined, even though the PostScript
Reference states it is not found in all products...  there doesn't
have to be anything in internaldict, but it has to exist.

Aandi Inston
Re: Adding printer memory postscript problem
#1227
Author: pleader
Date: Sat, 20 Jul 2002 12:29
10 lines
968 bytes
Rob, 

I'm just afraid that the HP people will point their fingers at Viking now... 

Aandi, 

Ah-hahhhh, but that's Quite another problem. 

Regards, 
Victor Lee.
Re: Adding printer memory postscript problem
#1251
Author: Tim Murray
Date: Sat, 27 Jul 2002 19:27
1 lines
1034 bytes
I have yet to encounter a problem HP printer -- native Adobe or emulated -- that did NOT work better with the AdobePS driver than with HP drivers (and, of couse, with the proper PPD).  In pre-Win2K systems, you're not supposed to use AdobePS with emulated printers, but in Win2K, it's okay.
Re: Adding printer memory postscript problem
#1253
Author: Dov Isaacs
Date: Sun, 28 Jul 2002 16:18
3 lines
1189 bytes
Actually, there is no AdobePS driver for Windows 2000 (or XP). Both Microsoft and Adobe deliver the same PSCRIPT5.DRV PostScript driver, although Adobe provides an installer that allows you to bypass the requirement of mucking around with system .inf files. The Adobe installer simply creates PostScript printer driver instances by the user's reference to a PPD file. 

- Dov
Re: Adding printer memory postscript problem
#1256
Author: Tim Murray
Date: Mon, 29 Jul 2002 07:16
13 lines
2518 bytes
I know that the Microsoft-supplied driver and the AdobePS are supposed to be the same code, but I ran some tests and found that they are not. (This was over a year ago, I think.) 

I started with two newly installed Win2K machines. On one I installed a PS printer via the Add Printer Wizard, and on the other I used AdobePS. Right away, the version numbers for the various DLLs were different. Things were further confounded if you added AdobePS to the Win2K-only machine and added a printer with the Wizard on the AdobePS machine -- as I recall, each one tries to overwrite the previous code.  

Similar behavior was found for HP-supplied drivers I tested; their installer, while being the joint MS-Adobe driver, forces its own DLLs over yours, even if yours are newer. 

One of the fixes addressed by Microsoft Hotfix Q310897, which is a roll-up of a number of earlier fixes, is that version numbers can be used: In Win2K, the decision to replace a file when another driver is loaded is based only on the file time and date stamp. WinXP is designed to honor versions. 

After loading this fix, I found that you could run the Wizard or AdobePS in any order, and versions would only increase. 

And besides testing for DLL versions, I've had a ton of hands-on experience fixing printer problems by installing AdobePS over Microsoft-supplied or HP-supplied drivers in an office of some fifteen floors' worth of mostly PS printers, some Adobe, some clones. 

So that's why I continue to refer to the AdobePS, Microsoft, and HP as separate drivers. If everyone shipped the same set of files, there would not be the need, except to point out *functional* differences like the bypassing of system .inf files and the use of PPD files.
Re: Adding printer memory postscript problem
#1257
Author: pleader
Date: Mon, 29 Jul 2002 08:43
4 lines
946 bytes
Despite Dov's authoritative assertion, there to be at least three or four different PSCRIPT5.DLLs floating around with unclear implications. 

Regards, 
Victor Lee.
Re: Adding printer memory postscript problem
#1259
Author: Lance K
Date: Mon, 29 Jul 2002 13:46
9 lines
1434 bytes
Tim and Victor, 

Well, sure, there ARE different dot release version numbers. 

If I recall correctly, and I'm not sure that I do, the version of the driver files installed by Windows 2000 was the oldest. The Adobe universal installer gave you a slightly newer version of a .dll or two, the version included in a Win2K service pack release was newer than that, etc., etc. 

But Dov was correct. There's no such thing as a "Microsoft" driver versus an "Adobe" driver, just newer dot release versions made available by each company when convenient, i.e., when Microsoft releases a service pack or Adobe updates its universal installer. 

Lance
Re: Adding printer memory postscript problem
#1258
Author: pleader
Date: Mon, 29 Jul 2002 14:03
4 lines
1165 bytes
My only point is that there are "under the hood" changes, nothing more. But of course many times reference has been made in these forums to "Microsoft drivers" and "Adobe drivers", especially in the context of getting PS clones to work. If I recall right I've never personally made that distinction. 

Regards, 
Victor Lee.
Re: Adding printer memory postscript problem
#1260
Author: Dov Isaacs
Date: Mon, 29 Jul 2002 15:43
3 lines
1295 bytes
The �differences� between the versions of PSCRIPT5.DLL and the accompanying support files is totally due to the lack of synchronization between Microsoft and Adobe releases. As we each release a version of the driver, that version includes all fixes and features to-date. Microsoft's Windows 2000 version of PSCRIPT5.DLL will hopefully �catch up� to the version in the Adobe Universal PostScript Driver Installer when Windows 2000 Service Pack 3 is released sometime soon. 

- Dov
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads