I was recently requested to debug a pre-.NET application Visual Basic, so I had to set up the environment for Windows 98 development… but nowdays all that software is deprecated and has no support. This is what I learned from my experience to get it up and running, but in case you can make a choice, I’d recommend you to rewrite the code in .NET, as this kind of DLL code relies platform, and things have changed a lot in 20 years.
Be careful to avoid deleting the recent Visual Studio versions, as they may have similar paths.
- The Visual Studio 6.0 files are by default under
C:\Program Files (x86)in 64 bits systems.
C:\Program Files (x86)\Microsoft Visual Studio\Common C:\Program Files (x86)\Microsoft Visual Studio\MSDN C:\Program Files (x86)\Microsoft Visual Studio\MSDN98 C:\Program Files (x86)\Microsoft Visual Studio\VB98 C:\Program Files (x86)\Microsoft Visual Studio\VC98 C:\Program Files (x86)\Microsoft Visual Studio\*.HTM C:\Program Files (x86)\Microsoft Visual Studio\*.TXT C:\Program Files (x86)\Common Files\Microsoft Shared\MSDesigners98 C:\Program Files (x86)\Common Files\Microsoft Shared\MSDN C:\Program Files (x86)\Common Files\Microsoft Shared\VS98 C:\Program Files (x86)\Common Files\Microsoft Shared\Wizards98
- Clean up the Windows registry entrys: run
regedit.exeand delete the following keys if they exist.
HKEY_LOCAL_MACHINE\Software\Microsoft\DevStudio HKEY_LOCAL_MACHINE\Software\Microsoft\HTML Help Collections HKEY_LOCAL_MACHINE\Software\Microsoft\MSVSDG HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Basic\6.0 HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Component Manager HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Modeler HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\6.0 HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\DevStudio HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\HTML Help Collections HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\MSVSDG HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Basic\6.0 HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Component Manager HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Modeler HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\VisualStudio\6.0 HKEY_CURRENT_USER\Software\Microsoft\DevStudio HKEY_CURRENT_USER\Software\Microsoft\MSVSDG HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\6.0 HKEY_CURRENT_USER\Software\Microsoft\Visual Modeler HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\6.0
First of all you will need a copy of the Visual Studio installer in your hard drive. Icopied the content of an old college licensed CD into a folder, and proceeded to edit.
SETUPWIZ.INIwith a text editor (e.g. Notepad++), and replace
VmPath=ie4\msjavx86.exe, which tries to install a really old Java implementation and makes the installation process fail, with an empty va. So the first part of the file should look like this:
[setup wizard] eula = eula.txt NTSP = NTsp3\nt4sp3_i.exe NTSpMinVer = 3 IE4 = ie4\ie4setup.exe CommonFilesMin = 50 IEIni=ie4check.ini WFCClean = setup\wfcclean.exe readme = readmevs.htm pid = setup.ini MSDN = setup.exe Acme = acmboot.exe AcmeId = vs98ecd1.inf STF = setup\vs98ent.stf DCOM98 = dcom98\dcom98.exe MSDNID = msdn3?1.inf NtSpUrl = ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/ IeUrl = http://www.microsoft.com/ie/ie40/download/ UsrUrl = http://msdn.microsoft.com/vstudio/register/default.htm RegUrl = http://www.microsoft.com/isapi/redir.dll?Prd=vstudio&Pver=98&Ar=register VmPath=
You must also edit the
SETUP.EXEproperties. Go to the context menu of the file (right click as default), select properties, and got to the ‘compatibility’ tab. Check that you have selected:
- Compatibility mode: execute as 'Windows XP (Service Pack 3)'.
- Configuration: 'execute this program as administrator'.
- Open the context menu of
SETUP.EXEand choose 'run as administrator'.
- Don’t install 'Source Safe', as it fails.
- When we get to 'choose the installation mode select 'Custom'. Then follow these steps:
Do not install (as they fail):
- Microsoft Visual FoxPro 6.0
- Microsoft Visual InterDev 6.0
- Microsoft Visual SourceDafe 6.0
- ActiveX (obsolete version, generates conflict with the current version)
- Install the unicode libraries: from the custom main menu, select the text 'Microsoft Visual C++ 6.0', and the button 'Change option' on the right side will be set as active. Click on it and follow a similar process for 'VC++ MFC and Template Libraries' and 'MS Foundation Class Libraries'. Finally select all these options:
- Static libraries
- Shared libraries
- Static libraries for Unicode
- Shared libraries for Unicode
- Browser database
- Source code
- Install the database: from the main 'Custom' menu, click on the 'Data Access' text , and the button 'Change option' on the right side will be set as active. Click on it and make sure that 'ADO, RDS and OLE DB Providers' is not selected. You will get a warning message saying that this component is esential for the application, but you should ignore it, as it will crash on Windows 10. Do select only the following options:
- Microsoft ODBC Drivers
- Remote Data Objects and Controls
- Data environment
- Install the tools: from the main 'Custom' menu, click on the 'Enterprise Tools' text, and the button 'Change option' on the right side will be set as active. Check that 'Visual Studio Analyzer' is not selected. Therefore, select only:
- Aplication Performance Explorer
- Visual Component Manager
- Visual Basic Enterprise Components
- VC++ Enterprise Tools
- Microsoft Visual Modeler
- As the last step, before pressing on 'Finish', do not let the program configure the environment vars.
- If you have waited more than 5 minutes and the program is still ‘configuring the system’, you can assume something has gone wrong and the install has been frozen somewhere. Cancel it, clean up (see the first section on top of this post) and start all over again, reading carefully the steps.
- If there is an error message about the Java machine you can ignore it. At that point you should be able by then to run 'Visual Basic' without the MSDN help package, so you get the bare bones yet fully functional experience.
Run it always in administrator mode (right click on Visual Basic 6.0, and select 'run as administrator'). Then, here it is, ready to run and debug ancient DLLs.
❗️ If you want it the program to run using a Microsoft Office 2010 instance, you will need to load some dependencies. Go to ‘Project/References’ and select:
- Visual Basic for Applications
- Visual Basic runtime objects and procedures
- Visual Basic objects and procedures
- OLE Automation
- Microsoft Excel 15.0 Object Library
- Microsoft Word 15.0 Object Library