WineHQ

Embedded Visual C++

No Screenshot

Submit Screenshot

New features in eVC++ 4.0 (since eVC++ 3.0)

  • Improved emulator
    • Greater fidelity to device OS image
    • ActiveSync connections (via network virtual switch)
  • Improved Debugging
    • Attach to running process
    • JIT attach to hung process
C++ Enhancements 
  • C++ structured exception handling
    • try
    • catch
    • throw
  • Runtime Type Information (RTTI)
  • Standard Template Library (STL)
Remote Tools 
  • Remote Spy++
  • Remote Registry Editor
  • Remote Heap Walker
  • Remote Process Viewer
  • Remote Zoomin
  • Remote File Viewer
  • Remote Call Profiler
    • “Testing Real-Time Systems in Windows CE .NET” by Mike Hall and Steve Maillet
  • Remote Kernel Tracker
    • Processes
    • Threads
    • Interrupts
  • Remote Performance Monitor
    • Graphical display with continual monitoring
    • Tracks: CPU usage, threads, processes, memory, network traffic, battery, among other values
  • Remote System Information
    • Snapshot of system state
    • Shows: OS version, CPU info, OEM code page, memory, power state, object store usage, active devices (COM1:, COM2:, etc.), user-interface colors, system metrics

Application Details:

Version: 4.0
License: Free to use
URL: http://msdn.microsoft.com/en-u...
Votes: 0
Latest Rating: Garbage
Latest Wine Version Tested: 6.0-rc2-staging

Maintainers: About Maintainership

No maintainers. Volunteer today!

Free Download eMbedded Visual C++ 4.0 Free Download eMbedded Visual C++ 4.0 SP4

Test Results

Selected Test Results

What works

The installer for EVC++ 4.0 can install without problems. Please see the extra comments for workaround for the SP4 installer.

Installation steps:

  1. Use wine 6 or newer, 5 is broken, between 4.20 and 5 might work but at least need hack for the installer
  2. Start with a clean wine prefix
  3. Use winecfg to set windows version to windows 2000
  4. Make sure you have a version of winetricks that includes the following fix: https://github.com/Winetricks/...
  5. Run winetricks -q mfc42 corefonts courier arial tahoma
  6. Run winetricks -q jet40
  7. Run winetricks -q art2kmin

At this point the install for eVC++ should just work.


What does not

Running EVC.EXE , it complains about missing SDK at startup even when SDK's are installed.

Workarounds

What was not tested

Any IDE functionality, given that it refuses to start up.

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

The installer for SP4 does not install, but neither does it install on modern MS Windows.

To get SP4 to install (both on wine and MS Windows) you need to unpack the official installer and then replace the file "eVC4SP4" with: https://archive.org/details/eV...

Also note that this software can't be used without installing an SDK. These are typically provided by your embedded board manufacturer.

However MS offers a standard SDK here: https://www.microsoft.com/en-u...


selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentNixOS 21.03Dec 25 20206.0-rc2-stagingYes No NoGarbageStekke 
ShowArch Linux x86_64Jun 15 20161.9.12No Not installable Garbagean anonymous user 
ShowGentoo LinuxNov 08 20081.1.8No Not installable Garbagean anonymous user 
ShowopenSUSE 10.3Aug 02 20081.1.2No Not installable Garbagean anonymous user 
ShowUbuntu 7.10 "Gutsy" i386 (+ variants like Kubuntu)Feb 24 20080.9.55.No Not installable Garbagean anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

HOWTO

­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
handle SIGSEGV pass nostop noprint
handle SIGTRAP nopass nostop noprint
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!

­
Additional installation hints

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"

Comments

Comments Disabled

Comments for this application have been disabled because there are no maintainers.
Back