I was speaking of the IDE's themselves and yes, the executables do seem to run fine. There seems to be a lot of VB6 IDE experience on Win7, but not much VB3 or VB4. These are my problems with the IDE's so far, in case anyone has overcome them.
VB3 - Installed OK and I used compatibility settings of Win XP SP2 and As Administrator as mentioned in a lot of posts I've seen. When I run the IDE (same compat), open a project I previously created in VB3 on an older PC and then try to create the EXE, it blows up with error "VB caused an access violation in ntdll.dll". And when I click Ignore on this, it blows again with "NTVDM has stopped".
VB4 - Installed OK with same compatibility settings as above, but setup ended with error "Could not remove <path>vb4setup.ttf" - no big deal, I guess, and you can physically go and delete it yourself afterwards. Also, if no Win XP SP2 compat, OLEPRO will abend when you run the IDE. Then when I open the same old VB3 project as above, it tells me it can't find the associated .VBX files, which is understandable because VB4 replaced this with corresponding .OCX files. VB4 is supposed to present the option to convert these vbx's with the ocx counterparts. What is really weird is that, in one of my hundreds of install/run tests, I once received an option the did automatically change over from vbx to ocx, although I swear this happened during installation, but maybe it was when I opened the old project (otherwise how would it know there was any vbx around, unless it was programmed to assume the possibility). Even in this case, I blew up with VB32.exe APPCRASH at stackhash_a021 (if I can read my writing from the notes I took).
I appreciate any suggestions to overcome the problems.
