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:
The product was released 1998-06.
Application Details:
| Version: | 1998 (6.0) |
| License: | Retail |
| URL: | http://www.visualstudio.net |
| Votes: | 0 |
| Latest Rating: | Silver |
| Latest Wine Version Tested: | 6.22-staging |
Maintainers: About Maintainership
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
Workarounds
What was not tested
VC++6 Compile, debug and run. Visual FoxPro Visual SourceSafe Visual InterDev
Hardware tested
Graphics:
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.
| Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
| Show | Oracle Linux 8 | Nov 25 2021 | 6.22-staging | Yes | Yes | No | Silver | Benjamin Shefte | |
| Current | Slackware 14.1 32 bit version | Jun 15 2014 | 1.7.20 | Yes | Yes | No | Bronze | an anonymous user | |
| Show | Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu) | Mar 11 2013 | 1.5.25 | Yes | Yes | No | Gold | Long Haul | |
| Show | Linux Mint 12 "Lisa" | Apr 13 2012 | 1.4-rc4 | Yes | Yes | No | Gold | an anonymous user | |
| Show | Ubuntu 10.04 "Lucid" i386 (+ variants like Kubuntu) | Jan 24 2011 | 1.2.2 | Yes | Yes | No | Silver | Christian Blackburn |
| Bug # | Description | Status | Resolution | Other apps affected |
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.
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).
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:
and then run winecfg to set Wine folder structure back up. If you used winetricks script as root you might also need to:
Again: Just run wine as regular user and all should be fine.
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":
2.) Run the following command, assuming you saved the snippet to "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):
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!
