New features in eVC++ 4.0 (since
Start of installation up to the point where it goes to install the Platform Manager
What does not
Everthing, installation crashes when installing the platform manager
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||NixOS 21.03||Dec 25 2020||6.0-rc2-staging||Yes||No||No||Garbage||Stekke|
|Show||Arch Linux x86_64||Jun 15 2016||1.9.12||No||Not installable||Garbage||an anonymous user|
|Show||Gentoo Linux||Nov 08 2008||1.1.8||No||Not installable||Garbage||an anonymous user|
|Current||openSUSE 10.3||Aug 02 2008||1.1.2||No||Not installable||Garbage||an anonymous user|
|Show||Ubuntu 7.10 "Gutsy" i386 (+ variants like Kubuntu)||Feb 24 2008||0.9.55.||No||Not installable||Garbage||an anonymous user|
Â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":Â
while(*++$x != 0x07B0B18B && $x < $end)
if $x != $end
set *(int*) $x = 0x5BC0335E
set *(int*)($x+4) = 0x900004C2
handle SIGSEGV pass nostop noprint
handle SIGTRAP nopass nostop noprint
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!Â
Note: Use the following CD key when installing this software: TRT7H-KD36T-FRH8D-6QH8P-VFJHQ
(from Microsoft Download page)
Due to bugs in installer you might need to correct the "folder for common files" name: "C:\Windows CE Tools