If I'm reading this correctly, and you've got two threads running, you might need to add some critical sections or events around your use of the BipBuffer; as the code stands it's not threadsafe.

Make sure that Want Return is set in the dialog editor.

Giving away full blown software packages threatens our lively hood, and as a group we should be smarter than that. I've yet to go to the doctor's office, a grocery store, or the "mall" and find a shop that says, "Hey, you know what? Take this for free". Matter of fact, our Medical insurance coverage just jumped up almost $50/mo. and will now cost my family more than a monthly car payment so we can have health insurance to go see a doctor. The only other group I can think of that gives something away for free, at least initially, are drug pushers. What I find most disturbing is that more people don't understand how giving things away for free has negatively impacted our industry. Heheheheh.... I can sum up all of this in one neat link. Warning: The following link refers to satire, and should not be taken literally Red Penguins

Rocky Moore wrote: We have the Internet, it is time to stop with all the "mail-in" junk! Alas, they rely on you (or rather, the majority of people) being unwilling to go through all of the hassle to get the rebate in order to be able to offer it. Statistically speaking, you can put an upper bound of only 15% of customers ever actually sending in the rebate form. Less, the more inconvenient you make it. Simon (Who once asked marketing exactly why they put rebates on all the products he shipped... answer: it's the same as knocking $5 off the store-price, but people see the $20 rebate and feel like you're knocking $20 off it, whether they send it in or not).

Test case was a do nothing dialog app (i.e. Just click through the wizard and compile in release) MFC Statically linked: 200kb WTL: 32kb And if you don't mind your app only running on NT4.0, Win2K or XP and up... then you can set the /ALIGN parameter on the linker to 16 bytes (IIRC), and get that down to: MFC Statically Linked: ~200kb WTL: 15kb. :-) Of course... you probably don't want to do that in production code. But hey, I kind of like having my console apps ~2kb in size :) Si

What is the big deal about WTL? It's possibly the coolest, most flexible way to write a Windows app. What does it do that MFC doesn't do? (And "code bloat" is not considered a valid response.) 1. Reduces Code Bloat. A WTL app will typically be 1/10th (or less) the size of an MFC app. For example, my fully fledged data plotting app that I wrote to analyze data from the Mass Spectrometer I'm writing control software for at work is 148kb in size. That's with the C runtime statically linked into it. It's not bad at all. 2. (My personal favorite reason), it uses assembly language thunks to map WNDPROCs to objects, unlike MFC which uses a Map to map pointers to classes. Not only does this make your code much more efficient if you're using a lot of windows in your app, but it makes the implementation of a window class MUCH more obvious. For example, you don't need to handle precreate messages in a special way; you just handle the WM_NCCREATE message. What doesn't it do that MFC does? 1. It doesn't lock you into a framework that you have to shoehorn your app design into. You can freely architect your application, with very few limitations. In the right hands, this is a good thing. In the wrong hands... well... go figure. Either way, it gives you the power to make that decision for yourself. 2. (Note: this applies to WTL/ATL3.1 only; I've not had chance to examine the 7.0 stuff) No file wrappers. No structured storage wrappers. This may or may not be a problem for you. Later versions have CString classes, etc. 3. No real classwizard / resource handler support in the system (although it does some things the same way as MFC). This is both a benefit and a curse; I hate the way MFC tramples all over resource files. 4. It doesn't get officially supported by Microsoft. I have the feeling that this may change eventually. 5. It doesn't put all those stupid AFX headers in every file you write. That's a big plus for me. Are the various app/class wizards still available? To an extent. You actually use those things? The mind boggles. Does it make development faster? Hell yes. I managed to put together an app in two weeks that would have taken several months previously. Oh, you meant vs. MFC, not vs. raw Win32? Oh, ok. It depends. If you're using MFC the way MFC was designed to be used, you'll Are your apps faster? It depends on the application domain. I'll say yes, with a caveat; namely, it depends on how you define "faster". Are your apps mor