3 replies to this topic

[Backwards Elation]

Haha, first post here, and it's a cry for help.

Okay, well, I'm having this problem with my game. I run on a Windows XP if anyone needs to know; I'm not certain what else needs to be said. But I'm trying to re-install Morrowind after my last games drive died (all games were, obviously, deleted), and I keep getting this error message that says:

<Disc 1> Catastrophic Failure

Now, I fiddled about for a bit, and found out that my game is trying to install on the old drive, which no longer exists. I want to put it onto the new games drive, but I see no option to change the destination. Does anyone know how to fix this? I checked a Tech Support page, and it said it has to do something with the registry, and that I'd have to call. I decided to post here first though, just in case anyone here knows the answer: that way, I can avoid being on hold forever.

So, can anyone help me? Or am I a blind bat flapping around in the wrong forum?

[Turkeymoo]

I tried to install Morrowind to a different directory and had the same problem. It won't let me change the installation path! :ranting:

[Backwards Elation]

Okay, I just figured it out.

What you have to do is make your directory (Bethesda Softworks/Morrowind, or whatever you want to call it), and install TES Construction Set first. After that, Morrowind gave me the option to change it, though at first it kept trying to install it in the same directory as TES.

Heck of a lot simpler solution than digging aroudn in the registry.

[White Wolf]

Assuming you have Windows 2000 or XP, as an alternative, you could try uninstalling Morrowind completely, manually deleting any files or folders it leaves behind, then downloading a rather useful little tool called Regscrub XP from here and running it. This will automatically scan your registry and highlight any problems it finds, including any registry entries left behind by Morrowind. It also automatically makes a backup just in case, but it is usually safe to just run, click on 'Select all Problems', then tell it to 'Fix all Problems'. I've experienced this problem myself with other programs, and Regscrub has sorted it for me, so it might work for you here.