I had a VB6 application setup file that was working perfectly on Windows Server 2003 32-bit OS.
Now the customer has moved to Windows Server 2012 64-bit on Intel Xeon CPU E5 which is x64-based processor.
The installer gives the error:
Setup Bootstrap for Visual Basic Setup Toolkit has stopped working
The error occurs when the installer is Copying Files and Processing VB6STKIT.DLL
What is the solution?
Related
I'm facing the following issue:
Background
I have a Win32 legacy application (exe & dll's) and drivers (dll's) written on Visual Studio 6.0 that used to run
well in Debug version on Windows Xp (Please Note: We need it in DEBUG configuration & not Release).
I copy the Visual studio 6.0's msvc* type dll's, MFC dll's & manifest files along with the exe to make it run.
Issue:
The same legacy 32-bit application & driver dll's have now been newly compiled in Visual Studio 2008 DEBUG mode.
It is then copied to a PC running on 64-bit Windows 10 PC (also tried Windows 7 without success) without having VS2008
installed. I copy the VS2008's msvc* type dll's (msvcp90d.dll, msvcr90d.dll), MFC dll's and manifest file (Microsoft.VC90.DebugCRT.manifest) also along with the exe.
On launching this debug version of the application (it does many initialization activities on startup and also calls the init methods of driver dll's) it crashes on starting up both on a 64-bit Windows 10 & Windows 7 PC.
What works:
When VS2008 is installed on the Windows 10 PC, the application's debug version launches correctly without crash and works fine.
(Also please note that same application's Debug build using the old Visual Studio 6.0 works fine on Windows 10).
What DOESN'T work:
When VS2008 is NOT installed on a Windows 10 PC, the application's debug version crashes while it is being launched.
Requirement
We absolutely need the DEBUG configuration of the application to run on the Windows 10 PC.
Development environment
OS for development: 64-bit Windows 7
Target OS: 64-bit Windows 10
IDE: Visual Studio 2008 SP1
Application & driver dlls/exe's: 32-bit
I have tried many workarounds like building by using 32-bit paths in VS2008 ($\Program Files (x86)\Microsoft SDKs\Windows..),
installed redistributables of VS2008 (both x86 & x64),
running as 'Administrator' user,
running in compatibility mode (Win Xp..),
copying dll's from system32 folder of a PC having VS2008 installed to a PC without VS2008 etc.. but the Debug build always crashes on it's startup.
Any help or pointers would be appreciated.
Please let me know if you would like to have further details.
Thank you in advance.
I've installed VS 2017 on Windows 7 machine and built the C++ project targeting 8.1 SDK, but the binaries are not starting on windows 7. The same works on Windows server 2016 and Windows 10 OS.
I had checked VC 2015 runtime is installed on both the windows server and windows 7 machine. And windows 8.1 SDK (as part of VS 2015?) is installed on my local machine running on Windows 7. Previously, I had Visual studio 2015 installed and the binaries used to work fine both on windows 7 and windows server.
I am not sure if the runtime dlls in windows\system32 are corrupted or changed due to VS 2017 installation.
PS: I noticed the same issue of exe not starting when running the newly installed firefox which comes with C-runtime dlls packed.
The problem turned out to be due to the use of the instruction set (AVX2) used by the dependency project, that wasn't available in the windows machine.
I have the 32-bit version of Windows 10. I have installed Visual Studio 2013 Ultimate, but I am unable to find the emulator for Windows Phone.
How can I test my application?
The Windows Phone SDK uses Hyper-V, which requires a 64-bit platform for the host.
See below for an excerpt. Note the requirements listed under Operating System.
System requirements for the emulator for Windows Phone 8
Your computer must meet the following requirements:
BIOS
In the BIOS, the following features must be supported:
Hardware-assisted virtualization.
Second Level Address Translation (SLAT).
Hardware-based Data Execution Prevention (DEP).
RAM
4 GB or more.
Operating system
Windows 8
64-bit
Pro edition or higher
Source: MSDN
Notice Regarding Universal Apps (UWP)
Universal Apps targeting Windows 10 can be created and tested on a 32-bit (x86) platform, but you will be unable to build and test applications for 64-bit (x64) and ARM platforms.
Source: MSDN
I am running VMWare 7 + Visual Studio 2010 on Windows 7 ultimate x64 as a host and Windows XP SP3 32bit as a guest on i7-3610qm. But when attempt to run record/replay function VMWare says that I have unsupported processor, but in the VMWare manual there is said that record/replay should be working on Intel pentium 4 and newer.
I was thinking of changing some settings in BIOS but which ones? Any ideas? Or alternative VM software with function record/replay?
I'm about to take the plunge and build a PC, and it will probably be 64-bit, which will use 64-bit VISTA, I suppose, since Windows 7 isn't out yet.
I'm a Visual Studio 2008 developer; will I need new versions of the software? I run the 32-bit versions on XP right now and deploy to a 64-bit Windows 2003 server that runs IIS in 32-bit mode.
Visual Studio 2008 only has a 32-bit version. This runs fine on Vista x64 and Win7 x64 though.