I've been running tournaments on it for 2 years with out a hitch. Never a single problem. I purposely got the Intel graphics card because this little wonder also subs as a media centre when I want to watch a movie.
Unfortunately this is probably irrelevant as far as the TD is concerned. The graphics demands of the TD are very small. It's all 2D and stuff just doesn't change very much, so it's producing probably a near zero load on your graphics hardware.
The issue is IE (not busting IE's chops, it would be the same for any browser). If the TD used a specific graphics solution, it could do things like ... when the clock changes, update the clock display and nothing else. This would be very fast. But the TD uses IE (which allows for very versatile customization), so when the clock changes, IE has to do a ton of calculations trying to figure out what does and what does not have to be re-rendered ... did the clock area get bigger because of the font, did it shift things around on the screen, do I have to re-render everything ... etc, etc. It can be taxing on the CPU. I have a desktop i7 3.something GHz quadcore (can't remember the specs) and the only time the TD makes even a noticeable dent is when running full screen a screen transition occurs to or from a complicated layout with lots of cells. I have a laptop i5 dual core, definitely can't remember the specs, but the TD takes a noticeable amount of CPU when running, even when nothing's really happening (just the clock updating). There's a big performance difference in the two machines.
When I hit the game tab, it takes up to 10 seconds for the screen to change.
THAT, however, I've not seen. And I can't imagine why it would happen. Does it take a long time for the Game tab to display the first time you visit that tab after opening the Settings window? Does it pause on revisits (without closing the Settings window in between)?
FYI: the Settings window "caches" each tab, so that when you revisit a tab it doesn't have to be re-rendered. So the first time you click on a tab will take just slightly longer to render then on repeat visits. But when the Settings window is closed, due to the way IE works those cached tabs go away. When you re-open the Settings window, each tab has to be rendered again, and you'll notice that slight delay the first time you click each tab again.
Corey, you are ALWAYS there to help, and that is much appreciated.
No worries, that's my job after all.
Seriously, I like to help, and if there's a bug I definitely want to identify and fix it if possible.