RobotC starts up take a long time in our fire-wall infrastructure. Then, I tested it on an open network it is fine. Does anyone have the similar experience? Guess start up going out to the network for authentication?

The slowness could also be caused by the check for the latest version. See if disabling it through this makes a difference:


= Xander

Thank you. I'll try that too tomorrow when I'm back in the lab.

Do you happen to have a PROXY server that you're using? We are adding support to ROBOTC for the activation system to use proxy servers.

On bootup, ROBOTC checks to see if it has internet connectivity by checking to see if it can phone home to the activation server (we used to check if we could get to ROBOTC.net, but people would be incorrectly told they had full internet connectivity but couldn't activate because their school was blocking the activation server). This check is used to verify that we can load the live start page and other items. Is the latency from loading the live start page, or is it before you even get to that point?

That's what I thought... yes, the latency seems to come from loading the live start page. I disabled both the "Load the splash startup page", and "Check for Newer Version of RobotC on Startup" did not. If it must do the online authentication, it needs to allow us to set it up to go through our proxy.

I have just actually tested it by removing our proxy using the same computer, same router. RobotC started up very quickly. Therefore, since we are running this as educational institution where there are many kids are using. We have to set it up to go through proxy. I am guessing you are using port 80...?? Anyway, the more desirable setup is to allow site license owner to go thru an internal proxy server. Thank you in advance for this.

Just to chime in here - We're working on a BETA release (mostly done) that will have PROXY support for the activation server functions. This should hopefully alleviate any slow response time for individuals using network wide proxy servers.

thank you...

Hi Everyone,

If you're having this issue it's related to using a Proxy server when doing any type of "activation" requests. If you are experiencing this issue, please e-mail me at tfriez (at) robotc [dot] net if you would like to assist us in testing a build with proxy support. Otherwise, the next update of ROBOTC will include this functionality.

Thanks!