Microsoft eMbedded Visual C++ 4.0 Windows 11 Error

I got an error after running the main installer on Windows 11

What is line 40 in said .reg file?

Set OS = platman.GetOS("wce400")
Also, aside - EVC4 seems to have some kind of 16bit component in the installer - when I tried installing EVC4 on Windows 10 x86, it prompted me to install NTVDM

Obviously, 64bit wouldn't have NTVDM - so I need to figure out what that component was. I think that's the one causing the error we talked about + the issue I'm having installing EVC4 SP4 on Windows 11 x64

@watamario15 mentioned only getting EVC4 SP3 to install on Windows 10/11. I'm assuming he had x64 - so I think there's some 16bit installer that the initial EVC4 install that's causing issues with patching.

Okay, here's what I've figured out:
On x64 Windows 11
EVT3 with no SDKs installed other than default HPC Pro SDK seems to work fine on Windows 11 x64
^Haven't tried HPC2k, CE2.12, or CE2.0 SDKs
EVC4 and CE4.0 SDK install / work fine on Windows 11 x64, but SP4 does not work (presumably SP3 does but I haven't tried) the EVC4 setup tries to install CE Platform Manager + some kind of driver which I believe is the 16 bit component of the installer
^I have noticed that the programs can be unstable at times though
On x86 Windows 10:
EVT3 with all of the SDKs seem to install right (CE2.0,CE2.11,CE3.0,CE2.12), SDKs register correctly + show up in Project Config (Even HPC2.0!), but the program crashes upon loading a project file and also the "New Project Screen" crashes
Here's the result


^The one fail I did do was install EVT3+EVC4 on the same computer
I'll do a factory reset for the PC and try EVT3 only with all SDKs - perhaps installing EVT3/EVC4 both caused the issue
It's a pain to get Windows 2000 / XP on this computer I have so I want to try one last time to get Windows 10 working

It won't be a 16-bit driver on NT4/2000. It doesn't support them. At worst it is a command line DOS executable.

Did it install to c:\program files or c:\program files (x86)?

Did you try running it in compatibility mode?

I'm focused on x86 Windows 10, so it was c:\program files
I gave up on x64 installs of the CE tools
Windows 10 x86 install stopped booting - the repair automatically uninstalled programs to "help" the PC boot - but subsequently - EVC3 no longer started up.

I'm going to try one last time - doing a clean install Windows 10 x86 - BUT NO EVC4 install - just EVT3 - and I'll do some rebooting in between the SDK installs and report back

Okay, you knew this but:
DO NOT INSTALL EVT3/EVC4 on the same Windows Install! That's what caused all of my issues.

Test results:
Windows 10 x86 - English
EVT3 with HPC Pro, HPC 2000, Windows CE 2.12, and HPC 2.0 Integration all working correctly!
Had to make sure "C:\Windows CE Tools "was the directory - Windows 10 seem to add some garbled characters after Windows CE Tools, which I removed
Windows 10 x86 - Japanese
EVC4 with Windows CE 4.0, 4.2, 5.0 SDKs all working correctly

Windows 11 x64 - English
EVT3 with HPC Pro, HPC 2000, Windows CE 2.12 SDKs working correctly
EDIT: HPC 2.0 SDK ALSO working correctly. I attached my modified .reg file that worked
^HPC 2.0 SDK does install correctly along but the registry doesn't seem to take even though the registry key- it saves successfully
HPC 2.0 does not show up in the build configuration

On Windows 11 x64, I modified the SDK/EVC installs so they're not in Program Files x86, they're in Program Files proper in case of path issues.
That said, I don't know if the registry somehow maps differently for x86 vs x64.

We know the registry set works on Windows 10 x86 at least.

Is there an easy way to compare the registry key with the certain directories to see if WOW64 modified them somehow, or the registry itself?
EDIT: Yes registry does map differently, I changed the files to include WOW6432Node in all of the paths and it works now the CE2.0 SDK


Edited by torch 2024-04-25 7:24 AM




Attachments
----------------
200-eVC-integration-x64-WOW6432Node.reg (113KB - 1 downloads)

It would be the paths, one of the problems with CE Platform Manager is that it uses hard coded paths all over the place. It's why I tell people to never change the install path for any of the CE Dev Tools. If you do, they won't work.

So another update for Windows 11 x64
all of the EVT3 SDKs work + including Windows CE 2.0 using my hacked regkey

BUT - do not install the PPC2002 SDK - that seems to screw everything up and introduce crashing.

Windows 11 likes to make the Windows CE Tools directory have "Windows CE Tools(x86" so I clip it to be Windows CE Tools.

Overall, I'm super happy everything is set up.

Does your H/PC 2.0 Integration package work with the PSPC 1.0 SDK? Obviously, that's outside the scope of this website. I'm not asking you to do/work on it. But if you show me where to go, maybe I can figure it out.

I have literally no clue, but as it is newer than the H/PC 2.0 SDK, I imagine that it will port over if you replicate the mod.

Sounds good! I don't mind putting in the work to test it out.

A few more questions:

1-Do you know where to locate the PSPC SDK 1.0? or the original website for that
^I doubt there's a JP version, but I just wanted to see what I could locate
2-Is there a way to "explode" the PSPC SDK setup, meaning, see what registry entries it uses - so I can use the H/PC 2.0 Mod as a basis to see if I can replicate it for the PSPC setup and compare to the registry entries you made for HPC 2.0 versus PSPC 1.0
3-Can I add the x64 regedit file I made to the H/PC Integration Mod 2.0 in the DLC?
^I don't want to make it confusing for users, but it is working all good for me!
But the H/PC 2.0 SDK needs to not be in Program Files x86, just in Program Files normal

1. there was never a web release for it, I'll PM you
2. yes, but it's all installshield encoded
3. yes, add a clear description for WOW users and what OS's need which reg file (XP x64, Vista 64, 7 x64, 8 x64, 8.1 x64, 10 x64, 11)

C:Amie and I have been PM'ing - but wanted to follow up with test results:

The Palm Size PC 1.0 SDK does install/register/compile code correctly after following this BUT USING MY x64 REGKEY earlier in the thread in place of the CESD article:
https://www.hpcfactor.com/support/cesd/200270/compiling_for_windows_ce_20_using_embedded_visual_c_30/
BUT only installing to C:\Windows CE Tools [NOTHING WITH x86 in its name]
SAME for any SDKs - NOT in x86 Program Files
then installing the PSPC SDK after

In addition, I tried my reg key and replicated these exact steps and was successful on:
Windows XP x64 [SP2]
Windows Vista x64 [SP2]
Windows 7 x64 [SP1]
Windows 8.0 x64
Windows 8.1 x64
Windows 10 x64 [22H2]
Windows 11 x64 [23H2]

So it's safe to say the regkey is universal - I mean I didn't test Server editions, Itanium editions, or ARM editions, but I'm satisfied.

What say you?