If you were using VC you could use the function _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF ); , included via , MSDN explains what it does. It's what I use, and a report of leaked memory appears in visual studio's output window whenever I forget to free memory, as well as a little hint whereabouts it occurred.

I can't seem to find an option to print date/time on source code printouts. Is there one?, or do I just have to do that myself...

for me its start at 9am, finish at 4:30pm

The only other thing I can think of apart from heat that I know causes drives to fail is voltage/surge/power supply related problems, or if a laptop, dropping it. Do the temps get much higher on hot days?

Are these drives adequately cooled? Two 7200rpm drives close together might be getting a bit warm and failing prematurely.

er um... win 3.1 is a program that runs on top of dos. You first need to get dos 6.22 installed, and then load windows on top. this is all so long ago now.... the bad old days... that ended when win95 came along, well, more or less.

Well... If VC6 is the only application you ever use on that monitor... Just live with it, buy another one in a couple years if you really have to... What difference is it gonna make anyway... so long as you can still read whats displayed in the output window of course...

try to ensure the cabs are not corrupted. To verify this, right click each cab, go properties->digital signatures->details. If it says its ok then the cab is perfect, if not then you need to redownload it. I just did all this a few weeks ago and it worked good for me. As an aside, changing a bit in a cab with a hex editor does cause it to fail its digital signature check, putting the bit back makes it right again. John

well... if you want the best solution... go for three monitors... just think... when using visual studio, have the code displayed on monitor one, the actual program on monitor two, and the watch/locals/ output on monitor three... all 17" lcd monitors 1280x1024.... yep, hey, why not stop there, monitor #4 displaying msdn or whatever....

this might form the basis of a good codeproject article, that is, a general overview of the techniques and entry points in windows where software is able to install itself etc. I myself recently spent a few hours getting rid of "CoolWebSearch" on a friends computer, Adaware wouldn't get rid of it, infact CWS actively deleted adaware everytime I downloaded it!! It turned out that CWS used both a BHO (browser helper object) and the registry key Appinit_Dlls to load itself into every running process, and reestablish its keys everytime you deleted them, each process seemed to guard the other, even in safe mode command prompt only it still loaded... A brilliant business model though, it kept setting a home page to a search site popping up a popup saying computer infected and offering to sell a spyware removal tool. Very clever... Interesting business strategy... I used a combination of autoruns from sysinternals.com and adaware and then overwrote the randomly named files containing the virus code with garbage to (finally) regain control. Firefox is a good choice for avoiding all this at present.