1
Applications / Re: GBM fails, looks for TCPIP32???
« on: 2011.01.16, 02:23:36 »
Thanks for reporting the issue with the dependency to TCPIP32 (also via PM).
I think I meanwhile found why it is now there. The library I included for the new RAW support does use some network byte order conversion functions (htons/ntohs, htonl/ntohl). Obviously I have overseen this when porting it to OS/2 for GBM. Usage of the functions/macros is pretty common in code developed for Unix/Linux. I'll see if I can replace them by GBM own implementations to get rid of the dependencies so that GBM will also work on Warp 3 again (although nobody complained yet).
Nevertheless with Warp 4 it is a good idea to go to 32bit TCP/IP stack alone for security and better performance. eCS user have it on-board from the beginning.
Only GBM version 1.70 and 1.71 are affected by the TCPIP32 dependency, older versions should be fine.
EDIT:
A patched GBM.DLL 1.71 for Warp 3/4 with 16bit TCPIP stack is now available from the GBM website. If you have such a system, I'd be interested in success reports
. All eCS users and users of Warp 4 with 32bit TCPIP stack can keep the original GBM.DLL. The next official release will have the fix incorporated.
I think I meanwhile found why it is now there. The library I included for the new RAW support does use some network byte order conversion functions (htons/ntohs, htonl/ntohl). Obviously I have overseen this when porting it to OS/2 for GBM. Usage of the functions/macros is pretty common in code developed for Unix/Linux. I'll see if I can replace them by GBM own implementations to get rid of the dependencies so that GBM will also work on Warp 3 again (although nobody complained yet).
Nevertheless with Warp 4 it is a good idea to go to 32bit TCP/IP stack alone for security and better performance. eCS user have it on-board from the beginning.
Only GBM version 1.70 and 1.71 are affected by the TCPIP32 dependency, older versions should be fine.
EDIT:
A patched GBM.DLL 1.71 for Warp 3/4 with 16bit TCPIP stack is now available from the GBM website. If you have such a system, I'd be interested in success reports
. All eCS users and users of Warp 4 with 32bit TCPIP stack can keep the original GBM.DLL. The next official release will have the fix incorporated.
.
. It took me about half an hour to hack a function in REXX that does almost the same as your dll. The benefit of having it coded in REXX is that no additional dll is required.