In article <5b4c6d1356d...@triffid.co.uk>,
Dave wrote:
> In article <5b4c616f4d...@mightyoak.org.uk>,
>Bob Latham wrote:
> > In article <5b4c526636li...@torrens.org>,
> >Richard Torrens (lists) wrote:
> > > In article <5b4c408979...@mightyoak.org.uk>,
> > >Bob Latham wrote:
> >
In article <5b4c7ad502d...@triffid.co.uk>,
Dave wrote:
> Begs a question, how does one go about finding any other apps that
> are loading/using that old module?
!Locate will happily look for instances of a file in a directory ...
which could be the whole disc if you want.
Most useful for
In article <5b4c616f4d...@mightyoak.org.uk>,
Bob Latham wrote:
> In article <5b4c526636li...@torrens.org>,
>Richard Torrens (lists) wrote:
> > In article <5b4c408979...@mightyoak.org.uk>,
> >Bob Latham wrote:
> > > Latest development version 6696 fails to start on RISC OS.
> > >
On Thu, Apr 04, 2024 at 04:52:58PM +0100, Bob Latham wrote:
> Yes, but an earlier socket is loaded by both UniPrint and Hermes from
> within the applications, there may be more.
This is a bug in UniPrint and Hermes: the reason we have the System
Merge tool is to prevent this exact situation: apps
In article <5b4c526636li...@torrens.org>,
Richard Torrens (lists) wrote:
> In article <5b4c408979...@mightyoak.org.uk>,
>Bob Latham wrote:
> > Latest development version 6696 fails to start on RISC OS.
> > Immediate error:
> > "Still watching sockets; can't be killed yet."
> > A machine
On 04 Apr, David Higton wrote:
> In message
> Rob Kendrick wrote:
> > On Thu, Apr 04, 2024 at 10:53:38AM +0100, Bob Latham wrote:
> > > Latest development version 6696 fails to start on RISC OS.
> > >
> > > Immediate error: "Still watching sockets; can't be killed yet."
> > >
> > >
In article <5b4c408979...@mightyoak.org.uk>,
Bob Latham 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
In message
Rob Kendrick wrote:
> On Thu, Apr 04, 2024 at 10:53:38AM +0100, Bob Latham 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.
>
> My
On Thu, Apr 04, 2024 at 10:53:38AM +0100, Bob Latham 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.
My /guess/ is that SocketWatch (or similar) is running via
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.
10 matches
Mail list logo