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.
What does not
What was not tested
I have run on a terminal window: export WINEARCH=win32 export WINEPREFIX=~/.local/share/wineprefixes/msvs60a cd ~ pmount /dev/sr0 wineboot --init winetricks cmd (workaround of bug 5322, works with "luck" of 95% on my PC, I don't know why!) winecfg (only to remove drive Z:=/ to speed up installation) cd /media/sr0/ wine SETUP.EXE FoxPro & Studio Analyzer must be unselected for a successful installation. FoxPro can be installed later using: winetricks mfc40 wine uninstaller Bugs: Can't select installation options using the mouse. Keyboard works using Tab, Up, Down an Spacebar. On file transfer, a unharmful MessageBox with the text "RemoveFontResource failed" stops the operation. Close the box using the OK button to continue. On VC++ startup, a MessageBox with the text "An incorrect version of MSVCRT.DLL is currently installed. You must run Setup again to install the correct DLL." appears. Fixed using: wine cmd cd /D C:\WINDOWS\SYSTEM32 del MSVCRT.DLL exit VB crash on building. Fixed using: wine cmd cd /D C:\WINDOWS\SYSTEM32 regsvr32 MSSTDFMT.DLL exit
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Slackware 14.1 32 bit version||Jun 15 2014||1.7.20||Yes||Yes||Bronze||an anonymous user|
|Current||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Mar 11 2013||1.5.25||Yes||Yes||Gold||Long Haul|
|Show||Linux Mint 12 "Lisa"||Apr 13 2012||1.4-rc4||Yes||Yes||Gold||an anonymous user|
|Show||Ubuntu 10.04 "Lucid" i386 (+ variants like Kubuntu)||Jan 24 2011||1.2.2||Yes||Yes||Silver||Christian Blackburn|
|Show||Ubuntu 9.04 "Jaunty" i386 (+ variants like Kubuntu)||Oct 13 2009||1.1.31||Yes||Yes||Gold||Lynxy|
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.
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:
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!