Snow Leopard Finder / file selection sequence ?, Snow Leopard Finder / file selection sequence ?

When I was on Mac OS 10.5... If I had a folder open, and a column of files going down the right side of the desktop... If I opened one of the files (by having the file selected and hitting the keystroke: Command + Down Arrow) - then closed the file, then hit Command + Tab to select the Finder, then hit Down Arrow to select the next file (to open it) - that sequence worked as described.
Now with 10.6 that no longer works - if a folder is open on the desktop. If a folder is open, in the above sequence, after I hit Command Tab to select the (file I just closed in the) Finder, the selection moves to the folder rather than back to the file I just closed.
Which is a giant PITA because I can no longer open and close I column of files in the finder w/o having to reach for the mouse.
Seems like there should be a way to fix that.
be

Interesting, never used that method, but will take a look in about 10 hours wgen I have 10.6 available.

Similar Messages

My operating system is Snow Leopard Version 10.6.8. I moved files in Adobe Bridge, how do I sinc to Finder?

My operating system is Snow Leopard, Version 10.6.8. I rearranged files in Adobe Bridge, how do I sinc my Finder?

10.5.8 is Leopard, not Snow Leopard. You need the Snow Leopard DVD;
You can get it only by phone now from Apple.
In the US, call 1-800-MY-APPLE and ask for a sales assistant. Last quoted price was $19.99 for the single-user and $29.99 for the family licence.
For other countries, check here; http://support.apple.com/kb/HE57
Don't forget to ask for Sales; the tech support guys can't help.
If you want Lion, rather than Mountain Lion, the same Sales team can give you a download code to use at the Mac AppStore.
To get the App Store, you need to update your new Snow Leopard from 10.6.3 (which is the version on the installer) to 10.6.8 with the combo update; http://support.apple.com/kb/DL1399
Be warned that the upgrades will render a lot of older software unusable, and will need new drivers for printers and scanners in all likelihood.

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

I'm running snow leopard. The try to open any .mov file in Quicktime, and I get an error message that says, "The document xyz.mov could not be opened. The movie is not in a format that Quicktime player understands. I'm a recent upgrade to Snow Leopard.

I'm running snow leopard. The try to open any .mov file in Quicktime, and I get an error message that says, "The document xyz.mov could not be opened. The movie is not in a format that Quicktime player understands. I'm a recent upgrade to Snow Leopard.
Help!
Thanks, Mark

Unfortunately, the error message gives no details about what codec might be missing or what it needs.
If the file can't be opened in QT, it only means you cannot use the QT "Inspector" window to check what compression formats were used to create the file. It does not mean you can't use the Finder "Information" window to check on the compression formats or use a third party media information window (e.g., like VLC which will open many compression formats not supported natively by QT) to determine what kind of data is included in the MOV wrapper. If the file cannot be opened in any app, it is usually a good sign that the file itself is corrupted.
It's a stupid error message. Apple should do better than that.
Error trapping is quite extensive but there are still many areas which require human oversight. The message is telling you that either the container has a problem (e.g., not properly terminated, non-standard, or corrupted) or that one or more of the compression formats used is not supported by your current codec component configuration or that the data was encoded using non-standard settings or preferences not supported by QT or that the fourCC code does not match the data contained in the file or that there are timecode inconsistencies, etc., etc., etc. In short there are a near infinite number of possible problems for which it would be very difficult/nearly impossible to program error trapping depending on your sourcing of content and how you process it before it reaches the player app. Think of it like trying to play a BD disc in an DVD player.
I'll call Apple support when I get a chance.
Chances are good that they will end up sending you back here. In any case, it is often a good idea to post a sample file for examination by other QT users. At the very least, they should be able to tell you if the sample file will play on other systems which would indicate whether or not the file itself is bad and under the best of circumstances whould allow them to examing the file in detail for various common problems.

Apple has broken Windows file sharing in Snow Leopard

Hi Folks,
Having a serious problem here.
Apple has broken Windows file sharing in Snow Leopard. Many others on the forums are experiencing the same thing. I was almost ready to fully switch to the Mac, then I thought I would upgrade to SL, then this happened...
OK so I have a Windows Server 2003 Small Business Server. It's pretty much the same as the standard Windows 2k3 server except that it throws in a few extras (And takes some things away). I'm also lead to believe, that there is a difference w.r.t. password signing/encryption or something?
Anyways, if I try and connect to my SBS server with the correct username and password (In different formats: Domain\username or just username), I get a "Unable to connect to server. Check IP..." blablabla. This happens after the password prompt has come up.
If I try and connect to my standard windows 2003 server box, it does work, just very slowly (Again, referring to the whole thing about how SBS treats password security differently).
So I ask a couple of things:
1) It would be appreciated if any other forums members could maybe help me get this going?
2) A plea to Apple - please fix this. It all worked perfectly in Leopard!
Apple probably haven't tested SL against SBS 2003 server. A lot of companies don't do this either as they think that it is just the same as the standard 2003 server (Which i hope Apple have tested against!)
Thanks guys

I have the same problem. Here are the details:
External Hard Drive with LAN (Buffalo Drivestation Flexnet: http://tinyurl.com/kk5mmu)
Mac OS X 10.6, on 3 different Mac Mini's
This error occurs on all computers when trying to copy a file to the 'SHARE' sharepoint on the SMB Drive:
"The Finder can't complete the operation because some data in "filename" can't be read or written. (Error Code -36)"
I CAN
Access / Read / Write this Drive in Windows XP
Access / Read / Write this Drive in OS X 10.5.7
Make new folder on this Drive in OS X 10.6
See a .DS_Store file which 10.6 has written to the Drive
Save a document to the drive from the Text Edit save dialog in 10.6
Save a document to the drive from the Pages save dialog in 10.6
Duplicate a document on the drive using Terminal (cp Untitled.pages Untitled2.pages) in 10.6
Copy anything to any other computer on the Network using 10.6
I CAN NOT
Copy a document to the Drive in 10.6
Duplicate a document on the Drive in 10.6
Save a PDF or JPG to the drive from the Preview save dialog in 10.6
This error happens every time. It is easily reproducible.
I hope that this information helps Apple get on to the problem soon.

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.

I can't read in Mavericks DVDs and Bluray data burn with UDF system files burn with Snow Leopard, please help me. Thanks

i can't read in Mavericks DVDs and Bluray data burn with UDF system files burn with Snow Leopard, please help me. Thanks

They are DVDs with video files from a little more than 2 GB per file, were burned in Snow Leopard, with UDF file system, now that I updated to Mavericks when I try to read disks displays the directory in the finder a moment and then disappear and does not display them show them more. It is impossible to read the discs, but only those who were burned with UDF file system. Thank you for your help.

I downloaded an update for my Safari web browser to "snow leopard". When I click on the .dmg file, a window opens up with a .pkg file but when I click on the .pkg file I get a prompt saying that it doesn't know what program to open it with. with a

I downloaded an update for my Safari web browser to "snow leopard". When I click on the .dmg file, a window opens up with a .pkg file but when I click on the .pkg file I get a prompt saying that it doesn't know what program to open it with.

I suspect if you're trying to open a file in 08 that's been opened in 09 the file has been updated to 09 and will not open in 08.

'save as' dialog removes file extensions under Snow Leopard. How do I stop this?

When I save a web page I sometimes use an existing file name as a template to reduce the amount of typing and chance for errors. Before I upgraded to 'Snow Leopard' the file type (.html) was on the file name. Now it is removed. This doesn't happen in Safari. How can I stop this from happening?

Hi hbman-
Here is a Support article on how to troubleshoot file download and save issues:
[[Unable to download or save files]]
Hope that helps!

Choose file name in Snow Leopard

In Leopard, when I run the StandardAdditions command *choose file name* and I click on an existing file listed in the resulting *Choose File Name* dialog, the +entire file name including file extension+ is placed into the *Save As:* text box, and that is what is returned when I click the Save button.
In Snow Leopard, when I do the same, only the file’s +base name+ is placed into the text box, and only the +base name+ is returned.
I need the Leopard behaviour.

hungryjoe wrote:
Appending a filename to the returned result is rather trivial
Trivial? Consider, in Leopard and before:
  |    set f *to choose file name*
  |    +(* At this point, f is a file specifier and exactly one of the following is true:+
  |          +• the file specified by f does not exist; or+
  |          +• the user wants to overwrite the file.+
  |     +And the file specified by f is exactly what the user chose. *)+
That’s one line. Compare that to Snow Leopard:
  |     property FileNameExtension : ".pdf"
  |
  |     repeat
  |           set f to +POSIX file+ ((POSIX path of ( *choose file name* )) & FileNameExtension)
  |           try
  |                 alias f
  |           *on error* number -1728 +-- can’t get reference; i.e. file does not exist+
  |                 *exit repeat*
  |           *end try*
  |           try
  |                 tell application "System Events" *to get the* name *of the* result
  |                 *display alert* "“" & the result & "” already exists. Do you want to replace it?" ¬
  |                       message "A file or folder with the same name already exists. " & ¬
  |                             "Replacing it will overwrite its current contents." ¬
  |                       as warning ¬
  |                       buttons {"Cancel", "Replace"} ¬
  |                       default button "Cancel" ¬
  |                       cancel button "Cancel"
  |                 if button returned *of the* result is "Replace" *then exit repeat*
  |           *on error* number -128 +-- User cancelled+
  |                 +-- ask again+
  |           *end try*
  |     *end repeat*
  |
  |     f
  |     +(* At this point, f is a file specifier and exactly one of the following is true:+
  |           +• the file specified by f does not exist; or+
  |           +• the user wants to overwrite the file.+
  |     +But the script has had to force a file name extension on the user,+
  |           +so the file specified by f is not actually what the user chose. *)+
You might do it differently as a matter of style, but you can’t do it simpler and you can’t do it shorter.
(Rant: do you have any idea how much fiddling it took me to come up with
  |           set f to +POSIX file+ ((POSIX path of ( …
to work around the fact that AppleScript doesn’t do what the AppleScript Language Guide says on pages 43 and 88.)
Perhaps you should file a bug report/feature request, however you see it at [http://bugreport.apple.com>.
I’ll do that tomorrow.

Zip file created in Snow Leopard can't be opened on a PC

Hi,
I've created a zip file of a folder containing Word and pdf files using File>Compress in Snow Leopard.
After emailing to clients, they cannot open the zip file on their PCs.
Any help? I thought zip was supposed to be universal.
Thanks in advance!

All clients, or some clients? How big are the zip files?
Usually when this happens, one of two things is going on: one of your mail servers is truncating the message (cutting off part of the attachment) because the message exceeds some pre-determined maximum message size (or the mailbox goes over a quota), OR one of you is running a virus/malware scanner on your mail server that objects to certain file types (it's not uncommon to strip .ZIP, .COM, and .EXE files).
There's also the possibility that a Windows client just doesn't understand the file's type. While that shouldn't be, it does happen sometimes (I've seen it with Lotus Notes, for example). In that case, the recipient should save the attachment as a file on their desktop and open it from the desktop.

In snow leopard, you could see the size of each file. Is this the case for os lion?each file

In Snow Leopard, you could see the size of the file which was shown at the bottom of the file. This does not appear to be the case with OS Lion. Am I wrong? Thank you for your help.

If you're referring to desktop icons, right click on the desktop > Show view options > check "show item information".

I need safari 5 to update safari 4.02 for new email provider have leopard on a g5 powermac can only find 5.1 download for snow leopard

i need safari 5 to update safari 4.02 for new email provider have leopard on a g5 powermac can only find 5.1 download for snow leopard is 5 still available

Click here for it.
(59866)

I could not open .osx file on my snow leopard

i could not open .osx file on my macbook air 10.6.8 snow leopard. what should i do.

Where is this file, on your MBP, or on a CD or DVD?
Do you have Rosetta installed?
What did you expect to happen when you double-clicked on it? What actually happened?

How do I send files from my IMAC via bluetooth to my ne Ipad. They will not "pair" but they are connected and discoverable. I send a file from Imac snow leopard OS X 10.6 to the ipad but the failure message says the ipad does not have the ncessary servr

How do I send files from my IMAC via bluetooth to my new Ipad? They will not "pair" but they are connected and discoverable. I send a file from Imac snow leopard OS X 10.6 to the ipadusing bluetooth, but the failure message says the ipad does not have the necessary services. What are these? Do I neeed to have iphoto and ms word to send pix and .doc files?

File Sharing over Bluetooth is not a feature of iOS devices. iOS does not include the required Bluetooth profiles to allow this. You cannot add this feature, so you may as well stop trying.

I running snow leopard on my MBP- where can I find the drivers for windows XP if I install them via bootcamp? Thanks!

I running snow leopard on my MBP- where can I find the drivers for windows XP if I install them via bootcamp? Thanks!

You won't find them until you are in Windows.
Helps to read even print the guide.
If you have auto run enabled, which is a security risk, the Apple setup.exe will run.
Otherwise, just run that.
Either use your OS X DVD, or use the drivers downloaded by Boot Camp Assistant.
Two different ways to get them.

Snow Leopard Finder / file selection sequence ?, Snow Leopard Finder / file selection sequence ?

Similar Messages

Maybe you are looking for