Originally Posted by tluxon
I'm not sure if I'm getting a defective download or something, but this installer package will not install on my Win 7 32-bit installation. I keep getting Error 1719 (Windows Installer not accessible), but it doesn't seem to have a problem installing and/or uninstalling everything else I throw at it.
I honestly would reinstall Windows if I were you. That is not a commonly seen error and indicates serious problems (I'm a software consultant that specializes in installation design and particularly Windows Installer). You would be getting a different message if it were a simple matter of insufficient permissions...your error indicates that the Windows Installer OS service has incurred substantial damage.
Now, you say that nothing else you throw at it causes the error, but I have no way of knowing what percentage of that stuff is in the Windows Installer .MSI format. Having consulted on the technology for 12 years, I am shocked at how much software still doesn't use it (granted, it is a bit complex...but legacy installer technologies simply can not get the job done safely, period). So I propose a test: Run another .MSI and see if the same message is generated. I recommend FreeUndelete, which is one of the few file undelete utilities that uses a Windows Installer .msi: http://www.officerecovery.com/freeundelete/
I expect that you'll get the same 1719 error result. My FireWire .MSI package is using almost no "custom actions" and is very strictly following Windows Installer best practices. Frankly, the amount of table-editing required to do that almost begs the question why didn't I use ORCA to create it from the ground up...Answer: I used to work for Wise and just sort of wanted it to be a Wise .msi. The next version most certainly won't be (it will be InstallShield, for basically the same reason).
So, why is the .msi installation better than grabbing the driver files and using the command line or Device Manager to manually install it? One word: Rollback.
Windows Installer is transactional and will roll off any changes if an error is encountered. So with a properly authored .MSI installation there are only two possible installation states: fully properly installed, or not at all installed.
If a manual installation (or legacy installation, such as Inno Setup, WiseScript, InstallShield ISScript, Nullsoft Installer, etc.) bombs out mid-way through, they just take their ball and go home; your machine is therefore left in a quasi-installed state where there typically is not enough logging/info available to do better than guessing at what has been altered and needs to be changed back. This is why no legacy installer is *ever* allowed on my systems...if it isn't .MSI it will become .MSI by my hands.
If you'd like for me to review your MSI log file, I will. To generate the log file, open an Administrator Command Prompt and type the following:
MSIEXEC.EXE /I "" /L*v "C:\\wherever\\Logfile.log"
This will produce a (perhaps largish) .log file that will have a lot of information in it (depending on how far into the install it gets before crapping out). /L is the logging command and the * means to log everything and the v means to be verbose, giving a *lot* of detail. This is something that is beyond legacy installations (and obviously manual installations) and gives the information needed to trace back the problem to its root, though sometimes it's like looking for a needle in a haystack.
I think reinstalling Windows is the smartest thing long-term (my assumption being that this indicates other underlying problems and that a fresh reinstall is ultimately a time saver vs. endless disparate troubleshooting). But if there are no other indications of trouble, perhaps this issue is a one-off impacting only the Windows Installer service (doubtful, but possible). I would recommend performing the steps outlined here
(this article is for Vista, but the same steps can be used on Windows 7).
Originally Posted by tluxon
So I guess that leaves me with the Tim M. Moore firestb driver package
that I've used for WinXP. Is that suppose to work with Windows 7 32-bit as well? Or do I need something else?
Yes, these will work with Windows 7 32-bit.