In article <5b4c6d1356dave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
> In article <5b4c616f4dbob@mightyoak.org.uk>,
> Bob Latham <bob@mightyoak.org.uk> wrote:
> > In article <5b4c526636Lists@Torrens.org>,
> > Richard Torrens (lists) <Lists@Torrens.org> wrote:
> > > In article <5b4c408979bob@mightyoak.org.uk>,
> > > Bob Latham <bob@mightyoak.org.uk> wrote:
> > > > Latest development version 6696 fails to start on RISC OS.
> > > > Immediate error:
> > > > "Still watching sockets; can't be killed yet."
> > > > A machine re-boot does not change this.
> > > > Bob.
> > >
> > > 6696 has an updated SockWatch module. Have you merged the !System
> > > in the zip with your own?
> > Yes, but an earlier socket is loaded by both UniPrint and Hermes from
> > within the applications, there may be more.
> > Bob.
> After updating System with the new one.
> I just went inside ...!Hermes.Resources.SockWatch and named it out
> (SockWatchXXX).
> No problems after that.
> Dave
Begs a question, how does one go about finding any other apps that are
loading/using that old module?
Thanks
Dave
--
Dave Triffid
No comments:
Post a Comment