Platform<=>version conflict or what?

[Jorma Paavola]

Phillip Stevens kirjoitti:

> =

> If you are finding debugging difficult to do by debugger,  my next
> advice would be to have the running program itself emit more information
> about what it is doing internally,  so that you can discover where things
> go wrong,  and why.  Either in print statements,  or out to a log
> file,  or somewhere.
> =

> Find out where the code first goes wrong.
> Understand why what the code is doing is wrong,  or won't work.
> Then change the code to fix it.
> =

> You might need to get the sources for both NSIS and wxPython in order
> to do this.
> =

> Also see:
> http://sourceforge.net/search/?group_artifact_id=3D373085&type_of_search=
=3Dartifact&group_id=3D22049&words=3D.DLL
> =

> For NSIS patches involving .dll's.
> =

> Also see:
> http://sourceforge.net/search/?type_of_search=3Dartifact&group_id=3D22049=
&words=3DWindows+98
> =

> For NSIS bugs that involve Windows 98.
> =

> Not sure if any of these might be related to the problem you are
> experiencing,  or not.  But if you haven't patched NSIS with any of the a=
vailable
> patches,  and a bug report looks like it might be related,  it might be w=
orth applying
> the patch for that problem,  if one is available.
> =

> All for now,
> =

> ---Phil
> =

>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wxPython-users-unsubscribe at lists.wxwidgets.org
>> For additional commands, e-mail:
>> wxPython-users-help at lists.wxwidgets.org

Hi Phil,

Thank you for your detailled advices for debugging - which is certainly =

the final way to solve the problem.
	- Unfortunately I think, that this would propably lead to patches =

necessary to sources of wxPython or NSIS, which I am not going make !
	- The reason for my opinion above is due the tests of my NSISed TestGUI =

carried on Win2k,Me,Xp and Vista and Non-NSISed runningtests of exe from =

py2exe-distfolder(not bundled)on all OS=B4s, where the sw works perfectly. =

Therefore I am convinced, that my sw is correct and problems  (of NSISed =

and bundled versions only) found on Win98 are "outside my control" ! ( A =

small change to succes could be to try make the sw on Win98 possible =

using older versions of python ,py2exe and NSIS - this is however the =

step, which I would like to avoid to keep my Win98 "clean" from any =

development sw=B4s)

I enclose the the load-phase image file(Moron.dwi)from NSISed version sw =

generated on Win98 by "Dependency Walker", where clearly can be seen =

that under parent USERENV.DLL four of five loaded modules partly are =

failing already on loading and especially NTDLL.DLL fails to load all =

the functions.

So therefore I suspect, that my Testsw has very little changes to =

survive when tryi=B4ing to run ?

Any comments ?


Jorma





-------------- next part --------------
A non-text attachment was scrubbed...
Name: Moron.dwi
Type: application/octet-stream
Size: 321391 bytes
Desc: not available
Url : http://lists.wxwidgets.org/pipermail/wxpython-users/attachments/20070=
706/19e81cf0/Moron.obj