Earlier in this thread I posted a problem with that issue...
You can put Oddcast into your startup folder, and it will start at bootup, and then you can set "auto connect" in Oddcast itself.
However I've found, apparently, if it cannot connect immediately upon startup, it will never connect unless you manually close it, then restart.
I see that you posted about problems making the initial connection after rebooting, and about problems with CPU usage, both issues I still have as well. So you're saying that the "auto connect" doesn't just control the initial connection, but subsequent reconnection attempts as well? That would explain why I've yet to find that my Oddcast had not restarted, since I do have this option checked.
For me, Oddcast has NEVER actually started on its own. But I've found that all you need to do is reselect the "Live Recording" options, and it will run without restarting the application.
I'm now wondering if my feed does in fact drop out periodically, as I'm showing a new mount time during the night. (I'll be showing a new one momentarily, after my Winders updates finish.)
Also, I find that, regardless of whether Oddcast is in the Startup folder or not, that it will not actually connect the first time it is run after startup. This is true even if I wait several minutes after the PC has fully booted. So there's definitely a bug in the software, in my opinion, and not necessarily a problem with the drivers not being loaded, as I had surmised earlier.