I have also seen that happen on a machine when the setup.exe was infected with a virus - the first thing it did was copy itself to setup.exet and then load that. On a machine with the virus checker turned on, it stripped out the virus, on the machine without virus checking, it gave the error you mentioned and failed to load.
Did you try running setup.exe with the virus checker running? Maybe it would help?
|