![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
|||
Product |
Print Console 2.0 or 1.0.4 connected to Brisque 3 or 4 via Screen2Go. | ||
Operating system |
Windows NT |
||
|
|
|||
Symptoms |
Spoolers (hot folders) crash, or job only partially images when using Screen2Go TIFFs from a Brisque. | ||
|
|
|||
Cause |
When using Screen2Go, a 1-bit TIFF is written to the local Brisque hard drive and then sent to the Print Console hot folder on the NT/Windows 2000 workstation via Hummingbird. If there is a delay in writing the TIFF file across the network (example: lots of network traffic), Print Console may assume that the file is finished writing when, in fact, it's only partially done writing. Print Console then moves the file to the Working folder and begins processing it. The spoolers/hot folders may crash doing a “null read“ (i.e. file isn't really there), or the file may partially process and then fail in TIFF Downloader. |
||
|
|
|||
Solution |
Increase the file stabilization time setting in the Print Console
Hot Folders pane to a larger, but still acceptable number (example:
60 seconds). The 10-second default setting may not be adequate when
the file is coming across the network from the Brisque via
Hummingbird.
Use the Brisque-to-Trendsetter direct connection when it becomes available. |
||
|
|
|||
Technical contact(s) |
|||
Submitted by |
|||
Date submitted |
19 Jan 2000 |
||