On May 18, 11:20=A0am, CyberTaz <onlygeneralt...@[EMAIL PROTECTED]
> wrote:
> Then it sounds like you're dealing with a corrupt do***ent. See the
> suggestions on this site for regaining a clean copy:
>
> http://word.mvps.org/Mac/Do***entCorruption.html
> HTH |:>)
> Bob Jones
> [MVP] Office:Mac
>
> On 5/17/08 8:24 PM, in article
> fc229abc-9522-45d6-972d-ade32fd4c...@[EMAIL PROTECTED]
"ATreloar=
"
>
> <andrew.trel...@[EMAIL PROTECTED]
> wrote:
> > On May 16, 8:35=A0pm, CyberTaz <onlygeneralt...@[EMAIL PROTECTED]
> wrote:
> >> I'm not seeing anything of the sort here (G5 Dual 2 GHz, 1.5 MB, OS X
> >> 10.4.11) regardless of whether the page breaks are natural or manual.
H=
ave
> >> also included Section Breaks & graphics in the printed selection.
>
> >> Have you recently checked to see if there is an update for your
printer=
's
> >> driver software? Have you repaired permissions & restarted your Mac
sin=
ce
> >> applying the update?
>
> > Yes, and yes.
>
> >> What's the nature of the content you're trying to print? Does it
happen=
with
> >> *every* do***ent or just a certain one? Is it just a certain ****tion
of=
a
>
> > Just a certain do***ent, any part seems to trigger it (so long as the
> > selection straddles a page boundary)
>
> >> certain doc, or regardless of what ****tion of any doc? Any problems
wit=
h
> >> other print jobs or printing from other programs in a similar
fa****on? =
What
>
> > No.
>
> >> if you print to PDF or click the Preview button - even while the
> >> responsiveness is occurring?
>
> > No response.
>
> >> It helps if you provide complete details including specific OS X
versio=
n -
>
> > 10.5.2, all updates applied. Intel MacBook (1st Gen), 2GB RAM.
>
> >> especially when peripherals are involved - Word (as is the case with
an=
y
> >> program) has little to do with printing, saving, etc. other than
callin=
g for
> >> the service. It's up to the OS & device driver to carry the ball from
t=
here.
>
> >> Regards |:>)
> >> Bob Jones
> >> [MVP] Office:Mac
>
> >> On 5/16/08 1:53 AM, in article
> >> 60233979-7c97-4c4c-a0f1-7638bf686...@[EMAIL PROTECTED]
>
> >> "ATreloar" <andrew.trel...@[EMAIL PROTECTED]
> wrote:
> >>> I have just upgraded to Word 12.1.0. Now, if I select a chunk of
text
> >>> that spans a page boundary, and do a File->Print, as soon as I tick
> >>> "Selected Text", the CPU usage of Word climbs to over 100% (dual CPU
> >>> machine, obviously) and it becomes unresponsive. I have to Force
Quit
> >>> it. If I select a chunk of text *within* a page boundary, it is
fine.
>
>
Many thanks - option 2 (copying everything except the last para mark)
fixed it.
|
