The bad news is running "hpt.exe toss" (without any configuration set) actually froze my OS/2 VM.
Earlier this week I backported HPT to Open Watcom 2.0, which can be used to build the 32-bit OS/2 & Windows versions.
I say "backported" loosely. SMAPI could once be built with the closed-source Watcom C 10.0. This was common when Paul Edwards ported Msged to 32-bit OS/2 in 1995, and when I ported MSGAPI38 (which was then renamed SMAPI) to Windows NT a few years later. Fast forward to 2021 and there's a working Watcom makefile (make/makefile.watcom) for each Husky module (huskylib, smapi, etc) needed to build HPT.
The makefile.watcom file for each module was written to be cross-platform, so you can cross-compile the OS/2 & Windows version from Linux, using the Linux version of OW 2.0. Or you can build it from Windows or OS/2 in the normal way, with the same makefile, without cross-compiling.
Theoretically the binaries should run on anything from Windows NT 3.1 and OS/2 2.0 onwards.
The forked modules are here:
https://github.com/zoomosis/huskylib
https://github.com/zoomosis/smapi
https://github.com/zoomosis/fidoconf
https://github.com/zoomosis/areafix
https://github.com/zoomosis/hpt
Any plans of watcom makefiles of other husky tools? Like sqpack, hptutil and hptkill? :)
Any plans of watcom makefiles of other husky tools? Like sqpack,
hptutil and hptkill? :)
I only have plans for htick and Msged, after I finish working on hpt.
I'm not familiar with the ones you listed.
Any plans of watcom makefiles of other husky tools? Like sqpack,
hptutil and hptkill? :)
I only have plans for htick and Msged, after I finish working on
hpt. I'm not familiar with the ones you listed.
Ok, I see.
The reason I asked is that I have seen crashes when using JAM with EMX builds of Husky. The watcom build has been working perfect now in my old OS/2 (WSeB).
The reason I asked is that I have seen crashes when using JAM with EMX builds of Husky. The watcom build has been working perfect now in my old OS/2 (WSeB).
It would be better to try to fix any serious bugs in the EMX build first.
Note that there was a bug accidentally introduced into the JAM code a
few weeks ago that has since been fixed. It affected all platforms.
That may be the cause of the bug you saw, though I can only speculate
without details.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,145 |
Nodes: | 15 (0 / 15) |
Uptime: | 84:31:56 |
Calls: | 230,055 |
Calls today: | 4 |
Files: | 59,453 |
D/L today: |
3 files (39K bytes) |
Messages: | 293,511 |
Posted today: | 2 |