File Sorting Confusion in Finder in OS X Snow Leopard

I am about to embark on renaming thousands of image files and want to make sure that once renamed, they all sort correctly. On running some simple naming tests to see how things may look in Finder, I have come up against a perplexing problem, which has utterly confounded me.
I duplicated a file witht a name consisting of a three digit number, several times. I renamed each duplicate by adding a series of zeros at the beginning consecutively, from one zero to three. These sorted as expected, as below. (I say "as expected", but I didn't know what to expect. They looked "uniform" though!)
000123.tif
00123.tif
0123.tif
123.tif
I repeated this using 234.tif, with the same results. However when I tried again with a randomly chosen number of 392.tif, they were sorted like this:
0392.tif
00392.tif
000392.tif
392.tif
Two further repeats using 427.tif, followed by 850.tif resulted in different, yet incorrect sorting arrangements to both those as well.
As if that wasn't confusing enough, I copied and pasted all sixteen files to a new folder. With the exception of the 123.tif and 234.tif series of files, all of them displayed in a completely different sorting arrangement to the originals. Repeating that, resulted in yet another configuration.
I've tried selecting different sorting arrangements in View and even restarted my Mac, with no success .
Can someone explain what is happening here?
Thanks in advance.

For photos at least, maybe Video also though, GraphicConverter has a powerful tools for many things, like resize...
http://www.lemkesoft.com/
Just be sure to save the changed one with a different name to peserve your big original pic

Similar Messages

HT5055 Just updated to lion and my cctv access has stopped functioning all I get is a white screen in the middle of the control panel where the camera shots should be. I think it is caused by JAVA but am confused as when i view on snow leopard it works

Just updated to lion and my cctv access has stopped functioning all I get is a white screen in the middle of the control panel where the camera shots should be. I think it is caused by JAVA but am confused as when i view on snow leopard it works can you help

Open "Java Preferences" either from spotlight or your utilities folder...it's probably going to say you need to install a java runtime. Then just click install!

How do I get multiple files/photos to stay open in CS3/mac snow leopard .7

I just switched over to a new mac book pro with snow leopard (version .7 I think). When working in Photoshop CS3 Extended, I can't seem to keep more than one file/photo open at a time. I have one open, then I try to open a second one and the one that had been open just closes. Can't find it minimized on the dock or anything - it just closes. This is craziness for photoshop.
Anyone else have this issue? What is the fix?

It is not possible to see two open documents side by side while you're in Tabbed Mode (duh!). You need to
GET OFF tab mode!
That's what guru Chris Cox has been trying to tell you from the very beginning (post #1).
So Uncheck the preference to Open Documents as Tabs,
Photoshop menu > Preferences > Interface > Panels & Documents > Open Documents as Tabs
then set your Screen Mode to Standard Screen Mode
You really should read the User Guide. Download the ENTIRE HELP file as a PDF from the Adobe Help site and study it carefully.
Wo Tai Lao Le
我太老了
Message was edited by: Tai Lao

RAW CR2 files cause Bridge / PS CS3 to quit after Snow Leopard

OS: Snow Leopard Fresh Install
Camera: Canon XTi
Files: Canon RAW CR2
Issue: Access of ANY kind to a RAW file causes the app(s) to quit.
Detail: Everything was fine in Leopard but for various reasons I did a fresh install of Snow Leopard. Wiped the drive and installed clean. Installed iLife 09 and then did any Apple updates. I then installed CS3 and did all the Adobe updates (Almost 600 MB). Used PS for some graphic stuff with no issue and thought everything was good until today. Went to Bridge and simply tried to navigate to my RAW photos and it quit. Tried opening a RAW in PS... same thing. Checked the ACR version and is was 4.6 but I reinstalled anyway... same. So, I uninstalled the fresh copy of CS3 and reinstalled to be safe... same. OK, now it was testing time. Navigated to the RAW files in Finder and can view them fine. I can quick preview them, open them in preview etc, so the OS raw support is fine. Same thing happens just trying to open the file with PS CS3 since it open using RAW.
I removed the RAW plugin and Bridge stayed open fine and displayed the files as generic thumbs. Put the plugin back and it dies again.
In Leopard the RAW Prefs were set to store the settings in the RAW database instead of sidecar files and I have tried putting the database file in from the pre-snow leopard backup. No luck. I am totally stumped any any ideas are welcome. I am about to restore the Leopard image.
Thanks in advance,
Razz

Thanks for the idea Carolyn.
Unfortunately it did not fix it. I had tried it before and tried it again after your post. Thing is, it can't be the cache since the install of bridge has never been used. As soon as I load it and try to go view my files it quits. I would expect this from an upgraded SL install but an erase & install with fresh CS3 and all the OS and Adobe updates should be smooth. I really don't want to go back to Leopard but have to be able to mess with my photos. Why would removing the raw plugin stop the failure? It is 1 file, the correct version and fresh installed. Not sure what to do except maybe start over and yet that could still fail and takes a LONG time. I hate to upgrade to CS4 since I am not sure where the issues is.
Maybe install SL again over the top as an upgrade?
Any other ideas?
Thanks, Razz

Finder crashes repeatedly under Snow Leopard

So, after updating to Snow Leopard from Leopard, I've got a problem with my Finder. Here's the deal...
Mac Mini, Intel Core Duo, 1.83ghz, 2gb
With Firefox 3.5 as the only active app, my Finder will crash while dragging files (jpg, pdf, flv) from 1 folder to another. It's not repeatable in any reliable way and doesn't always occur. I'd say 1 time out of 10 - 15 the Finder will crash and restart.
I've repaired permissions, cleaned all caches with Snow Leopard Cache cleaner, deleted Library/Preferences/com.apple.Finder.plist to no avail. Thought it may have been a third-party Quicklook generator left over from Leopard so I deleted the 2 generators which seemed relevant (folder.QLgenerator, flv.QLgenerator), restarted, still crashing.
Other potentially pertinent info... Have the latest version of Perian installed, problem occurs with or without Firefox being active.
I've pasted the crash long from a typical event. If anyone could help me decipher where to look I'd be eternally grateful (or at least really happy...). Thanks in advance for the help.
Process: Finder [188]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Identifier: com.apple.finder
Version: 10.6 (10.6)
Build Info: Finder_FE-6650000~6
Code Type: X86 (Native)
Parent Process: launchd [177]
Date/Time: 2009-09-20 16:35:11.053 -0500
OS Version: Mac OS X 10.6.1 (10B504)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000261
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.QuickTime 0x91d8780f PrivateQTGetMoviePlayabilityState_priv + 62
1 com.apple.QuickTime 0x91d877c1 QTGetMoviePlayabilityState_priv + 33
2 ...ickTimeComponents.component 0x9776f1c2 internalDoAction + 9663
3 ...ickTimeComponents.component 0x9775e59c _MCIdle + 61
4 ...ple.CoreServices.CarbonCore 0x946d360c CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
5 ...ickTimeComponents.component 0x97759e94 _MCComponentDispatch + 111
6 ...ple.CoreServices.CarbonCore 0x946cbcb6 CallComponentDispatch + 29
7 com.apple.QuickTime 0x91d8777f MCIdle + 37
8 com.apple.QuickTime 0x91d85669 QTOMovieObject::SendCommand(unsigned long, void const*) + 899
9 com.apple.QuickTime 0x91d68d8a DispatchQTMsg(void const*, unsigned long, unsigned long, unsigned long, QTOGenericObject*) + 240
10 com.apple.QuickTime 0x91d68bee QTObjectTokenPriv::SendMessageToObject(QTMessagePr iv*, unsigned long) + 178
11 com.apple.QuickTime 0x91d68155 QTObjectTokenPriv:ispatchMessage(QTMessagePriv*, void const*, __CFAllocator const*, unsigned long, unsigned long, ComponentMsgParam*, unsigned long, unsigned long) + 1249
12 com.apple.QuickTime 0x91d852e4 QTSendToObject + 98
13 com.apple.QTKit 0x925ac232 QTObjectTokenExecuteCommand + 83
14 com.apple.QTKit 0x9257ec02 -[QTMovie_QuickTime idle] + 303
15 com.apple.CoreFoundation 0x93c93139 _CFSetApplyFunction_block_invoke1 + 25
16 com.apple.CoreFoundation 0x93c7858a CFBasicHashApply + 202
17 com.apple.CoreFoundation 0x93c93101 CFSetApplyFunction + 177
18 com.apple.QTKit 0x925328f0 +[QTMovie_QuickTime idleAllMovies:] + 132
19 com.apple.Foundation 0x9517c9d4 __NSFireTimer + 141
20 com.apple.CoreFoundation 0x93c90eee __CFRunLoopRun + 6846
21 com.apple.CoreFoundation 0x93c8ed34 CFRunLoopRunSpecific + 452
22 com.apple.CoreFoundation 0x93c8eb61 CFRunLoopRunInMode + 97
23 com.apple.HIToolbox 0x92facfec RunCurrentEventLoopInMode + 392
24 com.apple.HIToolbox 0x92facda3 ReceiveNextEventCommon + 354
25 com.apple.HIToolbox 0x92facc28 BlockUntilNextEventMatchingListInMode + 81
26 com.apple.AppKit 0x95a36c95 _DPSNextEvent + 847
27 com.apple.AppKit 0x95a3650a -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
28 com.apple.AppKit 0x959f869b -[NSApplication run] + 821
29 com.apple.AppKit 0x959f0735 NSApplicationMain + 574
30 com.apple.finder 0x000061ca 0x1000 + 20938
31 com.apple.finder 0x0000618d 0x1000 + 20877
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x968d203a kevent + 10
1 libSystem.B.dylib 0x968d2768 dispatch_mgrinvoke + 215
2 libSystem.B.dylib 0x968d1bf9 dispatch_queueinvoke + 183
3 libSystem.B.dylib 0x968d198a dispatch_workerthread2 + 234
4 libSystem.B.dylib 0x968d1401 pthreadwqthread + 390
5 libSystem.B.dylib 0x968d1246 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib 0x968ab7da machmsgtrap + 10
1 libSystem.B.dylib 0x968abf47 mach_msg + 68
2 com.apple.CoreFoundation 0x93c8fdbf __CFRunLoopRun + 2447
3 com.apple.CoreFoundation 0x93c8ed34 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x93c947a4 CFRunLoopRun + 84
5 com.apple.DesktopServices 0x980752a9 TSystemNotificationTask::SystemNotificationTaskPro c(void*) + 643
6 ...ple.CoreServices.CarbonCore 0x9468a9fa PrivateMPEntryPoint + 68
7 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
8 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x968ca756 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x93ccf04d __CFSocketManager + 1085
2 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
3 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x968d1092 _workqkernreturn + 10
1 libSystem.B.dylib 0x968d1628 pthreadwqthread + 941
2 libSystem.B.dylib 0x968d1246 start_wqthread + 30
Thread 5:
0 libSystem.B.dylib 0x968d1092 _workqkernreturn + 10
1 libSystem.B.dylib 0x968d1628 pthreadwqthread + 941
2 libSystem.B.dylib 0x968d1246 start_wqthread + 30
Thread 6:
0 libSystem.B.dylib 0x968ab83a semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x968d93c1 pthread_condwait + 1066
2 libSystem.B.dylib 0x96908208 pthreadcond_timedwait_relativenp + 47
3 com.apple.finder 0x0002777f 0x1000 + 157567
4 com.apple.finder 0x000276ed 0x1000 + 157421
5 com.apple.finder 0x00006e12 0x1000 + 24082
6 com.apple.finder 0x00006d36 0x1000 + 23862
7 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
8 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x968d1092 _workqkernreturn + 10
1 libSystem.B.dylib 0x968d1628 pthreadwqthread + 941
2 libSystem.B.dylib 0x968d1246 start_wqthread + 30
Thread 8:
0 libSystem.B.dylib 0x968d1092 _workqkernreturn + 10
1 libSystem.B.dylib 0x968d1628 pthreadwqthread + 941
2 libSystem.B.dylib 0x968d1246 start_wqthread + 30
Thread 9:
0 libSystem.B.dylib 0x968ab83a semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x968d93c1 pthread_condwait + 1066
2 libSystem.B.dylib 0x96908208 pthreadcond_timedwait_relativenp + 47
3 ...ple.CoreServices.CarbonCore 0x946ab435 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore 0x946ab173 TSWaitOnSemaphoreCommon + 511
5 ...ickTimeComponents.component 0x97684255 ReadSchedulerThreadEntryPoint + 4698
6 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
7 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x968ab83a semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x968d93c1 pthread_condwait + 1066
2 libSystem.B.dylib 0x96908208 pthreadcond_timedwait_relativenp + 47
3 ...ple.CoreServices.CarbonCore 0x946ab435 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore 0x946ab173 TSWaitOnSemaphoreCommon + 511
5 ...ple.CoreServices.CarbonCore 0x94705674 AIOFileThread(void*) + 1127
6 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
7 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x968ab7da machmsgtrap + 10
1 libSystem.B.dylib 0x968abf47 mach_msg + 68
2 com.apple.CoreFoundation 0x93c8fdbf __CFRunLoopRun + 2447
3 com.apple.CoreFoundation 0x93c8ed34 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x93c947a4 CFRunLoopRun + 84
5 com.apple.QTKit 0x92547727 QTCALayerRendererPendingQWorkLoop + 586
6 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
7 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x968ab7da machmsgtrap + 10
1 libSystem.B.dylib 0x968abf47 mach_msg + 68
2 com.apple.CoreFoundation 0x93c8fdbf __CFRunLoopRun + 2447
3 com.apple.CoreFoundation 0x93c8ed34 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x93c947a4 CFRunLoopRun + 84
5 com.apple.QTKit 0x925fbd5b QTVisualContextImageProviderWorkLoop + 114
6 libSystem.B.dylib 0x968d8f39 pthreadstart + 345
7 libSystem.B.dylib 0x968d8dbe thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffff ebx: 0x91d877df ecx: 0xa0170cac edx: 0x00000000
edi: 0x00131b87 esi: 0x008b846c ebp: 0xbfffdfb8 esp: 0xbfffdf70
ss: 0x0000001f efl: 0x00010286 eip: 0x91d8780f cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000261

Hello All:
After reading many of the posts here and elsewhere in the discussions, I thought I'd add my own experience because nothing I've read sounds quite this bizarre. I installed Snow Leopard 3 days ago an everything seemed to be working fine. That lasted about 48 hours. Yesterday, I was copying the first CD of an audiobook, and the program froze. I restarted the computer and at the desktop, there was a Finder crash report (send to Apple). Before I could punch the button, the Finder attempted to relaunch, and another report came up. And another. And another. I'm not sure if the reports went to Apple, but as you'll see, if they did, Apple knows me pretty well by now.
I got the Shutdown panel to come up while this was going on and shut the computer down. When I rebooted, the same thing happened. So I started up from the Snow Leopard Install disk and ran Permission repair and Disk repair. Both showed no problems needing repair. Rebooted. Same thing.
The process was really fast. In the time it took me to shut down, 8 or 10 relaunches and 8 or 10 crash reports. So I started up from Disk Warrior, Snow Leopard version, rebuilt the directory and and checked all the files. No anomalies. Rebooted, and the same thing happened.
Of course, in my zeal to make this horror go away, I had completely forgotten about Safe Boot. So I did that, and went to the Preferences folder to toss com.apple.finder.plist. What a surprise. There were 30 or 40 (or maybe even 50) of those files, all except the most recent one suffixed with a number (example: com.apple.finder.plistx37g8d0 - that's not one of the real numbers). (I'm sure a Unix person could probably quickly explain this, but I thought it was one of the strangest things I've ever seen. It does seem clear that Finder was making a new plist every time it tried to relaunch. But it wasn't deleting any of the old ones.)
So I scrolled through screen after screen, selected and deleted them all. Rebooted and the computer came back. More or less. Now I seem to be experiencing random crashes, especially QuickLook when I'm in the middle of Spotlight. Also, some other crashes with names I don't even recognize because (I'm guessing) I'm not supposed to know they exist. Today those crashes seem to be slightly fewer (but not completely absent). And there were absolutely no crashes for the first 48 hours I used the new operating system. All my third party software was updated before I installed Snow Leopard.
I guess I'm not really asking for advice (but it would be appreciated, none the less). I could reinstall Snow Leopard, but from what I've read in the forums, that often does not seem to help very much. Even though, on this computer, I won't be able to enjoy 64-bit goodness, there are reasons I really don't want to go back to Leopard. First, the new system has things I like - upgrade to Automator, which I use a lot, new Services and others. Second, and more importantly, at least 2 of the third party apps I use a lot have revised upward to 10.6 only. So I guess I'll wait and hope for the best. But I must say, in 20 years of using Macs I've never come across anything quite this strange.
Sorry to bore you all by being so long-winded, but I thought that if anyone else ran into this weird situation, they might enjoy knowing they aren't the only ones.
John

Using Find My iPhone with Snow Leopard and iPhone 4S

I just upgraded my family's three iPhones from 3GS to 4S. I have a family MobileMe account and would like to continue to use Find My iPhone. I cannot upgrade my OSX on my Macbook Pro past Snow Leopard without rendering a professional app that I use for my business unusable. Is there a way to make this work with the new phones without upgrading to Lion / enabling iCloud? That is unfortunately not an option for me until the pro software app is made Lion compatible. Thanks.

I suppose you could set up a dual-boot environment and keep Snow Leopard in a small partition to run your business software. Clone your Snow Leopard partition into a second partition (with SuperDuper or similar) and upgrade this partion to Lion. Then remove unnecessary applications from the Snow Leopard partition and resize it to save space.
This arrangement would allow you to run Lion as you primary OS with most of your applications and maintain a boot option to Snow Leopard to run your business software until its updated. See http://reviews.cnet.com/8301-13727_7-20081187-263/how-to-keep-snow-leopard-when- upgrading-to-lion/.

Where do I find retail install for Snow Leopard?

Like, I keep seeing the upgrade packages on the store.apple.com but I don't see anything to just buy a fresh Snow Leopard OS to install on a hard drive that is totally blank. The Family Leopard pack for 49.99 just seems a little cheap to be a full install instead of an upgrade... I would like to find the full install but I am not seeing it on the apple store site.. maybe I am just blind....
BTW, this is on a macbook.

Apple does recommend that you purchase the Mac Box Set if you're upgrading from Tiger to Snow Leopard, but in this situation, you can get by with just the Snow Leopard disc, Single User ($29) or Family Pack ($49). Despite it's much lower price than previous Mac OS X operating systems, the disc does indeed work as a standalone installer.
I've sold hundreds of licenses of Mac OS X Snow Leopard, and I have yet to get a complaint.

Mac Pro can't find hard drive with Snow Leopard installed on

Hello there,
I have a three harddrive setup.
Harddrive 1 is in bay 1 and has two partitions.
1: For system and apps
2: For Documents and stuff
Hard drive 2+3 are in Bay 2+3 and are combined to a RAID 0 drive.
Some time ago I installed Leopard and the brand new an formatted hard drive.
It happened that it always took 2 start ups to run Leopard because always on the first time it didn t find the system on hard drive one. Pushing the 'D' button often helped.
Of course that was nothing to work with, although I at least could get some work done, once I loaded Leopard successfully.
So I tried Disk Utility, fsck without success.
I also tried the way of using fdisk to mark the partion as active, which only resulted in now not being able to boot at all.
Booting from DVD I also tried choosing my Leopard install on my hard drive as boot device (it has always shown up here) but still without success.
I am afraid things are quite messed up, since there were a few things happening at one time, which I am not overly happy about now. (Installing new RAM, installing SNOW LEOPARD on the new harddrive 1 in bay one, having still the RAID with LEOPARD on in bays 2+3).
I am already certain to do a fresh and complete reinstall of the system, I have my backup, but still there is some iTunes music and a few documents I haven't backed up yet, which I'd rather would not like to lose...
Put it short:
What could I do to get my system running at least once?
Thanks a lot,
max.

After some research I found out about the nice TargetDiskMode which I used to save all my important data with my MacBook.
http://support.apple.com/kb/HT1661
Ready to perform a complete and fresh install now!
Max.

Routinely can't find OS on Bootup - Snow Leopard

Every time I start my computer I have to hold down the "X" key to help it find Snow Leopard. I can also hold down Option to help it find the boot disk. I have no other operating systems on any of the hard drives. I have 4 internal hard drives. I just don't want to have to do this everytime. I'd like to press the power button to turn it on and go get some coffee.

Often this has to do with corrupt PRAM. In turn that is often related to a bad PRAM battery. You might get more help on that on the Mac Pro hardware forum. Depending upon how much you leave your computer totally disconnected from power a PRAM battery may only last a couple of years.
[Texas Mac Man's PRAM, battery, PMU tutorial|https://sites.google.com/site/macpram/mac-pram-nvram-cuda-pmu-battery- tutorial]
[Apple's PRAM reset directions|http://docs.info.apple.com/article.html?artnum=2238]

Mount option in finder is missing in snow leopard

with Leopard it was possible to click on a folder or drive then more option, this is not possible anymore. they must forgotten this option.

Unless I don't understand what you're saying, CONTROL-clicking on an item does what you want.

After software update for Lexmark printer, cannot print document as a file is missing. My iMac runs with Snow Leopard.

I have a Lexmark 3500 - 4500 series printer connected to my iMac via USB (as my iMac won't do the printing wirelessly. My iMac runs with Mac OS X, Snow Leopard, Version 10.6.8.
A few days ago, there were several software updates that I have installed as there was mention that they were for Mac OS X Lion.
Today, I tried to print a document, and it failed. The error message was: "Missing component: /Library/Printers/Lexmark/Drivers/.Resources/3500-4500 Series Color 2.lut".
I have re-installed the software from Lexmark without success.
Has anyone had a similar issue who can advise me, please?
Thank you.
Philippe

Have you tried installing the Lexmark software from the Apple site:
Lexmark Printer Drivers v2.4 for Mac OS X v10.6
You are running 10.6 which the above link is for, maybe Lion (10.7) doesn't need everything that 10.6 does. Try re-installing using the above link.

Where can i find a v10.6 Snow Leopard installation disc?

question above

Answer below:
http://store.apple.com/us/product/MC573Z/A?fnode=MTY1NDAzOA&mco=MTM3NDgwNzM

Can't open any excel files after installing Snow Leopard

I can't open any excel files after installing Snow Leopard. Is anyone else having this problem?
I have a standard iWork '08 install. Has anyone experienced? And better yet, know of a fix?

Welcome to Apple Discussions
Most users who have had a problem opening Office files with the iWork apps after upgrading to Snow Leopard have the problem fixed by updating to the latest versions. For iWork '08 that is Pages 3.0.3 & Numbers 1.0.3. For iWork '09 it's Pages 4.0.2 & Numbers 2.0.2. I don't use Keynote, but it should also be updated. If you're not running the latest versions & Software Update says your software is up to date, make sure the applications are where the installer initially put them. The updaters are very picky. If the location is not where the updater is programmed to look or if the folder doesn't have the name the updater looks for, it will not work. The applications cannot be renamed or moved. They must be in the iWork '08 or iWork '09 folder in Applications. That iWork folder must be named iWork '08 or iWork '09. If it doesn't have the '08 or '09 Software Update won't find them & the updaters won't work.

Freehand crashes in Snow Leopard when opening files

If you have the problem of Freehand MX etc crashing when opening files in Snow Leopard then this is for you.
In the Freehand application folder is a application callled (Freehand Clip Art Viewer) open this and use it to navigate to you file location, have Freehand open. Then just double click on the thumbnail of your file and it will open without any crash report.
Would pay to add this to the dock beside the Freehand Icon.
After an hour on the phone help desk advised me that freehand has been upgraded to Illustrator... Some people dont want this and i hope its helps a few hardcore Freehand nutters :-)

Thanks for the tip. I'll add another.
I've come across a few old-version FH files with missing fonts that would crash FH.
I use FontAgent Pro, with auto-activation turned on, as my font manager. Usually there's no problem. FAP activates unactivated fonts and the file opens properly.
However, I think that Snow Leopard sometimes incorrectly deals with font info in old FH files, and this can lead to a crash.
I find that if I open the FontAgent Pro application window first, and then open the problem file in FH, there's no crash. I get Freehand's 'missing font' dialog and am able to select an alternate font.

How to import raw files from nikon d750 to snow leopard

I can import raw files from my Nikon d80 to iPhoto on Snow Leopard without having to install Nikon software. However iPhoto won't import raw files from my Nikon d750. Has anyone out there had this problem?.

Mountain Lion is what Lion should have been in my opinion. I used Lion for a week and reverted to Snow Leopard. Another option is to have 2 operating systems installed, each on a different partition. You could then stay with Snow Leopard for most of your work.
Check to make sure your applications are compatible. PowerPC applications are no longer supported after 10.6.
Application Compatibility
Applications Compatibility (2)
Do a backup before installing.

File Sorting Confusion in Finder in OS X Snow Leopard

Similar Messages

Maybe you are looking for