Thursday, 13 August 2015

Re: Do Netsurf's errors get logged? (Syslog, Wimplog)

On 13 Aug 2015 as I do recall,
Jim Nagel wrote:

> Steve Fryatt wrote on 12 Aug:
>
> > On 12 Aug, cj wrote in message
> > <54f1f9a962chris@chris-johnson.org.uk>:
>
> >> In article <cd18f7f154.jim@abbeypress.net>,
> >> Jim Nagel <netsurf@abbeypress.co.uk> wrote:
> >>
> >>> Warning from Netsurf
> >>> The file could not be saved due to an error:
> >>> 'ADFS::Drive2.$.2310d/zip' is a directory
> >>
> >> This is a common error and nothing to do with Netsurf as such. It is due
> >> to some oddity with SparkFS and handling of zip files, and seems to depend
> >> on how the original zip was produced (software). I get it from
> >> Filer_Action when running SyncDisc jobs.
>
> > I'm not sure it's that odd. If SparkFS has been seen and the zip file has
> > the correct filetype, RISC OS will report the object to NetSurf as a
> > directory, not a file (/some/ calls will report it as an "image directory",
> > but others won't).
>
> In fact what caused the error was that the drive already had an object
> with the same name as the download I wanted to save ("2310d/zip").
> The text of the warning was totally inappropriate and misleading.
>
The 'misleading' error is simply the Filer telling you that you can't save a
file there because there is already a directory there.

> Anyway, it'd be more helpful if Netsurf's download routine would say
> "an object of that name already exists; do you want to overwrite it?"
> rather than relay this wuzzy "is a directory" wuzziness.
>
So it does, when the object in question is another file (try it and see).
RISC OS doesn't allow you to overwrite a directory with a file, probably for
reasons of potential massive data loss... and a zip file *is* a directory
when an appropriate image filing system is running (double-click on it and
you can see its directory structure)

--
Harriet Bazley == Loyaulte me lie ==

It is easier to fight for one's principles than to live up to them.

No comments:

Post a Comment