That sounds good selected or ticked on/off
"Enabled" isn't a bad word, so long as everyone uses it with the proper meaning. I use it myself in the context of configuring something.
If it is something particularly GUI-oriented, then checked/unchecked works well, and perhaps does well to distinguish the "front-end settings" from the back-end process itself.
and can't even believe I am having to respond to thread were a member says " isn't a good word there"
It's not the Kitz site I remember 3 years ago
I'll apologise partially, because I thought this was the thread where there was ongoing confusion mixing up the configuration / enabling of G.INP vs PhyR. Between the two threads, though, confusion appears to reign.
However, it is only partial. I don't apologise for attempting to seek clarity. I'd always rather err on the side of clarity. However, because it wasn't the right thread, my clumsy request for clarity itself added to confusion - and I do apologise for that aspect.
So, back to the core matter...
Can I ask why enabling PhyR is thought to be beneficial in the UK? IMO, it shouldn't be. Is there a belief that PhyR must be enabled in the modem for G.INP to activate?
I thought I'd experiment: I have an 8800NL too, and checked the GUI status. It started out with Downstream PhyR ticked and upstream unticked. G.INP was running downstream, and has been ever since it was first activated aeons ago.
So I unticked the downstream PhyR, and hit apply...
The modem resynced, and PPP reestablished. The actual line profile remained as before - with G.INP active downstream, no change to any properties.
The GUI confirms neither PhyR is now ticked. I double-checked with the command line ("ADSL profile --show"), and it thinks PhyReXmt is off/off.
I didnt think that PhyR was the same as G.INP. The PhyR settings in the modem don't seem to affect whether G.INP can activate... Is there anything else I can try?