Visual Studio

Version 6.0 (codenamed Aspen, after the ski resort in Colorado), was released in June 1998 and is the last version to run on the Windows 9x platform. Each version of each language in part also settled to v6.0, including Visual J++ which was prior v1.1, and Visual InterDev at the 1st release. The v6 edition of Microsoft was the core environment for the next four releases to provide programmers with an integrated look-alike platform. This led Microsoft to transition the development on the platform independent .NET Framework.

Visual Studio 6.0 did not include Visual J++, which Microsoft removed as part of a settlement with Sun Microsystems that required Microsoft Internet Explorer to not provide support for the Java Virtual Machine Environment.

Visual Studio 6.0 came in two editions: Professional and Enterprise. The Enterprise edition contained extra features not found in Professional edition, including:

  • Application Performance Explorer
  • Automation Manager
  • Microsoft Visual Modeler
  • RemAuto Connection Manager
  • Visual Studio Analyzer

The product was released 1998-06.

Application Details:

Version: 1998 (6.0)
License: Retail
Votes: 0
Latest Rating: Silver
Latest Wine Version Tested: 6.22-staging

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Install MS Java VM Install from ACMSETUP Visual Basic 6.0 Enterprise IDE Visual C++ Enterprise IDE

What does not

Install from SETUP.EXE ActiveX controls in VB6


What was not tested

VC++6 Compile, debug and run. Visual FoxPro Visual SourceSafe Visual InterDev

Hardware tested


  • GPU:
  • Driver:

Additional Comments

Change Windows Version to "Windows 98" Begin "[cd]:\SETUP.EXE", install MS-JavaVM, then wait until "winevdm.exe" crash. Copy "[cd]:\SETUP\*" to "[cd]:\" and launch: "[cd]:\ACMSETUP.EXE /Z BBOARD.DLL /T VS98ENT.STF" Install works fine from here... at the end, setup ask for restart, even if you click "Restart now" the setup return a error, then you need to exit without restart and run wineboot. Then the VB6 IDE and VC++6 IDE works. Done without any winetricks in a blank wineprefix.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowOracle Linux 8Nov 25 20216.22-stagingYes Yes NoSilverBenjamin Shefte 
CurrentSlackware 14.1 32 bit versionJun 15 20141.7.20Yes Yes Bronzean anonymous user 
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)Mar 11 20131.5.25Yes Yes GoldLong Haul 
ShowLinux Mint 12 "Lisa"Apr 13 20121.4-rc4Yes Yes Goldan anonymous user 
ShowUbuntu 10.04 "Lucid" i386 (+ variants like Kubuntu)Jan 24 20111.2.2Yes Yes SilverChristian Blackburn 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes


­Make sure you operate on a clean 32-bit WINEPREFIX (~/.wine)!

Prerequisite installation by using 'winetricks' script

Winetricks will take care of all needed installation prerequisites and work around some problems. Follow the instructions in the link to install it.

$ bash winetricks -q vcrun6 mfc40

Install steps to work around some bugs

After winetricks step start "winecfg" tool and select "Windows 98"­ from Windows Version Listbox.

Press "Apply" button. Press "Ok" button.

After the installation is finished, change the Windows version back to default (Windows XP).

/home/yourlogin/.wine is not owned by you / (Permission denied)

Never run wine as root (su, sudo)! Wine doesn't require to be run as root!

You will screw your WINEPREFIX and possibly other things up. If you have run Wine as root you need to:

$ sudo rm -rf ~/.wine

and then run winecfg to set Wine folder structure back up. If you used winetricks script as root you might also need to:

$ sudo rm -rf ~/.cache/winetricks/

Again: Just run wine as regular user and all should be fine.

Installing with Wine Windows versions set to NT4/2K/XP

Because bug 5322 will probably stand a long time, I present another method.

1.) Save the following snippet to a text file, for example "vc6-installer-fix":

set $x=0x410000
set $end=0x420000
while(*++$x != 0x07B0B18B && $x < $end)
if $x != $end
   set *(int*) $x = 0x5BC0335E
   set *(int*)($x+4) = 0x900004C2

2.) Run the following command, assuming you saved the snippet to "vc6-installer-fix":

$ winedbg --gdb setup.exe < vc6-installer-fix

NOTE: If the installer spawns a sub-installer that crashes due to this bug, you must first run the main installer and then attach to sub-installer with debugger.

This can be done in automated way (assuming the main installer has already started sub-installer):

$ winedbg --gdb $(( 16#$(winedbg --command "info proc" | grep your-sub-installer-process-name | cut -f 2 -d " ") )) < vc6-installer-fix

It tells winedbg to query process ids, filters out the target process, converts the PID to decimal and then starts winedbg in gdb proxy mode, attaching to target process and executing patch script.

This should work for all VC6 installers and even Embedded Visual C++ 4.x ones.

What does it do?

Basically it starts the installer under control of a debugger and the works around bug 5322 by in-memory patching execution flow.

NOTE: This method is not recommended for the average user!