Windows Installer

[Chuckles Clown]

I was attempting to install some updated HP software and the windows
installer is looking for a file that doesn't exist. Now I don't know how to
clear or change the path. It seems to default to this path over and over
again. What do I do?

[98 Guy]

I've cross-posted this to microsoft.public.win98.gen_discussion because
that's where most win-98 traffic happens.

When ever you get a message that your system or a program is looking for
a particular file, then simply go "Start -> Find -> Files or Folders"
and search your system for the file in question. If the file exists,
then copy to the file to the location where the system wants or is
expecting the file.

[MEB]

That's not necessarily the best answer.

That presumes the programmer properly placed the files/locations within
the setup procedure. IF there is a missing file or direction to the
WRONG area of the Win9X OS, then the issue may be that is is NOT
properly compiled for Win9X. DO NOT blindly install one or several of
the NT's dlls or even Win9X dll(s) into Win9X attempting to get it to work.
Though this DOES generally allow the installation, this may also place
files into the WRONG area; for example, the unicows.dll, which is NOT to
be placed for system-wide usage in the Win9X system folder, but ONLY in
the individual application's folder. AND, if one of the NT's dlls, it
may and will increase the vulnerabilities in Win9X.

A more generalized way is to look at the setup or similar .ini and
modify that after searching and finding the file elsewhere [such as in
Common Files] or by manually placing a copy of the missing .dll within
the application's folder [even to the point of pre-making the
application's folder with that file within it].
Or for winstaller [installshield] activities, these can be pre-expanded
and the setup files modified to reflect present locations [like /system
verses /system32] or back into the application's own folder.

An alternative method [and the best or easiest] of determining what
needs done is to *profile* the installation with *Dependency Walker*,
which will run the installer and locate and document all the errors
encountered during the temporary *profiled* install.

OR, if you found it necessary to temporarily place some missing file
into the Windows folders to finish the install:
After it is installed, modify the registry/hive entries to reflect the
application's own folder and move the file(s) {dlls} there.
When using this technique it is best to use one of the installation
monitoring programs to install the application so you have a reference
[text or otherwise] of what was done to the disk and system by the
install, which provides you with the registry/hive entries to modify.
Make sure to modify all relevant entries to reflect the change to the
application's folder.

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

[PCR]

I agree with MEB that some slight research need be done to determine
whether the file should or shouldn't go there. But I'm not sure what
path the OP is speaking of -- a destination or a source? State
precisely...?...

(1) What app is being installed
(2) What is the path in question
(3) What file(s) are involved
(4) What is the method of the install

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcr...@netzero.net

[Hot-text]

The Name of the file that doesn't exist would help?

"Chuckles Clown" <Cha...@golfland.com> wrote in message
news:6FFCCDE2-A814-4070...@microsoft.com...