RE: Why is EXW Win 3.1 application ?
That is fascinating... and it sure does explain a lot of Windows
weirdness and frustrations that I always attributed to Win32Lib. Rob, I
see that 2.3 beta of exw.exe's subsystem version is still set to 3.10.
1.) Will you be fixing this for the final release of 2.3?
2.) Will you be releasing an 'official' patch for version 2.2 of
exw.exe?
3.) If the answer to #2 is no, then do you have a problem with anybody
releasing a hacked version of pdexw.exe with the version set to 4.00?
IMO, it changes Windows behavior enough that I'll be using hacked
versions for future development...
-- Brian
Martin Stachon wrote:
> Rob Craig wrote:
> > Martin Stachon writes:
> > > I found an interesting thing.
> > > EXW is a Win 3.1 application.
> > > If I open Dr.Watson (drwatson.exe), and choose
> > > 'Tasks', it is shown there that exw is an 3.1 application
> > > all other are listed as 4.0.
> >
> > That's interesting.
> > Of course exw is not a 3.1 application.
> > It won't even run on 3.1 (unless you install
> > a special win32s layer on top of win 3.1)
> > But I guess there are some differences in the
> > way it runs. Thanks. I'll keep that in mind.
>
> Rob, it has nothing to do with the way
> it runs. It is about subsystem version in
> the PE header. I changed the version
> by changing offsets #000000C8 to #000000CA :
> from #03000A (3.10) to #040000 (4.0)
> (In unpacked exw) Now Windows treat exw as
> 4.0 application. I don't know about WATCOM,
> but I guess you can tell it to set the version.
> I think you should change it, users except
> 4.0 bahavior. (For example I was still
> wondering why in Font dialog I can't choose
> Script...). This also causes some differences
> in interpreted/translated code.
>
> Martin
>
>
|
Not Categorized, Please Help
|
|
