Please help

[Tuskerlove]

I need some techincal info.

I bought a new computer and when I went to reinstall my Dominions II game - I received this error on initialization

Installer verification failed.

This could be the result of an incomplete download, a failing disk, or (possible) corruption from a virus.

You can try to force an install using the /NCRC command line switch (but it is not recommended).

Has anyone ever run into this problem? I don't see any scratched on the Dominions II disk so I don't understand why it's not working.

Any help would be very appreciated as this is my favorite game and I can't stand that I can't play it.

I installed the new Direct X
Checked for viruses
No need to resurface the disk as I see nothing wrong with it

Thanks in advance,
Tuskerlove

[Gandalf Parker]

What operating system and Version?
Mac? Solaris? Linux? Windows?

[Arryn]

Originally posted by Gandalf Parker:
What operating system and Version?
Mac? Solaris? Linux? Windows?

Since he installed DirectX, it must be some flavor of Windows. Perhaps it's related to the new "copy-protection" that IW inflicted on us in a recent patch?

[Gandalf Parker]

Originally posted by Arryn:
Since he installed DirectX, it must be some flavor of Windows. Perhaps it's related to the new "copy-protection" that IW inflicted on us in a recent patch?

On install? I dont think anyone has come up with anything to stop an install on a new machine. Even if it was a re-install such blocks on Windows machines tend to be registry blocks

Ive installed my Dom discs many MANY times. On the same machine, different machines, different major operating systems even. I dont think the protection for it kicks in until you try to play it.

[Arryn]

Originally posted by Gandalf Parker:
On install? I dont think anyone has come up with anything to stop an install on a new machine. Even if it was a re-install such blocks on Windows machines tend to be registry blocks

If an app/dll that is called by the installer fails to run, the install *will* fail. I have seen this happen. Amongst the many years of software experience I have, 5 years of it is in writing installers for Windows systems. I assure you that installs can and do fail, under the right (wrong?) circumstances.

As a for-instance, suppose the installer were to check for an active net connection via network API calls. If the user does not have a working net connection (say, for a registration code or copy-protect check), the net API call will return false or fail. Depending on how the installer was written, the install could fail. And fail with an error message not dissimilar to what Tuskerlove is reporting.

I suspect that only the folks at IW are going to be able to definitively answer his question. All we can do is guess.

[Norfleet]

Originally posted by Tuskerlove:
You can try to force an install using the /NCRC command line switch (but it is not recommended).

You've answered your question.

If at first it doesn't work, force it. If it breaks, it needed to be replaced anyway.