In article <5b500541e6dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:
> In article <5b4ff405camec@npost.uk>, Chris Newman <mec@npost.uk> wrote:
> > In article <5b4d8b51fbnetsurf@avisoft.f9.co.uk>, Martin Avison
> > <netsurf@avisoft.f9.co.uk> wrote:
> > <Big snip>
> > > The correct way is that the latest version should be used
> > > everywhere, and the old ones removed (as long as the later fixed
> > > version has no incompatible API changes).
> > > Please see the long list of changes made since v0.04y (02-12-2002)
> > > that are included in v0.07 (11-01-2019) some 16 years later.
> > > Other applications may rely on some of those fixes and changes!
> > > The latest v0.07 AFAIK is available at https://www.aconet.nl/tools/
> > I have downloaded v0.07. It has an installation app to put the module
> > in
> > !System.310.Modules.Network.SockWatch
> > Ignoring that for the moment, I delved into the innards and put the
> > module in Hermes inside Netfetch in place of v0.04. Everything seems
> > to be working as normal. Nothing has fallen over. Therefore it seems
> > Hermes would not have any problem with v0.07.
> > I've not yet put it in 310 in case it clashes with Netsurf. I may
> > 'speriment later.
> Each to their own... :-)
> If you remember, I fixed my Hermes and Uniprint to use the SockWatch
> 0.07 in ...!System.310.Modules.Network.
> Neither Hermes nor Uniprint have had any problems with SockWatch 0.07
> in ...!System.310.Modules.Network since I made the changes.
> Netsurf 6696 needs SockWatch 0.07
Just wanted to se what would happen without fiddling with !un files
I ran the !ModInst from the 0.07 download but got an undefined
instruction error so I put it manually in System 310. Now running Netsurf
6697 happily.
--
Chris Newman
No comments:
Post a Comment