Platform<=>version conflict or what?

[Jorma Paavola]

Hi Phil,

Thanks for your good tips !
> =

> See the following thread:
> http://www.annoyances.org/exec/forum/win98/1010169708
> =

> I ran D.W. on one of my Apps here (not packaged with NSIS byw...),
> and I get the two "errors" on APPHELP.DLL and USERENV.DLL,  however
> my program continues past this point on Win98,  and runs fine.

These according to my knowledge are partly due the "unupdated versions =

of Win98" of those days !

In my case the module APPHELP.DLL is reported by DW (when running) as =

missing one but only on "delay-loaded"-basis ! According to Robin Dunn =

this under Win98 will however never be called and therefore that=B4s no =

problem ! (as stated before !)
APPHELP.DLL itselves is a module, which belongs to Xp and above only and =

is therefore obsolete on Win98 (and Me,Win2k as well)and will cause =

problems if added !!
The reason of existency is probably due the compilation phase of =

wx-python on from C++ on Xp, but is principally OK when marked with =

flags as delay-loaded !
The related correct module for Win9x and Win2k Os=B4s is SHLWAPI.DLL !

USERENV.DLL is a necessary module on win9x-OS=B4s and is not missing on my =

case on Win98 ( due the all updates done!)


> =

> See point #5 here: http://www.annoyances.org/exec/forum/win98/1010414182
> =

> I wonder if *maybe* this could be at the root of the problem,  ie when th=
e DLL
> is not found,  no one (the NSIS unpackager?) checks for an extended error=
 code,
> and knows to ignore the dll load error and attempt to continue the execut=
ion.??
> Just a guess...
> =

> ---Phil

Good guess !
This however is not exactly the explation on Win98 - not on my case only =

- but generally as well !
because:

- (because of load-mechanism of Win98) on load-phase of original pyexed =

sw from dist-folder (16 separate modules) DW (Windows) is not forced to =

check the code until the start point of application (and reports no =

Errors!) as the case is with NSISed version see rel. encl. image file =

Morol.dwi of DW versus Moron.dwi sent before !

- when running the original sw DW (Windows) is forced to continue =

loading of required modules to the starting point (and further) of =

application _CORE_.PYD and reports the same errors of child-modules =

under USERENV.DLL (obviously because these required functions of the =

modules don=B4t exist under Win98 ?).These functions however seem not to =

be on running-phase absolute necessary, because my sw is able to start =

and run normally ! Could be seen on DW=B4s image file Moro.dwi (sized 2.5 =

MB too big for NEWS), which tells everything what happens when sw is =

running succesfully under Win98

- when running the NSISed version (or py2-bundled ) of sw DW (Windows) =

(because of load-mechanism of Win98) is forced to check already at =

loading phase all the necessary modules until startpoint of application =

and finds then the said "lacks" of child-modules under USERENV.DLL. =

These lacks are then finally prohitibing the application to run (under =

Windows).

My guess of final conclusion now is:
- This is a  general incombitibilty problem of wx-Python-sw=B4s on Win98 ! =

(when sw=B4s developed on other OS=B4s )!
- this possible would require some changes (specially made for Win98) to =

wx-python source code or compilation flags ?
- the use of totally failing child-module of USERENV.DLL is NTTDL.DLL =

which (on my Win98 is original one and dated 1998 !) possible should be =

reconsidered (substituted or delay-loaded or?)or updated with a newer =

version (as the case is on Win2k !)

Any comments ?

Jorma

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Morol.dwi
Type: application/octet-stream
Size: 103127 bytes
Desc: not available
Url : http://lists.wxwidgets.org/pipermail/wxpython-users/attachments/20070=
708/8ae3a221/Morol.obj