 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / General / General / May 2008unable to delete certain files
I had occasion to delete Appleworks from my computer. I attempted to use the uninstall program on the Appleworks installer disk. Ran it according to the directions, and saw an apparent uninstall in progress. Got a message that the uninstallation was successful except that certain files could not be deleted for one reason or another. Feh! I examine the residue in my Trash, to see if any of the files there are shown to be locked. None of them is. Still, I cannot delete them because I am informed that certain named files are locked. I cannot for the life of me find those mysterious files. I really want to empty my Trash! So, what do I do? Can these stubborn and unwanted items be gotten rid of? I use an iMac, 800 mhz power PC G4 and system 10.4.11, 1 gig of RAM Thank you. tom koehler  SignatureI will find a way or make one. > I had occasion to delete Appleworks from my computer. I attempted to use the > uninstall program on the Appleworks installer disk. Ran it according to the [quoted text clipped - 8 lines] > unwanted items be gotten rid of? > I use an iMac, 800 mhz power PC G4 and system 10.4.11, 1 gig of RAM One way would be to open a terminal window and enter this command: rm -r /Users/you/.Trash Pay attention to the period character in front of ".Trash" above - it's important you type this command correctly. Another way would be to choose Finder > Secure Empty Trash from the Finder menu bar. SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR > One way would be to open a terminal window and enter this command: > > rm -r /Users/you/.Trash > > Pay attention to the period character in front of ".Trash" above - it's > important you type this command correctly. TIP: The above command may result in some interaction where prompts may ask you if you really wish to delete certain files. If you *really* don't care about what's in the trash and just want to nuke it all, a more forceful way to do this command would be: rm -rf /Users/you/.Trash The additional -f switch tells the rm tool to force the delete operation for all files rather than asking your permission. SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR > One way would be to open a terminal window and enter this command: > [quoted text clipped - 5 lines] > Another way would be to choose Finder > Secure Empty Trash from the > Finder menu bar. Thanks for your reply, jollyroger -- I had mixed results. First, my experience with the terminal program before this was zero. I've had enough experience with command line stuff elsewhen to know that syntax is key, so I followed your instructions as written here. Nothing. I then tried the Secure Empty Trash and that got rid of everything but a 28k Appleworks file. Well, this is progress, a good thing. I googled the web to try to learn a bit more about Unix commands. I saw where the command options were enclosed in square brackets, so I tried that, and got a "no match" response. Heh... more progress, but not quite what I'd expected. I did a little more fooling around and kept getting the same response, about no match. I took the stubborn file out of the trash and put it into its own little folder on the desktop and called the folder "xtrouble". I'm going to let it sit there while I do a bit more homework on this unix thing. Got a whole 'nother language to learn, I guess. Thanks for your time. tom k. SignatureI will find a way or make one. > > One way would be to open a terminal window and enter this command: > > [quoted text clipped - 19 lines] > I did a little more fooling around and kept getting the same response, about > no match. The square brackets are a meta-syntax signifying that the options are "optional" (most of them are). You don't actually enter the brackets as part of the command. Here is the synopsis for the rm command from the 'man rm' on-line manual page: rm [-dfiPRrvW] file ... All of the options in square brackets are not required. The basic command is just 'rm file'. Use the 'ls' command to see what is any directory. Here is the synopsis: ls [-ABCFGHLPRTWZabcdefghiklmnopqrstuwx1] [file ...] As you can see, there are a large number of single-character options, and the file name is optional too. Just type 'ls' (without the quotes) to list the files in the current directory. Type 'ls -a' to list the files including the ones that start with a period. Type 'ls -l' to get a long listing with date, time, and size of the file, etc. You can usually combine the single-character options like this: 'ls -al' (each utility handles command-line options differently, but there are guidelines and customs). Common commands to use for managing files are cd, ls, pwd, rm, mv, and cp. You can get the manual pages for these with the following: man cd man ls man pwd ... And, of course, man man will tell you how to use the man command. SignatureJim Gibson Posted Via Usenet.com Premium Usenet Newsgroup Services ---------------------------------------------------------- > The square brackets are a meta-syntax signifying that the options are > "optional" (most of them are). You don't actually enter the brackets as [quoted text clipped - 32 lines] > > will tell you how to use the man command. thank you for your time and for your response. My experience so far has indicated to me that I have a great deal to learn about this Unix beast before I get the results I want. Anent the manual pages, they are somewhat like a dictionary in that you have to know how to spell a word before you can look up how to spell it. As you said, "there are guidelines and customs" none of which I know at the moment. I do not want to discourage you or anyone else from trying to help me - I am grateful for any and all help. I know that I have more to learn before I succeed in this little project, and am going to do what I can. tom k. SignatureI will find a way or make one. > > One way would be to open a terminal window and enter this command: > > [quoted text clipped - 10 lines] > experience with command line stuff elsewhen to know that syntax is key, so I > followed your instructions as written here. Did you replace "you" in this path with the actual name of your home folder in /Users?: rm -r /Users/you/.Trash > Nothing. I then tried the Secure > Empty Trash and that got rid of everything but a 28k Appleworks file. Well, > this is progress, a good thing. If you highlight this AppleWorks file, then choose File > Get Info from the Finder menu bar, does it show it as being Locked. by chance? > I googled the web to try to learn a bit more about Unix commands. I saw where > the command options were enclosed in square brackets, so I tried that, and [quoted text clipped - 3 lines] > I did a little more fooling around and kept getting the same response, about > no match. I don't know where you saw square brackets, but that's not needed in the actual commands, and probably won't work - as you've already learned, it seems. ; ) > I took the stubborn file out of the trash and put it into its own little > folder on the desktop and called the folder "xtrouble". I'm going to let it > sit there while I do a bit more homework on this unix thing. Got a whole > 'nother language to learn, I guess. Have you restarted since? Next time you restart, see if you can then put the file in the trash and empty the trash. SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR > Did you replace "you" in this path with the actual name of your home > folder in /Users?: > > rm -r /Users/you/.Trash yes, I did. the result was this "rm:illegal option--/ usage:rm[-f|-i][-dPRrvW]file..." (quotation marks are mine) well, heck, I'll take out any space characters and try again, still not using square brackets. The result was this "tcsh:rm-r/Users/you/.Trash: command not found" (where "you" is my home folder name) The file is still in the trash. > If you highlight this AppleWorks file, then choose File > Get Info from > the Finder menu bar, does it show it as being Locked. by chance? I tried that (my first reaction after trying to empty the trash) and the file does not show being locked. Further, Ownership and Permissions shows that I can read and write. Attemps to just empty the trash give messages that Starting Points, Clippings, Appleworks Essentials, and Appleworks 6 are all locked. I did a cmd-F to locate these files and there was no Appleworks Essentials to be found. The other searches turned up well over a hundred files - some were PDFs, or html files or various other document files, none of which are Appleworks files. I am starting to feel like Br'er Rabbit, trying to move the Tar Baby outta his way. I'm not actually getting more and more stuck, but am getting a better idea of what I do not know. >> I googled the web to try to learn a bit more about Unix commands. I saw >> where [quoted text clipped - 9 lines] > actual commands, and probably won't work - as you've already learned, it > seems. ; ) well, the square brackets were part of the command format illustrated on at least one of the websites (cannot recall which, now. ) I was looking at. Also, in the results returned to me by an earlier attempt, the "usage" remark included square brackets in the option position following the rm command. Please underestand that I am not doubting the veracity of your (and others') remarks about the need of square brackets. I am doubting my own comprehension of just about everything I have encountered once I step through the looking glass into UnixLand. >> I took the stubborn file out of the trash and put it into its own little >> folder on the desktop and called the folder "xtrouble". I'm going to let [quoted text clipped - 3 lines] > > Have you restarted since? oh, yes, a couple of times. Next time you restart, see if you can then > put the file in the trash and empty the trash. I can move the file around at will and put it into the trash if I want, I just cannot delete the darned thing. I am not giving up. I'm gonna learn what I need to, to get this done. I am also grateful for your responses in this matter. I just have more learning to do, I guess. tom k. SignatureI will find a way or make one. Do this: Open the Trash so you can see the file. Open a Terminal window. Type: rm<space>-r<space> Substituting the space character for <space> Drag the file in the trash to the terminal window so the path to it is inserted. Press the Return key. SignatureWoodworking links and more at http://www.woodenwabbits.com > Do this: > [quoted text clipped - 12 lines] > > Press the Return key. interesting! never thought of dragon drops! Well, I tried it and when the return key is pressed, I see some business where a response is expected from me, regarding "Starting points". I hit the return key again, and now see a similar response, now about "clippings", and so on, down the line until I finally get something about the "directory is not empty" The trash is still pregnant with unwanted files - seen and unseen. I next tried Jolly Roger's suggestion about the -rf option, to forcibly delete everything, no questions asked. Well! The screen immediately filled with lines of response at each action taken by the unseen little man inside the box. The gist of which is, "action not permitted" and a final riposte, "the directory is not empty". The trash is, of course, still holding unwanted files. It would seem there are certain conditions when a file may not be removed at all, until certain other conditions are met. This thing is referring to locked files unseen by me. I'll admit ignorance of the necessary information. I am pretty sure I'm not stupid, though. I managed to learn some fundamentals of BASIC when I got my first Apple more than 20 years ago. I managed to learn enough PASCAL and FORTRAN more than 15 years ago to pass some college classes. I'm educable, I just don't know what the questions are. This has turned into more of a puzzle than I'd imagined. I'm retired. I got time. Thank you. tom k. SignatureI will find a way or make one. > Well, I tried it and when the return key is pressed, I see some business > where a response is expected from me, regarding "Starting points". I hit the > return key again, and now see a similar response, now about "clippings", and > so on, down the line until I finally get something about the "directory is > not empty" Try it again, and this time copy the text in the Terminal window and paste it into a reply. We need to see exactly what you're seeing. SignatureWoodworking links and more at http://www.woodenwabbits.com >> Well, I tried it and when the return key is pressed, I see some business >> where a response is expected from me, regarding "Starting points". I hit [quoted text clipped - 6 lines] > Try it again, and this time copy the text in the Terminal window and > paste it into a reply. We need to see exactly what you're seeing. Last login: Tue May 20 22:32:09 on ttyp1 Welcome to Darwin! [obfuscating-iMac:~] thomasvk% rm -r /Users/thomasvk/.Trash/ytrouble/AppleWorks\ 6.app/ override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//AppleWorks 6? override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/AppleWorks Essentials? override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/Clippings? override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/Starting Points? rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS: Directory not empty override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/AppleWorks Essentials? override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/Clippings? override rw-r--r-- thomasvk/staff uchg for /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/Starting Points? rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic: Directory not empty rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents: Directory not empty rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app/: Directory not empty [obfuscating-iMac:~] thomasvk% next run with -rf option Last login: Tue May 20 22:35:16 on ttyp1 Welcome to Darwin! [obfuscating-iMac:~] thomasvk% rm -rf /Users/thomasvk/.Trash/ytrouble/AppleWorks\ 6.app/ rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//AppleWorks 6: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/AppleWorks Essentials: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/Clippings: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS/Starting Points: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOS: Directory not empty rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/AppleWorks Essentials: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/Clippings: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic/Starting Points: Operation not permitted rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents/MacOSClassic: Directory not empty rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//Contents: Directory not empty rm: /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app/: Directory not empty [obfuscating-iMac:~] thomasvk% so, here it is tom k. SignatureI will find a way or make one. > override rw-r--r-- thomasvk/staff uchg for > /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//AppleWorks 6? The "uchg" indicates the files are locked. The 'rm -rf' command will delete locked files - no questions asked. Is the Mac OS X user account you are using an administrator account? If so, try this command: sudo rm -rf /Users/thomasvk/.Trash/* SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR >> override rw-r--r-- thomasvk/staff uchg for >> /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//AppleWorks 6? > > The "uchg" indicates the files are locked. The 'rm -rf' command will > delete locked files - no questions asked. In 10.5.2 it won't unless you're superuser, I just tried. I'm pretty sure that the behaviour here is the same in earlier OS Xes. > Is the Mac OS X user account you are using an administrator account? If > so, try this command: > > sudo rm -rf /Users/thomasvk/.Trash/* Yes, that works. Unlocking them first is another way: chflags -R nouchg /Users/thomasvk/.Trash/* rm -rf /Users/thomasvk/.Trash/* Cheers, Chris >>> override rw-r--r-- thomasvk/staff uchg for >>> /Users/thomasvk/.Trash/ytrouble/AppleWorks 6.app//AppleWorks 6? [quoted text clipped - 18 lines] > > Chris To Chris and Jolly Roger and Dave Balderstone, thank you for your help with this situation! I am rid of those pesky files! Of course, I have questions now. One of them is this: Just where were those locked files? All I could see in the trash was the one Appleworks file and it was just 28k. Were there some hidden or invisible files along for the ride in the trash? I plan to do some googling the web for help in learning more about this command line terminal program, too. Again, thanks to all of you who resonded to my query and helped me be rid of the stubborn trash! tom k. SignatureI will find a way or make one. > One of them is this: Just where were those locked files? All I could see in > the trash was the one Appleworks file and it was just 28k. Were there some > hidden or invisible files along for the ride in the trash? If you look at the terminal responses you were getting, you'll see they were inside the AppleWorks 6.app bundle. SignatureWoodworking links and more at http://www.woodenwabbits.com >> One of them is this: Just where were those locked files? All I could see >> in [quoted text clipped - 3 lines] > If you look at the terminal responses you were getting, you'll see they > were inside the AppleWorks 6.app bundle. ah, well, very good. Part of my battle then is learning how to comprehend what I'm reading. The more I learn, the more I find out that I haven't a clue - an endless puzzle. Thank you again, for your help. tom k. SignatureI will find a way or make one. > ah, well, very good. Part of my battle then is learning how to comprehend > what I'm reading. The more I learn, the more I find out that I haven't a clue > - an endless puzzle. > > Thank you again, for your help. You're willing to help yourself, which is something a lot of people who post here won't do. Funny how more people are willing to assist someone who's willing to work at solving the problem. ;-) SignatureWoodworking links and more at http://www.woodenwabbits.com > > Did you replace "you" in this path with the actual name of your home > > folder in /Users?: [quoted text clipped - 5 lines] > "rm:illegal option--/ > usage:rm[-f|-i][-dPRrvW]file..." (quotation marks are mine) You missed the space character between rm and -r. Wouldn't this be a whole lot easier if you copied and pasted the command? (hint hint) > well, heck, I'll take out any space characters and try again, still not using > square brackets. The result was this > "tcsh:rm-r/Users/you/.Trash: command not found" (where "you" is my home > folder name) Removing spaces will only make things worse. The command I gave you had spaces in all the appropriate places. Unix is very unforgiving - you must always enter commands precisely as they are meant to be entered. Copy and paste is best! > The file is still in the trash. Naturally - the command failed. > > If you highlight this AppleWorks file, then choose File > Get Info from > > the Finder menu bar, does it show it as being Locked. by chance? [quoted text clipped - 7 lines] > files - some were PDFs, or html files or various other document files, none > of which are Appleworks files. You don't need to search for them - they are in the trash. > I am starting to feel like Br'er Rabbit, trying to move the Tar Baby outta > his way. I'm not actually getting more and more stuck, but am getting a [quoted text clipped - 22 lines] > of just about everything I have encountered once I step through the looking > glass into UnixLand. Often, square brackets indicate a collection of items (in this case a collection of command-line options (a.k.a command-line switches). You can choose to use zero or more of the items in this collection, depending on what you want to do. > >> I took the stubborn file out of the trash and put it into its own little > >> folder on the desktop and called the folder "xtrouble". I'm going to let [quoted text clipped - 8 lines] > I can move the file around at will and put it into the trash if I want, I > just cannot delete the darned thing. So is it correct that now when you try to empty the trash, the system tells you an item in the trash is locked? SignatureNote: Please send all responses to the relevant news group. If you must contact me through e-mail, let me know when you send email to this address so that your email doesn't get eaten by my SPAM filter. JR > You missed the space character between rm and -r. Wouldn't this be a > whole lot easier if you copied and pasted the command? (hint hint) well I figured I'd missed something. Yes, it would be easier to cut and paste the command, but you know, this is all happening in the graphic interface, and the terminal window is a command line interface, a whole 'nother animal. It never occurred to me that such a maneuver would have been possible. As I said before, I have never worked with the terminal program before. My ignorance is very nearly perfect. I'm learning a little more with each mistake. >> well, heck, I'll take out any space characters and try again, still not >> using [quoted text clipped - 4 lines] > Removing spaces will only make things worse. The command I gave you had > spaces in all the appropriate places. yes, and depending upon how my screen display looks to me, I may or may not have seen obvious spaces, where you'd typed them. The fault is not yours, but mine, for not knowing where to *expect* spaces. >>> If you highlight this AppleWorks file, then choose File > Get Info from >>> the Finder menu bar, does it show it as being Locked. by chance? [quoted text clipped - 13 lines] > > You don't need to search for them - they are in the trash. If they were visible, I'd have seen them there. Only a single file name is visible to me. Again, I am thankful for your responses to my situation, here. tom k. SignatureI will find a way or make one. > I had occasion to delete Appleworks from my computer. I attempted to use the > uninstall program on the Appleworks installer disk. Ran it according to the [quoted text clipped - 9 lines] > I use an iMac, 800 mhz power PC G4 and system 10.4.11, 1 gig of RAM > Thank you. They could really still be open by something. That might be the Finder itself; quitting and restarting the Finder will often help. I used TinkerTool to restore Finder's Quit menu item, though there are other ways. Cheers, Chris >> I had occasion to delete Appleworks from my computer. I attempted to use >> the [quoted text clipped - 15 lines] > > They could really still be open by something. this is not impossible, but it is a very long shot. I cannot imagine what, why, or how. That might be the Finder > itself; quitting and restarting the Finder will often help. I have shut down and restarted. I have simply restarted - to no avail. > I used TinkerTool to restore Finder's Quit menu item, though there are > other ways. English is my native tongue, but I do not comprehend the above sentence. Sorry. Thank you for your response to my query, and thank you for your time. > Cheers, > > Chris Respects, tom k. SignatureI will find a way or make one. >>> I had occasion to delete Appleworks from my computer. I attempted to use >>> the [quoted text clipped - 20 lines] >> itself; quitting and restarting the Finder will often help. > I have shut down and restarted. I have simply restarted - to no avail. OK, well that probably rules out the file really being open :-) >> I used TinkerTool to restore Finder's Quit menu item, though there are >> other ways. > English is my native tongue, but I do not comprehend the above sentence. > Sorry. > Thank you for your response to my query, and thank you for your time. Sorry. The Finder has a secret Quit menu item, which is enabled when you change a preference. TinkerTool (www.bresink.de) will let you change that preference, but you can also do it from other tools. Such as the terminal: defaults write com.apple.Finder QuitMenuItem 1 Cheers, Chris |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.