Hi Dan,

You can either use the "Optimized Postscript" mode so that your form calls the images on the virtual drive, or you can download the images on your printer's hard drive so you can use "printer centric" mode.

Basically, the virtual drive exists to simulate a printer hard drive and allow you to configure and test your forms without sending everything to the printer. So your printer doesn't have a virtual drive, it has a hard drive.

Hope this clarifies how to proceed. Regards,
Olivier

When you download images, select two checkboxes - one for localhost and one for your ir 150. That'll make the images available when proofing on your local machine, and also make the images available on the ir 150 so you can take advantage of printer centric mode when printing.

One of our RIPs is only available via a "hold" queue. The image downloads would appear as jobs labeled "unknown". The operator just needs to print those jobs. When he hits print, the PostScript code required to store the image on the hard drive is executed, no output is generated and the image contained in that job is now available on the printer's hard disk. I mention that just in case you have a similar situation.

RIPs I've used in the past often have an option to print a list of resources on the printer's hard disk (including your images/forms). If that's not an option, I'm sure there's a bit of PostScript code laying around somewhere that will print out a list of internal resources. If you're using a stand alone RIP instead of the built-in RIP, you can just browse to the folder where images are stored and look over the files stored there.

Jim

Thanks for all of the responses I was able to solve my problem with your help. the imageName+'.pdf' workded the best for pointing images to the virtual drive on the local host. My document is now optimized and the process is running much smoother and faster. Thanks, Dan