Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx05.iad.POSTED!not-for-mail Subject: Re: win32 via odin Newsgroups: comp.os.os2.programmer.misc References: <83234834-db2d-42ac-8bc6-0fcf631f53b9n@googlegroups.com> <7ee4e13c-63ae-4c02-a17d-b183c5045e92n@googlegroups.com> From: Dave Yeo User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:45.0) Gecko/20100101 Firefox/45.0 SeaMonkey/2.42.9esr MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Lines: 12 Message-ID: <_O2tM.36419$KfH5.404@fx05.iad> X-Complaints-To: https://www.astraweb.com/aup NNTP-Posting-Date: Mon, 17 Jul 2023 03:44:58 UTC Date: Sun, 16 Jul 2023 20:44:56 -0700 X-Received-Bytes: 1500 Xref: csiph.com comp.os.os2.programmer.misc:1725 Paul Edwards wrote: > Crikey. I thought that OS/2 2.0 had done a total switch to 32-bit. No, there was still quite a bit of 16 bit code that needed updating and some never got updated even in the latest. Another consideration is that 16 bit functions are stuck needing to be in the lower memory range (below 1GB, or actually below 512MB - whatever DLLs are loaded. Mem /v will show your memory). Win32's got broken on OS/2 by MS forcing some DLL's to load above the 1GB barrier and even now some functions probably require OS/2 4.5+ for high memory access. Dave