In message <5b53b78dd7...@npost.uk>
Chris Newman wrote:
> 6697 works happily on my FAST Pi Compute Module 4 RISC OS 5.29
Also working fine here on my A9home RISC OS 4.39
Regards
Paul Stewart
In article ,
John-Mark Bell wrote:
> On 20/04/2024 12:32, Chris Newman wrote:
> > In article <5b53b78dd7...@npost.uk>, Chris Newman
> >
> >> I looked inside the !System that came with the download. There is no
> >> Socketwatch in the 310 modules directory so I added 0.07 manually.
> >> Made
On 20/04/2024 12:32, Chris Newman wrote:
In article <5b53b78dd7...@npost.uk>, Chris Newman wrote:
I looked inside the !System that came with the download. There is no
Socketwatch in the 310 modules directory so I added 0.07 manually. Made
no difference.
The SocketWatch changes have
In article <5b53b78dd7...@npost.uk>, Chris Newman wrote:
> > 6696 has an updated SockWatch module. Have you merged the !System in
> > the zip with your own?
> 6697 works happily on my FAST Pi Compute Module 4 RISC OS 5.29
> On Virtual Acorn Adjust 4.39 Windows 10 Acer netbook
> It
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
In article <5b504a7c4fnetsurf-users-...@aconet.nl>,
Frank de Bruijn wrote:
> On 11 Apr, Chris Newman wrote:
> > I ran the !ModInst from the 0.07 download but got an undefined
> > instruction error
> Not surprising. !ModInst appears to have a more than two decades old
> !RunImage. It was a
On 11 Apr, Chris Newman wrote:
> I ran the !ModInst from the 0.07 download but got an undefined
> instruction error
Not surprising. !ModInst appears to have a more than two decades old
!RunImage. It was a useful tool at the time, but I should really remove
it and switch to using the OS's System
In article <5b500541e6d...@triffid.co.uk>, Dave
wrote:
> In article <5b4ff405ca...@npost.uk>, Chris Newman wrote:
> > In article <5b4d8b51fbnets...@avisoft.f9.co.uk>, Martin Avison
> > wrote:
> >
> > > The correct way is that the latest version should be used
> > > everywhere, and the old
In article <5b4ff405ca...@npost.uk>,
Chris Newman wrote:
> In article <5b4d8b51fbnets...@avisoft.f9.co.uk>, Martin Avison
> wrote:
>
> > 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
> >
In article <5b4d8b51fbnets...@avisoft.f9.co.uk>, Martin Avison
wrote:
> 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
I have just sent this email to Andrew Rawnsley drawing his attention to
the problem
-
Hi Andrew,
The hardwired SockWatch in !Uniprint is causing errors and will prevent it
using updated SockWatch modules when they are
In article <0650874d5b.j...@rickman.argonet.co.uk>,
John Rickman wrote:
> In message
> Rob Kendrick wrote:
> > My /guess/ is that SocketWatch (or similar) is running via an
> > application launched at boot and it is an earlier version than
> > NetSurf requires, so NetSurf's !Run's
On Sat, Apr 06, 2024 at 10:22:54PM +0100, John Rickman wrote:
> At last nights RISC OS coding zoom meeting there was discussion of this
> SocketWatch issue and I was asked to write to this list seeking some
> information. We looked at the change log for v0.07 and tested the latest
> NetSurf
In message
Rob Kendrick wrote:
> My /guess/ is that SocketWatch (or similar) is running via an
> application launched at boot and it is an earlier version than NetSurf
> requires, so NetSurf's !Run's RMEnsure tries to replace it with a newer
> version?
At last nights RISC OS coding
On 05 Apr, David Higton wrote:
> > If you do the recommended SysMerge with the !System supplied in the
> > Netsurf development download, the latest SockWatch module will be
> > placed in: Boot:Resources.!System.310.Modules.Network
I always to the merge but the last version I downloaded was
In message <57b8cf4c5b.boase@bernard>
bern...@boase.myzen.co.uk wrote:
> On 5 Apr 2024, j...@jaharrison.me.uk wrote:
>
> > I have nothing at: System:Modules.Network.SockWatch. The only copy is
> > the one inside Hermes. There isn't even a: System:Modules.Network
> > directory.
On 5 Apr 2024, j...@jaharrison.me.uk wrote:
> I have nothing at: System:Modules.Network.SockWatch. The only copy is
> the one inside Hermes. There isn't even a: System:Modules.Network
> directory. Should I be worried?
If you do the recommended SysMerge with the !System supplied in the
In article <5b4cc7c00c...@mightyoak.org.uk>,
Bob Latham wrote:
> In article <5b4cbd5005d...@triffid.co.uk>,
>Dave wrote:
> > I fixed it here by changing the Uniserver and Hermes !Run file
> > "RMEnsure SocketWatch" entries to point to
> > System:Modules.Network.SockWatch instead of their
In message <5b4cca8189j...@jaharrison.me.uk>
John Harrison wrote:
> I have nothing at: System:Modules.Network.SockWatch. The only copy is
> the one inside Hermes. There isn't even a: System:Modules.Network
> directory. Should I be worried?
>
> RO 5.29 (15 February 21)
> IPv6 (25
In article <5b4cba41f5d...@triffid.co.uk>,
Dave wrote:
> If it's of any use to anyone else, on the RISC OS 6.20 install here,
> there are three occurrences of "SockWatch".
> ..$.!Boot.Choices.Users.Single.Boot.PreDesk.!UniPrint.SockWatch
>
In article <5b4cbd5005d...@triffid.co.uk>,
Dave wrote:
> I fixed it here by changing the Uniserver and Hermes !Run file
> "RMEnsure SocketWatch" entries to point to
> System:Modules.Network.SockWatch instead of their own internal
> SockWatch modules.
I have nothing at:
In article <5b4cba41f5d...@triffid.co.uk>,
Dave wrote:
> > !Locate will happily look for ...
> Ah Yes, I'd forgotten about that app, ...
It's extremely useful, and flexible. I use it a lot.
Thanks to Steve for producing it.
--
John Harrison
Website http://jaharrison.me.uk
Using 4té and
In article <5b4cbd5005d...@triffid.co.uk>,
Dave wrote:
> I fixed it here by changing the Uniserver and Hermes !Run file
> "RMEnsure SocketWatch" entries to point to
> System:Modules.Network.SockWatch instead of their own internal
> SockWatch modules.
Yes, that is a sensible way to do it but
In article <5b4cba41f5d...@triffid.co.uk>,
Dave wrote:
[Snippy]
> If it's of any use to anyone else, on the RISC OS 6.20 install here,
> there are three occurrences of "SockWatch".
> ..$.!Boot.Choices.Users.Single.Boot.PreDesk.!UniPrint.SockWatch
>
In article <5b4c7d5616nets...@avisoft.f9.co.uk>,
Martin Avison 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
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
34 matches
Mail list logo
