Publisher and Acrobat

[El Bimbo]

Hi all!

I have a question about MS Publisher 2003 Finnish version and Adobe Acrobat
Professional 6.02:

When I try to print something to Distiller (even empty page) it takes about
20 seconds before anything happens. Hole system is stuck. With Publisher
2000 there weren't any problems.

Any ideas?

Thanks,

EB

 

[°°MS-Publisher°°]

I think that is a fact of life you have to learn to live with. Who is at
fault well, Adobe in the left corner, MS in the right corner, and both are
to chicken to come out of their corners.
Acrobat 6.0 while being a good and well featured program, it is a typical
Adobe cludgy job in the programming dept made from a zillion API that need
to string and organise themselves before the program gets going.

 

[Miss Perspicacia Tick]

I think that is a fact of life you have to learn to live with. Who
is at fault well, Adobe in the left corner, MS in the right corner,
and both are to chicken to come out of their corners.
Acrobat 6.0 while being a good and well featured program, it is a
typical Adobe cludgy job in the programming dept made from a zillion
API that need to string and organise themselves before the program
gets going.

Actually, David, I have no problem with it. It takes less than a minute on
my system to turn a 10-20 page Publisher file to PDF and output the result.

Maybe the OP should deal with the "hole" they have in their system. That's
probably the cause of the problem... ;o)

 

[°°MS-Publisher°°]

MPT/Sarah/Cassandra/Amethyst/Black Witch/ Sick Witch/Haggard Old Bag you are
also a Blitisher liar as you would not have Adobe Acrobat Professional 6.02

 

[El Bimbo]

Acrobat 6.0 while being a good and well featured program, it is a
typical Adobe cludgy job in the programming dept made from a zillion
API that need to string and organise themselves before the program
gets going.

But this only occurs with Publisher 2003. With Publisher 2000 or any other
program, including other Office 2003 applications, there are no such delays
with Distiller.

I'm just wondering that if someone else has this problem, or is it just me?

EB

 

[Brian Kvalheim - [MSFT MVP]]

Check out the following kb articles:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821960&Product=pub2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;826360&Product=pub2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;282256&Product=pub2003

--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com
~pay it forward~

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[El Bimbo]

Check out the following kb articles:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821960&Product=pub2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;826360&Product=pub2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;282256&Product=pub2003

Thank you, but I don't get any errors, PDF's print out just fine -
eventually.

Problem is that annoying 20+ second waiting time when my machine freezes
completely when trying to print to Distiller. At the same time CPU usage is
less than 5%.

EB

 

[Brian Kvalheim - [MSFT MVP]]

Hi El Bimbo ([email protected]),
in the newsgroups
you posted:
|| Thank you, but I don't get any errors, PDF's print out just fine -
|| eventually.
||
|| Problem is that annoying 20+ second waiting time when my machine
|| freezes completely when trying to print to Distiller. At the same
|| time CPU usage is less than 5%.

Contact Adobe support.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com
~pay it forward~

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[El Bimbo]

Hi El Bimbo ([email protected]),
in the newsgroups

Contact Adobe support.

I already have, but you can guess what did they say: "Because Publisher is
only program where problem occurs, contact MS." And as we all know, no help
from there either.

EB

 

[°°MS-Publisher°°]

El Bimbo and you will not find a soul at MS that cares or has heard of
quality control.

However, I am pretty damn sure this is an Adobe problem.