Hello kerravon
Does anyone have any idea what the philosophy here is? Is someone (ie Arca NOAE) trying to bullet-proof ArcaOS from rogue executables, or are there not enough resources such that it is only OS/2 bugs found when running technically correct programs that are fixed?
I don't think so, for what I know the way ArcaOS runs binaries is the same as OS/2 Warp 4.52. There is no way to sign binaries and have any other extra security.
Not that I understand much of your conversation, but I tried the executable on my ArcaOS 5.1.0 VM.
I have this message when I try to run it (Full screen and Windowed version).
[C:\HOME\MARTIN\Downloads\TEMP]pdptest
SYS0193: C:\HOME\MARTIN\DOWNLOADS\TEMP\PDPTEST.EXE cannot be run in a OS/2
session.
It looks to me that is not a OS/2 binary and it does not hang my system.
Secondly, the pure 32-bit allows me to write a mini-clone of OS/2 either as an app that runs under another OS (e.g. UC386L that runs under Linux) or as a standalone OS (PDOS/386). Both available from http://pdos.org - new version that implements DosDevIOCtl uploaded a couple of minutes ago.
Note that "mini clone" means that it runs *certain* OS/2 executables - basically just the ones that were built with PDPCLIB (see makefile.wat). So anything that is C90-compliant, or uses ANSI x3.64 "extensions" and has been built with PDPCLIB or equivalent (I doubt that there is anything equivalent currently, but there is no barrier to that).
I have interest to know what are you doing there. I don't know if you can share in a different forum thread what are you doing and what are your goals with your project.
Regards