To answer posed questions:
#1) Yes. My previous experiences have been that, while on AC power, Doom3 flies. But, until I changed my bios, I could set the game's options to the lowest resolution, lowest detail and still would be choppy while on DC. That was, of course, when my BIOS was previously set to a cpu speed ceiling of 600mhz.
#2). Yes. After modifying my BIOS settings to make the computer run at maximum performance while on battery, I am now able to play Doom3 as smoothly and with as high as settings as I have previously been using while playing on AC power. FRAPS indicates framerates are comparable to AC power framerates now.
#3). Some confusion here. According to Luke's post, setting the BIOS to max DC power and setting the OS power settings to laptop/notebook scheme should basically allow the computer cpu to run at around 600mhz, but to tap into the extra 1400mhz when needed to help run demanding games/software. My settings correspond to this.
What is confusing is what these third party cpu-monitoring programs are reading to me. Mobmeter reads cpu speed locked at 2ghz, even though, according to Luke's post, it should be throttling down when using less-demanding applications. This has been discussed previously -- drawmonster stated mobmeter will not effectively read/report cpu speed once the BIOS is changed.
So, can we assume Mobmeter is inaccurate? Well, if you look back at Luke's post, the Sager tech guy stated Mobmeter should actually reflect the changes in cpu speed.
So, is Mobmeter accurate or what? If it is inaccurate, then I very well could be throttling up and down as in Luke's post, but the cpu speed is being erroneously reported at "locked-on" 2ghz. If it is accurate, then, despite the advice of Luke's post, there is no adjusting of cpu speed going-on to match the demands of the applications I am using.
So, let's forget about Mobmeter for a bit. What about SpeedswitchXP? This is another third party program that has perplexing results. The realtime graph function of this program seems to accurately reflect the demands certain apps place on the cpu load. Load stays low while running WMP, IE, Word, etc, but then hits the ceiling when playing Doom3. This makes sense -- I would expect the load to fluctuate with the apps I'm using.
Also, on SpeedswitchXP's graph, is a line plot for cpu speed. This is where things get interesting. The speed hovers at approx 30% of max (translate to 600mhz) no matter what app I run, including Doom3. So, what does this mean? Does it mean I am really stuck back at 600mhz for my cpu speed ceiling again? I don't think so, because Doom3 has been running superbly as if I'm on AC power. Again, that didn't happen until I modified my BIOS power settings to "Max Performance" this afternoon. So, despite what SpeedswitchXP graphs, I believe I'm running at a higher frequency than 600mhz.
Could it the lack of graphed fluctuation in cpu speed mean that SpeedswitchXP, like Mobilemeter, is unable to accurately report that value? That would seem odd, b/c it can report increased cpu load. So, why can't it report increased cpu speed?
So, to sum it all up . . . . I've followed Luke's advice. Doom3 runs great. None of the 3rd party software programs are reflecting any change in my cpu clockspeed, so I am unable to verify whether or not, as the Sager guy in Luke's post suggested, my cpu is able to throttle up and down to meet application demands while maximizing battery life as well. And that's what we really need to do here. This is the crux of this problem. Does making the recommended BIOS change fix this troublesome issue? Does it provide an alternative to the two crappy options of either: A) having cpu speed max out at 600mhz while on DC power to maximize battery life at the cost of performance; or, B) locking cpu speed at max all the time to maximize performance at the cost of battery life? Unfortunately, I don't think either Mobilemeter or SpeedswitchXP provide an accurate means of measuring this. Either that or, both are indeed accurate and the BIOS switch recommended in Luke's post does absolutely nothing.