running HPC2000 apps in HPC Pro?

Is there a guide or article somewhere around on running CE 3.0 apps on CE 2.11? Is that even a thing?

I don’t know about that but here’s one for pocket pc

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=3160&sta...

If someone compiled a CE3 executable instead of a 2.11 one, it generally means that it requires a CE3 API level, i.e. a function not present in older CE releases.

You may get lucky and it not, in which case you would need to edit the p.e. header major and minor subsystem versions
https://upload.wikimedia.org/wikipedia/commons/1/1b/Portable_Executa...

Ok, great info, thanks. Would those APIs mostly be resident in DLLs or is that a core aspect of the OS?

Where there are dll shrinkage, they'll be in DLL's as well as the kernel (that's what the BSP is).

For example the kernel will lack functionality not directly called for by the hardware, so no USB, serial terminal etc modules present, this rendering the presence of higher level DLL's useless.

Got it, thank you. I'll experiment

I also found this thread
https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=4904&sta...

Yeah, I got into it big time back then. I even got a CE 4.2 app to work on my Jornada 820, and a bunch of MIPS Pocket PC apps working even on my CE 2.01 Palm-size PCs - though there seemed to be bigger incompatibilities between the Pocket PC 2000 coredll.dll and the CE 2.11 Palm-size PC coredll.dll than between the Pocket PC coredll and the H/PC Pro one. Several apps that worked in H/PC Pro after hexediting the OS version wouldn't work on CE 2.11 Palm-size PCs.

Generally, the fewer DLLs required, the better the chances of making an app work in 2.11. Fewer DLLs generally means fewer function calls, which generally translates into fewer chances of incompatibility. And, of course, you have to change the OS versions on all the DLLs too.