I have an installer for a terminal emulation program that I'm
particularly fond of that I'd like to have running under Windows XP
Pro x64 (dual Xeon processors). I'm confronted with the good ol'
dialog about the file being valid but not for this platform (or
something to that effect) when I try to run the term. emulator's
original SETUP.EXE. I found reference to WinInstall LE as provided on
the Win2K Server CD and managed to obtain a copy. So, I collect the
"before" data on a "clean" WinXP Pro system by running DiscoZ.exe in
the Winstall folder of a Network Neighborhood Win2K system and then
run the term. emulator's SETUP.EXE on the WinXP PC, and get the term.
emulator installed. After a restart to make sure everything's loaded
properly and an initial invocation of the term. emulator to ensure
functionality, I collect the "after" data. I checked the MSI file with
WinInstall's package editor back on the Win2K system, and was dismayed
to find that none of the term. emulator's files (installed in C:
\Program Files\<term-emul-pgm>\ on the WinXP system) are cited. Any
ideas? (Note that I haven't even tried the MSI file on WinXP Pro x64,
yet. I'm just reviewing the MSI file's contents.) FWIW, the two
systems involved in creating the MSI are not part of a Windows domain,
but I had no trouble accessing the Win2K system from the WinXP Pro
system after authenticating upon trying to access the Win2K system
from the WinXP system's Network Neighborhood.
If there's a better (but still free [or relatively inexpensive])
alternative to WinInstall LE that would work better, or a fix for the
behavior described above, please advise.