Ethernet...sounds like it needs a delay for the net card to settle the run the autoconnect (its in right click in connect icon so could be run from a mini script in startup which includes a delay or checks the card is ready
mike
The Mission
ecomoney... very old post I know...but did you ever sort out the problems with the routers kicking some machines off the net?
Is it possible that this was an issue with dhcpcd not running within Puppy the way the router was expecting?
I have problems with some versions of puppy (old ones and new ones alike) not being acceptable to the router intermittently, and the router refuses to issue a dhcp lease. Sometimes loading a newer dhcpcd fixes the issues.
4.3.1 is the most reliable I have found. Also there is a lot of recognition recently that Puppy hasn't treated it's internal "hostname" as uniquely as routers expect that it should, and this has a bearing on how some routers handle each machine. Could this have a bearing on some of the cafe probs you saw?
Is it possible that this was an issue with dhcpcd not running within Puppy the way the router was expecting?
I have problems with some versions of puppy (old ones and new ones alike) not being acceptable to the router intermittently, and the router refuses to issue a dhcp lease. Sometimes loading a newer dhcpcd fixes the issues.
4.3.1 is the most reliable I have found. Also there is a lot of recognition recently that Puppy hasn't treated it's internal "hostname" as uniquely as routers expect that it should, and this has a bearing on how some routers handle each machine. Could this have a bearing on some of the cafe probs you saw?