Postscript from Quark not picked up by Apogee Create

[escdotdot]

Hi everyone!
For a number of years now we've been running Quark 4 (Mac OS 9) to print postscript to a hotfolder on a PC which Create Normalizer then picks up.
With our first MacOS X/Quark 6 combo we're having an odd problem that I hope someone can shed some light on.
When we print postscript from Quark 6 it creats the PS file OK, but Create doesn't seem to recognise it. It just sits in the hotfolder on the PC until you move the file to another folder (within that hotfolder), or even change the name slightly, after which it sees it and creates the PDF as normal (there are also no problems with the PDFs created).
Has anyone seen this before?
TIA.

[Scott]

I was using Create but got pretty discouraged how much it crashed when the preflight profiles are in place. Apogee Create is not OSX compatible. If you're printing from OSX to an OX9 only app, I would think thats where the problem lies. Who the hell knows though! Hahaha.

Good luck!
Scott

[escdotdot]

Thanks for your reply, Scott. I don't know about the preflight profiles side of things, but apogee hasn't crashed once in the time we've had it (AFAIK).
I've just spoken to Agfa's tech support, and they've laid the blame on OSX, something changed in the networking when it went from 10.2 to 10.3. Oh well.

We've committed to Apogee X, so perhaps that will sort things? Then again Mac OS X is going to 10.4 soon too, so there's plenty of opportunities for things to be fixed and/or broken. I'm looking forward to it.

Cheers!

[Scott]

If you are getting the Apogee X commercial (not the light version) then I think it comes with a new Create. Apparently it's been updated... yadda yadda.. but should work with OSX.

Scott

[escdotdot]

It'll be a while before we all start using it, so I won't know for while if it fixes this problem. We'll see.

ed

[almaink]

Creo has a new Quark 6.1 extention that writes good postscript from Quark6.1. Without it I had to backsave every Quark6 job to v5 or try to PDF it if I need to trap it.

[mufftang66]

I never had this problem until recently. We are on Apogee series 3 and we used to print to the Normalizer via appletalk from OS9 and OSx. Everything was ok.

Now recently we had to rebuild our entire Pilot machine, all new computer and a complete pilot reinstall (took about 10hours) :cry: We could not get appletalk to work on the new box for some reason... (possible faulty Win200 install?) so we are now sending to the input folders from OS9 and OSx via TCP/IP and frequently files will just sit in the input folder and Normalizer will not pick them up. Then the rest of the building starts whining cause their pages aren't going anywhere. What I do is just stop the Normalizer and start it again. and then pages start processign again.

Anyone have any ideas on this? It is a minor issue but a major annoyance.
:evil:

Thanks

JA
HOST Communications
Electronic Prepress Manager

[Scott]

Did the time limit change for checking the folder? If I remember you can set Create to check the hot folder "every five minutes", or "30 seconds" or something. Also, what if they write .ps to their desktop and manually put it in the hot folder.. same results?

Scott

[mufftang66]

the input folder polling defaults to 30 secs, i changed it to 10 secs just to test, but the issue still occurs.

i'll have to investigate printing ps to the desktop and manually moving files. it's hard to test because it seems to be pretty random so far.

JA
HOST Communications
Electronic Prepress Manager

[Scott]

Well, like most things in this business, there's rarely a solution...just a work-a-round. :?