Re: Fail 2890 json
"Gerald Dodson", on 13 Aug, wrote: > Has any one else had this version fail? Currently NetSurf starts with JavaScript enabled irrespective of any Choices saved previously. A new JavaScript engine is being incorporated but at the moment this is "work in progress" by which I mean it crashes a lot with the "NetSurf has detected a serious error and must exit window". The work around is to disable JavaScript before trying again. -- David Pitt
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
> > <54f1f9a962ch...@chris-johnson.org.uk>:
>
> >> In article ,
> >>Jim Nagel 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.
Fail 2890 json
Has any one else had this version fail? Gerald
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
On 13 Aug, Jim Nagel wrote in message
:
> Steve Fryatt wrote on 12 Aug:
>
> > On 12 Aug, cj wrote in message
> > <54f1f9a962ch...@chris-johnson.org.uk>:
>
> > > In article ,
> >>Jim Nagel 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.
...for the reason I've just explained above.
If you have SparkFS loaded, RISC OS's filing system interface will report
zip files as being directories to any applications which check file
information. It's how the magic of Image Filing Systems works.
The "object with the same name" is a zip file and, because you have SparkFS
loaded, it looks like a directory to the filing system. For similar effect,
try and overwrite a StrongHelp manual with StrongHelp running and see what
happens.
> 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.
The "'ADFS::Drive2.$.2310d/zip' is a directory" bit of the error is given to
NetSurf by filecore. NetSurf is just the messenger.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
Steve Fryatt wrote on 12 Aug:
> On 12 Aug, cj wrote in message
> <54f1f9a962ch...@chris-johnson.org.uk>:
>> In article ,
>>Jim Nagel 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.
>>> (2) The text of the warning was not recorded by !Syslog (whose job is to
>>> make it easy for people submitting bug reports to quote the exact
>>> wording of an error message). I searched the whole log and found
>>> nothing from Netsurf.
> Some confusion? There's no single SysLog log, so it isn't clear which "whole
> log" Jim searched...
I searched anything in !Syslog.Logs with a recent datestamp,
particularly the logfile called WIMP.
...
> NetSurf uses its own non-blocking error dialogues, so WimpLog won't
> ever see the errors reported.
> In terms of bug reporting, NetSurf's own log is far more detailed and
> far more useful.
Does Netsurf record a warning such as this one in its log file? Its
current files are 0 length, possibly because I have rebooted since the
incident, so can't check. But I searched for "warning" in an old
Netsurf logfile that I saved for some reason, and turned up nothing.
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.
--
Jim Nagelwww.archivemag.co.uk
