Prevent creation of .DS_Store files under Lion

I'm trying to do this on network drives; I understand it may not be possible on local drives. So I ran this command as sudo:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
It didn't work. It's still creating the files. I'm running 10.7.3 on a Macbook Pro. Is this even supposed to work under Lion?

You could try the free utility TinkerTool:

Similar Messages

How to open or install fonts from a .suit file under Lion?

How to open or install fonts from a .suit file under Lion? Thanks!

although I believe I *have* used the .suit extension when I was creating suitcase files for TrueType fonts.
You can get away with that because you haven't really changed anything. It's already a suitcase file, with a Type code of FFIL (the Creator code is mostly irrelevant). Adding .suit still tells the OS it's a suitcase.
However, if you do something silly like change the Type code to LWFN (the outline portion of a PST1 set), then neither Font Book, or any other font manager knows what to do with it. It's recognizing the LWFN code, but the data structure of course doesn't match. The file is still a Mac legacy TrueType font. Suitcase Fusion 5 tosses this on the screen when I change the Type code to the wrong one:
Changing the extension to something obviously wrong, like .otf produces the same message. It's trying to parse the data according to what the extension says it is, and nothing lines up.
Trying to use .ttf or .ttc also doesn't work. A Mac legacy suitcase TrueType font is not built the same as a .ttf or .ttc font. Either is technically correct (it is a TrueType font), but that's the only similarity. What's happening in that case is Mac legacy TT fonts have all of the data in the resource fork. When you add .ttf or .ttc to the name, the OS and any font manager then tries to find the data in the data fork. Nothing there.

How to permanently stop creation of .DS_Store files on desktop?

Ever since attempting to use .ds_store on Terminal to find hidden iTunes files, the system will not stop creating .DS_Store files on the desktop. I've tried using the defaults write com.apple.desktopservices DSDontWriteNetworkStores true command, to no avail. I'm relatively new to using Terminal, so if someone could offer any tips, that would be good. The file creation is more of an annoyance than a real problem, but I want to know how to stop it, since there is no info on this in other places. Thanks! ~ Eva

The DSDontWriteNetworkStores command only prevents creation on shared network drives.
.DS_Store files are always created locally (unless using something like TotalFinder to prevent that)
The reason you now see them on the Desktop is likely because during the process to track down iTunes files you enabled the option to "see" hidden files - issue the following command in Terminal to "undo" that:
defaults write com.apple.finder AppleShowAllFiles false
If you want the change to be immediate (rather than after logging out & back in or rebooting) then simply "restart" the Finder app, again in Terminal:
killall Finder
Johnny.

Preview crashing on several files under Lion "object cannot be nil"

Hi,
with several different files - old and new ones -, Preview simply crashes with the following error message after installing Lion on my MacBook Pro:
2011-08-15 09:16:06.255 Preview[435:60b] An uncaught exception was raised
2011-08-15 09:16:06.256 Preview[435:60b] *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
2011-08-15 09:16:06.262 Preview[435:60b] (
          0   CoreFoundation                      0x00007fff8fe25986 __exceptionPreprocess + 198
          1   libobjc.A.dylib                     0x00007fff95bbed5e objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff8fdcc818 -[__NSArrayM insertObject:atIndex:] + 296
          3   Preview                             0x0000000104f46cf9 Preview + 23801
          4   Preview                             0x0000000104f46a17 Preview + 23063
          5   Preview                             0x0000000104f465d1 Preview + 21969
          6   Preview                             0x0000000104f46175 Preview + 20853
          7   libdispatch.dylib                   0x00007fff9144990a _dispatch_call_block_and_release + 18
          8   libdispatch.dylib                   0x00007fff9144b77a _dispatch_main_queue_callback_4CF + 308
          9   CoreFoundation                      0x00007fff8fdbac0c __CFRunLoopRun + 1724
          10 CoreFoundation                      0x00007fff8fdba216 CFRunLoopRunSpecific + 230
          11 HIToolbox                           0x00007fff91dfb4ff RunCurrentEventLoopInMode + 277
          12 HIToolbox                           0x00007fff91e02c21 ReceiveNextEventCommon + 355
          13 HIToolbox                           0x00007fff91e02aae BlockUntilNextEventMatchingListInMode + 62
          14 AppKit                              0x00007fff92205191 _DPSNextEvent + 659
          15 AppKit                              0x00007fff92204a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
          16 AppKit                              0x00007fff924baa4d -[NSApplication _realDoModalLoop:peek:] + 610
          17 AppKit                              0x00007fff924ba681 -[NSApplication runModalForWindow:] + 120
          18 AppKit                              0x00007fff924adf06 -[NSAlert runModal] + 159
          19 AppKit                              0x00007fff92233d66 -[NSPersistentUIManager promptToIgnorePersistentState] + 818
          20 AppKit                              0x00007fff922083dd -[NSApplication _reopenWindowsAsNecessaryIncludingRestorableState:registeringAsReady:completion Handler:] + 173
          21 AppKit                              0x00007fff92208241 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 227
          22 AppKit                              0x00007fff92207fb1 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 330
          23 CoreFoundation                      0x00007fff8fe17f51 -[NSObject performSelector:withObject:withObject:] + 65
          24 Foundation                          0x00007fff8c3791c7 __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 101
          25 Foundation                          0x00007fff8c37814e -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 283
          26 Foundation                          0x00007fff8c377fdc _NSAppleEventManagerGenericHandler + 105
          27 AE                                  0x00007fff8cad9a85 _Z20aeDispatchAppleEventPK6AEDescPS_jPh + 200
          28 AE                                  0x00007fff8cad9963 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 38
          29 AE                                  0x00007fff8cad9857 aeProcessAppleEvent + 250
          30 HIToolbox                           0x00007fff91e0a12d AEProcessAppleEvent + 102
          31 AppKit                              0x00007fff922053dd _DPSNextEvent + 1247
          32 AppKit                              0x00007fff92204a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
          33 AppKit                              0x00007fff922013d6 -[NSApplication run] + 463
          34 AppKit                              0x00007fff9247f52a NSApplicationMain + 867
          35 Preview                             0x0000000104f42c64 Preview + 7268
          36 ???                                 0x0000000000000002 0x0 + 2
2011-08-15 09:16:06.263 Preview[435:60b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
*** First throw call stack:
          0   CoreFoundation                      0x00007fff8fe25986 __exceptionPreprocess + 198
          1   libobjc.A.dylib                     0x00007fff95bbed5e objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff8fdcc818 -[__NSArrayM insertObject:atIndex:] + 296
          3   Preview                             0x0000000104f46cf9 Preview + 23801
          4   Preview                             0x0000000104f46a17 Preview + 23063
          5   Preview                             0x0000000104f465d1 Preview + 21969
          6   Preview                             0x0000000104f46175 Preview + 20853
          7   libdispatch.dylib                   0x00007fff9144990a _dispatch_call_block_and_release + 18
          8   libdispatch.dylib                   0x00007fff9144b77a _dispatch_main_queue_callback_4CF + 308
          9   CoreFoundation                      0x00007fff8fdbac0c __CFRunLoopRun + 1724
          10 CoreFoundation                      0x00007fff8fdba216 CFRunLoopRunSpecific + 230
          11 HIToolbox                           0x00007fff91dfb4ff RunCurrentEventLoopInMode + 277
          12 HIToolbox                           0x00007fff91e02c21 ReceiveNextEventCommon + 355
          13 HIToolbox                           0x00007fff91e02aae BlockUntilNextEventMatchingListInMode + 62
          14 AppKit                              0x00007fff92205191 _DPSNextEvent + 659
          15 AppKit                              0x00007fff92204a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
          16 AppKit                              0x00007fff924baa4d -[NSApplication _realDoModalLoop:peek:] + 610
          17 AppKit                              0x00007fff924ba681 -[NSApplication runModalForWindow:] + 120
          18 AppKit                              0x00007fff924adf06 -[NSAlert runModal] + 159
          19 AppKit                              0x00007fff92233d66 -[NSPersistentUIManager promptToIgnorePersistentState] + 818
          20 AppKit                              0x00007fff922083dd -[NSApplication _reopenWindowsAsNecessaryIncludingRestorableState:registeringAsReady:completion Handler:] + 173
          21 AppKit                              0x00007fff92208241 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 227
          22 AppKit                              0x00007fff92207fb1 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 330
          23 CoreFoundation                      0x00007fff8fe17f51 -[NSObject performSelector:withObject:withObject:] + 65
          24 Foundation                          0x00007fff8c3791c7 __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 101
          25 Foundation                          0x00007fff8c37814e -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 283
          26 Foundation                          0x00007fff8c377fdc _NSAppleEventManagerGenericHandler + 105
          27 AE                                  0x00007fff8cad9a85 _Z20aeDispatchAppleEventPK6AEDescPS_jPh + 200
          28 AE                                  0x00007fff8cad9963 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 38
          29 AE                                  0x00007fff8cad9857 aeProcessAppleEvent + 250
          30 HIToolbox                           0x00007fff91e0a12d AEProcessAppleEvent + 102
          31 AppKit                              0x00007fff922053dd _DPSNextEvent + 1247
          32 AppKit                              0x00007fff92204a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
          33 AppKit                              0x00007fff922013d6 -[NSApplication run] + 463
          34 AppKit                              0x00007fff9247f52a NSApplicationMain + 867
          35 Preview                             0x0000000104f42c64 Preview + 7268
          36 ???                                 0x0000000000000002 0x0 + 2
terminate called throwing an exception
I have looked around for tips, but none of them seem to resolve the problem. Any help would be appreciated!

I have run some further tests. While I am still not sure what the underlying problem is, here's what happens in an example.
I create a new PDF from LaTeX using MacTeX 2011's pdflatex.
I run "Preview xxx.pdf" from the shell; Preview crashes as stated above.
I run "Preview" from the shell (note: no parameter), click "Don't restore Windows", and then manually open the pdf file inside Preview. The PDF is now shown without problems.
The same happens in many cases if I replace running "Preview xxx.pdf" in the shell by opening the PDF file by double clicking it in Finder.
Strange...

How to prevent .DS_Store files in specificied folders

Hello. I want to stop creation of .DS_Store files in Desktop and Picture/hoge folders only. Also I would like to keep its settings of .DS_Store files in other folders. When I googled the web I found so many pages explaining how to prevent .DS_Store in network folders, how to stop creation of .DS_Store files in all of the OSX system and usage of TotalFinder. Those are not what I am finding for. I want to stop creation of .DS_Store files in only particular folders. I can use AppleScript or Terminal commands. Thank you very much.

would creating an empty one, then locking it achieve what you need ?
+ locking existing ones as needed.
briefly checking here causes no obvious problems, Finder still alows changes, but reverted after relaunch.

Finder data not being written to .DS_Store file

The symptom of the problem I am experiencing is that the position of icons on my desktop (as well as icons in other folders in my home directory, as well as Finder window settings for folder in my home directory) are lost every time I log out. On a subsequent login, all of the icons "reflow" starting from the top right corner of the screen, just below the boot volume icon. I have been able to determine that this has to do with the .DS_Store file(s) in the Desktop folder and other folders of my home directory. If a .DS_Store file exists, the timestamp does not change when I change the icon layout and logout. If I delete the .DS_Store file, it is not re-created.
In my case, my home directory (and the child Desktop folder) is being mounted off an SMB share on a Windows 2003 server. My Mac is using AD authentication to the same Windows 2003 server, which is the domain controller. I'm logging in with my AD credentials, and my home directory mapping is picked up from the home directory field in AD.
Now, Googling this problem, I found a lot of people complaining about wanting to suppress the use/creation of the .DS_Store files on Windows network volumes. This led to an Apple KB article (http://support.apple.com/kb/HT1629) on how to modify a default to prevent the creation of .DS_Store files on network volumes--essentially the very behavior I am experiencing. The upshot of the KB article is to us the following command in terminal:
*defaults write com.apple.desktopservices DSDontWriteNetworkStores true*
I did a 'defaults read' to confirm this default isn't set on my install of Mac OS X 10.5.6--and it isn't. I then tried using the following variation in the hope I could force the behavior I wanted:
*defaults write com.apple.desktopservices DSDontWriteNetworkStores false*
Predictably, this had to effect.
The upshot is, NONE of the Finder data for files and folders in my home directory (icon positions, Finder view window defaults, etc.) is preserved between logons. And this is driving me nuts! I've spent several hours over the past two evening trying to troubleshoot this, and I've had no luck.
As a footnote, I'll mention that if I drag a folder from my home directory onto the local hard disk, the .DS_Store file is created/updated and things behave as expected (icon position and Finder window defaults are preserved). But, if I then drag the folder back over to my home directory, the values in the .DS_Store file become "frozen" and don't change.

Hey, try this:
1.
Put a file in a folder on your Desktop.
Edit: not your Desktop, but rather a typical local home on an HFS+ volume ~/Desktop
2.
Use "Get Info" to add a "Comment".
The comment can be up to somewhere between 700 and 800 characters.
3.
Copy the folder to a FAT formatted flash drive, SMB share, etc.
4.
Create a new folder on the flash drive.
5.
Move the file from the first folder to the second folder.
Confirm that the "Finder" shows the comment to be there.
6.
Quit the "Finder" - in 10.4 and earlier, this action would ensure that all .DS_Store files get updated, including transfer of comments. I.e. don't "relaunch" or "kill", etc. Enable and user the "Quit" menu, or use:<pre>
osascript -e 'tell application "Finder" to quit</pre>
7.
Now where's the comment?
In step 2, you could also have just created a file on the non-HFS volume and wasted your time typing in a 700 character comment.
In step 6, a more real-world scenario is ejecting the drive or logging out, but deliberately quitting the "Finder" is the most conservative way to ensure that changes get written to .DS_Store files and comments survive. In 10.5.6, even under these conditions, comments are lost.
Icon positions and view preferences are one thing, but with comments - that's real user-inputted data that Apple is playing fast and loose with. And if they no longer support comments on non-HFS volumes, the "Finder" shouldn't be showing you the comments when you double-check them in step 5, or allow them to be added in the alternate version of step 2.
..."C'mon Apple... what gives here?"...
Unfortunately, this "Discussions" site is not frequented by Apple devs. Have you considered filing a bug report? I wonder what they would tell you, eg. if the treatment of .DS_Store files actually does turn out to be a bug or is intentional as it suspiciously seems...
http://developer.apple.com/bugreporter/index.html

.DS_Store files on USB thumbdrives - a way to stop them from being created?

Hello!
Forgive me if this has been asked to death, but at school I need to copy homework files back and forth to the school's XP-based computers constantly. Because in any given day I usually update half a dozen files across the "homework" folder on my Powerbook, it's easier just to copy the entire folder (and its subfolders) to my 2-GB, FAT-32 formatted flash drive each night - all 500 files (and 150 MB). Of course, this also leaves hundreds of .DS_Store and ._filename files to clutter "Windows explorer" windows.
My question is how do I remove (and prevent creation of) these files selectively? I know that they are used by the finder to store thumbnails, spotlight comments, and labels. The big problem is that while I want to remove these files from the homework folder (and some other folders), I DO NOT want to remove them from a few other folders on the flash drive - which I use to make quick backups of files from my Mac.
I know that I can prevent OS X from creating them altogether with certain utilities, and I know that I can get third-party utilities that allow me to remove these files from flash drive and/or prevent the creation of the files for entire volumes, but is there something I can do to remove them from only certain folders?
Also, since I do not always know beforehand what directories I might make, I'd like to be able to create a "white list" of only certain directories (and their sub-directories)that won't be touched, while all others will have their ".DS_Store" and "._filename" files removed.
Finally, because I'm often a hurry when I go to copy files, I'd rather not sit there and run terminal commands or a program every time I copy a folder over to the flash drive. Is there some way to prevent them from being created in these certain folders altogether, automatically? An applescript or terminal command that I can program to run from the script menu perhaps? I don't mind opening a program or script, I just don't want to have to sit there manually removing the files.
Thanks,
-Dan

I had a similar problem awhile back and asked for help in the Applescript forum:
http://discussions.apple.com/thread.jspa?threadID=954738&tstart=0
Unfortunately the revised jive software formatting function here in the forums has totally messed up things like posted scripts. What you'll see in the scripts discussed is no longer what was there originally. I just now put a copy of the script I'm using up in zip format here:
http://homepage.mac.com/francines/.Public/CopyStrip2Fat.zip
Unzip and open in Script Editor to get some idea of what it is really supposed to be. The idiot formatting of the revised jive software has replaced some things with a carriage return, a semi-colon, and close quote, thus rendering some lines meaningless.
To see the source of the script I quoted, see this MacOSXHints thread:
http://www.macosxhints.com/article.php?story=20040726164957299
The script is in the comment by cougar718. You might take a look at other comments as well.
Francine
Francine
Schwieder

.DS_Store files undo delete command in Terminal

I was copying large quantities of files to a poorly formatted LaCie 3T external drive and kept coming up with interruptions in copying because the Finder kept "seeing" the creation of .DS_Store files. I researched and found a command for Terminal which stopped the OS from creating .DS_Store files. I restarted my laptop and sure enough, no more .DS files are being created.
I was then able to complete the massive transfer, I reformatted the drive, and returned all of the files to the 3T drive. Now everything's working alright.
My question is... How do I return the creation of .DS_Store files back to normal?
Can anyone drop me a line that I can insert into the terminal command line and get it done?
Thanks in advance.

You know, I did that, and nothing happened. So I then decided to re-install M.L., and I'm now manufacturing .DS_Store files with abandon.
I've been reading that it's not a popular kind of file for folks, especially those who are working with variously formatted devices. There are some obscure advantages to having the files sit around the hard drive.
Thanks for your advice, however. It's good to know that I wasn't so far off.

How do I prevent .DS_Store file creation on external usb drives?

Hi.
I can't connect my friends or colleagues external drives to my computer without my Mac creating dozens of ".DS_Store" files on them. It is very annoying.
How can I prevent the Mac from creating these ".DS_Store" files?
Thanks :o)

Thanks for the response :o)
If I suddenly would realize that my car is leaking oil, I would not buy a machine which automatically would fill up my oil tank to a acceptable level and also wipe up the oil after me. I would of course fix my car instead.
I want to take the problem by the root. It should be possible to turn the feature off, so that the files never will be created (and without mounting the filesystem as read-only).
Where can I turn off this feature?

How can I keep lion from generating .DS_Store files on windows network partitions, but not disable it for all network partitions?

How can I keep lion from generating .DS_Store files on windows network partitions, but not disable it for all network partitions? I am fimilar with changing the setting for all network partitions(defaults write com.apple.desktopservices DSDontWriteNetworkStores true), but that is undesirable when I connect my laptop to my home network. A preferable solution would be where I could control the writing of these files based on disk format (NTFS vs HFS+).

Go to MacUpdate or CNET Downloads and search for ds_store. There are numerous utilities for preventing them from being transferred to Windows systems.

F110 - How to prevent multiple creation of DME file?

Hello,
I need to prevent multiple creation of DME file for the same Payment Run (after it has been created once).
"Printout" bottom creates DME file and Payment Advice any time you trigger it.
I'm searching for some User Exit / BAdi / Function that will help me to add ABAP code that will check if DME file has already been created.
Thank You in Advance

Hello,
Please check if the flag "Create payment medium" is not flagged at the proposal and the payment run file.
If it is flagged the payment file will be generated. Also when you press the print out button, the print program will be called and the system will try to created a new payment file.
In order to avoid duplicated payments you should consider using the flag 'Payment Document Validation" in your print program.
If the 'Payment Document Validation' parameter is not set ON, documents already processed for payment can be selected and paid again in a subsequent payment run, when posting terminations have occurred.
Please refer to SAP Knowledge Base Article 1713825 in order to activate Payment Document Validation.
Another option is to suppress the"Create Payment Medium" flag at Proposal Run.
In this case you should check the following information:
Please restrict the activity 15 of object F_REGU_BUK in the user
profile/role
You may also refer to the available activities on this:
- 02 Edit parameters
- 03 Display parameters
- 11 Execute proposal
- 12 Edit proposal
- 13 Display proposal
- 14 Delete proposal
- 15 Create payment medium proposal
- 21 Execute payment run
- 23 Display payment run
- 24 Delete payment run payment data
- 25 Create payment media of payment run
- 26 Delete payment orders of payment run
- 31 Print payment medium manually
Kind Regards,
Fernando Evangelista

F110 - How to prevent the creation of DME file in Proposal Step

Hello,
I would like to prevent the creation of DME file in Proposal Step of Payment Run (F110).
Is it possible to suppress "Create Payment Medium" checkbox?
Many Thanks

If you are using the Payment Medium Workbench, there is perhaps a solution:
I found the following code in function module FI_PAYMEDIUM_OFX_20
* We abort the payment if the data is from a payment proposal. With
* OFX we can pay only if the data does not come from a payment
* proposal.
IF I_FPAYH-XVORL = 'X'.
MESSAGE E404 WITH I_FPAYH-LAUFD I_FPAYH-LAUFI
RAISING CANCEL_PAYMENT_MEDIUM.
ENDIF.
So I think it may be possible to solve your problem by using the event modules in transaction OBPM3, with your own function module based on the code given above. I have not tested such solution and I have no experience with these events, but I'm currently trying to use them for another problem.

After installing mountain lion, can i back up all my files from external time machine hard drive if i did the back up under Lion?

Hi. Want to find out before installing new Mountain Lion if I will be able to restore all my files (music, documents....) from my external hird drive if the back up was done under Lion. Or it is better to simply copy everything, altough it would be good to keep iTunes, contacts etc as well as they are at the moment. Could someone please tell me how to do it so I can go on with it and will not have to struggle after the installation? Many thanks.

You can do this. If you did an OS X Mountain Lion clean install, it will ask you to restore a backup, so connect a Time Machine disk and restore that

Whenever I open a file in Lion, other files of the same sort that I opened previously automatically open up. For example, if I open a .jpg file, numerous other .jpg files that I opened previously in the day open up. How do I prevent this from happening?

Whenever I open a file in Lion, other files of the same sort that I opened previously automatically open up. For example, if I open a .jpg file, numerous other .jpg files that I opened previously in the day open up. How do I close these files to prevent them from showing up again, like in previous versions?

Dealing With The Resume Feature of Lion
Managing Mac OS X Lion's application resume feature.
If you shutdown your computer you should get a dialog asking if you want applications to resume on the next startup. Simply uncheck the box to prevent that from occurring. Open General preferences and uncheck the option to Restore windows when quitting and re-opening apps. You can also install a third-party utility to control resume features on individual applications: RestoreMeNot or Application State Cleaner.
It is possible to completely stop the Resume feature although I'm unconvinced that it is that annoying. Nevertheless see the following:
If you have not yet done so you must first make your /Home/Library/ folder visible. Open the Terminal application in the Utilities folder. At the prompt paste the following command line:
chflags nohidden ~/Library
Press RETURN. Quit the Terminal application.
In the Finder navigate to the /Home/Library/Saved Application State/ folder. Delete the contents of the folder. Back up to the /Home/Library/ folder. Select the Saved Application State folder. Press COMMAND-I to open the Get Info window. In the Sharing and Permissions panel at the bottom click on the lock icon and authenticate. Set each of the listed entries to Read Only. Close the Get Info window.
Quit all open programs except the Finder (this is very important.) Next, navigate to the /Home/Library/Preferences/ByHost/ folder. Look for a .plist file with "com.apple.loginwindow." in the file name followed by some numbers in hexadecimal. Select the file. Press COMMAND-I to open the Get Info window and in the Sharing and Permissions panel click on the lock icon and authenticate. Set each of the listed entries to Read Only. Close the Get Info window. If you also find a file with the same filename but with a last extension of ".lockfile," then you should delete it.
The above should eliminate the Resume feature system-wide. Note that any future system updates or upgrades will likely undo these changes. You will then need to repeat this procedure assuming there are no major changes in OS X related to it.

Unable to use GarageBand under Lion: File not found.

I used Migration Assistant to copy all files, folders, applications, and settings to my new computer. The new computer can't open earlier GB projects I created NOR can I start new projects. Even Apple's own GB Demo Songs refuse to open. My old computer is an iMac Intel Core Duo running Snow Leopard. My new computer is an iMac Quad Core i7 running Lion (10.7.2). The message I receive when attempting to open old projects and demo songs, or create new projects, is the same: "The file couldn't be opened."
I reinstalled iLife and downloaded and installed all updates, but it still wouldn't work. I then re-installed all Apple Jam packs (though some wouldn't install completely in the much-newer environment) and I continue to get the same message, "The file couldn't be opened." My assumption is I need to delete one or more plist files but I don't have a clue where to begin.
I searched the knowledge base and forums but could find nothing about this, but I find it hard to believe somebody else hasn't had the same trouble. I'm hoping it's an easy fix! Thanks for any and all suggestions.

Hi, me too I have a similar problem. I have a macbook air mid-2011, Lion 10.7.2. I have been using GarageBand for a while now, even under Lion. And since this weekend, I can't open any of my files, nor can I create a new project. It says "Files cannot be opened". I do have the permission to read and write, so I don't know what's wrong. I did a test as a Guest and tried to open GarageBand, and yes I can do it. Still I don't know how I could create or open a Garageband project under my username. I have also tried to find my files with Time Machine but still GarageBand cannot open my old files. Any clues? Anyone?

Prevent creation of .DS_Store files under Lion

Similar Messages

Maybe you are looking for