WineHQ
Visual Studio 1998 (6.0)



Category: Main > Programming / Software Engineering > Visual Studio > 1998 (6.0)


NameVisual Studio
Version1998 (6.0)
License Retail
URLhttp://www.visualstudio.net
Votes  
RatingGold
Wine Version1.5.25
Maintainers of this version:
Description

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.

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)

What works

  • Installing Visual Studio
  • Running VB6/VC6
  • Compiling simplest applications and running them in WINE/native Windows


What does not

  • Installing the MSDN - it kept up saying it couldn't find some file
  • Every project that involves extra components (like CommonControls or other ActiveX stuff) - it fails with "Not enough memory"


What was not tested

  • Every other component of VS6 except Visual Basic and Visual C++


Additional Comments

Use Windows ME in winecfg while installing - 2000/98 do *not* work

Ignore the DCOM98 warning - you're perfect without it.
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)Mar 11 20131.5.25 Yes Yes Gold Long Haul 
ShowLinux Mint 12 "Lisa"Apr 13 20121.4-rc4 Yes Yes Gold an anonymous user 
ShowUbuntu 10.04 "Lucid" i386 (+ variants like Kubuntu)Jan 24 20111.2.2 Yes Yes Silver Christian Blackburn 
ShowUbuntu 9.04 "Jaunty" i386 (+ variants like Kubuntu)Oct 13 20091.1.31 Yes Yes Gold Lynxy 
ShowDebian GNU/Linux 5.0 "Lenny"Jun 10 20081.0-rc2 Yes No Garbage an anonymous user 


Known bugs
Bug # Description Status Resolution Other apps affected
33037 Visual Studio 6 can't be installed with WinVer >= Win2K (missing HKEY_PERFORMANCE_DATA 230, process object) NEW View

 
HOWTO

­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.

$ wget http://kegel.com/wine/winetricks­­
$ 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).­


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

­Because bug 5322 will proba­bly 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)
end
if $x != $end
   set *(int*) $x = 0x5BC0335E
   set *(int*)($x+4) = 0x900004C2
end
cont

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!


 
/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 thi­ngs 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 ~/winetrickscache

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

­­

 

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

MSDN Installation
by Long Haul on Monday March 11th 2013, 17:07
Install MSDN on the VS6 wineprefix. When the installation program finish, copy hhctrl.ocx from Windows XP to your wineprefix system32 directory. Override hhctrl.ocx with "native,builtin", then MSDN will run normally. To enable the index, install ie7 using winetricks & copy itircl.dll from Windows XP to your wineprefix system32 directory.

[post new] [reply to this]




   << Back

Page loaded in 0.08343 seconds.