Graphics Manager Crashes Publisher

[JWPlatt]

I have a problem with Graphics Manager crashing Publisher on larger
websites. As soon as I invoke it, Publisher crashes.

I had this problem with Publisher 2000 under Win98 and it remains in
Publisher 2002 under WinXP. I'll go out on a limb and assume it also
affects 2003.

Is there a Graphics Manager table entry limit of some sort? If I go
through and link as many picture files as I can (instead of embedding
them) to make the actual number of table entries smaller, will that
help? Or does linking too many files actually cause the problem?

 

[David Bartosik [MSFT MVP]]

You can zip and send the file to (e-mail address removed) with the steps you
use to reproduce the problem and I'll test it and/or get with MS on it.

David Bartosik - [MSFT MVP]
www.publishermvps.com
www.davidbartosik.com

 

[JWPlatt]

*You can zip and send the file to (e-mail address removed) with the
steps you
use to reproduce the problem and I'll test it and/or get with MS on
it.*

Will do. It's 12 MB zipped. I assume it will fit in your mailbox.

But in the meantime, are there any known issues or limits on the
Graphics Manager?

 

[David Bartosik [MSFT MVP]]

Got it, will get back to you.

Not that I am aware of.

David Bartosik - [MSFT MVP]
www.publishermvps.com
www.davidbartosik.com

 

[JWPlatt]

*Got it, will get back to you.*

Any progress?

 

[JWPlatt]

*Any progress? *

 

[JWPlatt]

*You can zip and send the file to (e-mail address removed) with the
steps you use to reproduce the problem and I'll test it and/or get
with MS on it.*

David, is there any news from MS or yourself about this issue?

 

[David Bartosik [MSFT MVP]]

I'll update the thread when I have something.

David Bartosik - [MSFT MVP]
www.publishermvps.com
www.davidbartosik.com

 

[JWPlatt]

*I'll update the thread when I have something.

David Bartosik - [MSFT MVP]*

Has it been long enough to ask again?

Has any progress been made on this issue


-
JWPlat

 

[David Bartosik [MSFT MVP]]

MS has reviewed and tested and responded.

There is no cap built into the graphics manager for handling a particular
number of graphics.

Crash was confirmed in 2000 and 2002, but crash is due to a problem in the
file not the program. Those two versions do not handle the problem well and
then don't respond well, they crash.

Crash could not be reproduced in 2003. Additionally they reviewed watson
data ( those crash sends you are prompted to send) and could not identify
hits on this.

Final word- there is a problem in the file, a problem which version 2003 can
manage.


Now my having gone over their findings and knowing about the
"bullet-proofing" they did with the 2003 release, something comes to mind,
and so I have a question for you.... was your Publisher file at any time
exposed to Norton AV on the same PC?

David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com

 

[JWPlatt]

*Now my having gone over their findings and knowing about the
"bullet-proofing" they did with the 2003 release, something comes to
mind, and so I have a question for you.... was your Publisher file at
any time exposed to Norton AV on the same PC?*

Well, yes, constantly - as a responsible user should. I have NAV 2003
on one computer and SAV 9.0 on another. Is Microsoft advising against
using NAV and SAV?

Now that you mention it, I did once have a problem reading another
users's .pub file and actually found a KB article on Symantec about
Publisher. I had forgotten about it.

Do I solve the problem by simply by disabling it during my Publisher
work? Are all Publisher files damaged by NAV/SAV? Can they be
repaired by saving while NAV/SAV is disabled? Has Microsoft or
Symantec addresses this other then making Pub 2003 more tolerant?

 

[David Bartosik [MSFT MVP]]

Norton AV has been proven to break MS Office files. All the more common with
Publisher files. There are KB's on how to use Norton with Office. But my
recommendation for years has been to not use Norton products. That's based
on my years of personal and professional experience, not including the reams
of MS communications I can't disclose spanning about 2 years that cover the
Norton "problem". My product recommendations are listed on my site
www.davidbartosik.com . Fwiw, all my clients and my peers and my associates
and pretty much anyone I even remotely know in IT run AVG or TrendMicro. I
myself prefer AVG because it's free to home users and pretty affordable for
my clients. Not only is NAV dangerous but many times when I have replaced
NAV with AVG on a machine that comes to me for help, AVG finds infections
already there and has to remove them.

Pub 2003 had to be engineered to block Norton's aggressive tactics. It is
also designed to not crash from a corrupted pub file (due to Norton), which
it's younger siblings will. But the corruption is not fixable, there will be
lost functionality in the file, Pub 2003 can't change that, it only manages
to "deal" with the bad stuff and not crash. I personally find the whole
matter all the more upsetting because I am left to wonder how many feature
requests and bug fixes (from the MVP's) didn't make it into 2003 because of
the man-hours that had to be sunk into bullet-proofing Publisher 2003 from
crappy third party software.

Feel free to use googles archives to trace this forum back thru for about
2-3 years and you can find the daily threads that weave thru the trail of
destruction NAV left on Publisher customers.

David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com

 

[JWPlatt]

*Feel free to use googles archives to trace this forum back thru for
about 2-3 years and you can find the daily threads that weave thru
the trail of destruction NAV left on Publisher customers.*

Don't mince words, David - How do you REALLY feel about NAV?

Same story with Publisher on SAV Corp Ed?

I'll look at the others you suggest, but I need central console
management. I hope they have it.

 

[JoAnn Paules [MSFT MVP]]

I used to be a Norton fan. And then they dropped the virus definition
updates for the version of NAV I was using at home forcing me to buy the
newer version. And then they jacked up the cost of the yearly subscription.
And then I learned about how it could screw up Publisher. Something had to
go! I now use AVG.