Panther - Helpful Information for OS 10.3

[LRK@adobeforums.com]

Helpful information for those who have Word and Acrobat 6 Pro

Slow Microsoft Word launch after Acrobat 6.0 Professional installation

Users are noticing slow launches from Microsoft Word v.X (part of the Office v.X package) after installing Adobe's recently released Acrobat 6.0 Professional package.

The installer places a number of resources including a "PDFMaker.Lib" file in the "Microsoft Office X" folder, which may be causing the delay in launch - or a complete stall accompanied by the spinning beach ball. MacFixIt reader Jim Delaney writes:

"I'm now experiencing an extraordinarily long start-up delay in MS Word with a fresh Normal template (i.e. startup with no Normal template in the MS Office Templates folder) after installing Acrobat 6.0 Professional. Trying to start with any normal template in the Templates folder results in a rotating cursor which never stops spinning (I'd call it an application freeze or hang, but it would actually appear that the application is trying to do something."

PDFMaker.Lib provides resources that get inserted into the Normal template for a Toolbar and macros in Word. These appear to be taking a very long time to initiate, or are stopping the Word launch process altogether.

This problem does not appear in Excel or PowerPoint.

Removing PDFMaker.Lib from the Microsoft Office X folder will resolve the problem, but obviously you will lose Acrobat functionality in Word.

Found at MacFixIt <http://www.macfixit.com/article.php?story=20030603073523853&query=spinning +beach+ball+word>

[LRK@adobeforums.com]

For some reason I started noticing the SBB again only this week. I began to pay attention to when it showed up. I was able to target MS Word X. So I went to MacFixIt and typed in "Spinning Beach Ball Word" and found that report.

I removed the PDFMaker.Lib from Word, restarted and was amazed at the difference. The SBB is gone.

The fact that the SBB just showed up this week reveals that Ann might be right in that something else is playing a factor... but removing that file corrected it. I also noticed that Word starts up in less than 2 seconds now.

[Ann_Shelbourne@adobeforums.com]

Curiouser and curiouser:

I replaced PDFMaker.Lib and launching Word now takes only 3 seconds!

However, I did prune the contents of MS fonts folder……

[LRK@adobeforums.com]

The genius is in her laboratory... :)

[Cindy@adobeforums.com]

Be sure a re-boot your machine in between tests. I notice that it is the first open that takes so long. After it has been opened it then opens real fast with no changes.

[LRK@adobeforums.com]

Now to resolve the electric currents that are still sparking all over the place. :)

[LRK@adobeforums.com]

Hey, watch it there John! :)

[LRK@adobeforums.com]

DiskWarrior 3.01

Has anyone else used DiskWarrior since the 3.01 upgrade?

Just wondering if it's working okay and safe to use as a maintenance tool occasionally.

[Glenn_Palmer@adobeforums.com]

Help! I used version 5.5 of Photoshop with MacOS 9.0.2 with no problems. I recently upgraded to Mac X.3 & 9.2. My Acer 124OUT scanner is seen by my Mac G4 under the apple in ABOUT YOUR MAC. However, my version of photo shop does not see the scanner even after downloading the newest version of the scanner driver and using the uninstall then reinstall. It worked once then the scanner was no longer seen under Mirascan, the software, in the USB mode.

I'm not sure if it's an Apple, Photoshop, Acer or me problem. Any Ideas how I can narrow or solve the problem?

[LRK@adobeforums.com]

My guess is that the scanner software is the problem. Have you checked for an upgrade for your driver?

[Cindy@adobeforums.com]

Take Image Capture out of your Applications folder (move it somewhere) and re-install your scanner software. See if that works

[Larryr544@adobeforums.com]

And restart your machine.

[Rick_McCleary@adobeforums.com]

OK, I know I'm a little behind the eight ball here, but I just upgraded to 10.2.8 from 10.2.6.

There's a strange problem--the menu bar clock blinks incessantly.
And inconsistently.
Can't get it to stay on contiunously.

I ran Cache Out X, repaired permissions. I've trashed the MenuBarClock preference and retarted, but the problem persists.

Any ideas?

Thanks - Rick

[Doug_Katz@adobeforums.com]

Rick, try chucking your Finder preference file. Dunno that this will work, but I've
had to do that once after an upgrade when desktop stuff was a little wack.

Now how 'bout Linda's question: Disk Warrior 3.01 upgrade. Are those of you
using it problem-free?

[Zeb@adobeforums.com]

I have used it once and it worked OK.

[Doug_Katz@adobeforums.com]

(Now I'm gonna interrupt my own attempt to get back to Linda's question...
undiagnosed ADD perhaps?):

Y'all remember in ATM Deluxe you could display "background information"
about a PS font... information that obviously was written right into the font
file? Stuff like who designed the font, when, and so forth? Is there any way
to display that information in FAP?

And did anyone see the article in the 2/8/04 Sunday NY Times about the
lamentable death of Adrian Frutiger's Courier at the US State Department?

And, oh yes: Linda's question about the Disk Warrior 3.0.1 upgrade?

[Buko@adobeforums.com]

Glenn, I have yet to see a scanner that works through OSX and classic even if you have the drivers loaded. your best bet is VueScan <http://www.hamrick.com>

[Zeb@adobeforums.com]

My Umax 5450 scanner works fine, 10.3.2/9.2.2 with Vistascan 3.7.5. :)

[Ramón_G_Castañeda@adobeforums.com]

Doug,

did anyone see the article in the 2/8/04 Sunday NY Times about the lamentable
death of Adrian Frutiger's Courier at the US State Department?





We had some fun with the news over in the Typography forum.

Just a couple of comments, though. The event is far from lamentable. Courier is, at least in my view and that of many others, arguably the ugliest typeface ever used.

Courier is by no means Adrian Frutiger's baby. It was designed eons ago by Howard Kettler of IBM for used in non-proportional typewriters in the mid 1900's. Frutiger simply redrew the typeface much later on, for use in the Selectric series of typewriters.

The original design parameters for Courier have nothing to do with modern typography, or even with good typography at all. It was intended as a typewriter font that had to meet the characteristics of being mono-spaced (hardly a goal of any typographer) to accommodate the limitations of mechanical typewriters, of not being too sharp and well defined so that the typewriter strokes would not cut through the bond paper, carbon paper (remember that?) and any subsequent copies, and of assuring that the counters and bowls (inner spaces) of letters like em, d, p, b, q, o, e, etc., would not fill with gunk from the typewriter ribbon too quickly.

Except for the first one, absolutely none of those considerations have a place in the typographic world or in the world of computers. It was adopted in the computer world only because a monospaced font was needed for programming and tabulations.

Good riddance.

[LRK@adobeforums.com]

Glen: I think Buko's suggestion might be a good one. When I was running OS9 and PS5 on a computer at work and at home I found the scanner drivers to be a constant bug thing.

Doug: Thanks for bringing my question back up about DiskWarrior. As for Courier, it's still my husband's favorite font for business. :\ Mainly for typing out minutes from board meetings.

Ronald Lanham in Post #732 gave us a heads up on the experience he had with DW 3.01...

WARNING: My update of DiskWarrior 3.0.1 is giving me error messages during
the process (i.e. not in the DW window) that volumes have been improperly
removed. It occurs between Step 8 and 9. (And I did no removing of any peripherals,
drives, partitions, etc.)

The exact error message is: Device Removal

The device you removed was not properly put away. Data might have been lost
or damaged. Before you unplug your device, you must first select its icon
in the Finder and choose Eject from the File menu.

It appears that the OS (10.3.2 in my case) is having problems with how DW
X 3.0.1 is unmounting the volumes. This doesn't happen for all partitions
but it has happened for several. And this is whether I have the partitions
visible in the Finder on the Desktop or if I have them hidden.

Make sure your partitions/disks are backed up before you use this update.

This is the very first time I have ever seen this or any other error messages
appear while using DW... and I've been using it virtually since it first
came out many years ago.