Thread View: adobe.psprinter.windows
5 messages
5 total messages
Started by Peter Howe
Thu, 25 Jul 2002 12:27
Using Windows 2000 to generate PS files for legacy system
Author: Peter Howe
Date: Thu, 25 Jul 2002 12:27
Date: Thu, 25 Jul 2002 12:27
17 lines
1971 bytes
1971 bytes
We have a legacy publication system which only supports PostScript level 1 files. Typically we use an Apple LaserWriter PPD (*LanguageLevel: "1") and printer driver 4.01 (NT) or 5.02 (Win2000) to generate PS files for the system. Following a migration from NT to Windows 2000 of PCs that generate the PostScript files, we are finding that processing of large PS files generated by Win 2000 (>80 pages) are being truncated in the system. The following message is generated even though there is no physical printer: "Print the document in parts. Reduce the number of fonts in the document. In the Device Settings page, make sure the Available PostScript Memory is accurate. For the output format, choose Optimize For Portability. Try one or more of the following, and then print again: This job requires more memory than is available in this printer" A posting in this forum suggested upgrading to the Adobe Universal PostScript driver to fix some problems in Windows 2000. I tried installing version 1.0.6 of the universal driver, but it doesn't support level 1 PostScript PPD. If anyone has any suggestions please let us know (e.g. is it possible to use the NT driver, supporting level 1 PS, on Windows 2000).
Re: Using Windows 2000 to generate PS files for legacy system
Author: Aandi Inston
Date: Thu, 25 Jul 2002 13:09
Date: Thu, 25 Jul 2002 13:09
12 lines
1237 bytes
1237 bytes
A assume this legacy system is a piece of hardware with its own memory (RAM)? This message suggests that you are running out of available memory in your legacy system. Each upgrade tends to require just a little more memory. Try doing at least part of what it says - check that the "available PostScript memory" is accurate. That is NOT the same as the amount of installed RAM. Aandi Inston
Re: Using Windows 2000 to generate PS files for legacy system
Author: Peter Howe
Date: Fri, 26 Jul 2002 13:35
Date: Fri, 26 Jul 2002 13:35
3 lines
1035 bytes
1035 bytes
The legacy system is a server which runs a PostScript interpreter. The only change is that the PCs which generate the PS files run Windows 2000 instead of NT. What we would like to do is generate the PS files to the same standard as on NT. Peter Howe
Re: Using Windows 2000 to generate PS files for legacy system
Author: Aandi Inston
Date: Fri, 26 Jul 2002 17:10
Date: Fri, 26 Jul 2002 17:10
13 lines
1418 bytes
1418 bytes
Well, it isn't really a question of "same standard". In each upgrade to Windows people want more features, and as a result the PostScript driver writes bigger headers, and the PostScript interpreter needs more memory. You can't run PostScript drivers from an older version of Windows. You should follow the recommendation in the final paragraph of my last message - in low memory situations this is essential. And if that doesn't help, realistically you should probably see if some of that legacy memory can be upgraded. Aandi Inston
Re: Using Windows 2000 to generate PS files for legacy system
Author: Tim Murray
Date: Sat, 27 Jul 2002 19:22
Date: Sat, 27 Jul 2002 19:22
5 lines
1341 bytes
1341 bytes
There is also a specific problem with certain fonts, such as the newer Arial Unicode, for example. The driver tries to download the whole thing, and it's 23 MB. Microsoft Hotfix Q310897 PostScript XP Rollup addresses this. The title implies it's for XP only, but it works for Win2K and ME as well. Your problem indicates a relationship to the number of pages, but it's worth a shot anyway.
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