Win98banter - View Single Post - I had planned to tell you about something great

mm · February 26th 08, 01:30 AM posted to microsoft.public.win98.gen_discussion

On Sun, 24 Feb 2008 23:00:16 -0500, "MEB" meb@not
wrote:

...

I"m going to try all three methods you've given me, but first I tried
Dependancy Walker and I have a couple questions.

Try using Dependency Walker to *profile* the installation/setup. This will
provide a detailed setup debug of any calls, exes, etc. that occur during
that attempt.
Open Dependency Walker, choose the installer exe, go to Profile on the tool
bar. Choose the level of profiling and run it. Wait until its completely
finished [this may take a while as it debugs all calls, program starts,
etc.].

Wow, this really gives a lot of info.

One line I've found so far (because it displays in red!) is worth
asking about:

GetProcAddress(0x7FCB0000 [SHELL32.DLL], "SHGetFolderPathW") called
from "SHFOLDER.DLL" at address 0x719317BD and returned NULL. Error:
The specified module could not be found (126).

The thing is, shfolder.dll is in C:\Windows\System, so I don't
understand why it couldn't find it. Unless I'm understanding the
message backwards. Shell32.dll is in the same folder.

Also: a few lines further up are, also in RED:
GetProcAddress(0xBFF70000 [KERNEL32.DLL], "FlsAlloc") called from
"MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The
specified module could not be found (126).
GetProcAddress(0xBFF70000 [KERNEL32.DLL], "FlsGetValue") called from
"MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The
specified module could not be found (126).
GetProcAddress(0xBFF70000 [KERNEL32.DLL], "FlsSetValue") called from
"MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The
specified module could not be found (126).
GetProcAddress(0xBFF70000 [KERNEL32.DLL], "FlsFree") called from
"MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The
specified module could not be found (126).

I also have Kernel32.dll and MSVCR71.DLL so I don't know what these
mean either. Maybe the called modules aren't at the right address??

I could look in the FATs etc. and check on that. What do you
recommend.

. In addition you can, if a MSI installer, use its debug to create a report
of the attempt.

How do I know if it is using an MSI installer? It does refer at
installation-start to the Install Shield Wizard.

Using the /? option after the install program, I see that it has 4
possible options. Do you think any of them might help me?
/Q Quiet mode
/T:full path specifies temporary working folder
/C Extract file only to the working folder when used with /T
/Ccmd Override Install Command defined by author

If you are inclined to email me
for some reason, remove NOPSAM :-)