If you happen to be in a situation, at work for example, where MSWord 2007 is forced upon you, you might want to join your local Microsoft abuse self-help group, or just refer to this article: benchmarking MS Word from 95 to 2007.
By default, on a 4GB 32-bit system, windows only gives 2GB to the application. To increase the amount of total user virtual address space, edit your boot.ini and include the /3GB option. With the /USERVA you can tweak the amount between 2 and 3 gigabyte. So you can not allocate more than 3GB for applications.
Furthermore, you must relink your application with the /LARGEADDRESSAWARE option to make use of this ‘4GT’ feature. You can also modify an existing binary by using editbin.
source: MSDN
I have been a long time satisfied user of Grisoft’s Antivirus suite, for my parent’s computer actually. What’s important for me is a good configurable email scanner and a fast on-access scanner. Until 7.5 AVG seemed OK in those aspects. However, last week, I upgraded AVG 8 as I thought this was just a regular upgrade. Little did I know they vistafied the crap out of (or rather in) it. The interface is dumbed down so you always need to use the advanced options menu. They added some bloat features like the link scanner[1] and antispyware stuff. But worst of all: it slows down the entire system! When even my mother complains the system has slowed down since the upgrade, you can be sure it is a remarkable slowdown 
I am guessing this must be a bug, maybe it does not occur on all systems. I can’t believe they would make such a jump downwards. In the meanwhile, I am looking for alternatives. Avira’s Antivir seems quite okay..?
[1] fortunately, you can remove this feature through a custom installer command
The 1989 C standard didn’t allow variable argument macros. They were added in the 1999 standard. To use one according to the standard, plug in “__VA_ARGS__” where you want the variable arguments. For example:#define print(…) real_print( __VA_ARGS__ , 0)
Of course, your compiler may or may not support either this feature or a nonstandard variation.
You might have guessed that, after all those years, the MS compiler still does not support them!!! arghh. crap.
I thought I already blogged this, but I can’t find it back, so let me try one more try as I seem to need this from time to time and then fail to remember the correct syntax! 
The scenario is: you have this huge error output on your console (for example a very long compiler error). Since it is quite long, console history is not big enough to see the beginning. You could of course increase the history size, but it’s not a real solution. Everyone knows how to redirect console output to a file, simply like this:
This is all nice and dandy, except, it doesn’t capture the error output (stderr) (which is exactly what we’re interested in ;)). You have to do some win32 console-fu as follows:
This tells the shell to redirect standard output (stdout) to output.txt and redirect error output to standard output.
You can read all this information in a nice collegebook format on MS’s KB.