Just installed VB6 on Windows 7 and not in VM and everything works fine. I had a few OCX problems at first but after registering them manually no more errors and it runs my old programs. As long as you install as the administrator user and right lick run as administrator to install it should install just fine. If you have installed with out doing that just log in as the administrator user and register manually the dll or ocx in CMD that where causing the problems.

It took a little time for it to do it's thing, but after I changed the compatibility mode on ACMBoot.exe and Setup.exe to Windows XP service pack 2, it installed just fine, Right click on the two exe's and go to properties, select the compatibility mode tab at the top, then check the "Run this program in compatibility mode for:", then select windows XP service pack 2 from the drop down box below it. run Setup.exe, it should install

If you have the HD space a dual boot XP/W7 configuration will give you the best of both worlds.

Rather than download the sizable installer to create a virtual "fake" XP within Windows 7 (W7) I configured a dual boot XP/W7 system and run all my "old stuff" including Visual Studio 6 on the XP side.

Visual Studio 6 is the most useful of the Microsoft Visual Studio suites to date seeing that most people are running legacy operating systems (XP & earlier.....Vista like ME before it was a total flop) .....no need for the user to install separate ".NET framework" runtimes to run your programs.

I'm really liking W7 so far........it seems to be a more efficient manager of memory & multi processor/core systems than XP was.

I'm running W7 Professional in my dual core (Intel) notebook & W7 Ultimate in my desktop which has two physical dual core (Intel) processors.

If you're running a post 2007 Toshiba laptop like I am you can download a software installer from the Toshiba website that will install suitable W7 device drivers.

I have installed vb6 WITH sp6 onto virtual XP and it worked fine. I agree with most that you have to "trick" 7 into thinking that you are running XP, it will respond to your application, only with SP6. Some API's still bombs, look at the install you had to go through with Vista, this will solve all your problems. Now what happened to that link again???? Search google and find vista/vb6...

I have an MSDN Pro subscription for VS2008. As part of that I am able to download VB6 enterprise from MS (not Visual Studio - just VB6) as an .iso.
After an initial compatibility warning the MSDN VB6 installs cleanly with no problems on Windows 7 (Ultimate x64). Does not try to install the Ms JVM and goes entirely without a hitch. The MSDN library for Oct 2001 (also from MS as MSDN subscription) installs as part of the process. (Did not install SS or Ent features as prev version was Pro).
Must run VB6.exe as administrator (add property to shortcut) to avoid registry accessing error on loading existing projects.
VS6 appears to have many setup issues which appear not to exist in the MS VB6 Ent .iso. Maybe a friendly MS person might provide a copy for Win 7 in lieu of a problematic VS6.

One major problem is structural. MDAC has changed and VB6 wants it like it used to be. They claim that happened in XP SP2. There is no hope for installing it native on Win7 (Vista in new clothes).

My VB6 install and projects reference only MDAC 3.6 which I believe is supported on Win7 and Vista. (Have istalled VS6 SP6) Found the following on Microsoft discussion forums under "Dao350.dll unsupported under Windows 7" in General Discussion at the following link which goes into significant detail -
http://www.microsoft.com/communities...r=US&sloc=&p=1
I am supporting some legacy sites currently running XP workstations but which may over time replace their existing PC's with Win7 PC's. If there is going to be an issue it would be nice to resolve it now rather than when it hits the fan.