>further to my whingeing about the compiled exes crashing - a number of you suggested I download and install the sp3, which was a pleasant way to spend the weekend! After 2 complete de/reinstalls I finally took the plunge and reinstalled sp3 last night.
>
>The good news is that my genmenux problem is sorted.
>
>The bad news is that the resultant compiled exes are no more stable than before.
>
>The worst news is that whereas the problem was only happening on my clients' machines it is now also happening on mine!
>
>Now that is stretching it!
>
>Having just done my fifth reboot of the afternoon, I'd be grateful for any further insights.
>
>All I can tell you is that the program is stable enough till you try to come out of it. Then, with 100% consistency (so far) it causes a major windows crash with an error message on the infamous blue screen along the lines of 'this application has caused a fatal error at 0E (or sometimes 0C if that helps) at a variety of addresses. we then have to do a complete cold reboot to recover.
>

You may have a problem with the version of DCOM installed on your system; if the registry entry HKEY_LOCAL_MACHINE\Software|Microsoft\OLE isn't present, you need to take the appropriate steps to install DCOM on your system, as I've outlined in the FAQ here on UT, and as discussed in an MSKB article based on the FAQ entry here.

If you uninstalled VS6 under NT, where you had installed any Service Packs subsequent to the initial VS6 install, you'll probably have to reapply the NT Service Pack, since uninstalling VS6 may have resulted in restoring an older version of a shared component updated by both VS and the Service Pack. I'd advise installing NT SP5 if you can, and if IE5 is installed, make certain that version 5.00.2314.1003 is installed.