Follow us on...
Follow us on Twitter Follow us on Facebook
Register
Page 2 of 2 FirstFirst 12
Results 9 to 15 of 15
  1. #9
    dukefang99 is offline Registered User
    Join Date
    Jan 2006
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Ah, ok well that didn't work but I did learn something new. The file won't leave its containing folder, which also refuses to be deleted. When I try to rename the file, I also get an error -43. The containing folder can, however, be moved wherever.

    Any other ideas?
    Last edited by dukefang99; January 2nd, 2006 at 12:17 PM.

  2. #10
    Mikuro's Avatar
    Mikuro is offline Crotchety UI Nitpicker
    Join Date
    Mar 2005
    Posts
    2,832
    Thanks
    8
    Thanked 74 Times in 64 Posts
    I often get strange permission settings when I use drop boxes. Get Info on the file (select the file and go to the File menu) and set the "owner" to your account and be sure the access level is "read & write". You might also need to do this for the containing folder.
    Mac mini — 1.25GHz G4, 1GB RAM — OS 10.5.8
    MacBook Pro — 2.26GHz C2D, 8GB RAM — OS 10.6.8

    Useful programs: Privoxy, Butler, ffmpegX, VLC, Perian, Tofu, Wcalc

  3. #11
    artov is offline Registered User
    Join Date
    Mar 2005
    Posts
    363
    Thanks
    0
    Thanked 15 Times in 14 Posts
    Quote Originally Posted by dukefang99
    Ah, ok well that didn't work but I did learn something new. The file won't leave its containing folder, which also refuses to be deleted. When I try to rename the file, I also get an error -43. The containing folder can, however, be moved wherever.

    Any other ideas?
    This comes from the notion that MAC OSX is Unix: Open Terminal.app, type
    sudo su - and give your password. You should be as root (the Unix superuser).
    Then type

    # cd ~yourname/Desktop

    (The # is your prompt, do not type it) you said it is on your desktop, right?

    Then type

    # ls -i

    You should see list on number, filename pairs. Check the number of the file.
    It is its inum (in Unix files are actually associated with inum; name is only an
    alias to the inum) .

    Then type

    # find . -inum 44444 -exec rm '{}' \;

    where 44444 is the number. The find command is switch army knife of
    Unix; in this case it search file with inum same as ls -i, then it executes
    the rm command and gives the name (in place of {}).

  4. #12
    dukefang99 is offline Registered User
    Join Date
    Jan 2006
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    wow ok, i think this is going to work, but I'm a little confused with the last line of command

    the inum is 2955126

    can you write out exactly what I would do in that last line of command again to get rid of this file? If you could even write it out in a way that I could simply copy and paste it into terminal I would be eternally greatful

    You're a lifesaver btw!!!!
    Last edited by dukefang99; January 2nd, 2006 at 01:39 PM.

  5. #13
    dukefang99 is offline Registered User
    Join Date
    Jan 2006
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    something is still wrong, I'll show you exactly what I'm writing and maybe you can tell me what I'm doing wrong:

    root# find . -inum 2955126 -exec rm '{}' \;

    is what I entered into the terminal, and when I do so all I get is this:

    find:

    and then it IMMEDIATELY skips to the next line of command. I have also tried the above command without the ending semicolon with the same result as well as replacing the two brackets with a name for the file...What am I doing wrong?

    Thanks again for all the help provided thus far!
    Last edited by dukefang99; January 2nd, 2006 at 07:24 PM.

  6. #14
    artov is offline Registered User
    Join Date
    Mar 2005
    Posts
    363
    Thanks
    0
    Thanked 15 Times in 14 Posts
    Quote Originally Posted by dukefang99
    something is still wrong, I'll show you exactly what I'm writing and maybe you can tell me what I'm doing wrong:

    root# find . -inum 2955126 -exec rm '{}' \;

    is what I entered into the terminal, and when I do so all I get is this:

    find:

    and then it IMMEDIATELY skips to the next line of command. I have also tried the above command without the ending semicolon with the same result as well as replacing the two brackets with a name for the file...What am I doing wrong?

    Thanks again for all the help provided thus far!
    The whole idea of the command was, that you do not have to type the
    filename (it had wierd characters, right?). Are you sure you typed

    cd "the directory where the file is" ?

    That is what the "." stand for.

    BTW: Do you have OSX 10.4.3 ? It's hard disk tool can fix even mounted
    disks, so it might do something to the file.

  7. #15
    ra3ndy's Avatar
    ra3ndy is offline Custom User Title
    Join Date
    Aug 2005
    Location
    Chicago, IL
    Posts
    653
    Thanks
    0
    Thanked 2 Times in 2 Posts
    Make sure you type:

    cd ~yourname/Desktop

    and hit enter before you type:

    find . -inum 2955126 -exec rm '{}' \;

 

 
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Unrecognized Internal Modem
    By surgyn in forum Mac OS X System & Mac Software
    Replies: 2
    Last Post: July 11th, 2005, 03:21 PM
  2. Possible to enforce file name characters in OS X?
    By Gareth in forum Mac OS X System & Mac Software
    Replies: 1
    Last Post: November 12th, 2004, 07:55 PM
  3. non-standard characters?
    By nervus in forum Mac OS X System & Mac Software
    Replies: 8
    Last Post: October 7th, 2003, 01:28 PM
  4. Pocket CD-r from Sony Camera unrecognized
    By wapstar in forum Mac Classic System & Software
    Replies: 3
    Last Post: January 9th, 2003, 02:39 PM
  5. CD-RW unrecognized since X.1
    By infinityBBC in forum Mac OS X System & Mac Software
    Replies: 0
    Last Post: November 21st, 2001, 06:07 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •