Re: NSFileManager - "Can't read ..." - Strange update
Re: NSFileManager - "Can't read ..." - Strange update
- Subject: Re: NSFileManager - "Can't read ..." - Strange update
- From: Shon <email@hidden>
- Date: Wed, 20 Jul 2005 19:48:08 -0400
Hardcoding a source path proved effective. I chose a source and
destination paths in my home directory ... and the code works
perfectly! I chose a source path outside of my home directory and it
continued to work.
I have a CD mounted in my CD-ROM drive since ... oh, sometime last
week. I decided to hardcode the CD-ROM path next. I started the app,
inserted the USB disk and ... it failed to copy from the CD-ROM. I
can, of course, copy from the CD-ROM manually (Finder, Terminal...).
So, it seems to be limited to /Volumes.
Can anyone suggest that this is NOT a bug?
::S
On 7/20/05, Shon <email@hidden> wrote:
> Haris:
> Yes, your assumption is correct: I'm attempting to copy the entire mounted
> external drive. I hadn't considered testing with various
> folders/permissions because the system shows 'rwxrwxrw'. I will test as you
> suggest.
>
> SA Dev:
> I've tried with various other automounted volumes (USB drives, CD-ROMs) and
> it doesn't seem to be limited to a particular partition type. In addition
> to Haris' suggestion, I'll be trying some other path as you suggest.
>
> ::S
>
>
>
> On 7/20/05, SA Dev <email@hidden> wrote:
> > Shon:
> >
> > Thanks for finally providing all the details in one post. ;-) This
> > is indeed an odd problem. A suggestion if I may: Try running the copy
> > path code with some other source (on receiving mount notification,
> > for example, don't use the mounted path but hard-code something like,
> > say, /Users/shon/Desktop/SomeTestFolder). See if that
> makes it happy.
> >
> > The reason I suggest this is that there may be some weird device-
> > specific stuff going on here. You're mounting a FAT-32 volume, right
> > (I think you said that)? If so, you may very well have found a
> > weakness. Either way, testing it with some other source path will
> > tell you whether the problem is with that volume or your code.
> >
> > Also, what version of OS X are you running on? You might want to
> > search for known issues.
> >
> >
> >
> > On Jul 19, 2005, at 10:24 PM, Shon wrote:
> >
> > > Originally, this is exactly what I was doing, but launching the app
> > > from a terminal (so I'd know the current directory). I've since
> > > discovered the error of my ways and have corrected the code to contain
> > > a proper absollute path for the destination.
> > >
> > > My more recent messages contain the code and logs ... and evidence of
> > > the sill-present error. :-(
> > >
> > > --Shon
> > >
> > > On 7/19/05, Aaron Burghardt < email@hidden> wrote:
> > >
> > >>
> > >> On Jul 19, 2005, at 1:39 PM, Shon wrote:
> > >>
> > >> I didn't copy/paste that path; it is indeed "/Volumes/SHONSD". I
> > >> don't key
> > >> this path in, it comes from the notification. The destination path is
> > >> "./temp/" and is currently hard-coded into the app.
> > >>
> > >> You specify "./temp/", but do you know where "./" is? If you
> > >> aren't setting
> > >> the the current working directory, read the docs on the NSFileManager
> > >> methods:
> > >>
> > >> - (NSString *)currentDirectoryPath
> > >>
> > >> - (BOOL)changeCurrentDirectoryPath:(NSString *)path
> > >> Hope that helps.
> > >>
> > >> Aaron
> > >>
> > >>
> > >>
> > >>
> > > _______________________________________________
> > > Do not post admin requests to the list. They will be ignored.
> > > Cocoa-dev mailing list (email@hidden)
> > > Help/Unsubscribe/Update your Subscription:
> > > 40silentalcove.net
> > >
> > > This email sent to email@hidden
> > >
> >
> >
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden