P
Paul
JohnD said:Thank you for that advice. Unfortunately, the file that Install wants -
moviemk.exe - is not on my XP Pro install CD either.
:
Did you remember to search for "moviemk.ex_" ?
In a previous post, I tried to explain compressed files, and naming
conventions. The uncompressed file would be "moviemk.exe". If it
is stored compressed, they change the character on the end to an
underscore character. That is how you're supposed to know it is
compressed. It also screws up searching for that file by name.
Which is the reason, when I'm searching for files, I don't add
the extension to the end. If I'm searching, I look for "moviemk"
with the search command, and just accept the fact I'm going to
get all sorts of stuff.
You can expand a file using the system utility called "expand".
For example, let's say you find a copy of moviemk.ex_ . Open
a command prompt window, and first try
expand -D moviemk.ex_
That will cause the utility to print the name of the file as
it would appear when unexpanded (always a good plan to verify).
Next, you can use that name information, to do the actual expansion.
This step makes the file you wanted, from the compressed one.
(And if you lose track of what you did with the output file, just
search on the name again.)
expand moviemk.ex_ moviemk.exe
The program prints this out in response to the command.
Expanding moviemk.ex_ to moviemk.exe.
moviemk.ex_: 1243742 bytes expanded to 3558912 bytes, 186% increase.
Now you have a moviemk.exe, all ready to pass to your installer.
But you still have a whole pile of other files to expand. I tried
to explain before, that the INF file contains a list of stuff to
do, and from that file, you can guess at what files it is going to
need to finish the installation.
I use 7ZIP for expansion tasks, as it is a tiny bit easier
to use. Still not as efficient as I'd like, but better than
the command window and the above method.
HTH,
Paul