See also this MSDN article by Paul DiLascia.

Copy msvcrt.dll (or msvcrtd.dll for a debug build) to \winnt\system32 (or similar).

Don't go for marketing research, trust your INTUITION. Start small, home office, no personel. If you need the finance, try to get a 24-hour per week consultancy or other free-lance job. The rest of your time, go for it and you will succeed. And in the unlikely case after say a year the market appears to be not there, you can always go back to your 9 to 5 job. You have not failed, you have dared to live, you've had a lot of fun, and as David said, a lot of useful experience! Sito Dekker

Typical case of shameless stealing from the open-source copy cats. Matlab and the likes have this kind of capabilities for many, many years.

Best and appropriate way to do this is to use a character style in which you check "Do not check spelling or grammar." Mark all function / variable names with this character style, using a shortcut key. Of course you also might define a separate style for each category. Works fine on Office XP. As an added bonus you can change all your function names, member variables to another font/color/special effect, e.g. to bold blue courier. Have fun! Sito Dekker

The following lines are sufficient to crash Win2k. #include <stdio.h> void main(void) { printf("\t\b\b"); } Sito Dekker

Take a look at VenturCom. Their RTX product is a so-called real-time extension to Windows NT. They use a modified HAL which catches interrupts before NT gets a chance to process them. This way, deterministic interrupt response times can be guaranteed. A real time "RTX API" is provided to access a bunch of real-time primitives. I've used RTX in a large project at my previous employer and it worked quite well. A big plus was that you could compile, run and debug your program under NT entirely (except for the hard real-time aspects of course), and then simply recompile and run on RTX to get real-time deterministic behaviour. Sito Dekker

No, you're not. It takes ages to download. The quality may be relatively good for the internet, but this only shows the sad state of the internet: the quality is still VERY poor compared to the average animation movie. Furthermore, I find the violence disgusting. There is no story, let alone something to be learned.

In the Visual SourceSafe Administrator 6.0 there is an option "Use network name for automatic login" in Tools, Options, General. Don't know about 5.0 though. Anyway, in 6.0 it works great, I'm on Win2k and NEVER need to log in to SourceSafe. Sito Dekker

I used it and I like the tool. But I immediately had the same thought as you, why does this program not offer me to actually install the patches, it would make life so much easier. I was also amazed by the amount of patches not installed, even warnings, printed by the program, while regularly running Windows Update. Sito Dekker

Take this one fragment on the home page: "and just hang out and help each other learn". It's word by word copied from CodeProject. Coincidence??????

Don Box probably has helped shaping this strategy, a.o. by his contributions to SOAP. Personally, I think .Net is a master move, bold indeed for a large company like Microsoft. However, as with every "paradigm shift", the change won't happen overnight. Microsoft can't afford not to support and even update its legacy for years to come. No big enhancements any more, of course, but enough to allow us to program "the old way" for a long time. And, yes, for systems programming (a niche, let us not forget) .Net will be far, far away.

> You're assuming something that is totally false, but which is assumed > by many people (including managers) - that UI design is easy. I don't read this from Jim's text. He assumes that UI design is as easy or as difficult as programming in general. UI design and programming require, to a large extend, the same skill set, of which "being able to organise" is one of the most important. For both disciplines one must understand and analyse the user's problem and, unless the problem at hand is trivial, design a proper modular solution. One can make use of best practices, but no solid "mathematical" theory how to do this exists. The UI designer / programmer has to rely on common sense and feeling for good modularity, which can come from talent and/or experience. So I fully agree with Jim: a good UI designer will be a good programmer, and vice versa. Sito Dekker