Platform<=>version conflict or what?

[Jorma Paavola]

Phillip Stevens kirjoitti:
> Hi Jorma,
> 
> Here is some info about the search order of .DLL's:
> http://msdn2.microsoft.com/en-us/library/ms682586.aspx
> 
> Since you say it extracts the files into a Temp folder,  I'm guessing
> that it should add this Temp Folder to the Path (for 98 anyway...).
> Is it possible that the Path has grown too long,  or that you are out
> of environment space on the Win98 system?  If so the Path maybe has
> been truncated,  Or maybe it fails to modify the Path,  and that is
> the problem.
> 
> The error message says that it cannot find the file.  If a file really is
> there,  I'd wonder if it can't find it it because the Path isn't
> pointing to it.  In the other OS'es it may be using the other search
> mechanisms available in order to locate the .DLL.
> 
> If this isn't it,  it's probably time to run it under a debugger
> (IDLE, GDB, or other),  set some breakpoints,  run to just before
> where things break,  and then single step along and see what's really
> going on,  at the moment when things do break.  And which .DLL is
> involved,  as that might provide a clue.
> 
> ---Phil
> 
> 
Hi Phil,

Debugging of NSISed single exe-file is not very easy task and therefore 
I decided first to study the behaviour of my NSISed single file 
executable on Win98 with "Dependency Walker", which normally gives a 
very detailled analysis of running sw´s.

I found some very odd things:

1)When Testsw loaded the following files were marked with "module 
warnings", which means:
"Module warning. This module is either missing one or more export 
functions that are required by its parent module, is of the wrong CPU 
type, or failed to initialize when being loaded."

- NTDLL.DLL
- KERNEL32.DLL
- ADVAPI32.DLL
- USER32.DLL

Also some dynamic dependencies gave warnings, which possible may not be 
  so critical especially when not loaded !

2)When clicking "start profiling" (run) "DW" will start to slow down and 
finally clears (automatically - not logigal!) nearly all of all history 
tracing so that you cannot see what really happened ! Finally the same 
errormsg. appears as before

3)When clicking "stop profiling" during profiling, profiling don´t stop 
immediately, but is going on abt. 3 s.
When stopped strange things happen:
- "DW" keeps the whole tracing from beginng to stop moment
-  my NSISed TestGUI(.exe) suddenly pops up and works normally !!!? *)



4) The recources are
at the beginning (no modules loaded):
- System resources = 78%
- User resources = 78%
- GDI resources = 94%

when "DW"-profiling stopped and NSISed TestGUI(.exe) running *):
- System resources = 66%
- User resources = 66%
- GDI resources = 89%

Unfortunately I cannot evaluate, if the problems may lay on "module 
warnings" reported by "DW" on load phase or  on possible lack of 
resources or somewhere else?

Some advice ?


Best regards,

Jorma Paavola

PS. The "warned modules" are certainly NOT missing ! - something else ...?