| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5667.1 | what version of installshield? | ALFSS2::CHURCHE_J | Nothing endures but change | Tue Feb 11 1997 05:58 | 8 |
|
InstallShield was recently updated by the vendor to v3.0.111. It fixes
problems with using it on alpha platforms. The vendor can be reached
at http:/www.stirling.com
jc
nt support/csc
|
| 5667.2 | | 8153::tecotoo.mro.dec.com::mayer | Danny Mayer | Tue Feb 11 1997 07:05 | 6 |
| This usually happens if you are trying to install using an old
Installshield kit which has not been updated to support NT 4.0. Look at
the setup.exe, _INST32A.EX_ or _INST32I.EX_ and see if they are later than
say July, 1996. This is almost certainly NOT an FX!32 problem.
Danny
|
| 5667.3 | still need help on this one | CSC32::G_OGLESBY | Ginny Oglesby 592-4731 CSC/CS | Tue Feb 11 1997 14:36 | 17 |
| How do I determine what version of InstallShield kit I'm running? I need a list of all files
associated with InstallShield so I can verify versions, etc.
If I install over a network drive, am I using Installshield locally or remote? In my case both local
and remote intalls are failing.
setup.exe C:\WINNT40\system32 58KB Version 4.00
I know the remote install files are ok, as I can install the application from other Alphastations, 4.0.
I even did a new nt4.0 build on a scratch drive on my system, and was able to do the remote, or local
install. It has to be a file on my system disk, but I need a rundown of what files to check.
I guess I need some help on understanding how Installshield works, so I can track this down.
Thanks again for all help.
Ginny
|
| 5667.4 | | 8153::tecotoo.mro.dec.com::mayer | Danny Mayer | Wed Feb 12 1997 08:17 | 13 |
| If you are building with Installshield, there's a Menu Item in the
Program Manager (or the Start Menu if you are on NT 4.0) called Version Checker
which will give you a list of versions of all the components.
You need to look at the date of setup.exe and _INST32*.EX_ etc, to see
what is going on. I don't keep track of file sizes. I'd also strongly
urge you to make sure you clean out your TEMP directory (whereever the TEMP
environmental variable points to). I once ran into a problem trying to install
something and it keep trying to install something totally unrelated. It took
me hours to figure out that there were files left over from an aborted
install that hadn't gotten cleaned up.
Danny
|
| 5667.5 | Cleaning out \Temp fixed the problem | CSC32::G_OGLESBY | Ginny Oglesby 592-4731 CSC/CS | Wed Feb 12 1997 08:40 | 3 |
| Thanks Danny! I deleted my Temp directory, and now my installs are working.
Ginny
|
| 5667.6 | For Alpha. For intel, 4:00AM on file _inst32i.ex_ | DECWET::KOWALSKI | Time's not for saving | Wed Feb 12 1997 08:51 | 9 |
| V 3.00.101 is dated July 24, 1996 3:00 AM
Look for this date in the kit on file
_inst32a.ex_
Unfortunately, there is no accurate version
information inside their uncompressed
executables on a product's kit.
Mark
|