techman210
Member
I've used a couple of the different packages for providing a feed.
I've noticed that in my limited experience, they have trouble establishing the feed after a power-loss reboot. This seems to stem more from the delay between the feed software going active, and the internet connection establishing itself. It seems the software just "gives up" after a short time and remains offline until manual intervention.
I've created a batch file that runs >3-4 minutes of pings before invoking the feed software and that has improved reliability quite a bit.
Are there any other ideas? I did see some "freeware" that would delay the start of a program on start-up, but IDEALLY, it would be great if the feed software kept trying longer before giving up, or had a clickable box (or 2-digit dialog box) that would allow the feed provider to delay the feed "x" minutes after start-up.
I've noticed that in my limited experience, they have trouble establishing the feed after a power-loss reboot. This seems to stem more from the delay between the feed software going active, and the internet connection establishing itself. It seems the software just "gives up" after a short time and remains offline until manual intervention.
I've created a batch file that runs >3-4 minutes of pings before invoking the feed software and that has improved reliability quite a bit.
Are there any other ideas? I did see some "freeware" that would delay the start of a program on start-up, but IDEALLY, it would be great if the feed software kept trying longer before giving up, or had a clickable box (or 2-digit dialog box) that would allow the feed provider to delay the feed "x" minutes after start-up.
