Re: Why thunk in OS/2? or at all?
 
>  MG> OS/2 since 2.0 is 32 bit so why do you need to call 16 bit
>  MG> code? Why not completely use 32 bit code?
> There are several cases in which thunking is necessary.  Many people are
> working with existing 16-bit OS/2 1.x programs, and may therefore have existi
> 16-bit OS/2 1.x modules or DLLs.  In some cases, the DLLs may only be availab
> in object form, so rebuilding them or porting them to 32-bit OS/2 is not an
> option.

> the Vio/Mou/Kbd API services, will require thunking, even when writing new

> -- Mike

First off I have to apologize for replying so late. I am running sooo far
behind on my reading.... :-)

Thank you for the information. It really helped me "get a grip" on why
thunking was needed.
Thank you again,
Mike.

--- VFIDO 7.05