Mail Archives: djgpp-workers/2001/08/13/15:14:01
> > The original code leaked DPMI selector like a sive on Win2K when building
> > LIBC on Win 2K, it was a night mare to have to restart every minute or two.
>
> By ``original code'' I meant the patch posted by Charles.
Actually no - he means the V2.03 or CVS code. My code fixes the problem
on Win2K and XP, but it makes some assumptions which haven't been validated
on other platforms and might be dangerous. I actually think my code would
probably work fine everywhere, but Andris has a fix which appears safe
instead of making assumptions - but doesn't work at all on Win 2000.
> > The issue I had was that Charles patch was for Win 2K and Andris patch was
> > for Win 98. I wanted to have the same source and executables for both Win 98
> > and 2K. Between the patch from Charles that was for Win 2K issues and
> > Andris and your comments about this last week I thought it best to only
> > enable the code in Charles's patch on my Win 2K box and don't enable the
> > function calls when running on my Win 98 box. I thought it was better safe
> > than sorry.
>
> If there's a conflict between different patches, I suggest to discuss
> that and arrive at a unified solution. Rushing into rebuilding
> packages before we have an agreed solutioin that should be good for
> all platforms might be a waste of resources.
We're working on it, but you can't even do builds without some fix on
Win2K.
We don't need anything on CWSDPMI.
We only need the CWS patch code on NT/Win2K/XP.
For other platforms we want to probably check access rights, but I'd
prefer to avoid making 16,000 DPMI calls to scan all the selectors.
So we have working prototypes, but no final code.
- Raw text -