>>One other (probably rare, but it happened to me) possibility,
>>solved for me by an MS techie, was that when I built my distribution I had an anti-virus scanner running that caused a foul-up in the build. Once I disabled the av program, all was well. MS says try your build with nothing else running, if you're at your wits end, as I was.
>>Just thought I'd mention this albeit remote possibility...
>
>Thanks for the tip about anti-virus scanner. In this case I am not running one. I am developing with Win95, since I had heard that this was the best platform to develop on for going either up to NT or down to Win 3.1 systems. I am hearing that I need to uninstall Win31s "manually" before installing. I am wondering if this also applies for installing the runtime version (EXE w/ESL file) of a program?
>
>Thanks,

No, no trouble with EXE/ESL. Win32 causes all the grief. I personally didn't need to do uninstalls (and didn't dare to, since users had other 32-bit apps installed). I did have 3D missing on some 3.1 machines evidently due to Win32 file conflicts (or that's my guess), but they all installed OK once I got past that anti-virus thing. Can you test your install on a 3.1 PC that's never had Win32 on it? That might narrow down the problem...