1 |
On Thursday 03 January 2008, Jesús Guerrero wrote: |
2 |
> On Thu, 3 Jan 2008 13:24:34 -0800 |
3 |
> |
4 |
> "James Ausmus" <james.ausmus@×××××.com> wrote: |
5 |
> > Some installation programs will completely decompress all contained |
6 |
> > files prioer to running the actual setup/install application - you |
7 |
> > might try running the executable, then, while it is running, but |
8 |
> > without actually going through the installation steps, search the hard |
9 |
> > drive for any files that were unpacked - you might find where it |
10 |
> > unpacked files and, if you're lucky, it might contain all contents - |
11 |
> > 32 bit and 64 bit. |
12 |
> |
13 |
> Usually in c:\windows\temp\, at least, that was the trend when |
14 |
> I used to use windows, many years ago. |
15 |
|
16 |
It also could be in: |
17 |
|
18 |
c:\Documents and Settings\<user_name>\Local |
19 |
Settings\Temp\<temporary_installation_folder> |
20 |
|
21 |
or it may be in a subfolder of said application within: |
22 |
|
23 |
c:\Program Files\<application name>\<installation_subfolder> |
24 |
|
25 |
If you know what the name of the 64bit file is you can run search on c:\ while |
26 |
the installation executable is running. |
27 |
|
28 |
BTW, the unzip command should be run on Linux rather than MS Windows. |
29 |
-- |
30 |
Regards, |
31 |
Mick |