| @ATTACK - @PDisk.On |
| QTIPS - Postscript Driver Problem |
| QTIPS - Assorted Oddments |
| A RevTI Techie Replies - Mike Pope - Revelation Technologies (UK) Ltd |
| Networked %SK% |
| Network Contention |
| Directory Exists on Novell |
| QTIPS - String Space Format Errors |
| QTIPS - Postscript Driver Problem |
| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
RevMedia FKB
| Document | V3I8A4 |
| Title | QTIPS - Postscript Driver Problem |
| Keywords | POSTSCRIPT DRIVER PDISK NETWORK |
| Text | Novell users will be aware of the bug in PDISK which truncates output files if the file is directed to a network DRIVE (Directing the file to a local drive solves the problem) However users of the Postscript driver under AREV 2 1 face a double problem the system automatically PDISKs files to disk before printing them This means that Postscript output on a network is frequently truncated Mike Pope of RevTI (UK) Ltd and I looked at this problem and established that the fix was straightforward The Postscript driver uses the sort file specification to establish where to place the PDISKed file so if this is set to a local DRIVE in the environment window the problem disappears For optimum efficiency this ought to be a hard disk DRIVE but it will work with a FLOPPY DRIVE if you do not have a hard disk It is said that the PDISK truncation bug is fixed in release 2 11 (Volume 3 Issue 8 Page 8) |
Page last modified: 31/01/03