You are welcome, interesting if it works out 
And if not, I recommend the Roadshow stack.
Wow, there's a whole heap of confusion here. I'm not familiar with INet but you seemed to have almost a working config from the outset. You could ping local machines and the router. You just need to make sure the default route/gateway is pointing at your router (192.168.1.1) and also confirm you're pointing at the correct DNS server (also likely 192.168.1.1).
If you try to 'ping google.com' from the CLI, this will test if name resolution is working. It will also confirm if you're using the correct gateway. If that fails 'unknown host' then DNS is not configured properly, if it resolves the name to IP but the ping fails then it's likely an incorrect default route.
Steve
p.s. As others have mentioned AmiTCP, I wrote an install guide here:
http://blog.netting.org.uk/2015/07/19/amitcp-and-configuration-of-cnet-device/
